linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sendfile: allows bypassing of notifier events
Date: Wed, 21 Nov 2012 09:43:27 +1100	[thread overview]
Message-ID: <20121120224327.GJ2591@dastard> (raw)
In-Reply-To: <20121120163133.11806.15152.stgit@bob.linux.org.uk>

On Tue, Nov 20, 2012 at 04:31:34PM +0000, Alan Cox wrote:
> From: Scott Wolchok <swolchok@umich.edu>
> 
> Signed-off-by: Alan Cox <alan@linux.intel.com>
> Resolves-bug: https://bugzilla.kernel.org/show_bug.cgi?id=12812

Please add a suitable commit message describing the bug and the fix.
Pointers to bug reports are good references, but they don't replace
a properly written commit message.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

      reply	other threads:[~2012-11-20 22:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-20 16:31 [PATCH] sendfile: allows bypassing of notifier events Alan Cox
2012-11-20 22:43 ` Dave Chinner [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=20121120224327.GJ2591@dastard \
    --to=david@fromorbit.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).