linux-kernel - Re: [PATCH 3/4] net: dsa: mv88e6xxx: Implement .port_change_mtu/.port_max

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] [day] [month] [year] [list]

Message-ID: <bbd66a44-900c-68cf-244d-4d8e505d05eb@alliedtelesis.co.nz>
Date:   Thu, 23 Jul 2020 21:16:22 +0000
From:   Chris Packham <Chris.Packham@...iedtelesis.co.nz>
To:     Andrew Lunn <andrew@...n.ch>
CC:     "vivien.didelot@...il.com" <vivien.didelot@...il.com>,
        "f.fainelli@...il.com" <f.fainelli@...il.com>,
        "davem@...emloft.net" <davem@...emloft.net>,
        "kuba@...nel.org" <kuba@...nel.org>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 3/4] net: dsa: mv88e6xxx: Implement
 .port_change_mtu/.port_max_mtu


On 24/07/20 9:02 am, Andrew Lunn wrote:
> On Thu, Jul 23, 2020 at 08:50:27PM +0000, Chris Packham wrote:
>> On 24/07/20 1:31 am, Andrew Lunn wrote:
>>> On Thu, Jul 23, 2020 at 03:59:41PM +1200, Chris Packham wrote:
>>>> Add implementations for the mv88e6xxx switches to connect with the
>>>> generic dsa operations for configuring the port MTU.
>>> Hi Chris
>>>
>>> What tree is this against?
>> $ git config remote.origin.url
>> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>> $ git describe `git merge-base HEAD origin/master`
> Hi Chris
>
> Networking patches are expected to be against net-next. Or net if they
> are fixes. Please don't submit patches to netdev against other trees.

OK. I'll try to remember that for next time. For this series in 
particular it's a little hard for me to test net-next because the 
hardware in question relies on a bunch of code that is not upstream.