From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Andrew Morton <akpm@linux-foundation•org>
Cc: linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>,
Christoph Hellwig <hch@lst•de>, Jens Axboe <axboe@kernel•dk>,
Al Viro <viro@zeniv•linux.org.uk>
Subject: Re: linux-next: Tree for July 7
Date: Thu, 15 Jul 2010 09:45:13 +1000 [thread overview]
Message-ID: <20100715094513.8941fa25.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20100714152042.5b83f03b.akpm@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 554 bytes --]
Hi Andrew, Al,
On Wed, 14 Jul 2010 15:20:42 -0700 Andrew Morton <akpm@linux-foundation•org> wrote:
>
> Bug is still there. Reverting ""Make ->drop_inode() just return
> whether inode needs to be dropped" makes it go away.
>
> Al, please don't just dump crap in linux-next and then ignore bug reports.
> People are trying to get work done here.
I will revert that commit in linux-next today if it is still there (and
not fixed).
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2010-07-14 23:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-07 6:55 linux-next: Tree for July 7 Stephen Rothwell
2010-07-07 23:20 ` Andrew Morton
2010-07-07 23:41 ` [PATCH -next] IR: jvc-decoder needs BITREVERSE Randy Dunlap
2010-07-08 0:21 ` linux-next: Tree for July 7 Andrew Morton
2010-07-14 22:20 ` Andrew Morton
2010-07-14 23:45 ` Stephen Rothwell [this message]
2010-07-15 0:27 ` Andrew Morton
2010-07-15 0:46 ` Dave Chinner
2010-07-15 0:53 ` Andrew Morton
2010-07-15 2:12 ` Dave Chinner
2010-07-15 7:18 ` Dave Chinner
-- strict thread matches above, loose matches on Subject: below --
2011-07-07 7:25 Stephen Rothwell
2009-07-07 6:34 Stephen Rothwell
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=20100715094513.8941fa25.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=akpm@linux-foundation$(echo .)org \
--cc=axboe@kernel$(echo .)dk \
--cc=hch@lst$(echo .)de \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=viro@zeniv$(echo .)linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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