From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Erez Zadok <ezk@cs.sunysb.edu>
Cc: hch@infradead.org, viro@ftp.linux.org.uk,
akpm@linux-foundation.org, krh@redhat.com, airlied@linux.ie,
rolandd@cisco.com, James.Bottomley@HansenPartnership.com,
hjk@linutronix.de, vandrove@vc.cvut.cz, mfasheh@suse.com,
hugh@veritas.com, perex@perex.cz, avi@qumranet.com,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] VM: vm_ops->fault takes explicit struct file
Date: Sat, 26 Apr 2008 09:32:35 +0200 [thread overview]
Message-ID: <4812DA93.6020707@s5r6.in-berlin.de> (raw)
In-Reply-To: <200804252320.m3PNK0Bw014449@agora.fsl.cs.sunysb.edu>
Erez Zadok wrote:
> For convenience of review and bisectability, I present the changes as one
> patch here. If desired, I can split it for each subsystem.
Hmm, a split patch won't be useful; it won't compile.
Besides, this change doesn't look too intrusive to me. For example,
changes like this...
[...]
> --- a/drivers/ieee1394/dma.c
> +++ b/drivers/ieee1394/dma.c
> @@ -232,7 +232,7 @@ void dma_region_sync_for_device(struct dma_region *dma, unsigned long offset,
> #ifdef CONFIG_MMU
>
> static int dma_region_pagefault(struct vm_area_struct *vma,
> - struct vm_fault *vmf)
> + struct vm_fault *vmf, struct file *file)
> {
> struct dma_region *dma = (struct dma_region *)vma->vm_private_data;
>
...are unlikely to cause objections or merge rejects. ACK from me for
the ieee1394 part, FWIW.
PS: It's an obscure and unimportant fact, but you are not required to
Cc krh on changes in drivers/ieee1394; he is interested in
drivers/firewire which is separate code.
--
Stefan Richter
-=====-==--- -=-- ==-=-
http://arcgraph.de/sr/
prev parent reply other threads:[~2008-04-26 7:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-25 23:20 Erez Zadok
2008-04-26 7:32 ` Stefan Richter [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4812DA93.6020707@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=airlied@linux.ie \
--cc=akpm@linux-foundation.org \
--cc=avi@qumranet.com \
--cc=ezk@cs.sunysb.edu \
--cc=hch@infradead.org \
--cc=hjk@linutronix.de \
--cc=hugh@veritas.com \
--cc=krh@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mfasheh@suse.com \
--cc=perex@perex.cz \
--cc=rolandd@cisco.com \
--cc=vandrove@vc.cvut.cz \
--cc=viro@ftp.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®