[PATCH 3/4 ] SCSI: Support Type C RAID controller
1. To support Type C RAID controller, ACB_ADAPTER_TYPE_C, i.e. PCI device ID: 0x1880. Signed-off-by: Nick Cheng< nick.cheng(a)areca.com.tw > --- ... 4 May 2010 00:15
PATCH 2/4 ] SCSI: Support 1024 scatter-gather list entries and improve AP while FW trapped and behaviors of EHs
1. To support 4M/1024 scatter-gather list entry, reorganize struct ARCMSR_CDB and struct CommandControlBlock 2. To modify arcmsr_probe 3. In order to help fix F/W issue, add the driver mode for type B card 4. To improve AP's behavior while F/W resets 5. To unify struct MessageUnit_B's members' naming in all OS dri... 4 May 2010 00:15
SCSI: Support HW reset for EH and polling scheme for scsi device
1. To support instantaneous report for SCSI device existing by periodic polling 2. In arcmsr_iop_xfer(), inform AP of F/W's deadlock state to prevent endless waiting 3. To block the coming SCSI command while the driver is handling bus reset 4. To support HW reset in bus reset error handler Signed-off-by: Nick Che... 4 May 2010 00:15
(none)
unsubscribe linux-kernel -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ ... 4 May 2010 00:15
(none)
unsubscribe linux-kernel -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ ... 4 May 2010 00:15
linux-next: manual merge of the crypto tree with the arm tree
Hi Herbert, Today's linux-next merge of the crypto tree got a conflict in arch/arm/mach-omap2/devices.c between commit 883413341e479d4e9f9c69def4884b4c6e1cef4e ("ARM: 6046/1: ARM: OMAP: register PMU IRQs during board initialisation") from the arm tree and commit ee5500c45c4860a84bba502c6d9ef5af6395dad6 ("crypto:... 4 May 2010 17:57
Staging: adis16255: Fix compile error
The main work of this driver is providing sys node for users to access data. Which directory will this driver be placed after moving from staging? It's better to rewrite it based on IIO. Otherwise, the architecture for this kind of driver will be difficult to be consistent. -barry On Mon, May 3, 2010 at 1:05 AM... 4 May 2010 11:12
[BUG] perf_events: PERF_FORMAT_GROUP not working correctly when monitoring another task
In the last couple of days, I've run across what appears to be a kernel bug in 2.6.33.3 (haven't tested later kernels yet) having to do with using the PERF_FORMAT_GROUP feature in combination with enable_on_exec and reading counts from a remote task. What happens is that when we go to read the entire group up, only ... 3 May 2010 23:08
linux-next: manual merge of the msm tree with the arm tree
Hi Daniel, Today's linux-next merge of the msm tree got a conflict in arch/arm/mach-msm/Kconfig between commit 4b53eb4f5d78416456bb969ce30e3bed2731d744 ("arm: msm: allow ARCH_MSM to have v7 cpus") from the arm tree and commit e17047ea51cc2eac3e920e5a669f99efd44f446f ("arm: msm: smd: use either package v3 or v4 ... 4 May 2010 17:57
ext4: Don't send extra barrier during fsync if there are no dirty pages.
On Thu, 2010-04-29 at 16:51 -0700, Darrick J. Wong wrote: Hmm. A while ago I was complaining that an evil program that calls fsync() in a loop will send a continuous stream of write barriers to the hard disk. Ted theorized that it might be possible to set a flag in ext4_writepage and clear it in ext4_sync... 4 May 2010 16:49