This is a note to let you know that I've just added the patch titled
staging: comedi: jr3_pci: fix iomem dereference
to the 3.6-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
staging-comedi-jr3_pci-fix-iomem-dereference.patch
and it can be found in the queue-3.6 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <[email protected]> know about it.
>From e1878957b4676a17cf398f7f5723b365e9a2ca48 Mon Sep 17 00:00:00 2001
From: Ian Abbott <[email protected]>
Date: Thu, 27 Sep 2012 17:45:27 +0100
Subject: staging: comedi: jr3_pci: fix iomem dereference
From: Ian Abbott <[email protected]>
commit e1878957b4676a17cf398f7f5723b365e9a2ca48 upstream.
Correct a direct dereference of I/O memory to use an appropriate I/O
memory access function. Note that the pointer being dereferenced is not
currently tagged with `__iomem` but I plan to correct that for 3.7.
Signed-off-by: Ian Abbott <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
---
drivers/staging/comedi/drivers/jr3_pci.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/drivers/staging/comedi/drivers/jr3_pci.c
+++ b/drivers/staging/comedi/drivers/jr3_pci.c
@@ -884,7 +884,7 @@ static int jr3_pci_attach(struct comedi_
}
/* Reset DSP card */
- devpriv->iobase->channel[0].reset = 0;
+ writel(0, &devpriv->iobase->channel[0].reset);
result = comedi_load_firmware(dev, "jr3pci.idm", jr3_download_firmware);
dev_dbg(dev->class_dev, "Firmare load %d\n", result);
Patches currently in stable-queue which might be from [email protected] are
queue-3.6/staging-comedi-s626-don-t-dereference-insn-data.patch
queue-3.6/staging-comedi-jr3_pci-fix-iomem-dereference.patch
queue-3.6/staging-comedi-fix-memory-leak-for-saved-channel-list.patch
queue-3.6/staging-comedi-don-t-dereference-user-memory-for-insn_inttrig.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
