From: Andrew Morton <akpm@linux-foundation.org>
To: David Miller <davem@davemloft.net>
Cc: sfr@canb.auug.org.au, netdev@vger.kernel.org, paulus@samba.org,
jeff@garzik.org, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 2/2] Rename get_property to of_get_property: drivers/net
Date: Sun, 29 Apr 2007 00:43:48 -0700 [thread overview]
Message-ID: <20070429004348.ea30f3fc.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070428.204754.62343452.davem@davemloft.net>
On Sat, 28 Apr 2007 20:47:54 -0700 (PDT) David Miller <davem@davemloft.net> wrote:
> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Sun, 29 Apr 2007 11:44:46 +1000
>
> > So can I take this as a future OK for architecture specific network
> > drivers changes to go through the architecture trees (cc'd to you)?
>
> It's been my experience that if I'm just working through some
> platform or bus specific API changes, people like Jeff tend to
> not mind if it goes via ARCH trees and the like.
This all started with me having a dummyspit over yet another huge reject
because of intersections between subsystem trees.
Normally we get away with it but when there's so much material pending,
things deteriorate.
next prev parent reply other threads:[~2007-04-29 7:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 4:51 [PATCH 1/2] get_property returns const Stephen Rothwell
2007-04-27 4:55 ` [PATCH 2/2] Rename get_property to of_get_property: drivers/net Stephen Rothwell
2007-04-28 15:30 ` Jeff Garzik
2007-04-29 1:44 ` Stephen Rothwell
2007-04-29 3:47 ` David Miller
2007-04-29 7:43 ` Andrew Morton [this message]
2007-05-02 14:15 ` Kumar Gala
2007-05-02 14:17 ` Jeff Garzik
2007-05-02 15:53 ` Kumar Gala
2007-05-02 16:00 ` Jeff Garzik
2007-05-02 16:14 ` Kumar Gala
2007-05-04 14:40 ` 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=20070429004348.ea30f3fc.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=jeff@garzik.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=paulus@samba.org \
--cc=sfr@canb.auug.org.au \
/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).