On Tue, 13 Mar 2007, Christoph Hellwig wrote:
On Wed, Mar 14, 2007 at 07:21:41AM +1100, Kandan Venkataraman wrote:
All comments have been taken care of.
Description:
A file_operations structure variable called loop_fops is initialised with
the default block device file operations
On Tue, 13 Mar 2007, Christoph Hellwig wrote:
On Wed, Mar 14, 2007 at 07:21:41AM +1100, Kandan Venkataraman wrote:
All comments have been taken care of.
Description:
A file_operations structure variable called loop_fops is initialised with
the default block device file operations
On Wed, Mar 14, 2007 at 07:21:41AM +1100, Kandan Venkataraman wrote:
> All comments have been taken care of.
>
> Description:
>
> A file_operations structure variable called loop_fops is initialised with
> the default block device file operations (def_blk_fops).
> The mmap operation is
All comments have been taken care of.
Description:
A file_operations structure variable called loop_fops is initialised with
the default block device file operations (def_blk_fops).
The mmap operation is overriden with a new function called loop_file_mmap.
A vm_operations structure variable
All comments have been taken care of.
Description:
A file_operations structure variable called loop_fops is initialised with
the default block device file operations (def_blk_fops).
The mmap operation is overriden with a new function called loop_file_mmap.
A vm_operations structure variable
On Wed, Mar 14, 2007 at 07:21:41AM +1100, Kandan Venkataraman wrote:
All comments have been taken care of.
Description:
A file_operations structure variable called loop_fops is initialised with
the default block device file operations (def_blk_fops).
The mmap operation is overriden with
All comments have been taken care of.
Description:
A file_operations structure variable called loop_fops is initialised with
the default block device file operations (def_blk_fops).
The mmap operation is overriden with a new function called loop_file_mmap.
A vm_operations structure
All comments have been taken care of.
Description:
A file_operations structure variable called loop_fops is initialised with
the default block device file operations (def_blk_fops).
The mmap operation is overriden with a new function called loop_file_mmap.
A vm_operations structure
There were a couple more white spaces, instead of tabs, hopefully this is
the last of them:-)
Signed-off-by: Kandan Venkataraman [EMAIL PROTECTED]
diff -uprN linux-2.6.19.2/drivers/block/loop.c
linux-2.6.19.2-new/drivers/block/loop.c
--- linux-2.6.19.2/drivers/block/loop.c 2007-03-03
The patch file seems to start in the same line as the sign off
So I will introduce a new line at the end of my mail, hopefully that will
fix that problem.
Signed-off-by: Kandan Venkataraman [EMAIL PROTECTED]
diff -uprN linux-2.6.19.2/drivers/block/loop.c
I have included the patch as a text file. This is the only way I could get
the patch to work from an email.
Thank you for your patience
Signed-off-by: Kandan Venkataraman [EMAIL PROTECTED]diff -uprN linux-2.6.19.2/drivers/block/loop.c
linux-2.6.19.2-new/drivers/block/loop.c
---
On Fri, 2 Mar 2007 22:13:46 +1100 (EST) Kandan Venkataraman wrote:
> I am resending the message. The first few lines in the diff of the
> original message seemed to have an extra space added by the time it got to
> the mailing list. Hopefully this does not happen the second time around.
>
>
I am resending the message. The first few lines in the diff of the
original message seemed to have an extra space added by the time it got to
the mailing list. Hopefully this does not happen the second time around.
Also, I missed out on putting a tab space on one line.
I have incorporated all
I have incorporated all the changes you mentioned, except for one. Thank you very much for taking the time to
review the code. I still retreive def_blk_fops as I did before, but I have put this in a separate function for now.
I have included a test program. Before you run the test program,
I have incorporated all the changes you mentioned, except for one. Thank you very much for taking the time to
review the code. I still retreive def_blk_fops as I did before, but I have put this in a separate function for now.
I have included a test program. Before you run the test program,
I am resending the message. The first few lines in the diff of the
original message seemed to have an extra space added by the time it got to
the mailing list. Hopefully this does not happen the second time around.
Also, I missed out on putting a tab space on one line.
I have incorporated all
On Fri, 2 Mar 2007 22:13:46 +1100 (EST) Kandan Venkataraman wrote:
I am resending the message. The first few lines in the diff of the
original message seemed to have an extra space added by the time it got to
the mailing list. Hopefully this does not happen the second time around.
Also, I
I have included the patch as a text file. This is the only way I could get
the patch to work from an email.
Thank you for your patience
Signed-off-by: Kandan Venkataraman [EMAIL PROTECTED]diff -uprN linux-2.6.19.2/drivers/block/loop.c
linux-2.6.19.2-new/drivers/block/loop.c
---
The patch file seems to start in the same line as the sign off
So I will introduce a new line at the end of my mail, hopefully that will
fix that problem.
Signed-off-by: Kandan Venkataraman [EMAIL PROTECTED]
diff -uprN linux-2.6.19.2/drivers/block/loop.c
There were a couple more white spaces, instead of tabs, hopefully this is
the last of them:-)
Signed-off-by: Kandan Venkataraman [EMAIL PROTECTED]
diff -uprN linux-2.6.19.2/drivers/block/loop.c
linux-2.6.19.2-new/drivers/block/loop.c
--- linux-2.6.19.2/drivers/block/loop.c 2007-03-03
On Thu, 1 Mar 2007 16:25:16 +1100 Kandan Venkataraman wrote:
Sorry, I missed seeing your reposted patch when I replied to the
earlier patch.
> The patch is for tracking writes made to a loop device made through mmap.
How did you test this? (what program(s))
> Two new ioctls have been added.
On Thu, 1 Mar 2007 02:40:41 +0100 Kandan Venkataraman wrote:
> The patch is for tracking writes made to a loop device made through
> mmap.
>
> A file_operations structure variable called loop_fops is initialised
> with the default block device file operations (def_blk_fops).
> The mmap
On Thu, 1 Mar 2007 02:40:41 +0100 Kandan Venkataraman wrote:
The patch is for tracking writes made to a loop device made through
mmap.
A file_operations structure variable called loop_fops is initialised
with the default block device file operations (def_blk_fops).
The mmap operation is
On Thu, 1 Mar 2007 16:25:16 +1100 Kandan Venkataraman wrote:
Sorry, I missed seeing your reposted patch when I replied to the
earlier patch.
The patch is for tracking writes made to a loop device made through mmap.
How did you test this? (what program(s))
Two new ioctls have been added.
The patch is for tracking writes made to a loop device made through mmap.
A file_operations structure variable called loop_fops is initialised with the
default block device file operations (def_blk_fops).
The mmap operation is overriden with a new function called loop_file_mmap.
A
The patch is for tracking writes made to a loop device made through
mmap.
A file_operations structure variable called loop_fops is initialised
with the default block device file operations (def_blk_fops).
The mmap operation is overriden with a new function called
loop_file_mmap.
A
The patch is for tracking writes made to a loop device made through
mmap.
A file_operations structure variable called loop_fops is initialised
with the default block device file operations (def_blk_fops).
The mmap operation is overriden with a new function called
loop_file_mmap.
A
The patch is for tracking writes made to a loop device made through mmap.
A file_operations structure variable called loop_fops is initialised with the
default block device file operations (def_blk_fops).
The mmap operation is overriden with a new function called loop_file_mmap.
A
28 matches
Mail list logo
