[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20130831.225057.1874268263797742541.davem@davemloft.net>
Date: Sat, 31 Aug 2013 22:50:57 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: bjorn@...k.no
Cc: netdev@...r.kernel.org, kaber@...sh.net, jiri@...nulli.us,
linville@...driver.com, linux-wireless@...r.kernel.org, j@...fi,
libertas-dev@...ts.infradead.org, gregkh@...uxfoundation.org,
devel@...verdev.osuosl.org, forest@...ttletooquiet.net,
stephen@...workplumber.org, dan.carpenter@...cle.com
Subject: Re: [PATCH v2 net-next 0/9] set addr_assign_type when inheriting a
dev_addr
From: Bjørn Mork <bjorn@...k.no>
Date: Fri, 30 Aug 2013 18:08:43 +0200
> Copying the dev_addr from a parent device is an operation
> common to a number of drivers. The addr_assign_type should
> be updated accordingly, either by reusing the value from
> the source device or explicitly indicating that the address
> is stolen by setting addr_assign_type to NET_ADDR_STOLEN.
>
> This patch set adds a helper copying both the dev_addr and
> the addr_assign_type, and use this helper in drivers which
> don't currently set the addr_assign_type. Using NET_ADDR_STOLEN
> might be more appropriate in some of these cases. Please
> let me know, and I'll update the patch accordingly.
>
> Changes in v2:
> - assuming addr_len == ETH_ALEN to allow optimized memcpy
> - dropped the vt6656 patch due to addr_len being unset in that driver
Looks good, series applied, thanks.
--
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
Powered by blists - more mailing lists