On 1/16/2014 3:42 AM, Martin K. Petersen wrote:
"nab" == Nicholas A Bellinger writes:
nab> The issue is that existing fs/bio-integrity.c code always assumes
nab> client/initiator mode, in that it will attempt to
nab> bio_integrity_generate() protection information in the submit_bio
nab> WRITE p
Hello,
I'd like to attend LSF/MM 2014. Whether expose persitent memory
directly to the CPU or hide it behind a PCIe IO controller, I'm
interested to learn/discuss the short and long term mechanisms that
exploiting its benefits of fast, bytes-addressable, non-volatile.
Last year I mainly worked on
On resume, the SD driver currently waits until the block driver finishes
executing a disk start command with blk_execute_rq. This patch changes
the sd_resume callback to use blk_execute_rq_nowait instead, which allows
it to return immediately, thus allowing the next device in the pm queue
to resume
On resume, the ATA port driver currently waits until the AHCI controller
finishes executing the port wakeup command. This patch changes the
ata_port_resume callback to issue the wakeup and then return immediately,
thus allowing the next device in the pm queue to resume. Any commands
issued to the A
This patch reduces S3 resume time from 10+ seconds to less than a second
on systems with SATA drives. It does this by making ata port and scsi disk
resume non-blocking.
This is v4, sent in response to Tejun Huo's comments and with some small
fixes made after testing.
OVERVIEW
The essential issue
> "nab" == Nicholas A Bellinger writes:
nab> Mmm, missed that detail. So that would take care of the
nab> passthrough for the WRITE case then..
nab> How about a passthrough on the READ completion side for target
nab> fabrics doing a hardware VERIFY..? Any preferences how this should
nab> w
On Wed, 2014-01-15 at 20:42 -0500, Martin K. Petersen wrote:
> > "nab" == Nicholas A Bellinger writes:
>
> nab> The issue is that existing fs/bio-integrity.c code always assumes
> nab> client/initiator mode, in that it will attempt to
> nab> bio_integrity_generate() protection information in
Hi Quinn,
Thanks for the response. Comments are inline below..
On Wed, 2014-01-15 at 22:14 +, Quinn Tran wrote:
> Nicholas,
>
> Answer for the following is below.
>
>
> There are still some bugs to be resolved. Namely:
>
> * Determine how to save 'point-to-point' NVRAM settings across t
> "nab" == Nicholas A Bellinger writes:
nab> The issue is that existing fs/bio-integrity.c code always assumes
nab> client/initiator mode, in that it will attempt to
nab> bio_integrity_generate() protection information in the submit_bio
nab> WRITE path, and bio_integrity_verify() of protectio
On 14-01-15 06:10 PM, Nicholas A. Bellinger wrote:
On Wed, 2014-01-15 at 12:27 -0800, Zach Brown wrote:
Discussing copy offloading at LSF is appropriate because it can involve
so many layers of the stack:
- high level syscall interface
- in-kernel high level entry point for nfsd
- fs spec
Hi,
>>> >> >> +- clocks : Reference to the clock entry.
>>> >> >> +- phys : PHY reference with parameter 0.
>>> >> >
>>> >> > The specific value of the phy-specifier shouldn't matter to this
>>> >> > binding. What should matter is what it logically corresponds to.
On Fri, 2013-12-20 at 15:54 +0100, Hannes Reinecke wrote:
> Hi all,
>
> (before leaving for holiday ...)
>
> I'd like to attend LSF 2014.
>
> During that I'd like to discuss the current status of the SCSI EH
> and the future planned updates.
>
> As discussed during last year's LSF the SCSI erro
On Fri, 2014-01-10 at 13:27 -0500, Mike Snitzer wrote:
> I would like to attend to participate in discussions related to topics
> listed in the subject. As a maintainer of DM I'd be interested to
> learn/discuss areas that should become a development focus in the months
> following LSF.
+1 on the
On Wed, 2014-01-15 at 12:27 -0800, Zach Brown wrote:
> Discussing copy offloading at LSF is appropriate because it can involve
> so many layers of the stack:
>
> - high level syscall interface
> - in-kernel high level entry point for nfsd
> - fs specific implementations (btrfs and ocfs2 cow, n
Hi all,
I'd like to discuss the current state of scsi-mq prototype code.
And now that blk-mq is upstream for v3.13, exploring the remaining TODO
items towards an initial scsi-mq merge sometime before 2015 is upon us.
The benefits of scsi-mq remain unchanged:
- Utilizes blk-mq's native per-cpu
On Wed, 2014-01-15 at 20:03 +0200, sagi grimberg wrote:
> On 1/8/2014 10:36 PM, Nicholas A. Bellinger wrote:
> > From: Nicholas Bellinger
> >
> > Hi MKP & SCSI folks,
> >
> > This series contains initial support for target mode DIF Type1+Type3
> > emulation within target core, RAMDISK_MCP device b
Nicholas,
Answer for the following is below.
There are still some bugs to be resolved. Namely:
* Determine how to save 'point-to-point' NVRAM settings across target
restart
* Figure out why the initiator logs in, but doesn't perform LUN scan on
the first login attempt
* Determine if it's po
On Tue, Jan 14, 2014 at 03:30:11PM +0200, Sergey Meirovich wrote:
> Hi Cristoph,
>
> On 8 January 2014 16:03, Christoph Hellwig wrote:
> > On Tue, Jan 07, 2014 at 08:37:23PM +0200, Sergey Meirovich wrote:
> >> Actually my initial report (14.67Mb/sec 3755.41 Requests/sec) was about
> >> ext4
> >
Hi,
>> >> >> +- clocks : Reference to the clock entry.
>> >> >> +- phys : PHY reference with parameter 0.
>> >> >
>> >> > The specific value of the phy-specifier shouldn't matter to this
>> >> > binding. What should matter is what it logically corresponds to.
>> >
From: Stephen M. Cameron
Signed-off-by: Stephen M. Cameron
---
drivers/scsi/hpsa.c | 45 +
drivers/scsi/hpsa_cmd.h |2 ++
2 files changed, 47 insertions(+), 0 deletions(-)
diff --git a/drivers/scsi/hpsa.c b/drivers/scsi/hpsa.c
index 14862f9
From: Stephen M. Cameron
Otherwise we could wind up using incorrect raid map data, and
then very bad things would likely happen.
Signed-off-by: Stephen M. Cameron
---
drivers/scsi/hpsa.c |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/drivers/scsi/hpsa.c b/drivers/sc
This series applies to kernel/git/jejb/scsi.git for-next branch
This is a big patch series. Most of the changes have to do
with enabling alternate command submission paths for certain i/os
to bypass the Smart Array RAID firmware stack and submit i/o's
more directly to physical devices -- solid st
Hi Giridhar & Co,
A few more questions below..
On Wed, 2014-01-15 at 16:06 +, Giridhar Malavali wrote:
>
> > On Jan 14, 2014, at 10:02 PM, "Nicholas A. Bellinger"
> > wrote:
> >
> > From: Nicholas Bellinger
> >
> > Hi Saurav & Co,
> >
> > Here is the updated NPIV patch on top of the ori
From: Stephen M. Cameron
Don't wait for *all* commands to complete, only for accelerated mode
commands.
Signed-off-by: Stephen M. Cameron
---
drivers/scsi/hpsa.c | 22 --
1 files changed, 16 insertions(+), 6 deletions(-)
diff --git a/drivers/scsi/hpsa.c b/drivers/scsi/hp
From: Stephen M. Cameron
Do no rescan on every events -- way too many rescans are
triggered if we don't filter the events. Limit rescans
to be triggered by the following set of events:
* controller state change
* enclosure hot plug
* physical drive state change
* logical drive state change
From: Scott Teel
Add controller-based data-at-rest encryption compatibility
to ioaccel2 path (HP SSD Smart Path).
Encryption feature requires driver to supply additional fields
for encryption enable, tweak index, and data encryption key index
in the ioaccel2 request structure.
Encryption enable
From: Stephen M. Cameron
Signed-off-by: Scott Teel
Acked-by: Stephen M. Cameron
---
drivers/scsi/hpsa.c | 65 +++
drivers/scsi/hpsa.h |1 +
2 files changed, 66 insertions(+), 0 deletions(-)
diff --git a/drivers/scsi/hpsa.c b/drivers/scsi/h
From: Scott Teel
Change the handling of HP SSD Smart Path errors with status:
0x02 CHECK CONDITION
0x08 BUSY
0x18 RESERVATION CONFLICT
0x40 TASK ABORTED
So that they get retried on the RAID Path.
Signed-off-by: Scott Teel
Acked-by: Stephen M. Cameron
---
drivers/scsi/hpsa.c | 45 +++
From: Stephen M. Cameron
Signed-off-by: Stephen M. Cameron
---
drivers/scsi/hpsa.c | 10 ++
1 files changed, 10 insertions(+), 0 deletions(-)
diff --git a/drivers/scsi/hpsa.c b/drivers/scsi/hpsa.c
index eab21bb..fb0950c 100644
--- a/drivers/scsi/hpsa.c
+++ b/drivers/scsi/hpsa.c
@@ -1
From: Stephen M. Cameron
Signed-off-by: Stephen M. Cameron
---
include/linux/pci_ids.h |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/include/linux/pci_ids.h b/include/linux/pci_ids.h
index 97fbecd..0154d9b 100644
--- a/include/linux/pci_ids.h
+++ b/include/linux/pci_i
From: Stephen M. Cameron
On encountering unexpected error conditions from driver initiated
commands, print something useful like CDB and sense data rather than
something useless like the kernel virtual address of the command buffer.
Signed-off-by: Stephen M. Cameron
---
drivers/scsi/hpsa.c |
From: Scott Teel
Allow SSD Smart Path for a controller to be disabled by
the user, regardless of settings in controller firmware
or array configuration.
To disable: echo 0 > /sys/class/scsi_host/host/acciopath_status
To re-enable: echo 1 > /sys/class/scsi_host/host/acciopath_status
To chec
From: Scott Teel
Signed-off-by: Scott Teel
Acked-by: Stephen M. Cameron
---
drivers/scsi/hpsa.c |2 +-
drivers/scsi/hpsa.h |2 +-
drivers/scsi/hpsa_cmd.h |2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/scsi/hpsa.c b/drivers/scsi/hpsa.c
index 6f
From: Scott Teel
Allow driver to schedule a rescan whenever a request fails on the ioaccel2 path.
This eliminates the possibility of driver getting stuck in non-ioaccel mode.
IOaccel mode (HP SSD Smart Path) is disabled by driver upon error detection.
Driver relied on idea that request would be
From: Scott Teel
Load balance across members of a N-way mirror set, and
handle the meta-RAID levels: R10, R50, R60.
Signed-off-by: Scott Teel
Acked-by: Stephen M. Cameron
---
drivers/scsi/hpsa.c | 174 +--
1 files changed, 168 insertions(+), 6
From: Scott Teel
Signed-off-by: Scott Teel
Signed-off-by: Joe Handzik
Signed-off-by: Mike Miller
Acked-by: Stephen M. Cameron
---
drivers/scsi/hpsa.c | 325 ---
drivers/scsi/hpsa.h | 20 +++
drivers/scsi/hpsa_cmd.h |1
3 files chang
From: Stephen M. Cameron
Code was confused and assumed that page zero was not
VPD page and all non-zero pages were VPD pages.
Signed-off-by: Stephen M. Cameron
---
drivers/scsi/hpsa.c | 18 +-
1 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/drivers/scsi/hpsa.c
From: Stephen M. Cameron
For shared SAS configurations, hosts need to poll Smart Arrays
periodically in order to be able to detect configuration changes
such as logical drives being added or removed from remote hosts.
A register on the controller indicates when such events have
occurred, and the
From: Scott Teel
Signed-off-by: Scott Teel
Acked-by: Stephen M. Cameron
---
drivers/scsi/hpsa.c |9 +
1 files changed, 5 insertions(+), 4 deletions(-)
diff --git a/drivers/scsi/hpsa.c b/drivers/scsi/hpsa.c
index 9628e12..7cab95f 100644
--- a/drivers/scsi/hpsa.c
+++ b/drivers/scsi/
From: Stephen M. Cameron
* Do not check event bits on locked up controllers to
see if they need to be rescanned.
* Do not initiate any device rescans on controllers
which are known to be locked up.
Signed-off-by: Stephen M. Cameron
---
drivers/scsi/hpsa.c | 39 +++
From: Scott Teel
Signed-off-by: Scott Teel
Acked-by: Stephen M. Cameron
---
drivers/scsi/hpsa.c |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/drivers/scsi/hpsa.c b/drivers/scsi/hpsa.c
index 39500d6..3db772f 100644
--- a/drivers/scsi/hpsa.c
+++ b/drivers/scsi/hpsa.
From: Stephen M. Cameron
Signed-off-by: Stephen M. Cameron
---
drivers/scsi/hpsa.c |3 ++-
drivers/scsi/hpsa_cmd.h |1 +
2 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/drivers/scsi/hpsa.c b/drivers/scsi/hpsa.c
index ebca59b..fbf41c7 100644
--- a/drivers/scsi/hpsa.c
+
From: Mike MIller
Signed-off-by: Mike MIller
Acked-by: Stephen M. Cameron
---
drivers/scsi/hpsa.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/drivers/scsi/hpsa.c b/drivers/scsi/hpsa.c
index f0bd511..e471782 100644
--- a/drivers/scsi/hpsa.c
+++ b/drivers/scsi/hpsa
From: Scott Teel
Signed-off-by: Scott Teel
Acked-by: Stephen M. Cameron
---
drivers/scsi/hpsa.c | 25 +
1 files changed, 25 insertions(+), 0 deletions(-)
diff --git a/drivers/scsi/hpsa.c b/drivers/scsi/hpsa.c
index f88bb73..39500d6 100644
--- a/drivers/scsi/hpsa.c
++
From: Scott Teel
Underlying firmware cannot handle task abort on accelerated path (SSD Smart
Path).
Change abort requests for accelerated path commands to physical target reset.
Send reset request on normal IO path.
Signed-off-by: Scott Teel
Signed-off-by: Mike Miller
Acked-by: Stephen M. Cam
From: Stephen M. Cameron
Signed-off-by: Stephen M. Cameron
Signed-off-by: Scott Teel
---
drivers/scsi/hpsa.c | 111 ---
drivers/scsi/hpsa.h |1
drivers/scsi/hpsa_cmd.h |2 -
3 files changed, 78 insertions(+), 36 deletions(-)
diff -
From: Mike Miller
Signed-off-by: Mike Miller
Acked-by: Stephen M. Cameron
---
drivers/scsi/hpsa.c | 22 ++
drivers/scsi/hpsa.h |8
drivers/scsi/hpsa_cmd.h | 99 +++
3 files changed, 129 insertions(+), 0 deletions(-)
diff
From: Stephen M. Cameron
Signed-off-by: Mike Miller
Acked-by: Stephen M. Cameron
---
drivers/scsi/hpsa.c | 50 ++
drivers/scsi/hpsa.h |3 +++
2 files changed, 53 insertions(+), 0 deletions(-)
diff --git a/drivers/scsi/hpsa.c b/drivers/scsi
From: Stephen M. Cameron
When rescanning for logical drives, store information about whather
raid offload is enabled for each logical drive, and update the driver's
internal record of this.
Signed-off-by: Stephen M. Cameron
---
drivers/scsi/hpsa.c |9 +
1 files changed, 9 insertion
From: Stephen M. Cameron
When commands sent down the "fast path" fail, they must be re-tried down the
normal RAID path. We do this by kicking i/o's back to the scsi mid layer with
a DID_SOFT_ERROR status, which causes them to be retried. This won't work for
SG_IO's and other non REQ_TYPE_FS i/o
From: Matt Gates
For certain i/o's to certain devices (unmasked physical disks) we
can bypass the RAID stack firmware and do the i/o to the device
directly and it will be faster.
Signed-off-by: Matt Gates
Signed-off-by: Stephen M. Cameron
---
drivers/scsi/hpsa.c | 296 +++
From: Matt Gates
This is normally optional, but for SSD Smart Path support (in
subsequent patches) it is required.
Signed-off-by: Matt Gates
Acked-by: Stephen M. Cameron
---
drivers/scsi/hpsa.c |8
drivers/scsi/hpsa_cmd.h |1 +
2 files changed, 5 insertions(+), 4 deletion
From: Matt Gates
We were clobbering the SCSI status and setting
cmd->result = DID_SOFT_ERROR << 16; to get a retry,
but better to let the mid layer handle the unit
attention.
Signed-off-by: Matt Gates
Acked-by: Stephen M. Cameron
---
drivers/scsi/hpsa.c |4 +---
1 files changed, 1 inserti
From: Scott Teel
For "mode 1" io accelerated commands, the command tag is in
a different location than for commands that go down the normal
RAID path, so the abort handler needs to take this into account.
Signed-off-by: Scott Teel
Signed-off-by: Mike Miller
Signed-off-by: Stephen M. Cameron
-
From: Matt Gates
There is an extended report luns command which contains
additional information about physical devices. In particular
we need to get the physical device handle so we can use an
alternate i/o path for fast physical devices like SSDs so
we can speed up certain i/o's by bypassing th
From: Stephen M. Cameron
This enables sending i/o's destined for RAID logical drives
which can be serviced by a single physical disk down a different,
faster i/o path directly to physical drives for certain logical
volumes on SSDs bypassing the Smart Array RAID stack for a
performance improvement
From: Stephen M. Cameron
Immediately following a hard board reset, There are some
mandatory delays during which we must not access the board
and during which we might miss the "not ready" status,
therefore it is a mistake to look for and expect to see
the "not ready" status.
Signed-off-by: Steph
From: Stephen M. Cameron
This used to be the default, but at some point the firmware guys
changed the default and I failed to notice. Now to get unit
attention notifications, you must twiddle a bit indicating you
want them.
Signed-off-by: Stephen M. Cameron
---
drivers/scsi/hpsa.c |7
From: Stephen M. Cameron
Much simpler and avoids races starting/stopping the thread.
Signed-off-by: Stephen M. Cameron
---
drivers/scsi/hpsa.c | 103 +--
drivers/scsi/hpsa.h |3 +
2 files changed, 28 insertions(+), 78 deletions(-)
diff --gi
From: Stephen M. Cameron
The field contains more bits than just the one
to indicate whether scsi prefetch should be turned on.
Signed-off-by: Stephen M. Cameron
---
drivers/scsi/hpsa.c | 14 +++---
drivers/scsi/hpsa_cmd.h |3 ++-
2 files changed, 9 insertions(+), 8 deletions(
From: Stephen M. Cameron
This relies on a kernel thread which I wish to remove and
replace with a work queue based solution.
Signed-off-by: Stephen M. Cameron
---
drivers/scsi/hpsa.c | 128 ---
drivers/scsi/hpsa.h | 13 -
2 files changed,
From: Stephen M. Cameron
This relies on a kernel thread which I wish to replace with a
work queue based solution.
Signed-off-by: Stephen M. Cameron
---
drivers/scsi/hpsa.c | 50 ++
drivers/scsi/hpsa.h |1 -
2 files changed, 2 insertions(+),
On Wednesday 15 January 2014 13:08:47 Loc Ho wrote:
> >> >> +- clocks : Reference to the clock entry.
> >> >> +- phys : PHY reference with parameter 0.
> >> >
> >> > The specific value of the phy-specifier shouldn't matter to this
> >> > binding. What should matter
Hi,
>>
>> >> +- clocks : Reference to the clock entry.
>> >> +- phys : PHY reference with parameter 0.
>> >
>> > The specific value of the phy-specifier shouldn't matter to this
>> > binding. What should matter is what it logically corresponds to.
>>
>> I not quit
Evidently some wacky USB-ATA bridges don't recognize the SYNCHRONIZE
CACHE command, as shown in this email thread:
http://marc.info/?t=13897835622&r=1&w=2
The fact that we can't tell them to drain their caches shouldn't
prevent the system from going into suspend. Therefore sd_sync_ca
On Wed, Jan 15, 2014 at 01:30:53PM +0100, Hannes Reinecke wrote:
> Commit 254f796b9f22b1944c64caabc356a56caaa2facd updated
> the driver to use 16 MSI-X vectors, despite the fact that
> older controllers would provide only 4.
> This was causing MSI-X registration to drop down to INTx
> mode. But as
Discussing copy offloading at LSF is appropriate because it can involve
so many layers of the stack:
- high level syscall interface
- in-kernel high level entry point for nfsd
- fs specific implementations (btrfs and ocfs2 cow, nfs)
- vfs helper for offloading block copies for ext*,xfs
- b
Hi,
> [...]
>
>> + * The APM X-Gene PHY consists of two PLL clock macro's (CMU) and lanes.
>> + * The first PLL clock macro is used for internal reference clock. The
>> second
>> + * PLL clock macro is used to generate the clock for the PHY. This driver
>> + * configures the first PLL CMU, the se
On Wednesday 15 January 2014 12:04:02 Loc Ho wrote:
>
> >> +- clocks : Reference to the clock entry.
> >> +- phys : PHY reference with parameter 0.
> >
> > The specific value of the phy-specifier shouldn't matter to this
> > binding. What should matter is what it
Hi,
>> +- clocks : Reference to the clock entry.
>> +- phys : PHY reference with parameter 0.
>
> The specific value of the phy-specifier shouldn't matter to this
> binding. What should matter is what it logically corresponds to.
I not quite following this. Are y
On Wed, Jan 15, 2014 at 08:01:04AM -0500, Tejun Heo wrote:
> Hello,
>
> On Tue, Jan 14, 2014 at 04:31:40PM -0800, Todd E Brandt wrote:
>
> > Signed-off-by: Todd Brandt
> > Signed-off-by: Arjan van de Ven
> >
> > drivers/ata/libata-core.c | 32 +---
> > 1 file c
On 1/8/2014 10:36 PM, Nicholas A. Bellinger wrote:
From: Nicholas Bellinger
Hi MKP & SCSI folks,
This series contains initial support for target mode DIF Type1+Type3
emulation within target core, RAMDISK_MCP device backend, and tcm_loop
fabric driver.
DIF emulation is enabled via a new 'pi_pr
On Fri, Jan 10, 2014 at 03:20:44PM +0100, Rafael J. Wysocki wrote:
> [Cc: adding linux-scsi for the MPT changes, Ben for powerpc, Matthew for
> platform/x86 and Konrad for Xen]
>
> On Friday, December 06, 2013 02:21:50 AM Rafael J. Wysocki wrote:
>
> [...]
>
> >
> > OK
> >
> > To be a bit mor
On Wed, Jan 15, 2014 at 02:36:36PM +0100, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
> Subject: powerpc / eeh_driver: Use global PCI rescan-remove locking
>
> Race conditions are theoretically possible between the PCI device
> addition and removal in the PPC64 PCI error recovery driver an
Hi Alan,
On 01/15/2014 06:19 PM, Alan Stern wrote:
> On Wed, 15 Jan 2014, Daniel Mack wrote:
>
>> Hi,
>>
>> Sorry for the long, primarily holiday-related delay on this.
>>
>> On 12/18/2013 09:46 PM, Alan Stern wrote:
>>> On Wed, 18 Dec 2013, Daniel Mack wrote:
I'm facing an issue putting an
On Wed, 15 Jan 2014, Daniel Mack wrote:
> Hi,
>
> Sorry for the long, primarily holiday-related delay on this.
>
> On 12/18/2013 09:46 PM, Alan Stern wrote:
> > On Wed, 18 Dec 2013, Daniel Mack wrote:
> >> I'm facing an issue putting an embedded system to sleep while a Lacie
> >> external USB ha
Sent from my iPhone. Please excuse any typos.
> On Jan 14, 2014, at 10:02 PM, "Nicholas A. Bellinger"
> wrote:
>
> From: Nicholas Bellinger
>
> Hi Saurav & Co,
>
> Here is the updated NPIV patch on top of the original here:
>
> [PATCH] qla2xxx: Enhancements to enable NPIV support for QLO
From: Rafael J. Wysocki
Subject: powerpc / eeh_driver: Use global PCI rescan-remove locking
Race conditions are theoretically possible between the PCI device
addition and removal in the PPC64 PCI error recovery driver and
the generic PCI bus rescan and device removal that can be triggered
via sys
Hello,
On Tue, Jan 14, 2014 at 04:31:40PM -0800, Todd E Brandt wrote:
> Signed-off-by: Todd Brandt
> Signed-off-by: Arjan van de Ven
>
> drivers/ata/libata-core.c | 32 +---
> 1 file changed, 17 insertions(+), 15 deletions(-)
>
> Signed-off-by: Todd Brandt
>
Please start a new thread when you're posting a new version of the
whole series && don't use the same patch title for the patches. They
do different things. They need different names.
Thanks.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a mes
Commit 254f796b9f22b1944c64caabc356a56caaa2facd updated
the driver to use 16 MSI-X vectors, despite the fact that
older controllers would provide only 4.
This was causing MSI-X registration to drop down to INTx
mode. But as the controller support performant mode, the
initialisation will become conf
On Wed, Jan 15, 2014 at 07:10:39AM +, Loc Ho wrote:
[...]
> + * The APM X-Gene PHY consists of two PLL clock macro's (CMU) and lanes.
> + * The first PLL clock macro is used for internal reference clock. The second
> + * PLL clock macro is used to generate the clock for the PHY. This driver
>
On Wed, Jan 15, 2014 at 07:10:38AM +, Loc Ho wrote:
> Signed-off-by: Loc Ho
> Signed-off-by: Tuan Phan
> Signed-off-by: Suman Tripathi
> ---
> .../devicetree/bindings/phy/apm-xgene-phy.txt | 94
>
> 1 files changed, 94 insertions(+), 0 deletions(-)
> create mod
On Wed, Jan 15, 2014 at 07:11:48AM +, Loc Ho wrote:
> Signed-off-by: Loc Ho
> Signed-off-by: Tuan Phan
> Signed-off-by: Suman Tripathi
> ---
> .../devicetree/bindings/ata/apm-xgene.txt | 68
>
> 1 files changed, 68 insertions(+), 0 deletions(-)
> create mod
Hi,
Sorry for the long, primarily holiday-related delay on this.
On 12/18/2013 09:46 PM, Alan Stern wrote:
> On Wed, 18 Dec 2013, Daniel Mack wrote:
>> I'm facing an issue putting an embedded system to sleep while a Lacie
>> external USB hard disk is connected. Relevant kernel messages that occur
85 matches
Mail list logo
