From: David Miller <davem@davemloft.net>
To: timur@freescale.com
Cc: netdev@vger.kernel.org, leoli@freescale.com, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] ucc_geth: use correct UCCE macros
Date: Thu, 08 Jan 2009 11:18:33 -0800 (PST) [thread overview]
Message-ID: <20090108.111833.163761985.davem@davemloft.net> (raw)
In-Reply-To: <ed82fe3e0901071217y44900869n7af2e99d6174fd45@mail.gmail.com>
From: "Timur Tabi" <timur@freescale.com>
Date: Wed, 7 Jan 2009 14:17:04 -0600
> On Wed, Jan 7, 2009 at 2:12 PM, Timur Tabi <timur@freescale.com> wrote:
>
> > This patch will break ucc_geth.c if my other patch, "powerpc: add Ethernet
> > UPSMR definitions to QE library" isn't also applied. That patch is currently
> > in Kumar's 'next' branch, so it will make 2.6.29-rc0. Therefore, it should
> > be safe to apply this patch to 'net-next' today, with the understanding that
> > everything will be peachy once Linus pulls everyone's 2.6.29 branches.
>
> David,
>
> as I mentioned here, Kumar already has the pre-req patch in his 'next'
> branch (for 2.6.29), so if you apply this patch to your 'next',
> ucc_geth.c will break until Linus pulls from Kumar and you pull from
> Linus. I think that's OK.
I think I'll wait for Kumar's stuff to hit Linus's tree, then
apply this patch.
The patch is safely stored in my inbox and patchwork so there
is no need to fear it getting lost :-)
next prev parent reply other threads:[~2009-01-08 19:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 20:12 [PATCH] ucc_geth: use correct UCCE macros Timur Tabi
2009-01-07 20:17 ` Timur Tabi
2009-01-08 19:18 ` David Miller [this message]
2009-01-08 19:20 ` Timur Tabi
2009-01-11 8:25 ` David Miller
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=20090108.111833.163761985.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=leoli@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=timur@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).