mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: chunfeng.yun@mediatek.com,
	 AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>
Cc: kishon@kernel.org, matthias.bgg@gmail.com,
	 linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org,
	 linux-phy@lists.infradead.org, linux-kernel@vger.kernel.org,
	 kernel@collabora.com
Subject: Re: [PATCH v1 0/2] MediaTek TPHY Cleanups
Date: Thu, 26 Jun 2025 17:47:06 -0700	[thread overview]
Message-ID: <175098522610.106297.547358788124214801.b4-ty@kernel.org> (raw)
In-Reply-To: <20250623120315.109881-1-angelogioacchino.delregno@collabora.com>


On Mon, 23 Jun 2025 14:03:13 +0200, AngeloGioacchino Del Regno wrote:
> While doing my usual round of cleanups, I've found some room for
> improvement in the MediaTek T-PHY driver. This series performs some
> cleanups on that.
> 
> AngeloGioacchino Del Regno (2):
>   phy: mediatek: tphy: Clarify and add kerneldoc to mtk_phy_pdata
>   phy: mediatek: tphy: Cleanup and document slew calibration
> 
> [...]

Applied, thanks!

[1/2] phy: mediatek: tphy: Clarify and add kerneldoc to mtk_phy_pdata
      commit: 9cc82c2498b4fac77fb2438080458e42c1d0d5cb
[2/2] phy: mediatek: tphy: Cleanup and document slew calibration
      commit: d6306fc5d77b7cbdf75a90159f58ebb84ae6f02a

Best regards,
-- 
~Vinod



      parent reply	other threads:[~2025-06-27  0:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-23 12:03 AngeloGioacchino Del Regno
2025-06-23 12:03 ` [PATCH v1 1/2] phy: mediatek: tphy: Clarify and add kerneldoc to mtk_phy_pdata AngeloGioacchino Del Regno
2025-06-24  7:25   ` neil.armstrong
2025-06-23 12:03 ` [PATCH v1 2/2] phy: mediatek: tphy: Cleanup and document slew calibration AngeloGioacchino Del Regno
2025-06-24  7:28   ` neil.armstrong
2025-06-27  0:47 ` Vinod Koul [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=175098522610.106297.547358788124214801.b4-ty@kernel.org \
    --to=vkoul@kernel.org \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=chunfeng.yun@mediatek.com \
    --cc=kernel@collabora.com \
    --cc=kishon@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=matthias.bgg@gmail.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

all inboxes | Powered by JetHome®