On Friday 26 July 2013 09:01 AM, Andy Grover wrote:
>
> It's one thing to claim a prerogative of "upstream", but for this to
> make sense, there needs to be an actual community around the upstream.
> And if there's going to be submissions for review, then there needs to
> be someone in charge of th
Hi, Hannes:
On 07/15/2013 06:33 PM, Ren Mingxin wrote:
I noticed that the dd time had been reduced from 6m+ to 2m+ when the
'eh_deadline' was set as 30s, but the dd time was 6m+(nearly the same
as default - 'eh_deadline' was 0) when the 'eh_deadline' was set as
10s. I havn't been able to dig fur
- Original Message -
> [Adding missing cc to linux-scsi]
> On Thu, 2013-07-25 at 23:33 +0200, John Kacur wrote:
> > Hi
> >
> > We're seeing this on a 3.6 kernel with the real-time patch applied, but it
> > looks like it is relevant with the real-time patch in the latest kernel
This shou
On 12/07/13 17:52, Jan Vesely wrote:
> Hi
>
> These patches modify __bio_add_page to accept pages that extent the last bio
> segment. some drivers craft their buffers and rely on this behavior (see
> message in patch 2 for details)
>
>
> jan
>
> v4: whitespace fixes to make checkpatch happy
>
On Friday, July 26, 2013 09:37:09 AM Aaron Lu wrote:
> On 07/25/2013 10:52 PM, Tejun Heo wrote:
> > On Thu, Jul 25, 2013 at 01:47:03PM +0800, Aaron Lu wrote:
> >> Binding ACPI handle to SCSI device has several drawbacks, namely:
> >> 1 During ATA device initialization time, ACPI handle will be need
On Fri, Jul 26, 2013 at 06:28:02AM -0400, John Kacur wrote:
>
>
> - Original Message -
> > [Adding missing cc to linux-scsi]
> > On Thu, 2013-07-25 at 23:33 +0200, John Kacur wrote:
> > > Hi
> > >
> > > We're seeing this on a 3.6 kernel with the real-time patch applied, but it
> > > look
On Thu, Jul 25, 2013 at 07:16:39PM -0700, Nicholas A. Bellinger wrote:
> On Tue, 2013-07-16 at 10:39 -0700, Nicholas A. Bellinger wrote:
> > On Mon, 2013-07-15 at 16:41 -0500, scame...@beardog.cce.hp.com wrote:
> > > Hi,
> > >
> > > I have some questions about your scsi-mq prototype. I have
> > >
This path series contain driver's fixes and updates.
Seungwon Jeon (7):
scsi: ufs: amend the ocs handling with fatal error
scsi: ufs: find out sense data over scsi status values
scsi: ufs: fix the setting interrupt aggregation counter
scsi: ufs: add dme configuration primit
Fatal error in OCS(overall command status) field indicates
error conditions which is not covered by UFSHCI.
It means that host cannot define the result of command status
and therefore host may need to check transfer response UPIU's
response and status field.
It was actually found that 'CHECK CONDIT
Except for 'GOOD' and 'CHECK CONDITION', other status value
in Response UPIU may or may contain sense data. If a non-zero
value is in the Data Segment Length field, it means that UPIU
has Sense Data in the Data Segment area.
Signed-off-by: Seungwon Jeon
---
drivers/scsi/ufs/ufs.h|1 +
dr
LACTH(Interrupt aggregation counter threshold) value is allowed
up to 0x1F and current setting value is the maximum.
This value is related with NUTRS(max:0x20) of HCI's capability.
Considering HCI controller doesn't support the maximum, LATCH
setting should be adjusted with possible value.
For that
Implements to support GET and SET operations of the DME.
These operations are used to configure the behavior of
the UNIPRO. Along with basic operation, {Peer/AttrSetType}
can be mixed.
Signed-off-by: Seungwon Jeon
---
drivers/scsi/ufs/ufshcd.c | 88 +
'drivers/scsi/ufs/unipro.h' is added.
Attributes in the layers of the UNIPRO stack can be
read and written via the DME.
Signed-off-by: Seungwon Jeon
---
drivers/scsi/ufs/unipro.h | 130 +
1 files changed, 130 insertions(+), 0 deletions(-)
create mode
Setting PA_PWRMode using DME_SET triggers the power mode
change. And then the result will be given by the HCS.UPMCRS.
This operation should be done atomically.
Signed-off-by: Seungwon Jeon
---
drivers/scsi/ufs/ufshcd.c | 80 ++--
drivers/scsi/ufs/ufshcd.
UIC attributes can be set with using DME_SET command for
power mode change. For configuration the link capability
attributes are used, which is updated after successful
link startup.
Signed-off-by: Seungwon Jeon
---
drivers/scsi/ufs/ufshcd.c | 74 +++-
d
- Original Message -
> On Fri, Jul 26, 2013 at 06:28:02AM -0400, John Kacur wrote:
> >
> >
> > - Original Message -
> > > [Adding missing cc to linux-scsi]
> > > On Thu, 2013-07-25 at 23:33 +0200, John Kacur wrote:
> > > > Hi
> > > >
> > > > We're seeing this on a 3.6 kernel wi
>From 4c01ac362210c38cdbaddd0a75c24c7070e77dfa Mon Sep 17 00:00:00 2001
From: John Kacur
Date: Fri, 26 Jul 2013 16:06:18 +0200
Subject: [PATCH] hpsa: fix warning with smp_processor_id() in preemptible
section Signed-off-by: John Kacur
On a 3.6-rt (real-time patch) kernel we are seeing the follo
On Fri, Jul 12, 2013 at 05:48:09PM -0400, Santosh Shilimkar wrote:
> The series is an attempt to move ARM port to NO_BOOTMEM. As discussed
> on list NO_BOOTMEM move needed updates to max*pfn meaning to be maximum
> PFNs but that breaks the dma_mask for few block layer drivers since
> ARM start of p
Ritesh,
We have put immense labor and love in creating LIO and targetcli. Please
just take a look at the code, the wiki, the manual, target-devel - we have
poured years of our lives into this project, and we look forward to
implementing many more exciting ideas. Asking us to just abandon this is -
On Friday 26 July 2013 11:10 AM, Russell King - ARM Linux wrote:
> On Fri, Jul 12, 2013 at 05:48:09PM -0400, Santosh Shilimkar wrote:
>> The series is an attempt to move ARM port to NO_BOOTMEM. As discussed
>> on list NO_BOOTMEM move needed updates to max*pfn meaning to be maximum
>> PFNs but that
The IO command size is 128 bytes for these new controllers as opposed to 64
for the old 8001 controller.
The Adaptec out-of-tree driver did this correctly. After comparing the two
this turned out to be the crucial difference.
So don't hardcode the IO command size, instead use pm8001_ha->iomb_size
This is kernel 3.9.9-302.fc19.x86_64.
I plugged in a BN Nook (a usb mass storage device), used it, and
ejected it. This makes suspend fail:
[50135.265514] PM: Entering freeze sleep
[50135.265517] Suspending console(s) (use no_console_suspend to debug)
[50135.287724] sd 7:0:0:0: [sdb] Synchronizi
2013/7/26 Martin Peschke :
> On Mon, 2013-07-15 at 20:52 +0900, Akinobu Mita wrote:
>> With module parameter num_parts > 0, partition table is built on the
>> ramdisk storage when loading the driver. Unfortunately, there is an
>> endianness bug in sdebug_build_parts(). So the partition table is n
On 7/23/13 1:04 PM, "Chris Leech" wrote:
>I hit this during driver probe with the latest fnic updates (this trace
>is from a backport into a distro kernel, but the issue is the same).
>
>> BUG: sleeping function called from invalid context at mm/slab.c:3113
>> in_atomic(): 0, irqs_disabled(): 1,
On Fri, 26 Jul 2013, Andy Lutomirski wrote:
> This is kernel 3.9.9-302.fc19.x86_64.
>
> I plugged in a BN Nook (a usb mass storage device), used it, and
> ejected it. This makes suspend fail:
>
> [50135.265514] PM: Entering freeze sleep
> [50135.265517] Suspending console(s) (use no_console_sus
On Fri, 2013-07-26 at 08:29 -0500, scame...@beardog.cce.hp.com wrote:
> On Thu, Jul 25, 2013 at 07:16:39PM -0700, Nicholas A. Bellinger wrote:
> > On Tue, 2013-07-16 at 10:39 -0700, Nicholas A. Bellinger wrote:
> > Hi Stephen & Robert,
> >
> > Just curious if you've been able to make any progre
On Fri, 26 Jul 2013, Andy Lutomirski wrote:
> This is kernel 3.9.9-302.fc19.x86_64.
>
> I plugged in a BN Nook (a usb mass storage device), used it, and
> ejected it. This makes suspend fail:
>
> [50135.265514] PM: Entering freeze sleep
> [50135.265517] Suspending console(s) (use no_console_sus
On Thu, 2013-07-25 at 20:09 -0600, Jens Axboe wrote:
> On Thu, Jul 25 2013, Nicholas A. Bellinger wrote:
> > On Thu, 2013-07-25 at 12:16 +0200, Alexander Gordeev wrote:
> > > On Mon, Jul 22, 2013 at 02:10:36PM -0700, Nicholas A. Bellinger wrote:
> > > > Np. FYI, you'll want to use the latest commi
On Fri, 2013-07-26 at 14:14 -0700, Nicholas A. Bellinger wrote:
> On Thu, 2013-07-25 at 20:09 -0600, Jens Axboe wrote:
> > On Thu, Jul 25 2013, Nicholas A. Bellinger wrote:
> > > On Thu, 2013-07-25 at 12:16 +0200, Alexander Gordeev wrote:
> > > > On Mon, Jul 22, 2013 at 02:10:36PM -0700, Nicholas A
Hi Hans,
Thanks for addressing the comment.
Acked-by: anandkumar.santha...@pmcs.com
Regards
Anand
-Original Message-
From: Hans Verkuil [mailto:hverk...@xs4all.nl]
Sent: Friday, July 26, 2013 10:14 PM
To: linux-scsi@vger.kernel.org
Cc: Anand Kumar Santhanam; lindar_...@usish.com; San
On Wed, 2013-06-19 at 12:15 -0700, Joe Perches wrote:
> Don't emit OOM warnings when k.alloc calls fail when
> there there is a v.alloc immediately afterwards.
>
> Converted a kmalloc/vmalloc with memset to kzalloc/vzalloc.
Hey Jiri.
What's your schedule for accepting or rejecting
these sorts of
On Thu, Jul 25, 2013 at 10:52:29AM -0400, Tejun Heo wrote:
>
> I like it but am wondering why we weren't doing this before. Was the
> acpi support added before we made ata objects proper devices?
Yes.
--
Matthew Garrett | mj...@srcf.ucam.org
--
To unsubscribe from this list: send the line "uns
32 matches
Mail list logo
