From: Steven Whitehouse <swhiteho@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Linus Torvalds <torvalds@osdl.org>,
Jan Engelhardt <jengelh@linux01.gwdg.de>,
linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: GFS2 & DLM merge request
Date: Fri, 22 Sep 2006 17:02:24 +0100 [thread overview]
Message-ID: <1158940944.11901.417.camel@quoit.chygwyn.com> (raw)
In-Reply-To: <20060922143627.GA24953@infradead.org>
Hi,
On Fri, 2006-09-22 at 15:36 +0100, Christoph Hellwig wrote:
> On Fri, Sep 22, 2006 at 03:37:54PM +0100, Steven Whitehouse wrote:
> > Hi,
> >
> > Linus, I believe that all the outstanding issues raised by Christoph,
> > Jan and others relating to GFS2 and DLM are now settled. Please
> > therefore consider pulling from:
>
> Clear NACK from me. The mails I replied to where only the mails Jan started
> nitpicking and I looked a little deeper at what he already quoted, maybe
> 5% of the codebase. Given the horrors I found there I'm pretty sure there
> will be quite a few more. And given the amount of junk Andrew plans to push
> to Linus for 2.6.19 I'll be pretty busy to look at that, aswell as looking
> at things I promised David for month now, so I'm a little busy.
>
Well I hope that we don't have too many more "horrors" left in the code.
It has after all been out for review many times in the last year and I
hope we've not done too bad a job of incorporating all the suggested
changes so far.
When I spoke to you at OLS you did promise me that you'd look at the
code in more detail and that was more than a month ago now. I know there
is a lot else to be reviewed as well as GFS2 and we need to wait our
place in the queue as it were, but it would be helpful to know where
that place is, so we can then try our best to work with the process.
> > include/linux/fs.h | 3
> > include/linux/iflags.h | 102
> > include/linux/kernel.h | 1
> > mm/filemap.c | 3
> > mm/readahead.c | 1
>
> And while we're at it, please don't push core change as part of a subsystem
> tree ever. They should go into clearly marked and separately patches via
> -mm.
Ok, I'm quite happy to do that. They are pretty minor changes, but the
usual argument is that such changes are not acceptable until there is
something in the kernel that makes use of them, and they have to happen
one way around or the other,
Steve.
next prev parent reply other threads:[~2006-09-22 15:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-22 14:37 Steven Whitehouse
2006-09-22 14:36 ` Christoph Hellwig
2006-09-22 16:02 ` Steven Whitehouse [this message]
2006-09-22 16:11 ` Andrew Morton
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=1158940944.11901.417.camel@quoit.chygwyn.com \
--to=swhiteho@redhat.com \
--cc=akpm@osdl.org \
--cc=hch@infradead.org \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®