netdev - Re: [PATCH 2/2] Rename get_property to of_get

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <3802D7AD-67EC-4FA2-B361-A388AFCB0B94@kernel.crashing.org>
Date:	Wed, 2 May 2007 09:15:36 -0500
From:	Kumar Gala <galak@...nel.crashing.org>
To:	David Miller <davem@...emloft.net>
Cc:	sfr@...b.auug.org.au, jeff@...zik.org, paulus@...ba.org,
	akpm@...ux-foundation.org, linuxppc-dev@...abs.org,
	netdev@...r.kernel.org
Subject: Re: [PATCH 2/2] Rename get_property to of_get_property: drivers/net


On Apr 28, 2007, at 10:47 PM, David Miller wrote:

> From: Stephen Rothwell <sfr@...b.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 +-

But is related to an arch API cleanup.

- k

-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html