netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: David Miller <davem@davemloft.net>
Cc: Steve.Glendinning@smsc.com, ian.saturley@smsc.com,
	linux-arm-kernel@lists.arm.linux.org.uk, netdev@vger.kernel.org,
	stanley.miao@windriver.com
Subject: Re: [PATCH REPOST 0/5] convert arm platforms to smsc911x
Date: Mon, 19 Jan 2009 21:31:59 +0000	[thread overview]
Message-ID: <20090119213159.GJ18301@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20090119.131517.149029812.davem@davemloft.net>

On Mon, Jan 19, 2009 at 01:15:17PM -0800, David Miller wrote:
> From: Steve.Glendinning@smsc.com
> Date: Mon, 19 Jan 2009 09:53:54 +0000
> 
> > Russell King - ARM Linux <linux@arm.linux.org.uk> wrote on 19/01/2009 
> > 09:22:57:
> > > On Mon, Jan 19, 2009 at 04:04:34PM +0800, stanley.miao wrote:
> > > > On Sun, 2009-01-18 at 21:53 -0800, David Miller wrote:
> > > > > I've applied patches 1 and 2, the smsc911x driver changes.
> > > > > 
> > > > > I can pull the platform changes into net-next-2.6 as well
> > > > > if people don't think there will enough conflicts to cause
> > > > > problems.
> > > > 
> > > > I think  the platform data had better stay in arm tree.
> > > 
> > > What would be the impact if patches 3 to 5 got merged before 1 and 2?
> > 
> > It would not break compilation, but it would probably break ethernet 
> > support
> > on those three platforms.
> 
> That's why I suggested they go where the dependency is for
> proper functionality.

Ok, as I see it, the files with the highest chance of conflicting
in this set are the defconfig files.

Therefore, may I suggest that the defconfig updates are split from 3-5
and sent via my tree, the remainder via davem's net-next-2.6 tree?

  reply	other threads:[~2009-01-19 21:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-15  9:07 [PATCH REPOST 0/5] convert arm platforms to smsc911x Steve Glendinning
2009-01-15  9:07 ` [PATCH 1/5] smsc911x: add support for platform-specific irq flags Steve Glendinning
2009-01-15  9:07   ` [PATCH 2/5] smsc911x: register isr as IRQF_SHARED Steve Glendinning
2009-01-15  9:08     ` [PATCH 3/5] arm: convert pcm037 platform to use smsc911x Steve Glendinning
2009-01-15  9:08       ` [PATCH 4/5] arm: convert realview " Steve Glendinning
2009-01-15  9:08         ` [PATCH 5/5] arm: convert omap ldp " Steve Glendinning
2009-01-15  9:23           ` stanley.miao
2009-01-19 22:35           ` Russell King - ARM Linux
2009-01-20  0:30             ` David Miller
2009-01-19  5:53 ` [PATCH REPOST 0/5] convert arm platforms to smsc911x David Miller
2009-01-19  8:04   ` stanley.miao
2009-01-19  9:22     ` Russell King - ARM Linux
2009-01-19  9:53       ` Steve.Glendinning
2009-01-19 21:15         ` David Miller
2009-01-19 21:31           ` Russell King - ARM Linux [this message]
2009-01-19 22:12             ` 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=20090119213159.GJ18301@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=Steve.Glendinning@smsc.com \
    --cc=davem@davemloft.net \
    --cc=ian.saturley@smsc.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=stanley.miao@windriver.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).