[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJZOPZJHr0fpAaUM_X0Bwa1PtTO0ra3KLu5AFdir2ShKGFrukA@mail.gmail.com>
Date: Fri, 23 May 2014 09:38:42 +0300
From: Or Gerlitz <or.gerlitz@...il.com>
To: Veaceslav Falico <vfalico@...il.com>
Cc: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Jay Vosburgh <j.vosburgh@...il.com>,
Andy Gospodarek <andy@...yhouse.net>,
Eyal Perry <eyalpe@...lanox.com>
Subject: Re: [PATCH net-next 2/2] bonding: remove alb_set_mac_address()
On Thu, May 22, 2014 at 5:57 PM, Veaceslav Falico <vfalico@...il.com> wrote:
>
> On Thu, May 22, 2014 at 05:36:19PM +0300, Or Gerlitz wrote:
>>
>>
>> So with this patch @ hand, no more touching of the underlying device
>> dev_addr field directly -- or we still have more accesses of this
>> such, e.g in bond_alb_set_mac_address() and/or friends?
>
>
> Sorry, but no :(. I'm still working on it, and already sent several
> patchsets approaching it :).
>
> Hopefully it will be ready next week. If you need it urgently - patches welcome :)
Hey -- no rush, I just asked as heads up since we have some proposed
mlx4 driver change which was done also under the assumption that
bonding touches directly the underlying dev_addr directly and I wanted
to see where this stands, so we can re-evaluate the driver patch
Or.
--
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