From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Scott Wood <scottwood@freescale.com>
Cc: Kumar Gala <galak@gate.crashing.org>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: fs_enet build breakage
Date: Tue, 19 May 2009 07:50:44 +1000 [thread overview]
Message-ID: <1242683444.16901.1.camel@pasglop> (raw)
In-Reply-To: <20090518172016.GB18620@b07421-ec1.am.freescale.net>
On Mon, 2009-05-18 at 12:20 -0500, Scott Wood wrote:
> > I'm pretty sure the driver changes to address this are in dave's
> net-
> > next tree.
>
> Won't this break git bisect?
>
> Not to mention anyone trying to use your tree now...
Right, though if you have the commit ID in DaveM tree, I can work with
him to sort out that driver, for example by having the same commit in
my tree.
Ben.
next prev parent reply other threads:[~2009-05-18 21:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-18 7:01 fs_enet build breakage Benjamin Herrenschmidt
2009-05-18 13:23 ` Kumar Gala
2009-05-18 17:20 ` Scott Wood
2009-05-18 21:50 ` Benjamin Herrenschmidt [this message]
2009-05-19 6:59 ` Kumar Gala
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=1242683444.16901.1.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=galak@gate.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.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 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).