Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Mon, 5 Jun 2023 18:49:12 +0200
From:   Andrew Lunn <andrew@lunn.ch>
To:     Michal Smulski <michal.smulski@ooma.com>
Cc:     "msmulski2@gmail.com" <msmulski2@gmail.com>,
        "f.fainelli@gmail.com" <f.fainelli@gmail.com>,
        "olteanv@gmail.com" <olteanv@gmail.com>,
        "davem@davemloft.net" <davem@davemloft.net>,
        "edumazet@google.com" <edumazet@google.com>,
        "kuba@kernel.org" <kuba@kernel.org>,
        "pabeni@redhat.com" <pabeni@redhat.com>,
        "linux@armlinux.org.uk" <linux@armlinux.org.uk>,
        "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "simon.horman@corigine.com" <simon.horman@corigine.com>,
        "kabel@kernel.org" <kabel@kernel.org>,
        "ioana.ciornei@nxp.com" <ioana.ciornei@nxp.com>
Subject: Re: [PATCH net-next v7 0/1] net: dsa: mv88e6xxx: implement USXGMII
 mode for mv88e6393x
Message-ID: <87a5491e-6697-48d3-94fe-aa2c6f5ab129@lunn.ch>
References: <20230605053954.4051-1-msmulski2@gmail.com>
 <b38bd01c-dbaa-440d-93ae-b1b772f8e8e1@lunn.ch>
 <BYAPR14MB2918D3EBDA5120130D12BAB2E34DA@BYAPR14MB2918.namprd14.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <BYAPR14MB2918D3EBDA5120130D12BAB2E34DA@BYAPR14MB2918.namprd14.prod.outlook.com>
Precedence: bulk

On Mon, Jun 05, 2023 at 04:32:03PM +0000, Michal Smulski wrote:
> Andrew,
> 

> I will remove this line and resend v7. This was a mistake on my
> part. However, could you clarify on what is the best way to let
> reviewers know what changed between different version of the same
> patch? It seemed to me that changlist should not be part of the git
> commit message and hence I decided to add 'cover-letter' email for
> each new version of the patch so that it would not be part of the
> applied patch to net-next git repo (but it would also be easy to
> match changelist email with patch email to people reviewing latest
> patch)

Some people think the history is actually useful, it shows what has
been considered etc and the patch matured.

However, anything text after the --- marker in a patch will get
discarded by git am when the patch is merged. So you can place the
history there.

	Andrew