From: Krzysztof Kozlowski <krzk@kernel.org>
To: Sowon Na <sowon.na@samsung.com>,
robh@kernel.org, conor+dt@kernel.org, vkoul@kernel.org,
alim.akhtar@samsung.com, kishon@kernel.org
Cc: krzk+dt@kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH v3 1/3] dt-bindings: phy: Add ExynosAutov920 UFS PHY bindings
Date: Tue, 19 Nov 2024 08:50:38 +0100 [thread overview]
Message-ID: <80771196-0233-4c64-bf8f-f7a1ca0693c6@kernel.org> (raw)
In-Reply-To: <20241118021009.2858849-2-sowon.na@samsung.com>
On 18/11/2024 03:10, Sowon Na wrote:
> Add samsung,exynosautov920-ufs-phy compatible for ExynosAuto v920 SoC.
>
> Signed-off-by: Sowon Na <sowon.na@samsung.com>
> Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> ---
Read carefully guides before posting new versions. You already got one
such reminder, how many are needed?
<form letter>
This is a friendly reminder during the review process.
It looks like you received a tag and forgot to add it.
If you do not know the process, here is a short explanation:
Please add Acked-by/Reviewed-by/Tested-by tags when posting new
versions, under or above your Signed-off-by tag. Tag is "received", when
provided in a message replied to you on the mailing list. Tools like b4
can help here. However, there's no need to repost patches *only* to add
the tags. The upstream maintainer will do that for tags received on the
version they apply.
https://elixir.bootlin.com/linux/v6.5-rc3/source/Documentation/process/submitting-patches.rst#L577
If a tag was not added on purpose, please state why and what changed.
</form letter>
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-11-19 7:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20241118021011epcas2p397736dd9e5c7d96d799716e09919c136@epcas2p3.samsung.com>
2024-11-18 2:10 ` [PATCH v3 0/3] Support ExynosAutov920 ufs phy driver Sowon Na
[not found] ` <CGME20241118021011epcas2p21593217ccf58afddad5ce36f510e7cb6@epcas2p2.samsung.com>
2024-11-18 2:10 ` [PATCH v3 1/3] dt-bindings: phy: Add ExynosAutov920 UFS PHY bindings Sowon Na
2024-11-19 5:20 ` Alim Akhtar
2024-11-19 6:36 ` 나소원/SOWON NA
2024-12-18 1:32 ` 나소원/SOWON NA
2024-12-18 7:53 ` Krzysztof Kozlowski
2024-12-24 14:59 ` Vinod Koul
2024-11-19 7:50 ` Krzysztof Kozlowski [this message]
[not found] ` <CGME20241118021011epcas2p4b71dadce42a321213bdf8d445a312a8f@epcas2p4.samsung.com>
2024-11-18 2:10 ` [PATCH v3 2/3] phy: samsung-ufs: support ExynosAutov920 ufs phy driver Sowon Na
2024-11-27 2:46 ` Alim Akhtar
2024-12-24 14:58 ` Vinod Koul
2024-12-26 2:12 ` 나소원/SOWON NA
[not found] ` <CGME20241118021011epcas2p3db133a3cffb13fba8ce3c973d8ffff65@epcas2p3.samsung.com>
2024-11-18 2:10 ` [PATCH v3 3/3] arm64: dts: exynosautov920: add ufs phy for ExynosAutov920 SoC Sowon Na
2024-11-27 2:47 ` Alim Akhtar
2024-11-27 6:09 ` 나소원/SOWON NA
2024-12-17 1:29 ` [PATCH v3 0/3] Support ExynosAutov920 ufs phy driver 나소원/SOWON NA
2024-12-17 5:23 ` Krzysztof Kozlowski
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=80771196-0233-4c64-bf8f-f7a1ca0693c6@kernel.org \
--to=krzk@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kishon@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sowon.na@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).