linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Lukas Timmermann <linux@timmermann.space>,
	Alim Akhtar <alim.akhtar@samsung.com>,
	Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
	Russell King <linux@armlinux.org.uk>,
	linux-arm-kernel@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, Alexandre Marquet <tb@a-marquet.fr>
Subject: Re: [PATCH v2 3/3] ARM: samsung: exynos5250: Allow CPU1 to boot
Date: Thu, 4 Dec 2025 13:38:06 +0100	[thread overview]
Message-ID: <aTGAruX7N/7ZT0ur@duo.ucw.cz> (raw)
In-Reply-To: <39ac918c-0394-495b-b717-dfa0fd35d7dc@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 2007 bytes --]

On Thu 2025-12-04 13:02:00, Krzysztof Kozlowski wrote:
> On 04/12/2025 12:55, Pavel Machek wrote:
> > On Thu 2025-12-04 12:54:03, Krzysztof Kozlowski wrote:
> >> On 04/12/2025 12:53, Pavel Machek wrote:
> >>> On Thu 2025-12-04 12:51:36, Krzysztof Kozlowski wrote:
> >>>> On 04/12/2025 12:22, Pavel Machek wrote:
> >>>>> Also please cc: phone-devel mailing list with phone related patches.
> >>>>
> >>>> You don't have to. This list is not part of any upstream Linux kernel
> >>>> process (see `git grep`), it's not relevant to upstream kernel development.
> >>>
> >>> Yes, you should. Its a relevant mailing list.
> >>
> >> git grep for it. Stop inventing rules.
> > 
> > Who is inventing rules here? Stop sabotaging review process.
> 
> You invented rule that some specific list of your interest has to be
> CCed, even though no one knows about that list and it is nowhere documented.

No. I'm asking people to please cc the mailing list so that interested
people can see the patches. It is you blabbering nonsense about "git
grep" and "get_maintainer" as if those were rules.

> > "Many kernel-related lists are hosted on vger.kernel.org; you can find a
> > list of them at http://vger.kernel.org/vger-lists.html.  There are
> > kernel-related lists hosted elsewhere as well, though."
> 
> This proves nothing. There are just some lists there. No one has to cc
> whatever list there just because Pavel Machek asks them. Kernel process
> defines it or not. Not you.

And not you.

Kernel process is to cc relevant people, and relevant mailing lists,
SubmittingPatches points you to http://vger.kernel.org/vger-lists.html
. If people are interested in the patch (for example because they
reacted to previous version), you should cc them. People in
phone-devel expressed interest in phone-related kernel development, so
you should cc them.

								Pavel
-- 
I don't work for Nazis and criminals, and neither should you.
Boycott Putin, Trump, Netanyahu and Musk!

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2025-12-04 12:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-25 15:12 [PATCH v2 0/3] Add support for exynos5250-manta (Google Nexus 10) Lukas Timmermann
2025-11-25 15:12 ` [PATCH v2 1/3] dt-bindings: ARM: samsung: Add Google Manta (Nexus 10) Lukas Timmermann
2025-11-25 15:12 ` [PATCH v2 2/3] ARM: dts: exynos: " Lukas Timmermann
2025-11-26  9:10   ` Krzysztof Kozlowski
2025-11-27 20:01     ` Lukas Timmermann
2025-11-28  9:01       ` Krzysztof Kozlowski
2025-11-25 15:12 ` [PATCH v2 3/3] ARM: samsung: exynos5250: Allow CPU1 to boot Lukas Timmermann
2025-11-26  9:24   ` Krzysztof Kozlowski
2025-11-27 11:53     ` Lukas Timmermann
2025-12-04 11:22   ` Pavel Machek
2025-12-04 11:51     ` Krzysztof Kozlowski
2025-12-04 11:53       ` Pavel Machek
2025-12-04 11:54         ` Krzysztof Kozlowski
2025-12-04 11:55           ` Pavel Machek
2025-12-04 12:02             ` Krzysztof Kozlowski
2025-12-04 12:38               ` Pavel Machek [this message]
2025-11-25 15:20 ` [PATCH v2 0/3] Add support for exynos5250-manta (Google Nexus 10) Krzysztof Kozlowski
2025-11-25 15:22   ` Krzysztof Kozlowski
2025-11-26 22:46 ` Rob Herring

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aTGAruX7N/7ZT0ur@duo.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=alim.akhtar@samsung.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=linux@timmermann.space \
    --cc=robh@kernel.org \
    --cc=tb@a-marquet.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).