linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: dhowells@redhat.com, linux-m68k@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Linux-Arch <linux-arch@vger.kernel.org>
Subject: Re: [GIT PULL] Disintegrate UAPI for m68k
Date: Fri, 05 Oct 2012 13:50:21 +0100	[thread overview]
Message-ID: <7854.1349441421@warthog.procyon.org.uk> (raw)
In-Reply-To: <CAMuHMdWYdKPgVR8hvcXN1qmm7nqCyjWV3NPHzdVHG_H8F20-3w@mail.gmail.com>

Geert Uytterhoeven <geert@linux-m68k.org> wrote:

> I assume these c6x and asm-generic changes are the ones you just asked Linus
> to pull?

Yes.

> Doesn't it make more sense to ask us (the individual arch maintainers) to
> pull our parts after Linus has pulled the generic part?

I suppose so.

> Do you want this ("our parts") to go in 3.7 or 3.8?

3.7 would be nice, but I know not everyone is willing to pull in this merge
window.  It might also make sense to wait for (a) Linus to pull those and (b)
Arnd to pass the asm-generic changes along too.

The main reason I'd like to get things moved along asap is that the
preparatory patches get things into a known state upon which these commits can
be pulled.  However, the state is going to degrade over time as people make
changes which requires more preparatory patches:-/

David

      parent reply	other threads:[~2012-10-05 12:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <17383.1349380286@warthog.procyon.org.uk>
2012-10-05  5:05 ` [GIT PULL] Disintegrate UAPI for m68k Geert Uytterhoeven
2012-10-05 12:50 ` David Howells [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=7854.1349441421@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@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 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).