linux-kernel - Re: [PATCH net-next v7 0/1] net: dsa: mv88e6xxx: implement USXGMII mode for mv88e6393x

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: <b38bd01c-dbaa-440d-93ae-b1b772f8e8e1@lunn.ch>
Date:   Mon, 5 Jun 2023 14:41:52 +0200
From:   Andrew Lunn <andrew@...n.ch>
To:     msmulski2@...il.com
Cc:     f.fainelli@...il.com, olteanv@...il.com, davem@...emloft.net,
        edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
        linux@...linux.org.uk, netdev@...r.kernel.org,
        linux-kernel@...r.kernel.org, simon.horman@...igine.com,
        kabel@...nel.org, ioana.ciornei@....com,
        Michal Smulski <michal.smulski@...a.com>
Subject: Re: [PATCH net-next v7 0/1] net: dsa: mv88e6xxx: implement USXGMII
 mode for mv88e6393x

On Sun, Jun 04, 2023 at 10:39:53PM -0700, msmulski2@...il.com wrote:
> From: Michal Smulski <michal.smulski@...a.com>
> 
> Changelist:
> * do not enable USXGMII for 6361 chips
> * track state->an_complete with state->link 
> 
> *** BLURB HERE ***

Hi Michal

Please remember to remove the *** BLURB HERE ***. What often happens
is that a branch is created for a patchset, and then the branch is
merged and the content of patch 0/X is used as the merge commit
message. So this can end up in the git history.

For a single patch, you are not required to have a patch 0/X.

	 Andrew