public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Willy Tarreau <w@1wt.eu>
Cc: oliver.pntr@gmail.com, stable@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [stable] [RFC, 2.6.26.2-rc1] NFS: Ensure we call nfs_sb_deactive() after releasing the directory inode
Date: Mon, 4 Aug 2008 11:34:44 -0700	[thread overview]
Message-ID: <20080804183444.GB20191@kroah.com> (raw)
In-Reply-To: <20080802174220.GF615@1wt.eu>

On Sat, Aug 02, 2008 at 07:42:20PM +0200, Willy Tarreau wrote:
> Oliver,
> 
> most of your mails are line-wrapped at some locations :
> 
> > diff --git a/fs/nfs/unlink.c b/fs/nfs/unlink.c
> > index 3adf8b2..f089e58 100644
> > --- a/fs/nfs/unlink.c
> > +++ b/fs/nfs/unlink.c
> > @@ -95,10 +95,11 @@ static void nfs_async_unlink_done(struct rpc_task
> > *task, void *calldata)
> ^^^^^^^^
> see here.
> 
> You may have to fix your mailer (or use another one).

{sigh}

Yes, all of these patches are linewrapped.

Now, I can either go through and edit them all by hand and fix them up,
or Oliver can fix his email client to not doing this anymore, saving
everyone time in the future.

I choose the latter.

Oliver, consider all of the patches you just send out as dropped.  Can
you resend the ones that are actually bugfixes, with out being
linewrapped?

thanks,

greg k-h

  reply	other threads:[~2008-08-04 18:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-02 12:10 [RFC, 2.6.26.2-rc1] NFS: Ensure we call nfs_sb_deactive() after releasing the directory inode Oliver Pinter
2008-08-02 17:42 ` Willy Tarreau
2008-08-04 18:34   ` Greg KH [this message]
2008-08-04 18:36     ` [stable] " Greg KH
2008-08-04 19:50       ` Oliver Pinter

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=20080804183444.GB20191@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oliver.pntr@gmail.com \
    --cc=stable@kernel.org \
    --cc=w@1wt.eu \
    /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