From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: linux-phy@lists.infradead.org, Vinod Koul <vkoul@kernel.org>,
linux-arm-kernel@lists.infradead.org,
Marek Szyprowski <m.szyprowski@samsung.com>,
linux-scsi@vger.kernel.org, Avri Altman <avri.altman@wdc.com>,
Kishon Vijay Abraham I <kishon@ti.com>,
Jaehoon Chung <jh80.chung@samsung.com>,
Chanho Park <chanho61.park@samsung.com>,
Alim Akhtar <alim.akhtar@samsung.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
linux-samsung-soc@vger.kernel.org,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
linux-kernel@vger.kernel.org
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH 1/2] phy: samsung: unify naming and describe driver in KConfig
Date: Tue, 5 Oct 2021 00:34:37 -0400 [thread overview]
Message-ID: <163340840528.12126.5919262965845250313.b4-ty@oracle.com> (raw)
In-Reply-To: <20210924132658.109814-1-krzysztof.kozlowski@canonical.com>
On Fri, 24 Sep 2021 15:26:57 +0200, Krzysztof Kozlowski wrote:
> We use everywhere "Samsung" and "Exynos", not the uppercase versions.
> Describe better which driver applies to which SoC, to make configuring
> kernel for Samsung SoC easier.
>
>
Applied to 5.16/scsi-queue, thanks!
[2/2] scsi: ufs: exynos: unify naming
https://git.kernel.org/mkp/scsi/c/ce580e47e848
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2021-10-05 4:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-24 13:26 [PATCH 1/2] phy: samsung: unify naming and describe driver in KConfig Krzysztof Kozlowski
2021-09-24 13:26 ` [PATCH 2/2] scsi: ufs: exynos: unify naming Krzysztof Kozlowski
2021-09-28 6:16 ` Alim Akhtar
2021-09-29 2:46 ` Martin K. Petersen
2021-10-01 6:16 ` [PATCH 1/2] phy: samsung: unify naming and describe driver in KConfig Vinod Koul
2021-10-05 4:34 ` Martin K. Petersen [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=163340840528.12126.5919262965845250313.b4-ty@oracle.com \
--to=martin.petersen@oracle.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=chanho61.park@samsung.com \
--cc=jejb@linux.ibm.com \
--cc=jh80.chung@samsung.com \
--cc=kishon@ti.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=vkoul@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).