linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: sfr@canb.auug.org.au, netdev@vger.kernel.org,
	linuxppc-dev@ozlabs.org, paulus@samba.org,
	akpm@linux-foundation.org, David Miller <davem@davemloft.net>
Subject: Re: [PATCH 2/2] Rename get_property to of_get_property: drivers/net
Date: Wed, 02 May 2007 12:00:23 -0400	[thread overview]
Message-ID: <4638B597.20604@garzik.org> (raw)
In-Reply-To: <9B877BC8-C064-4CD1-9325-5C3EA925346E@kernel.crashing.org>

Kumar Gala wrote:
> 
> On May 2, 2007, at 9:17 AM, Jeff Garzik wrote:
> 
>> Kumar Gala wrote:
>>> On Apr 28, 2007, at 10:47 PM, David Miller 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.
>>> Is this acceptable?   Just want to make sure before I ask Paul to 
>>> pull some changes that touches the following drivers:
>>> drivers/net/fs_enet/mac-scc.c           |    2 +-
>>> drivers/net/ucc_geth.c                  |   30 ++++----
>>> drivers/serial/cpm_uart/cpm_uart_cpm1.c |    4 +-
>>> drivers/serial/cpm_uart/cpm_uart_cpm2.c |    4 +-
>>
>> I don't see a patch, just a diffstat.
> 
> I haven't sent a patch, just asking the question if I need to break it 
> up or not.

Without seeing the patch, I have no idea...

	Jeff

  reply	other threads:[~2007-05-02 16:00 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
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 [this message]
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=4638B597.20604@garzik.org \
    --to=jeff@garzik.org \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=galak@kernel.crashing.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).