All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: linuxppc-dev@ozlabs.org
Cc: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>,
	Milton Miller <miltonm@bga.com>
Subject: Re: [patch 00/18] PS3 patches for 2.6.23
Date: Tue, 12 Jun 2007 21:25:19 +0200	[thread overview]
Message-ID: <200706122125.19398.arnd@arndb.de> (raw)
In-Reply-To: <466EE45A.4050104@am.sony.com>

On Tuesday 12 June 2007, Geoff Levand wrote:
>=20
> > The dependent series is currently split per file. =A0 While this makes =
it=20
> > easier to see what a given area looks like after all the patches, it=20
> > means that the kernel compile will break during the series. =A0Breaking=
=20
> > git bisect is frowned upon, so it will need to be re-split for merge. =
=A0
> > (Or disable the ps3 system bus during the merge of the series).
>=20
>=20
> Yes, I realize the state of the patches. =A0I will try to rework them for
> the next round. =A0As the existing PS3 support is incomplete, I don't
> think there will be many doing a git-bisect with PS3 support enabled.

I think it's ok to split the patches like this for review purposes.

=46or the upstream merge, it's probably best if Geoff commits all
patches with cross-dependencies as a single git checkin, and asks
Paul (or me) to pull from there. That will take care of the git-bisect
problem, and give a nicer changelog at the same time.

Of course, patches that only have directed dependencies should go
in as separate changesets whereever that makes sense.

	Arnd <><

      reply	other threads:[~2007-06-12 19:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-06  2:59 [patch 00/18] PS3 patches for 2.6.23 Geoff Levand
2007-06-11  7:08 ` Milton Miller
2007-06-12  5:03   ` Benjamin Herrenschmidt
2007-06-12 18:22   ` Geoff Levand
2007-06-12 19:25     ` Arnd Bergmann [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=200706122125.19398.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=Geert.Uytterhoeven@sonycom.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=miltonm@bga.com \
    /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.