mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Steven Whitehouse <swhiteho@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	Linus Torvalds <torvalds@osdl.org>,
	Jan Engelhardt <jengelh@linux01.gwdg.de>,
	linux-kernel@vger.kernel.org
Subject: Re: GFS2 & DLM merge request
Date: Fri, 22 Sep 2006 09:11:34 -0700	[thread overview]
Message-ID: <20060922091134.8602588b.akpm@osdl.org> (raw)
In-Reply-To: <1158940944.11901.417.camel@quoit.chygwyn.com>

On Fri, 22 Sep 2006 17:02:24 +0100
Steven Whitehouse <swhiteho@redhat.com> wrote:

> > >  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,

There's no 100% comfortable solution to this.  Steven presumably needs
those changes present in his tree so he can test.

What I usually suggest is that the developer get the core changes reviewed
on-list at an early stage and then explicitly flag their presence in the
covering description when sending the please-pull email.

      reply	other threads:[~2006-09-22 16:11 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
2006-09-22 16:11     ` Andrew Morton [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=20060922091134.8602588b.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=hch@infradead.org \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=swhiteho@redhat.com \
    --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®