Re: [PATCH 1/4] vfs: add file_dentry()

On Thu, Mar 17, 2016 at 10:02:00AM +0100, Miklos Szeredi wrote: > Add a new helper, file_dentry() [*], to get the filesystem's own dentry > from the file. This simply compares file_inode(file->f_path.dentry) to > file_inode(file) and if they are equal returns file->f_path.dentry (this is > the

Re: [PATCH 1/4] vfs: add file_dentry()

On Thu, Mar 17, 2016 at 10:02:00AM +0100, Miklos Szeredi wrote: > Add a new helper, file_dentry() [*], to get the filesystem's own dentry > from the file. This simply compares file_inode(file->f_path.dentry) to > file_inode(file) and if they are equal returns file->f_path.dentry (this is > the

Re: [PATCH 1/4] vfs: add file_dentry()

On Mon, Mar 21, 2016 at 01:02:15AM -0400, Theodore Ts'o wrote: > I have this patch in the ext4.git tree, but I'd like to get an > Acked-by from Al before I send a pull request to Linus. > > Al? Any objections to my sending in this change via the ext4 tree? >

Re: [PATCH 1/4] vfs: add file_dentry()

On Mon, Mar 21, 2016 at 01:02:15AM -0400, Theodore Ts'o wrote: > I have this patch in the ext4.git tree, but I'd like to get an > Acked-by from Al before I send a pull request to Linus. > > Al? Any objections to my sending in this change via the ext4 tree? >

Re: [PATCH v11 3/9] arm64: add copy_to/from_user to kprobes blacklist

Hi James, On 18/03/2016:06:12:20 PM, James Morse wrote: > Hi Pratyush, > > On 18/03/16 14:43, Pratyush Anand wrote: > > On 18/03/2016:02:02:49 PM, James Morse wrote: > >> In kernel/entry.S when entered from EL0 we test for TIF_SINGLESTEP in the > >> thread_info flags, and use

Re: [PATCH v11 3/9] arm64: add copy_to/from_user to kprobes blacklist

Hi James, On 18/03/2016:06:12:20 PM, James Morse wrote: > Hi Pratyush, > > On 18/03/16 14:43, Pratyush Anand wrote: > > On 18/03/2016:02:02:49 PM, James Morse wrote: > >> In kernel/entry.S when entered from EL0 we test for TIF_SINGLESTEP in the > >> thread_info flags, and use

[GIT PULL] MD for 4.6

Hi Linus, Could you please pull the MD update for 4.6? This update mainly fixes bugs. - A raid5 discard related fix from Jes - A MD multipath bio clone fix from Ming - raid1 error handling deadlock fix from Nate and corresponding raid10 fix from myself - A raid5 stripe batch fix from Neil - A

[GIT PULL] MD for 4.6

Hi Linus, Could you please pull the MD update for 4.6? This update mainly fixes bugs. - A raid5 discard related fix from Jes - A MD multipath bio clone fix from Ming - raid1 error handling deadlock fix from Nate and corresponding raid10 fix from myself - A raid5 stripe batch fix from Neil - A

Re: [PATCH 1/4] vfs: add file_dentry()

On Thu, Mar 17, 2016 at 10:02:00AM +0100, Miklos Szeredi wrote: > From: Miklos Szeredi > > This series fixes bugs in nfs and ext4 due to 4bacc9c9234c ("overlayfs: Make > f_path always point to the overlay and f_inode to the underlay"). > > Regular files opened on overlayfs

Re: [PATCH 1/4] vfs: add file_dentry()

On Thu, Mar 17, 2016 at 10:02:00AM +0100, Miklos Szeredi wrote: > From: Miklos Szeredi > > This series fixes bugs in nfs and ext4 due to 4bacc9c9234c ("overlayfs: Make > f_path always point to the overlay and f_inode to the underlay"). > > Regular files opened on overlayfs will result in the

Re: [PATCH v3] ARC: [dts] Introduce Timer bindings

On Sunday 20 March 2016 06:12 AM, Rob Herring wrote: > On Fri, Mar 18, 2016 at 10:56:29AM +0530, Vineet Gupta wrote: >> ARC Timers have historically been probed directly. >> As precursor to start probing Timers thru DT introduce these bindings >> Note that to keep series bisectable, these bindings

Re: [PATCH v3] ARC: [dts] Introduce Timer bindings

On Sunday 20 March 2016 06:12 AM, Rob Herring wrote: > On Fri, Mar 18, 2016 at 10:56:29AM +0530, Vineet Gupta wrote: >> ARC Timers have historically been probed directly. >> As precursor to start probing Timers thru DT introduce these bindings >> Note that to keep series bisectable, these bindings

[GIT PULL] ARC changes for 4.6-rc1

Hi Linus, ARC changes for 4.6-rc1. Nothing too exciting here although diffstat hows more files touched than usual due to some sweeping defconfig / DT updates. Please pull ! Thx, -Vineet -> The following changes since commit fc77dbd34c5c99bce46d40a2491937c3bcbd10af: Linux 4.5-rc6

[GIT PULL] ARC changes for 4.6-rc1

Hi Linus, ARC changes for 4.6-rc1. Nothing too exciting here although diffstat hows more files touched than usual due to some sweeping defconfig / DT updates. Please pull ! Thx, -Vineet -> The following changes since commit fc77dbd34c5c99bce46d40a2491937c3bcbd10af: Linux 4.5-rc6

Re: Suspicious error for CMA stress test

On Fri, Mar 18, 2016 at 02:32:35PM +0100, Lucas Stach wrote: > Hi Vlastimil, Joonsoo, > > Am Freitag, den 18.03.2016, 00:52 +0900 schrieb Joonsoo Kim: > > 2016-03-18 0:43 GMT+09:00 Vlastimil Babka : > > > On 03/17/2016 10:24 AM, Hanjun Guo wrote: > > >> > > >> On 2016/3/17 14:54,

Re: Suspicious error for CMA stress test

On Fri, Mar 18, 2016 at 02:32:35PM +0100, Lucas Stach wrote: > Hi Vlastimil, Joonsoo, > > Am Freitag, den 18.03.2016, 00:52 +0900 schrieb Joonsoo Kim: > > 2016-03-18 0:43 GMT+09:00 Vlastimil Babka : > > > On 03/17/2016 10:24 AM, Hanjun Guo wrote: > > >> > > >> On 2016/3/17 14:54, Joonsoo Kim

RE: [PATCH] usb: xhci: Fix incomplete PM resume operation due to XHCI commmand timeout

> -Original Message- > From: Alan Stern [mailto:st...@rowland.harvard.edu] > Sent: Friday, March 18, 2016 7:51 PM > To: Rajesh Bhagat > Cc: linux-...@vger.kernel.org; linux-kernel@vger.kernel.org; > gre...@linuxfoundation.org; mathias.ny...@intel.com; Sriram Dash

RE: [PATCH] usb: xhci: Fix incomplete PM resume operation due to XHCI commmand timeout

> -Original Message- > From: Alan Stern [mailto:st...@rowland.harvard.edu] > Sent: Friday, March 18, 2016 7:51 PM > To: Rajesh Bhagat > Cc: linux-...@vger.kernel.org; linux-kernel@vger.kernel.org; > gre...@linuxfoundation.org; mathias.ny...@intel.com; Sriram Dash > > Subject: Re:

Re: [PATCHv4 08/25] thp: support file pages in zap_huge_pmd()

"Kirill A. Shutemov" writes: > [ text/plain ] > On Fri, Mar 18, 2016 at 07:23:41PM +0530, Aneesh Kumar K.V wrote: >> "Kirill A. Shutemov" writes: >> >> > [ text/plain ] >> > split_huge_pmd() for file mappings (and DAX too) is implemented

Re: [PATCHv4 08/25] thp: support file pages in zap_huge_pmd()

"Kirill A. Shutemov" writes: > [ text/plain ] > On Fri, Mar 18, 2016 at 07:23:41PM +0530, Aneesh Kumar K.V wrote: >> "Kirill A. Shutemov" writes: >> >> > [ text/plain ] >> > split_huge_pmd() for file mappings (and DAX too) is implemented by just >> > clearing pmd entry as we can re-fill this

RE: [PATCH] usb: xhci: Fix incomplete PM resume operation due to XHCI commmand timeout

> -Original Message- > From: Mathias Nyman [mailto:mathias.ny...@linux.intel.com] > Sent: Friday, March 18, 2016 4:51 PM > To: Rajesh Bhagat ; linux-...@vger.kernel.org; linux- > ker...@vger.kernel.org > Cc: gre...@linuxfoundation.org; mathias.ny...@intel.com;

RE: [PATCH] usb: xhci: Fix incomplete PM resume operation due to XHCI commmand timeout

> -Original Message- > From: Mathias Nyman [mailto:mathias.ny...@linux.intel.com] > Sent: Friday, March 18, 2016 4:51 PM > To: Rajesh Bhagat ; linux-...@vger.kernel.org; linux- > ker...@vger.kernel.org > Cc: gre...@linuxfoundation.org; mathias.ny...@intel.com; Sriram Dash > > Subject:

Re: [PATCH] sparc: Convert naked unsigned uses to unsigned int

From: Joe Perches Date: Thu, 10 Mar 2016 15:21:43 -0800 > Use the more normal kernel definition/declaration style. > > Done via: > > $ git ls-files arch/sparc | \ > xargs ./scripts/checkpatch.pl -f --fix-inplace --types=unspecified_int > > Signed-off-by: Joe Perches

Re: [PATCH] sparc: Convert naked unsigned uses to unsigned int

From: Joe Perches Date: Thu, 10 Mar 2016 15:21:43 -0800 > Use the more normal kernel definition/declaration style. > > Done via: > > $ git ls-files arch/sparc | \ > xargs ./scripts/checkpatch.pl -f --fix-inplace --types=unspecified_int > > Signed-off-by: Joe Perches Applied.

linux-next: Tree for Mar 21

Hi all, Please do not add any v4.7 related material to your linux-next included trees until after v4.6-rc1 is released. Changes since 20160318: The ext4 tree gained a conflict against Linus' tree. The drm tree still had its build failure for which I applied a fix patch. Non-merge commits

linux-next: Tree for Mar 21

Hi all, Please do not add any v4.7 related material to your linux-next included trees until after v4.6-rc1 is released. Changes since 20160318: The ext4 tree gained a conflict against Linus' tree. The drm tree still had its build failure for which I applied a fix patch. Non-merge commits

[PATCH v3 07/23] ncr5380: Remove BOARD_REQUIRES_NO_DELAY macro

The io_recovery_delay macro is intended to insert a microsecond delay between the chip register accesses that begin a DMA operation. This is reportedly needed for some ISA boards. Reverse the sense of the macro test so that in the common case, where no delay is required, drivers need not define

[PATCH v3 10/23] ncr5380: Merge DMA implementation from atari_NCR5380 core driver

Adopt the DMA implementation from atari_NCR5380.c. This means that atari_scsi and sun3_scsi can make use of the NCR5380.c core driver and the atari_NCR5380.c driver fork can be made redundant. Signed-off-by: Finn Thain Reviewed-by: Hannes Reinecke

[PATCH v3 07/23] ncr5380: Remove BOARD_REQUIRES_NO_DELAY macro

The io_recovery_delay macro is intended to insert a microsecond delay between the chip register accesses that begin a DMA operation. This is reportedly needed for some ISA boards. Reverse the sense of the macro test so that in the common case, where no delay is required, drivers need not define

[PATCH v3 10/23] ncr5380: Merge DMA implementation from atari_NCR5380 core driver

Adopt the DMA implementation from atari_NCR5380.c. This means that atari_scsi and sun3_scsi can make use of the NCR5380.c core driver and the atari_NCR5380.c driver fork can be made redundant. Signed-off-by: Finn Thain Reviewed-by: Hannes Reinecke Tested-by: Michael Schmitz ---

[PATCH v3 09/23] ncr5380: Adopt uniform DMA setup convention

Standardize the DMA setup hooks so that the DMA implementation in atari_NCR5380.c can be reconciled with pseudo DMA implementation in NCR5380.c. Calls to NCR5380_dma_recv_setup() and NCR5380_dma_send_setup() return a negative value on failure, zero on PDMA transfer success and a positive byte

[PATCH v3 09/23] ncr5380: Adopt uniform DMA setup convention

Standardize the DMA setup hooks so that the DMA implementation in atari_NCR5380.c can be reconciled with pseudo DMA implementation in NCR5380.c. Calls to NCR5380_dma_recv_setup() and NCR5380_dma_send_setup() return a negative value on failure, zero on PDMA transfer success and a positive byte

[PATCH v3 14/23] ncr5380: Reduce max_lun limit

The driver has a limit of eight LUs because of the byte-sized bitfield that is used for busy flags. That means the maximum LUN is 7. The default is 8. Signed-off-by: Finn Thain Tested-by: Michael Schmitz --- Changed since v1: - Reduce

[PATCH v3 03/23] ncr5380: Remove REAL_DMA and REAL_DMA_POLL macros

For the NCR5380.c core driver, these macros are never used. If REAL_DMA were to be defined, compilation would fail. For the atari_NCR5380.c core driver, REAL_DMA is always defined. Hence these macros are pointless. Signed-off-by: Finn Thain Reviewed-by: Hannes

[PATCH v3 14/23] ncr5380: Reduce max_lun limit

The driver has a limit of eight LUs because of the byte-sized bitfield that is used for busy flags. That means the maximum LUN is 7. The default is 8. Signed-off-by: Finn Thain Tested-by: Michael Schmitz --- Changed since v1: - Reduce shost->max_lun limit instead of adding 'MAX_LUN' limit.

[PATCH v3 03/23] ncr5380: Remove REAL_DMA and REAL_DMA_POLL macros

For the NCR5380.c core driver, these macros are never used. If REAL_DMA were to be defined, compilation would fail. For the atari_NCR5380.c core driver, REAL_DMA is always defined. Hence these macros are pointless. Signed-off-by: Finn Thain Reviewed-by: Hannes Reinecke Tested-by: Michael

[PATCH v3 12/23] sun3_scsi: Adopt NCR5380.c core driver

Add support for the custom Sun 3 DMA logic to the NCR5380.c core driver. This code is copied from atari_NCR5380.c. Signed-off-by: Finn Thain Reviewed-by: Hannes Reinecke Tested-by: Michael Schmitz --- The Sun 3 DMA code is

[PATCH v3 11/23] atari_scsi: Adopt NCR5380.c core driver

Add support for the Atari ST DMA chip to the NCR5380.c core driver. This code is copied from atari_NCR5380.c. Signed-off-by: Finn Thain Reviewed-by: Hannes Reinecke Tested-by: Michael Schmitz --- drivers/scsi/NCR5380.c|

[PATCH v3 01/23] g_ncr5380: Remove CONFIG_SCSI_GENERIC_NCR53C400

This change brings a number of improvements: fewer macros, better test coverage, simpler code and sane Kconfig options. The downside is a small chance of incompatibility (which seems unavoidable). CONFIG_SCSI_GENERIC_NCR53C400 exists to enable or inhibit pseudo DMA transfers when the driver is

[PATCH v3 12/23] sun3_scsi: Adopt NCR5380.c core driver

Add support for the custom Sun 3 DMA logic to the NCR5380.c core driver. This code is copied from atari_NCR5380.c. Signed-off-by: Finn Thain Reviewed-by: Hannes Reinecke Tested-by: Michael Schmitz --- The Sun 3 DMA code is still configured by macros. I have simplified things slightly but I

[PATCH v3 11/23] atari_scsi: Adopt NCR5380.c core driver

Add support for the Atari ST DMA chip to the NCR5380.c core driver. This code is copied from atari_NCR5380.c. Signed-off-by: Finn Thain Reviewed-by: Hannes Reinecke Tested-by: Michael Schmitz --- drivers/scsi/NCR5380.c| 32 drivers/scsi/atari_scsi.c |

[PATCH v3 01/23] g_ncr5380: Remove CONFIG_SCSI_GENERIC_NCR53C400

This change brings a number of improvements: fewer macros, better test coverage, simpler code and sane Kconfig options. The downside is a small chance of incompatibility (which seems unavoidable). CONFIG_SCSI_GENERIC_NCR53C400 exists to enable or inhibit pseudo DMA transfers when the driver is

[PATCH v3 08/23] ncr5380: Use DMA hooks for PDMA

Those wrapper drivers which use DMA define the REAL_DMA macro and those which use pseudo DMA define PSEUDO_DMA. These macros need to be removed for a number of reasons, not least of which is to have drivers share more code. Redefine the PDMA send and receive hooks as DMA setup hooks, so that the

[PATCH v3 08/23] ncr5380: Use DMA hooks for PDMA

Those wrapper drivers which use DMA define the REAL_DMA macro and those which use pseudo DMA define PSEUDO_DMA. These macros need to be removed for a number of reasons, not least of which is to have drivers share more code. Redefine the PDMA send and receive hooks as DMA setup hooks, so that the

[PATCH v3 18/23] ncr5380: Remove DONT_USE_INTR and AUTOPROBE_IRQ macros

Signed-off-by: Finn Thain Reviewed-by: Hannes Reinecke Tested-by: Michael Schmitz --- drivers/scsi/NCR5380.c | 12 +--- drivers/scsi/NCR5380.h |4 drivers/scsi/arm/oak.c |2 --

[PATCH v3 20/23] atari_scsi: Set a reasonable default for cmd_per_lun

This setting does not need to be conditional on Atari ST or TT. Signed-off-by: Finn Thain Tested-by: Michael Schmitz --- Changed since v1: - Set the default cmd_per_lun to 4 based on test results. Changed since v2: - Revert the default

[PATCH v3 13/23] ncr5380: Remove disused atari_NCR5380.c core driver

Now that atari_scsi and sun3_scsi have been converted to use the NCR5380.c core driver, remove atari_NCR5380.c. Also remove the last vestiges of its Tagged Command Queueing implementation from the wrapper drivers. The TCQ support in atari_NCR5380.c is abandoned by this patch. It is not merged

[PATCH v3 18/23] ncr5380: Remove DONT_USE_INTR and AUTOPROBE_IRQ macros

Signed-off-by: Finn Thain Reviewed-by: Hannes Reinecke Tested-by: Michael Schmitz --- drivers/scsi/NCR5380.c | 12 +--- drivers/scsi/NCR5380.h |4 drivers/scsi/arm/oak.c |2 -- drivers/scsi/dmx3191d.c |2 -- drivers/scsi/dtc.c | 12 +++-

[PATCH v3 20/23] atari_scsi: Set a reasonable default for cmd_per_lun

This setting does not need to be conditional on Atari ST or TT. Signed-off-by: Finn Thain Tested-by: Michael Schmitz --- Changed since v1: - Set the default cmd_per_lun to 4 based on test results. Changed since v2: - Revert the default cmd_per_lun to 2, like in the v1 patch, because a

[PATCH v3 13/23] ncr5380: Remove disused atari_NCR5380.c core driver

Now that atari_scsi and sun3_scsi have been converted to use the NCR5380.c core driver, remove atari_NCR5380.c. Also remove the last vestiges of its Tagged Command Queueing implementation from the wrapper drivers. The TCQ support in atari_NCR5380.c is abandoned by this patch. It is not merged

[PATCH v3 17/23] ncr5380: Remove remaining register storage qualifiers

Signed-off-by: Finn Thain Reviewed-by: Hannes Reinecke Tested-by: Michael Schmitz --- drivers/scsi/NCR5380.c |6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) Index: linux/drivers/scsi/NCR5380.c

[PATCH v3 15/23] dmx3191d: Drop max_sectors limit

The dmx3191d driver is not capable of DMA or PDMA so all transfers use PIO. Now that large slow PIO transfers periodically stop and call cond_resched(), the max_sectors limit can go away. Signed-off-by: Finn Thain Reviewed-by: Hannes Reinecke ---

[PATCH v3 16/23] ncr5380: Fix register decoding for debugging

Decode all bits in the chip registers. They are all useful at times. Fix printk severity so that this output can be suppressed along with the other debugging output. Signed-off-by: Finn Thain Reviewed-by: Hannes Reinecke Tested-by: Michael Schmitz

[PATCH v3 17/23] ncr5380: Remove remaining register storage qualifiers

Signed-off-by: Finn Thain Reviewed-by: Hannes Reinecke Tested-by: Michael Schmitz --- drivers/scsi/NCR5380.c |6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) Index: linux/drivers/scsi/NCR5380.c === ---

[PATCH v3 15/23] dmx3191d: Drop max_sectors limit

The dmx3191d driver is not capable of DMA or PDMA so all transfers use PIO. Now that large slow PIO transfers periodically stop and call cond_resched(), the max_sectors limit can go away. Signed-off-by: Finn Thain Reviewed-by: Hannes Reinecke --- drivers/scsi/dmx3191d.c |1 - 1 file

[PATCH v3 16/23] ncr5380: Fix register decoding for debugging

Decode all bits in the chip registers. They are all useful at times. Fix printk severity so that this output can be suppressed along with the other debugging output. Signed-off-by: Finn Thain Reviewed-by: Hannes Reinecke Tested-by: Michael Schmitz --- drivers/scsi/NCR5380.c | 42

[PATCH v3 22/23] mac_scsi: Fix pseudo DMA implementation

Fix various issues: Comments about bus errors are incorrect. The PDMA asm must return the size of the memory access that faulted so the transfer count can be adjusted accordingly. A phase change may cause a bus error but should not be treated as failure. A bus error does not always imply a phase

[PATCH v3 22/23] mac_scsi: Fix pseudo DMA implementation

Fix various issues: Comments about bus errors are incorrect. The PDMA asm must return the size of the memory access that faulted so the transfer count can be adjusted accordingly. A phase change may cause a bus error but should not be treated as failure. A bus error does not always imply a phase

[PATCH v3 23/23] ncr5380: Call complete_cmd() for disconnected commands on bus reset

I'm told that some targets are liable to disconnect a REQUEST SENSE command. Theoretically this would cause a command undergoing autosense to be moved onto the disconnected list. The bus reset handler must call complete_cmd() for these commands, otherwise the hostdata->sensing pointer will not get

[PATCH v3 19/23] ncr5380: Update usage documentation

Update kernel parameter documentation for atari_scsi, mac_scsi and g_NCR5380 drivers. Remove duplication. Signed-off-by: Finn Thain Reviewed-by: Hannes Reinecke --- Documentation/scsi/g_NCR5380.txt | 17 ++-

[PATCH v3 02/23] ncr5380: Remove FLAG_NO_PSEUDO_DMA where possible

Drivers that define PSEUDO_DMA also define NCR5380_dma_xfer_len. The core driver must call NCR5380_dma_xfer_len which means FLAG_NO_PSEUDO_DMA can be eradicated from the core driver. dmx3191d doesn't define PSEUDO_DMA and has no use for FLAG_NO_PSEUDO_DMA, so remove it there also. Signed-off-by:

[PATCH v3 23/23] ncr5380: Call complete_cmd() for disconnected commands on bus reset

I'm told that some targets are liable to disconnect a REQUEST SENSE command. Theoretically this would cause a command undergoing autosense to be moved onto the disconnected list. The bus reset handler must call complete_cmd() for these commands, otherwise the hostdata->sensing pointer will not get

[PATCH v3 19/23] ncr5380: Update usage documentation

Update kernel parameter documentation for atari_scsi, mac_scsi and g_NCR5380 drivers. Remove duplication. Signed-off-by: Finn Thain Reviewed-by: Hannes Reinecke --- Documentation/scsi/g_NCR5380.txt | 17 ++- Documentation/scsi/scsi-parameters.txt | 11 +++---

[PATCH v3 02/23] ncr5380: Remove FLAG_NO_PSEUDO_DMA where possible

Drivers that define PSEUDO_DMA also define NCR5380_dma_xfer_len. The core driver must call NCR5380_dma_xfer_len which means FLAG_NO_PSEUDO_DMA can be eradicated from the core driver. dmx3191d doesn't define PSEUDO_DMA and has no use for FLAG_NO_PSEUDO_DMA, so remove it there also. Signed-off-by:

[PATCH v3 06/23] ncr5380: Remove PSEUDO_DMA macro

For those wrapper drivers which only implement Programmed IO, have NCR5380_dma_xfer_len() evaluate to zero. That allows PDMA to be easily disabled at run-time and so the PSEUDO_DMA macro is no longer needed. Also remove the spin counters used for debugging pseudo DMA drivers. Signed-off-by: Finn

[PATCH v3 21/23] atari_scsi: Allow can_queue to be increased for Falcon

The benefit of limiting can_queue to 1 is that atari_scsi shares the ST DMA chip more fairly with other drivers (e.g. falcon-ide). Unfortunately, this can limit SCSI bus utilization. On systems without IDE, atari_scsi should issue SCSI commands whenever it can arbitrate for the bus. Make that

[PATCH v3 06/23] ncr5380: Remove PSEUDO_DMA macro

For those wrapper drivers which only implement Programmed IO, have NCR5380_dma_xfer_len() evaluate to zero. That allows PDMA to be easily disabled at run-time and so the PSEUDO_DMA macro is no longer needed. Also remove the spin counters used for debugging pseudo DMA drivers. Signed-off-by: Finn

[PATCH v3 21/23] atari_scsi: Allow can_queue to be increased for Falcon

The benefit of limiting can_queue to 1 is that atari_scsi shares the ST DMA chip more fairly with other drivers (e.g. falcon-ide). Unfortunately, this can limit SCSI bus utilization. On systems without IDE, atari_scsi should issue SCSI commands whenever it can arbitrate for the bus. Make that

[PATCH v3 00/23] ncr5380: Eliminate macros, reduce code duplication, fix bugs etc

This patch series has more macro elimination and some tweaks to the DMA hooks so that all the wrapper drivers can share the same core DMA algorithm. This resolves the major discrepancies between the two core drivers, which relate to code conditional on the REAL_DMA and PSEUDO_DMA macros. After

[PATCH v3 04/23] atari_NCR5380: Remove DMA_MIN_SIZE macro

Only the atari_scsi and sun3_scsi drivers define DMA_MIN_SIZE. Both drivers also define NCR5380_dma_xfer_len, which means DMA_MIN_SIZE can be removed from the core driver. This removes another discrepancy between the two core drivers. Signed-off-by: Finn Thain

[PATCH v3 04/23] atari_NCR5380: Remove DMA_MIN_SIZE macro

Only the atari_scsi and sun3_scsi drivers define DMA_MIN_SIZE. Both drivers also define NCR5380_dma_xfer_len, which means DMA_MIN_SIZE can be removed from the core driver. This removes another discrepancy between the two core drivers. Signed-off-by: Finn Thain Tested-by: Michael Schmitz ---

[PATCH v3 00/23] ncr5380: Eliminate macros, reduce code duplication, fix bugs etc

This patch series has more macro elimination and some tweaks to the DMA hooks so that all the wrapper drivers can share the same core DMA algorithm. This resolves the major discrepancies between the two core drivers, which relate to code conditional on the REAL_DMA and PSEUDO_DMA macros. After

[PATCH v3 05/23] ncr5380: Disable the DMA errata workaround flag by default

The only chip that needs the workarounds enabled is an early NMOS device. That means that the common case is to disable them. Unfortunately the sense of the flag is such that it has to be set for the common case. Rename the flag so that zero can be used to mean "no errata workarounds needed".

[PATCH v3 05/23] ncr5380: Disable the DMA errata workaround flag by default

The only chip that needs the workarounds enabled is an early NMOS device. That means that the common case is to disable them. Unfortunately the sense of the flag is such that it has to be set for the common case. Rename the flag so that zero can be used to mean "no errata workarounds needed".

Re: [PATCH 0/2] ARM: uniphier: UniPhier updates for Linux 4.6-rc1 (2nd round)

Hi Arnd, 2016-03-19 8:49 GMT+09:00 Masahiro Yamada : > Hi Arnd, > > 2016-03-19 1:49 GMT+09:00 Arnd Bergmann : >> On Tuesday 15 March 2016 11:01:00 Masahiro Yamada wrote: >>> Olof, Arnd, >>> >>> >>> I sent my patches around -rc4 and >>> took action

Re: [PATCH 0/2] ARM: uniphier: UniPhier updates for Linux 4.6-rc1 (2nd round)

Hi Arnd, 2016-03-19 8:49 GMT+09:00 Masahiro Yamada : > Hi Arnd, > > 2016-03-19 1:49 GMT+09:00 Arnd Bergmann : >> On Tuesday 15 March 2016 11:01:00 Masahiro Yamada wrote: >>> Olof, Arnd, >>> >>> >>> I sent my patches around -rc4 and >>> took action soon as requested. >>> >>> But, my series is

[git pull] drm pull for 4.6-rc1

Hi Linus, This is the main drm pull request for 4.6 kernel. The highlights are below, and there are a few merge conflicts, but I think they should all be simple enough for you to take care off. At least at the moment they are just the writecombine interface changes. Overall the coolest thing

[git pull] drm pull for 4.6-rc1

Hi Linus, This is the main drm pull request for 4.6 kernel. The highlights are below, and there are a few merge conflicts, but I think they should all be simple enough for you to take care off. At least at the moment they are just the writecombine interface changes. Overall the coolest thing

Re: [PATCH v3] staging: netlogic: Fixed alignment of parentheseis checkpatch warning

On Sat, 19 Mar 2016 19:22:09 -0700, Joe Perches said: > On Sun, 2016-03-20 at 07:48 +0530, Parth Sane wrote: > > Hi, > > Thanks for pointing out that the changes have been done. Nevertheless > > this was a good learning exercise. How do I check which changes have > > already been done? > > Use

Re: [PATCH v3] staging: netlogic: Fixed alignment of parentheseis checkpatch warning

On Sat, 19 Mar 2016 19:22:09 -0700, Joe Perches said: > On Sun, 2016-03-20 at 07:48 +0530, Parth Sane wrote: > > Hi, > > Thanks for pointing out that the changes have been done. Nevertheless > > this was a good learning exercise. How do I check which changes have > > already been done? > > Use

Re: [PATCH 2/3] x86/topology: Fix AMD core count

On Mon, Mar 21, 2016 at 11:07:44AM +0800, Huang Rui wrote: > On Fri, Mar 18, 2016 at 05:41:01PM +0100, Borislav Petkov wrote: > > On Fri, Mar 18, 2016 at 04:03:47PM +0100, Peter Zijlstra wrote: > > > It turns out AMD gets x86_max_cores wrong when there are compute > > > units. > > > > > > The

Re: [PATCH 2/3] x86/topology: Fix AMD core count

On Mon, Mar 21, 2016 at 11:07:44AM +0800, Huang Rui wrote: > On Fri, Mar 18, 2016 at 05:41:01PM +0100, Borislav Petkov wrote: > > On Fri, Mar 18, 2016 at 04:03:47PM +0100, Peter Zijlstra wrote: > > > It turns out AMD gets x86_max_cores wrong when there are compute > > > units. > > > > > > The

Re: [PATCH 2/3] x86/topology: Fix AMD core count

On Fri, Mar 18, 2016 at 05:41:01PM +0100, Borislav Petkov wrote: > On Fri, Mar 18, 2016 at 04:03:47PM +0100, Peter Zijlstra wrote: > > It turns out AMD gets x86_max_cores wrong when there are compute > > units. > > > > The issue is that Linux assumes: > > > > nr_logical_cpus = nr_cores *

Re: [PATCH 2/3] x86/topology: Fix AMD core count

On Fri, Mar 18, 2016 at 05:41:01PM +0100, Borislav Petkov wrote: > On Fri, Mar 18, 2016 at 04:03:47PM +0100, Peter Zijlstra wrote: > > It turns out AMD gets x86_max_cores wrong when there are compute > > units. > > > > The issue is that Linux assumes: > > > > nr_logical_cpus = nr_cores *

RE: [PATCH v3 4/4] mtd: spi-nor: Disable Micron flash HW protection

Hi, Yunhai You mean that EVCR.bit7 cannot clear(enable quad mode) if not write SR.bit7 to 0? They don't have any connection each other. > -Original Message- > From: Yunhui Cui [mailto:yunhui@nxp.com] > Sent: Friday, March 18, 2016 6:09 PM > To: Bean Huo 霍斌斌 (beanhuo); Yunhui Cui >

RE: [PATCH v3 4/4] mtd: spi-nor: Disable Micron flash HW protection

Hi, Yunhai You mean that EVCR.bit7 cannot clear(enable quad mode) if not write SR.bit7 to 0? They don't have any connection each other. > -Original Message- > From: Yunhui Cui [mailto:yunhui@nxp.com] > Sent: Friday, March 18, 2016 6:09 PM > To: Bean Huo 霍斌斌 (beanhuo); Yunhui Cui >

Re: [LKP] [lkp] [futex] 65d8fc777f: +25.6% will-it-scale.per_process_ops

Hi, Thomas, Thanks a lot for your valuable input! Thomas Gleixner writes: > On Fri, 18 Mar 2016, Huang, Ying wrote: >> Usually we will put most important change we think in the subject of the >> mail, for this email, it is, >> >> +25.6% will-it-scale.per_process_ops > >

Re: [LKP] [lkp] [futex] 65d8fc777f: +25.6% will-it-scale.per_process_ops

Hi, Thomas, Thanks a lot for your valuable input! Thomas Gleixner writes: > On Fri, 18 Mar 2016, Huang, Ying wrote: >> Usually we will put most important change we think in the subject of the >> mail, for this email, it is, >> >> +25.6% will-it-scale.per_process_ops > > That is confusing on

[PATCH] regulator: Lookup unresolved parent supplies before regulators cleanup

Commit 6261b06de565 ("regulator: Defer lookup of supply to regulator_get") moved the regulator supplies lookup logic from the regulators registration to the regulators get time. Unfortunately, that changed the behavior of the regulator core since now a parent supply with a child regulator marked

[PATCH] regulator: Lookup unresolved parent supplies before regulators cleanup

Commit 6261b06de565 ("regulator: Defer lookup of supply to regulator_get") moved the regulator supplies lookup logic from the regulators registration to the regulators get time. Unfortunately, that changed the behavior of the regulator core since now a parent supply with a child regulator marked

[PATCH] regulator: Remove unneded check for regulator supply

The regulator_resolve_supply() function checks if a supply has been associated with a regulator to avoid enabling it if that is not the case. But the supply was already looked up with regulator_resolve_supply() and set with set_supply() before the check and both return on error. So the fact that

[PATCH] regulator: Remove unneded check for regulator supply

The regulator_resolve_supply() function checks if a supply has been associated with a regulator to avoid enabling it if that is not the case. But the supply was already looked up with regulator_resolve_supply() and set with set_supply() before the check and both return on error. So the fact that

RE: [PATCH v5 3/5] ARM: at91: pm: configure PMC fast startup signals

Hi Alexandre, > -Original Message- > From: Alexandre Belloni [mailto:alexandre.bell...@free-electrons.com] > Sent: 2016年3月18日 1:15 > To: Yang, Wenyou > Cc: Ferre, Nicolas ; Jean-Christophe Plagniol- > Villard ;

RE: [PATCH v5 3/5] ARM: at91: pm: configure PMC fast startup signals

Hi Alexandre, > -Original Message- > From: Alexandre Belloni [mailto:alexandre.bell...@free-electrons.com] > Sent: 2016年3月18日 1:15 > To: Yang, Wenyou > Cc: Ferre, Nicolas ; Jean-Christophe Plagniol- > Villard ; Russell King ; linux- > ker...@vger.kernel.org; devicet...@vger.kernel.org;

[PATCH 1/1] x86/perf/intel/uncore: remove ev_sel_ext bit support for PCU

From: Kan Liang The ev_sel_ext in PCU_MSR_PMON_CTL is locked. So there could be #GP if writing that bit to 1. Also there is no public events which use the bit. This patch removes ev_sel_ext bit support for PCU. Signed-off-by: Kan Liang ---

[PATCH 1/1] x86/perf/intel/uncore: remove ev_sel_ext bit support for PCU

From: Kan Liang The ev_sel_ext in PCU_MSR_PMON_CTL is locked. So there could be #GP if writing that bit to 1. Also there is no public events which use the bit. This patch removes ev_sel_ext bit support for PCU. Signed-off-by: Kan Liang --- arch/x86/events/intel/uncore_snbep.c | 7 ++- 1

Re: [GIT PULL] Protection Keys (pkeys) support

So I finally got around to this one and the objtool pull request, and note that there's a conflict in the arch/x86/Kconfig file. And I'm not sending this email because the conflict would have been hard to resolve - it was completely trivial. But the conflict does show that once again people are

Re: [GIT PULL] Protection Keys (pkeys) support

So I finally got around to this one and the objtool pull request, and note that there's a conflict in the arch/x86/Kconfig file. And I'm not sending this email because the conflict would have been hard to resolve - it was completely trivial. But the conflict does show that once again people are

[GIT PULL] xfs: updates for 4.6-rc1

Hi Linus, Can you please pull the XFS update from the location below? There's quite a lot in this request, and there's some cross-over with ext4, dax and quota code due to the nature of the changes being made. There are conflicts with the ext4 code that has already been merged this cycle. Ted

[GIT PULL] xfs: updates for 4.6-rc1

Hi Linus, Can you please pull the XFS update from the location below? There's quite a lot in this request, and there's some cross-over with ext4, dax and quota code due to the nature of the changes being made. There are conflicts with the ext4 code that has already been merged this cycle. Ted

  1   2   3   4   5   6   7   8   9   10   >