linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Christoph Lameter <clameter@sgi.com>
Cc: mingo@elte.hu, apw@shadowen.org, sam@ravnborg.org,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [patch 02/19] x86: Use kbuild.h
Date: Wed, 16 Apr 2008 12:15:50 -0700	[thread overview]
Message-ID: <20080416121550.b31f828c.akpm@linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0804161044250.12019@schroedinger.engr.sgi.com>

On Wed, 16 Apr 2008 10:44:55 -0700 (PDT)
Christoph Lameter <clameter@sgi.com> wrote:

> On Wed, 16 Apr 2008, Ingo Molnar wrote:
> 
> > 
> > * Ingo Molnar <mingo@elte.hu> wrote:
> > 
> > > * Christoph Lameter <clameter@sgi.com> wrote:
> > > 
> > > > Drop the macro definitions in asm-offsets_*.c and use kbuild.h
> > > 
> > > thanks Christoph, applied.
> > 
> > the dependency i missed was the existence of include/linux/kbuild.h ;-) 
> > Anyway:
> > 
> > Acked-by: Ingo Molnar <mingo@elte.hu>
> 
> Yes sorry this is dependent on other patches merged by Andrew. This is the 
> classic case of arch changes that depend on core changes.

Yeah, I tricked a few people that way yesterday ;)

For this series I cc'ed 30-odd people on the core patch
(add-kbuildh-that-contains-common-definitions-for-kbuild-users.patch) and
then cc'ed them individually on the dependent patch (eg,
sparc-use-kbuildh-instead-of-defining-macros-in-asm-offsetsc.patch).  So
hopefully it was somewhat obvious what was going on.

In the case of *-use-get-put_unaligned_-helpers.patch it was more obscure
because the core patch
(kernel-add-common-infrastructure-for-unaligned-access.patch) came in a lot
earlier so nobody got to see it.  That tricked 'em.

Perhaps I should put "depends on -mm's
kernel-add-common-infrastructure-for-unaligned-access.patch" in the
changelog.  Problem is that I'd never remember to take that out before
sending the patch onwards.

I guess I could add "this depends on a patch which is only in -mm" into
that email somehow.

hm.  Oh well, it doesn't happen very often.




Related:

I'm now sitting on things like:

kernel-add-common-infrastructure-for-unaligned-access.patch
...
input-use-get_unaligned_-helpers.patch


Strictly and formally, the merge process for these is

a) I send kernel-add-common-infrastructure-for-unaligned-access.patch to
Linus.

b) He merges it

c) I send input-use-get_unaligned_-helpers.patch to Dmitry

d) He merges it

e) He sends input-use-get_unaligned_-helpers.patch to Linus

f) Linus merges it.


This is a lot of fuss and there's a non-zero chance that we'll miss the
merge window.  So I like people to send along acked-by's for this sort of
thing so I can scoot them along to Linus straight away.


--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

      reply	other threads:[~2008-04-16 19:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080414221846.967753424@sgi.com>
     [not found] ` <20080414221808.269371488@sgi.com>
     [not found]   ` <20080414221846.735656759@sgi.com>
2008-04-14 22:22     ` [patch 10/19] blackfin: Use kbuild.h instead of defining macros in asm-macros.c Mike Frysinger
     [not found]   ` <20080414221848.428938934@sgi.com>
2008-04-15  8:14     ` [patch 17/19] Use kbuild.h instead of defining macros in asm-offsets.c Martin Schwidefsky
2008-04-15  9:55   ` [patch 11/19] frv: " David Howells
2008-04-15 19:09     ` Christoph Lameter
     [not found]   ` <20080414221844.876647987@sgi.com>
2008-04-16 13:01     ` [patch 02/19] x86: Use kbuild.h Ingo Molnar
2008-04-16 14:10       ` Ingo Molnar
2008-04-16 17:44         ` Christoph Lameter
2008-04-16 19:15           ` 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=20080416121550.b31f828c.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=apw@shadowen.org \
    --cc=clameter@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@elte.hu \
    --cc=sam@ravnborg.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;
as well as URLs for NNTP newsgroup(s).