[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y9lyMEDfvQQybtor@COLIN-DESKTOP1.localdomain>
Date: Tue, 31 Jan 2023 11:55:28 -0800
From: Colin Foster <colin.foster@...advantage.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Lee Jones <lee@...nel.org>, patchwork-bot+netdevbpf@...nel.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org, linux@...linux.org.uk,
richardcochran@...il.com, f.fainelli@...il.com, andrew@...n.ch,
UNGLinuxDriver@...rochip.com, alexandre.belloni@...tlin.com,
claudiu.manoil@....com, vladimir.oltean@....com, pabeni@...hat.com,
edumazet@...gle.com, davem@...emloft.net,
krzysztof.kozlowski+dt@...aro.org, robh+dt@...nel.org
Subject: Re: [PATCH v5 net-next 00/13] add support for the the vsc7512
internal copper phys
On Tue, Jan 31, 2023 at 11:45:38AM -0800, Jakub Kicinski wrote:
> On Tue, 31 Jan 2023 09:06:22 +0000 Lee Jones wrote:
> > Please don't do that. The commits do not have proper Acked-by tags.
> >
> > The plan is to merge these via MFD and send out a pull-request to an
> > immutable branch. However, if you're prepared to convert all of the:
> >
> > Acked-for-MFD-by: Lee Jones <lee@...nel.org>
> >
> > to
> >
> > Acked-by: Lee Jones <lee@...nel.org>
>
> Sorry, I must have been blind yesterday because I definitely double
> checked this doesn't touch mfd code. And it does :/
>
> The patches should not be sent for net-next if they are not supposed
> to be applied directly. Or at the very least says something about
> merging in the cover letter!
My apologies. I wasn't sure how these cross-tree syncs would be done
(and I recognize Lee even asked during a previous submission.) I'll be
more verbose in cover letters moving forward, should I ever be
submitting against multiple trees like this.
Powered by blists - more mailing lists