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]
Date:   Wed, 18 Oct 2017 14:59:28 -0700
From:   Scott Branden <scott.branden@...adcom.com>
To:     Andy Gospodarek <andrew.gospodarek@...adcom.com>
Cc:     Andrew Lunn <andrew@...n.ch>,
        "David S. Miller" <davem@...emloft.net>,
        "Allan W. Nielsen" <allan.nielsen@...rosemi.com>,
        Raju Lakkaraju <Raju.Lakkaraju@...rosemi.com>,
        Florian Fainelli <f.fainelli@...il.com>,
        BCM Kernel Feedback <bcm-kernel-feedback-list@...adcom.com>,
        linux-kernel@...r.kernel.org, Steve Lin <steven.lin1@...adcom.com>,
        netdev <netdev@...r.kernel.org>
Subject: Re: [PATCH 0/1] net: ethtool: add SmartNIC reset support

+netdev@...r.kernel.org


On 17-10-18 02:30 PM, Andy Gospodarek wrote:
> On Wed, Oct 18, 2017 at 12:31:28PM -0700, Scott Branden wrote:
>> Hi Andrew,
>>
>>
>> On 17-10-18 12:16 PM, Andrew Lunn wrote:
>>>> Yes, there is also a management processor.
>>> O.K.
>>>
>>> Maybe it would be nice to add some more text to the commit message to
>>> make this clear. Define what an application processor is, and how it
>>> differs from a management processor. But othersize:
>> OK -will add more description to differentiate management processor vs.
>> application processor(s).
>>> Reviewed-by: Andrew Lunn <andrew@...n.ch>
>>>
>>> I assume you have another kernel patch to actually make use of this?
>>> It is normal to post the user of a new API in the same series as the
>>> API.
>> I actually wanted to get agreement that the bit define could be added to
>> ethtool before implementing it in driver.
>> If this direction approved we'll implement in driver and submit with this
>> patch series.
> I just noticed that you did not also post this to netdev@...r.kernel.org.  I
> suspect you are more likely to get review and acceptance if that list is cc'd.
>
> I'm not positive that Linus will take networking patches off this list.
>
>>>       Andrew
>> Thanks,
>>   Scott

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ