copy of write for disk blocks

Hi, Is it feasible to add support for copy of write for disk blocks within the block layer itself ? Setting a flag in the struct bio will cause the block layer to copy the original data before over writing it. Regards. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel"

Re: [PATCH] Change request_irq() to use struct net_device *dev->name

Hi, On Fri, Jul 26, 2013 at 12:08 AM, Aaro Koskinen wrote: > Hi, > > On Thu, Jul 25, 2013 at 10:33:24PM +0400, Sergei Shtylyov wrote: >>It's also called managed device API. In fact, I've never heard it >> named devres API. If I understood it correctly it has to just calls devm_request_region

Re: [PATCH] Change request_irq() to use struct net_device *dev->name

Hi, On Thu, Jul 25, 2013 at 10:49 AM, Prashant Shah wrote: > Hi, > >> You should also remove the definition of DRV_NAME, since it is no longer >> used. The changelog should probably mention that this will change the >> interrupt name (which appears in /proc/interrup

Re: [PATCH] Change request_irq() to use struct net_device *dev->name

Hi, > You should also remove the definition of DRV_NAME, since it is no longer > used. The changelog should probably mention that this will change the > interrupt name (which appears in /proc/interrupts for example) from "wd" > to "eth%d". > I will resend the patch. Regards. -- To unsubscribe fr

[PATCH] Change request_irq() to use struct net_device *dev->name

Signed-off-by: Prashant Shah --- drivers/net/ethernet/8390/wd.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/net/ethernet/8390/wd.c b/drivers/net/ethernet/8390/wd.c index 03eb3ee..b43a63f 100644 --- a/drivers/net/ethernet/8390/wd.c +++ b/drivers/net/ethernet

Re: Bad magic number and

Hi, On Fri, Dec 28, 2012 at 10:57 AM, Manish Katiyar wrote: > > > On Thu, Dec 27, 2012 at 8:29 PM, sham pavman > wrote: >> >> I've tried that as well.. and the result is the same. >> I've little idea on how to start debugging. >> If you can provide some info it would be great. Check your mkfs a

Re: [PATCH 1/1] staging: usbip: remove an unnecessary lock in usbip_event_happened. The variable "happened" is local. So I think there is no need to lock here.

Hi, > int happened = 0; > > - spin_lock(&ud->lock); > if (ud->event != 0) > happened = 1; > - spin_unlock(&ud->lock); > > return happened; I am guessing locking was intended to protect ud->event along with happened so that (checking the value of

Re: [PATCH] fs: Introducing Lanyard Filesystem

Hi, On Sun, Aug 19, 2012 at 5:08 AM, Dan Luedtke wrote: > + > + /* allocate filesystem private data */ > + fsi = kzalloc(sizeof(*fsi), GFP_KERNEL); > + if (!fsi) > + return -ENOMEM; > + spin_lock_init(&fsi->lock); > + sb->s_fs_info = fsi; > + > +