Resending with correct linux-scsi address - please rteply to this one if
you see duplicate messages.
I am using Linux 3.4.0 with a 53c1030 and a tape library that sometimes
barfs for yet unknown reasons. When it happens, I get a BUG with
backtrace and this scsi channel is dead until I reboot.
On Tue, 2012-07-10 at 11:44 +0300, Meelis Roos wrote:
Resending with correct linux-scsi address - please rteply to this one if
you see duplicate messages.
I am using Linux 3.4.0 with a 53c1030 and a tape library that sometimes
barfs for yet unknown reasons. When it happens, I get a BUG
Hello all,
sorry for resending this twice to the lists. Initially I thought
mailing James directly was not appropriate, but I was now told that
get_maintainer.pl is actually speaking the truth and I am supposed to
do just that.
For the purposes of automatically testing udisks and gvfs
Add removable module parameter to set the removable attribute of any
subsequently created debug block device. It is a writable driver option, so
that you can switch between removable and fixed media block devices in
between the add_host calls.
This is useful for being able to test the different
I am using Linux 3.4.0 with a 53c1030 and a tape library that sometimes
barfs for yet unknown reasons. When it happens, I get a BUG with
backtrace and this scsi channel is dead until I reboot. Seems to be
something with either generic scsi error handling or with mpt scsi.
I think it
On Tue, 2012-07-10 at 14:54 +0300, Meelis Roos wrote:
I am using Linux 3.4.0 with a 53c1030 and a tape library that sometimes
barfs for yet unknown reasons. When it happens, I get a BUG with
backtrace and this scsi channel is dead until I reboot. Seems to be
something with either
Hi James,
These patches have been posted to lkml and have been in linux-next
for sometime through Andrew Morton's tree.
I think they should be taken through your tree for next merge window.
Can you please merge these ?
Thanks and regards,
Venkat.
Namjae Jeon (1):
drivers/scsi/ufs: fix
Otherwise it counter intuitively returns 0 if device is present.
Signed-off-by: Venkatraman S svenk...@ti.com
Reviewed-by: Namjae Jeon linkinj...@gmail.com
Acked-by: Santosh Y santos...@gmail.com
Cc: James Bottomley james.bottom...@hansenpartnership.com
Signed-off-by: Andrew Morton
Use macro module_pci_driver and get rid of boilerplate code. No
functional changes.
Signed-off-by: Venkatraman S svenk...@ti.com
Acked-by: Santosh Y santos...@gmail.com
Cc: James E.J. Bottomley jbottom...@parallels.com
Signed-off-by: Andrew Morton a...@linux-foundation.org
---
On Tue, 2012-07-10 at 19:39 +0530, Venkatraman S wrote:
From: Namjae Jeon linkinj...@gmail.com
Currently the UFS host driver has returned incorrect values for SUCCESS
and FAILED. Fix it to return the correct value to the upper layer.
Signed-off-by: Namjae Jeon linkinj...@gmail.com
From: Namjae Jeon linkinj...@gmail.com
Currently the UFS host driver has returned incorrect values for SUCCESS
and FAILED. Fix it to return the correct value to the upper layer.
Signed-off-by: Namjae Jeon linkinj...@gmail.com
Acked-by: Santosh Y santos...@gmail.com
Signed-off-by: Venkatraman S
This is a resubmission of 3 of 19 patches from ~1 year ago. The rest were
integrated by the other subsystem maintainers at the time. I believe the
hiccup was some confusion as to whether this would cause an issue on PPC
(http://www.spinics.net/lists/linux-scsi/msg53079.html). However, this was
The PCIE capability offset is saved during PCI bus walking. It will
remove an unnecessary search in the PCI configuration space if this
value is referenced instead of reacquiring it.
Signed-off-by: Jon Mason jdma...@kudzu.us
Cc: Ravi Anand ravi.an...@qlogic.com
Cc: Vikas Chaudhary
The PCIE capability offset is saved during PCI bus walking. It will
remove an unnecessary search in the PCI configuration space if this
value is referenced instead of reacquiring it. Also, pci_is_pcie is a
better way of determining if the device is PCIE or not (as it uses the
same saved PCIE
The PCIE capability offset is saved during PCI bus walking. It will
remove an unnecessary search in the PCI configuration space if this
value is referenced instead of reacquiring it. Also, pci_is_pcie is a
better way of determining if the device is PCIE or not (as it uses the
same saved PCIE
On 07/09/2012 09:51 PM, Robert Trace wrote:
Huh.. I just retested this and I'm seeing really random behavior.
Ok, with a refined test I've been able to reliably reproduce this and I
bisected it back to commit 85ef06d1d252f6a2e73b678591ab71caad4667bb in
Linus' tree (introduced between 3.0 and
On Mon, Jul 2, 2012 at 8:47 PM, Arnd Bergmann a...@arndb.de wrote:
On Monday 02 July 2012, Vinayak Holikatti wrote:
This patch separates PCI and core UFS host controller driver.
In the current implementation PCI specific code is with ufshcd.c.
To provide way for adding multiple bus glue
Thanks Venkat !
2012/7/11, Venkatraman S svenk...@ti.com:
From: Namjae Jeon linkinj...@gmail.com
Currently the UFS host driver has returned incorrect values for SUCCESS
and FAILED. Fix it to return the correct value to the upper layer.
Signed-off-by: Namjae Jeon linkinj...@gmail.com
On Mon, Jul 2, 2012 at 8:57 PM, Arnd Bergmann a...@arndb.de wrote:
On Monday 02 July 2012, Vinayak Holikatti wrote:
+static struct platform_driver ufshcd_pltfrm_driver = {
+ .probe = ufshcd_pltfrm_probe,
+ .remove = __devexit_p(ufshcd_pltfrm_remove),
+#ifdef CONFIG_PM
+
On Mon, Jul 2, 2012 at 8:50 PM, Arnd Bergmann a...@arndb.de wrote:
On Monday 02 July 2012, Vinayak Holikatti wrote:
+static struct amba_id ufshcd_amba_ids[] = {
+ {
+ /* Fake id for Primecell.*/
+ .id = 0x00041FF0,
+ .mask = 0x000f,
20 matches
Mail list logo
