From: Andrew Morton <akpm@osdl.org>
To: "Jan Beulich" <JBeulich@novell.com>
Cc: hch@infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rmmod notifier chain
Date: Thu, 8 Sep 2005 18:46:59 -0700 [thread overview]
Message-ID: <20050908184659.6aa5a136.akpm@osdl.org> (raw)
In-Reply-To: <432073610200007800024489@emea1-mh.id2.novell.com>
"Jan Beulich" <JBeulich@novell.com> wrote:
>
> >>> Christoph Hellwig <hch@infradead.org> 08.09.05 17:16:24 >>>
> >On Thu, Sep 08, 2005 at 05:03:58PM +0200, Jan Beulich wrote:
> >> (Note: Patch also attached because the inline version is certain to
> get
> >> line wrapped.)
Suggest you get a new email setup.
> ...
> That's funny - on one hand I'm asked to not submit huge patches (not by
> you, but by others), but on the other hand not having the consuming code
> in the same patch as the providing one is now deemed to be a problem.
Nope.
Each patch should do a single logical thing. That doesn't mean that we
want to trickle patches in across a period of months. It means that a
bunch of spearate (and separately reviewed) patches can all go in at the
same time.
So the split-it-up request is for reviewing (and debugging) convenience
only.
next prev parent reply other threads:[~2005-09-09 1:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-08 15:03 [PATCH] rmmod notifier chain Jan Beulich
2005-09-08 15:11 ` Patrick McHardy
2005-09-08 15:16 ` Jan Beulich
2005-09-08 15:16 ` Christoph Hellwig
2005-09-08 15:20 ` viro
2005-09-08 15:22 ` Jan Beulich
2005-09-09 1:46 ` Andrew Morton [this message]
2005-09-09 12:44 ` Jan Beulich
2005-09-09 13:44 ` Jesper Juhl
2005-09-09 15:37 ` Paul Jackson
2005-09-09 18:27 ` Andrew Morton
2005-09-12 6:49 ` Jan Beulich
2005-09-12 7:10 ` Andrew Morton
2005-09-08 15:33 ` Tom Rini
2005-09-08 15:48 ` Jan Beulich
2005-09-09 9:42 ` [PATCH] rmmod notifier chain (attempt 2) Jan Beulich
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=20050908184659.6aa5a136.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=JBeulich@novell.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.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 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.