linux-kernel - Re: [Patch v3 0/4] add NETCMIX block control support on i.MX95

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: <20240829-ambrosial-smart-wombat-fb571e@lemur>
Date: Thu, 29 Aug 2024 09:28:01 -0400
From: Konstantin Ryabitsev <konstantin@...uxfoundation.org>
To: Abel Vesa <abel.vesa@...aro.org>
Cc: mturquette@...libre.com, sboyd@...nel.org, robh@...nel.org, 
	conor+dt@...nel.org, shawnguo@...nel.org, s.hauer@...gutronix.de, festevam@...il.com, 
	abelvesa@...nel.org, peng.fan@....com, Wei Fang <wei.fang@....com>, 
	linux-clk@...r.kernel.org, devicetree@...r.kernel.org, imx@...ts.linux.dev, 
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [Patch v3 0/4] add NETCMIX block control support on i.MX95

On Thu, Aug 29, 2024 at 10:53:28AM GMT, Abel Vesa wrote:
> > [1/4] dt-bindings: clock: add i.MX95 NETCMIX block control
> >       commit: 4b78b54762dbfc2f22f28655fa3cf6f5d50de197
> > [2/4] dt-bindings: clock: add RMII clock selection
> >       commit: b4f62001ccd3fa953769ccbd313c9a7a4f5f8f3d
> > [3/4] clk: imx95: enable the clock of NETCMIX block control
> >       commit: 42dc425fa8b5be982bcc2025d5bf30be8b26da86
> > [4/4] arm64: dts: imx95: Add NETCMIX block control support
> >       (no commit info)
> 
> For some reason, b4 ty thinks it's OK to mention this 4th patch as
> applied, while it is obviously not.
> 
> I only applied the first 3 patches.

Sorry for the confusion.

It's because you did "b4 am" on the entire series. We couldn't find the
matching commit for 4/4, but this often happens because maintainers tweak the
title or the patch contents, so we can't always assume that the patch wasn't
applied just because we can't find the exact match.

If you know you're going to apply a subset, it's best to run "b4 am -P 1-3" so
that b4 knows for a fact that you only intended to apply a subset.

-K