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: <CAJKOXPft4eHTbA6qPA2MzyKZPhcxGUbJmfR3ykPaGuXRvacnEw@mail.gmail.com>
Date: Fri, 3 Oct 2025 16:14:28 +0900
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Ravi Patel <ravi.patel@...sung.com>
Cc: jesper.nilsson@...s.com, mturquette@...libre.com, sboyd@...nel.org, 
	robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org, 
	s.nawrocki@...sung.com, cw00.choi@...sung.com, alim.akhtar@...sung.com, 
	linus.walleij@...aro.org, tomasz.figa@...il.com, catalin.marinas@....com, 
	will@...nel.org, arnd@...db.de, ksk4725@...sia.com, kenkim@...sia.com, 
	pjsin865@...sia.com, gwk1013@...sia.com, hgkim05@...sia.com, 
	mingyoungbo@...sia.com, smn1196@...sia.com, shradha.t@...sung.com, 
	inbaraj.e@...sung.com, swathi.ks@...sung.com, hrishikesh.d@...sung.com, 
	dj76.yang@...sung.com, hypmean.kim@...sung.com, linux-kernel@...r.kernel.org, 
	linux-arm-kernel@...ts.infradead.org, linux-samsung-soc@...r.kernel.org, 
	linux-arm-kernel@...s.com, devicetree@...r.kernel.org, 
	linux-gpio@...r.kernel.org
Subject: Re: [PATCH v4 0/6] Add support for the Axis ARTPEC-8 SoC

On Fri, 3 Oct 2025 at 14:45, Ravi Patel <ravi.patel@...sung.com> wrote:
>
> Hi Krzysztof,
>
> The dt-bindings patch was merged earlier in v3 series (https://lore.kernel.org/linux-samsung-soc/175664688891.195158.13270877080433356384.b4-ty@linaro.org/ on 31st August)
> into respective maintainer repo.
> Then I have been asked to drop the applied v3 patches and send rebased v4 series (https://lore.kernel.org/linux-samsung-soc/15508cb4-843c-42d1-8854-5eabd79ca0df@kernel.org/)
>
> Since the 4 patches from v3 series has been already merged, I have not the mentioned dependency while sending remaining v4 patches considering
> It is going to same maintainer repo and it will be applied in sequence.
>
> For future patches (like artpec-9), I will mention the dependency even it is merged in same repo.
>

I know what happened, so no need to explain that. Single maintainer
repo doesn't matter, it's irrelevant and you mentioning it means you
didn't read the maintainer soc profiles I asked. You still don't get
the problem about what happened, at least judging by above expansion,
and this means you will repeat the same mistakes.

I will not proceed with further artpec patches until you really
understand how the process works, through existing documentation.
Please do your homework, to reduce the workload on maintainers.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ