Hi Luis,
Sorry for delay in response. Actually I was looking for the history of
this section of code but I couldn't find it. Anyway this is dead code
and we are fine with removing this dead code.
James,
Please consider this patch as Acked-by: "Sreekanth Reddy"
Regards,
Sreekanth
On Wed, Apr
On Fri, May 29, 2015 at 1:23 PM, Luis R. Rodriguez wrote:
> On Wed, Apr 29, 2015 at 12:50 PM, Luis R. Rodriguez wrote:
>> On Tue, Apr 21, 2015 at 1:46 PM, Luis R. Rodriguez
>> wrote:
>>> From: "Luis R. Rodriguez"
>>>
>>> If and when this gets enabled the driver could should split
>>> up IO memo
On Wed, 2015-06-03 at 15:33 -0700, James Bottomley wrote:
> On Wed, 2015-06-03 at 15:12 -0700, Nicholas A. Bellinger wrote:
> > On Wed, 2015-06-03 at 13:00 -0700, James Bottomley wrote:
> > > OK, this gives us a cross tree dependency on the SCSI header split
> > > patches. Nic, if you base your
On Wed, 2015-06-03 at 15:12 -0700, Nicholas A. Bellinger wrote:
> On Wed, 2015-06-03 at 13:00 -0700, James Bottomley wrote:
> > On Wed, 2015-06-03 at 18:16 +1000, Stephen Rothwell wrote:
> > > Hi Nicholas,
> > >
> > > After merging the target-updates tree, today's linux-next build (x86_64
> > > al
On Wed, 2015-06-03 at 13:00 -0700, James Bottomley wrote:
> On Wed, 2015-06-03 at 18:16 +1000, Stephen Rothwell wrote:
> > Hi Nicholas,
> >
> > After merging the target-updates tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> >
> > drivers/target/target_core_fabric_lib
From: Keith Mange
Use correct defaults for values determined by protocol negotiation,
instead of resetting them with every scsi controller.
Tested-by: Alex Ng
Signed-off-by: Keith Mange
Signed-off-by: K. Y. Srinivasan
---
drivers/scsi/storvsc_drv.c | 33 +++--
1
From: Keith Mange
Use a single value to track protocol versions to simplify
comparisons and to be consistent with vmbus version tracking.
Tested-by: Alex Ng
Signed-off-by: Keith Mange
Signed-off-by: K. Y. Srinivasan
---
drivers/scsi/storvsc_drv.c | 35 +--
1
From: Keith Mange
Allow WRITE_SAME for Windows10 and above hosts.
Tested-by: Alex Ng
Signed-off-by: Keith Mange
Signed-off-by: K. Y. Srinivasan
---
drivers/scsi/storvsc_drv.c |6 +-
1 files changed, 5 insertions(+), 1 deletions(-)
diff --git a/drivers/scsi/storvsc_drv.c b/drivers/sc
In the function storvsc_channel_init(), error code was not getting
set correctly in some of the failure cases. Fix this issue.
Signed-off-by: K. Y. Srinivasan
Reported-by: Dan Carpenter
---
drivers/scsi/storvsc_drv.c | 12 +---
1 files changed, 9 insertions(+), 3 deletions(-)
diff --
From: Keith Mange
Currently we are making decisions based on vmbus protocol versions
that have been negotiated; use storage potocol versions instead.
Tested-by: Alex Ng
Signed-off-by: Keith Mange
Signed-off-by: K. Y. Srinivasan
---
drivers/scsi/storvsc_drv.c | 109 ++
From: Keith Mange
Rather than look for sets of specific protocol versions,
make decisions based on ranges. This will be safer and require fewer changes
going forward as we add more storage protocol versions.
Tested-by: Alex Ng
Signed-off-by: Keith Mange
Signed-off-by: K. Y. Srinivasan
---
dr
From: Keith Mange
Use storage protocol version instead of vmbus protocol
version when determining storage capabilities.
Tested-by: Alex Ng
Signed-off-by: Keith Mange
Signed-off-by: K. Y. Srinivasan
---
drivers/scsi/storvsc_drv.c |8
1 files changed, 4 insertions(+), 4 deletions(
Cleanup version handling as well as base feature detection on storage
version as opposed to host version.
In this version, I have addressed comments from Dan Carpenter.
K. Y. Srinivasan (1):
scsi: storvsc: Set the error code correctly in failure conditions
Keith Mange (6):
scsi: storvsc: Rat
On Wed, 2015-06-03 at 18:16 +1000, Stephen Rothwell wrote:
> Hi Nicholas,
>
> After merging the target-updates tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/target/target_core_fabric_lib.c: In function
> 'target_get_pr_transport_id_len':
> drivers/target/ta
Meelis,
Yes, please revert that patch (it should never have deleted the calls to
__constant_cpu_to_le16 (those fields are all LE in the HW/nvram)).
-Joe
-Original Message-
From: mr...@math.ut.ee [mailto:mr...@math.ut.ee] On Behalf Of Meelis Roos
Sent: Wednesday, June 03, 2015 1:21 AM
To
This patch fix some "a ethernet" in MODULE_DESCRIPTIONS in
fcoe_transport.c
Signed-off-by: Masanari Iida
---
drivers/scsi/fcoe/fcoe_transport.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/scsi/fcoe/fcoe_transport.c
b/drivers/scsi/fcoe/fcoe_transport.c
ind
v2: use debug log level to silence the unsurprising information
v1: A user of scsi_track_queue_full should pass to the function
a constant value untill the queue-depth changes, otherwise the
internal logic in scsi_track_queue_full rejects the change.
Other users of this function use a 'sdev->queue
On Wed, 2015-06-03 at 09:37 -0500, Suravee Suthikulanit wrote:
> On 5/28/2015 9:38 PM, Mark Salter wrote:
> > On Wed, 2015-05-20 at 17:09 -0500, Suravee Suthikulpanit wrote:
> >> >Fromhttp://www.uefi.org/sites/default/files/resources/ACPI_6.0.pdf,
> >> >section 6.2.17 _CCA states that ARM platforms
On 5/28/2015 9:38 PM, Mark Salter wrote:
On Wed, 2015-05-20 at 17:09 -0500, Suravee Suthikulpanit wrote:
>Fromhttp://www.uefi.org/sites/default/files/resources/ACPI_6.0.pdf,
>section 6.2.17 _CCA states that ARM platforms require ACPI _CCA
>object to be specified for DMA-cabpable devices. Therefo
On Wed, Jun 3, 2015 at 3:54 PM, James Bottomley
wrote:
> On Wed, 2015-06-03 at 13:37 +, James Bottomley wrote:
>> On Wed, 2015-06-03 at 11:29 +0200, Jiri Slaby wrote:
>> > On 06/03/2015, 08:35 AM, gre...@linuxfoundation.org wrote:
>> > > From 74856fbf441929918c49ff262ace9835048e4e6a Mon Sep 17
On Wed, 2015-06-03 at 13:37 +, James Bottomley wrote:
> On Wed, 2015-06-03 at 11:29 +0200, Jiri Slaby wrote:
> > On 06/03/2015, 08:35 AM, gre...@linuxfoundation.org wrote:
> > > From 74856fbf441929918c49ff262ace9835048e4e6a Mon Sep 17 00:00:00 2001
> > > From: Mark Hounschell
> > > Date: Wed,
On Wed, 2015-06-03 at 11:29 +0200, Jiri Slaby wrote:
> On 06/03/2015, 08:35 AM, gre...@linuxfoundation.org wrote:
> > From 74856fbf441929918c49ff262ace9835048e4e6a Mon Sep 17 00:00:00 2001
> > From: Mark Hounschell
> > Date: Wed, 13 May 2015 10:49:09 +0200
> > Subject: sd: Disable support for 256
This makes lockdep very unhappy, rightly so. If you execute
one end_io function inside another you basŃ–cally nest every possible
lock taken in the I/O completion path. Also adding more work
to the hardirq path generally isn't a smart idea. Can you explain
what issues you were seeing and how much
This change fixes a compilation warning that happens if SCSI_UFS_QCOM
is compiled as a module.
Also this patch fixes an error happens when insmod the module:
"ufs_qcom: module license 'unspecified' taints kernel."
Signed-off-by: Yaniv Gardi
---
drivers/scsi/ufs/ufs-qcom.c | 7 ++-
1 file ch
It does so by adding the following changes:
1. Introducing SCSI_UFS_QCOM as a platform device. Its probe
function registers a set of vops to its driver_data.
2. Adding an optional device tree sub-node, under SCSI_UFSHCD_PLATFORM.
Now, the probe function of SCSI_UFSHCD_PLATFORM invokes the pro
This change is required in order to be able to build the component
as a module.
Signed-off-by: Yaniv Gardi
---
drivers/scsi/ufs/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/scsi/ufs/Kconfig b/drivers/scsi/ufs/Kconfig
index e945383..5f45307 100644
--- a/dri
Export the following functions in order to avoid build errors
when the component PHY_QCOM_UFS is compiled as a module:
ERROR: "ufs_qcom_phy_disable_ref_clk" [drivers/scsi/ufs/ufs-qcom.ko] undefined!
ERROR: "ufs_qcom_phy_enable_ref_clk" [drivers/scsi/ufs/ufs-qcom.ko] undefined!
ERROR: "ufs_qcom_phy
V2:
In this Version, comments from reviewers were addressed
and also, added another change: PATCH v2 4/4
In this change we glue the variant attributes (vops, etc)
at the time of the platform probing, so they can be used
by the driver when it doing its initialization phase.
V1:
The following combin
Debian packaged 4.0.4 hangs on qla2xxx init so I decided to try latest
git (4.1.0-rc6-00040-gc46a024). Got the following error:
[ 71.232300] ERROR(1): Cheetah error trap taken afsr[00100800]
afar[07fd00100040] TL1(0)
[ 71.350495] ERROR(1): TPC[6f4a4c] TNPC[6f4a50] O7[6f4a40] TSTA
On Mon, 10 Nov 2014, Christoph Hellwig wrote:
> On Mon, Nov 03, 2014 at 03:09:47PM -0500, Chad Dupuis wrote:
> > We should revert that change. What were some of the other failures you were
> > seeing?
>
> Can you please send me the revert ASAP?
Since QLogic is still silent on this one, I will se
Fix compilation errors on forgotten #include and warnings when
CONFIG_PCI is not set.
Reported-by: Jim Davis
Signed-off-by: Johannes Thumshirn
---
drivers/scsi/advansys.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/scsi/advansys.c b/drivers/scsi/advansys.c
i
31 matches
Mail list logo
