From: Krzysztof Kozlowski <krzk@kernel.org>
To: nandhini.srikandan@intel.com, fancer.lancer@gmail.com,
broonie@kernel.org, robh+dt@kernel.org,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: devicetree@vger.kernel.org, mgross@linux.intel.com,
kris.pan@intel.com, kenchappa.demakkanavar@intel.com,
furong.zhou@intel.com, mallikarjunappa.sangannavar@intel.com,
mahesh.r.vaidya@intel.com
Subject: Re: [PATCH v1 2/2] spi: dw: Remove Intel Thunder Bay SOC support
Date: Wed, 13 Dec 2023 12:54:24 +0100 [thread overview]
Message-ID: <c41a2243-afd5-48f7-87f9-62f4a482b514@kernel.org> (raw)
In-Reply-To: <20231213060836.29203-3-nandhini.srikandan@intel.com>
On 13/12/2023 07:08, nandhini.srikandan@intel.com wrote:
> From: Nandhini Srikandan <nandhini.srikandan@intel.com>
>
> Remove Intel Thunder Bay specific code as the product got cancelled and
> there are no end customers or users.
Please use scripts/get_maintainers.pl to get a list of necessary people
and lists to CC (and consider --no-git-fallback argument). It might
happen, that command when run on an older kernel, gives you outdated
entries. Therefore please be sure you base your patches on recent Linux
kernel.
Other patches for removal of ThunderBar had the same issue, so it seems
like a consistent practice in your team. Can you fix it?
Please use subject prefixes matching the subsystem. You can get them for
example with `git log --oneline -- DIRECTORY_OR_FILE` on the directory
your patch is touching.
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-12-13 11:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 6:08 [PATCH v1 0/2] Remove Intel Thunder Bay SOC support nandhini.srikandan
2023-12-13 6:08 ` [PATCH v1 1/2] spi: dw: " nandhini.srikandan
2023-12-13 6:08 ` [PATCH v1 2/2] " nandhini.srikandan
2023-12-13 11:54 ` Krzysztof Kozlowski [this message]
2023-12-13 16:32 ` [PATCH v1 0/2] " Mark Brown
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=c41a2243-afd5-48f7-87f9-62f4a482b514@kernel.org \
--to=krzk@kernel.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fancer.lancer@gmail.com \
--cc=furong.zhou@intel.com \
--cc=kenchappa.demakkanavar@intel.com \
--cc=kris.pan@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=mahesh.r.vaidya@intel.com \
--cc=mallikarjunappa.sangannavar@intel.com \
--cc=mgross@linux.intel.com \
--cc=nandhini.srikandan@intel.com \
--cc=robh+dt@kernel.org \
/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).