From: Andrew Morton <akpm@linux-foundation.org>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: Jan Harkes <jaharkes@cs.cmu.edu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
stable@kernel.org
Subject: Re: wrong order of arguments of ->readdir()
Date: Mon, 16 Jul 2007 14:01:34 -0700 [thread overview]
Message-ID: <20070716140134.389f1669.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070716204930.GK21668@ftp.linux.org.uk>
On Mon, 16 Jul 2007 21:49:30 +0100
Al Viro <viro@ftp.linux.org.uk> wrote:
> On Mon, Jul 16, 2007 at 01:44:24PM -0700, Andrew Morton wrote:
> > Today is not being a good day.
> >
> > This bug was already fixed. The following mistakes were made:
> >
> > a) Jan's patch was misleadingly titled "coda: avoid lockdep warning in
> > coda_readdir"
> >
> > b) Jan's patch had no changelog
> >
> > c) Jen's patch was not cc'ed to any mailing list
>
> ... said patch (presumably being an obvious fix of obvious roothole)
> had not been sent to mainline immediately.
Please send a copy to stable@kernel.org
> > d) Al's patch was not sent to the maintainer. Nor to me. Nor was it
> > staged in any tree which I can get at so that I could inform people of
> > the upcoming conflict/duplication/etc.
>
> Coda is still maintained? That's certainly news to me - I'm not being
> sarcastic, but my impression had been that coda got abandoned several
> years ago.
Jan does stuff occasionally.
next prev parent reply other threads:[~2007-07-16 21:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200707152359.l6FNx3oN023117@hera.kernel.org>
2007-07-16 20:44 ` wrong order of arguments of ->readdir() Andrew Morton
2007-07-16 20:49 ` Al Viro
2007-07-16 21:01 ` Andrew Morton [this message]
2007-07-16 23:04 ` Jan Harkes
2007-07-16 21:47 ` Jan Harkes
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=20070716140134.389f1669.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jaharkes@cs.cmu.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.