1. 17 6月, 2021 1 次提交
    • L
      PCI: ixp4xx: Add a new driver for IXP4xx · f7821b49
      Linus Walleij 提交于
      This adds a new PCI controller driver for the Intel IXP4xx
      (IX425, IXP435 etc), based on the XScale microarchitecture.
      
      This replaces the old driver in arch/arm/mach-ixp4xx/common-pci.c
      which utilized the ARM-specific BIOS32 PCI framework,
      and all parameterization for such things as memory and
      IO space as well as interrupt swizzling is done from the
      device tree.
      
      The plan is to phase out and delete the old driver piecemal.
      
      The __raw_writel() and __raw_readl() are used for accessing
      the PCI controller for the same reason that these accessors
      are used in the timer, IRQ and GPIO drivers: the platform
      will alter its address bus pattern based on whether the
      system is booted in big- or little-endian mode. For this
      reason all register on IXP4xx must always be accessed in
      native (CPU) endianness.
      
      This driver supports 64MB of PCI memory space, but not the
      indirect access of 1GB that is available in the old driver.
      We can address that later if and only if there are users
      that need all 1GB of PCI address space. Krzysztof reports
      having to use indirect MMIO only once for a VGA card. There
      is work ongoing for general indirect MMIO. (In practice
      the indirect MMIO is performed by writing address and
      writing and reading values into/from a controller
      register.)
      
      Tested by booting the NSLU2, attaching a USB stick, mounting
      and browsing the drive.
      
      Link: https://lore.kernel.org/linux-arm-kernel/m37edwuv8m.fsf@t19.piap.pl/
      Cc: Arnd Bergmann <arnd@arndb.de>
      Cc: Imre Kaloz <kaloz@openwrt.org>
      Cc: Krzysztof Halasa <khalasa@piap.pl>
      Cc: Zoltan HERPAI <wigyori@uid0.hu>
      Cc: Raylynn Knight <rayknight@me.com>
      Acked-by: NBjorn Helgaas <bhelgaas@google.com>
      Reviewed-by: NArnd Bergmann <arnd@arndb.de>
      Acked-by: NLorenzo Pieralisi <lorenzo.pieralisi@arm.com>
      Signed-off-by: NLinus Walleij <linus.walleij@linaro.org>
      f7821b49
  2. 07 5月, 2021 1 次提交
  3. 06 5月, 2021 1 次提交
  4. 04 5月, 2021 2 次提交
  5. 01 5月, 2021 2 次提交
    • M
      afs, rxrpc: Add Marc Dionne as co-maintainer · c5197b4e
      Marc Dionne 提交于
      Add Marc Dionne as a co-maintainer for kafs and rxrpc.
      Signed-off-by: NMarc Dionne <marc.dionne@auristor.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      c5197b4e
    • L
      MAINTAINERS: assign pagewalk.h to MEMORY MANAGEMENT · a3ddd79a
      Lukas Bulwahn 提交于
      Patch series "kernel-doc and MAINTAINERS clean-up".
      
      Roughly 900 warnings of about 21.000 kernel-doc warnings in the kernel
      tree warn with 'cannot understand function prototype:', i.e., the
      kernel-doc parser cannot parse the function's signature.  The majority,
      about 600 cases of those, are just struct definitions following the
      kernel-doc description.  Further, spot-check investigations suggest that
      the authors of the specific kernel-doc descriptions simply were not
      aware that the general format for a kernel-doc description for a
      structure requires to prefix the struct name with the keyword 'struct',
      as in 'struct struct_name - Brief description.'.  Details on kernel-doc
      are at the Link below.
      
      Without the struct keyword, kernel-doc does not check if the kernel-doc
      description fits to the actual struct definition in the source code.
      Fortunately, in roughly a quarter of these cases, the kernel-doc
      description is actually complete wrt.  its corresponding struct
      definition.  So, the trivial change adding the struct keyword will allow
      us to keep the kernel-doc descriptions more consistent for future
      changes, by checking for new kernel-doc warnings.
      
      Also, some of the files in ./include/ are not assigned to a specific
      MAINTAINERS section and hence have no dedicated maintainer.  So, if
      needed, the files in ./include/ are also assigned to the fitting
      MAINTAINERS section, as I need to identify whom to send the clean-up
      patch anyway.
      
      Here is the change from this kernel-doc janitorial work in the
      ./include/ directory for MEMORY MANAGEMENT.
      
      This patch (of 2):
      
      Commit a520110e ("mm: split out a new pagewalk.h header from mm.h")
      adds a new file in ./include/linux, but misses to update MAINTAINERS
      accordingly.  Hence,
      
        ./scripts/get_maintainers.pl include/linux/pagewalk.h
      
      points only to lkml as general fallback for all files, whereas the
      original include/linux/mm.h clearly marks this file part of MEMORY
      MANAGEMENT.
      
      Assign include/linux/pagewalk.h to MEMORY MANAGEMENT.
      
      Link: https://lkml.kernel.org/r/20210322122542.15072-1-lukas.bulwahn@gmail.com
      Link: https://lkml.kernel.org/r/20210322122542.15072-2-lukas.bulwahn@gmail.comSigned-off-by: NLukas Bulwahn <lukas.bulwahn@gmail.com>
      Cc: Joe Perches <joe@perches.com>
      Cc: Ralf Ramsauer <ralf.ramsauer@oth-regensburg.de>
      Cc: Jonathan Corbet <corbet@lwn.net>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      a3ddd79a
  6. 30 4月, 2021 3 次提交
  7. 26 4月, 2021 1 次提交
  8. 25 4月, 2021 1 次提交
  9. 23 4月, 2021 6 次提交
  10. 21 4月, 2021 2 次提交
  11. 20 4月, 2021 9 次提交
  12. 17 4月, 2021 2 次提交
  13. 16 4月, 2021 1 次提交
  14. 15 4月, 2021 2 次提交
  15. 14 4月, 2021 6 次提交