devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Pavel Machek <pavel@ucw.cz>, Alec Su <ae40515@yahoo.com.tw>
Cc: agross@kernel.org, bjorn.andersson@linaro.org,
	robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
	sboyd@codeaurora.org, linux-arm-msm@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	y.oudjana@protonmail.com
Subject: Re: [PATCH v3 0/2] Add support for Xiaomi Mi 5s Plus
Date: Mon, 30 May 2022 09:35:18 +0200	[thread overview]
Message-ID: <11b5c026-26ef-6b79-fbd9-f994a21e6755@linaro.org> (raw)
In-Reply-To: <20220530070738.GI1363@bug>

On 30/05/2022 09:07, Pavel Machek wrote:
> Hi!
> 
>> This series adds the device tree for Xiaomi Mi 5s Plus (xiaomi-natrium)
>> smartphone which is based on Snapdragon 821 SoC.
> 
> Please cc phone-devel@ mailing list with phone-related patches.

I think you need to come up with some smart content-pattern for
get_maintainers, because there is little chance I will remember to
manually Cc some different mailing lists depending on type of some
device or some other factor. I remember just to cc soc folks on certain
patches and that's it. Nothing else fits my memory. :) To avoid the
problem of poor human memory, we have a tool - scripts/get_maintainer.pl
- and contributors are encouraged to use that one. If you want to be
cc-ed, please either work on proper maintainers entry or set up some
custom lei filters.

Best regards,
Krzysztof

      reply	other threads:[~2022-05-30  7:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220520120449.12996-1-ae40515.ref@yahoo.com.tw>
2022-05-20 12:04 ` [PATCH v3 0/2] Add support for Xiaomi Mi 5s Plus Alec Su
2022-05-20 12:04   ` [PATCH v3 1/2] dt-bindings: arm: qcom: Document xiaomi,natrium board Alec Su
2022-05-20 12:04   ` [PATCH v3 2/2] arm64: dts: qcom: msm8996-xiaomi-natrium: Add support for Xiaomi Mi 5s Plus Alec Su
2022-05-30  7:07   ` [PATCH v3 0/2] " Pavel Machek
2022-05-30  7:35     ` Krzysztof Kozlowski [this message]

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=11b5c026-26ef-6b79-fbd9-f994a21e6755@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=ae40515@yahoo.com.tw \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=robh+dt@kernel.org \
    --cc=sboyd@codeaurora.org \
    --cc=y.oudjana@protonmail.com \
    /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).