From: patchwork-bot+chrome-platform@kernel.org
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: gregkh@linuxfoundation.org, andersson@kernel.org,
chrome-platform@lists.linux.dev, linux-usb@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] usb: typec: mux: Remove the "svid" device property checks
Date: Mon, 10 Jul 2023 05:53:19 +0000 [thread overview]
Message-ID: <168896839903.3413.16844292204313046489.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230526131434.46920-1-heikki.krogerus@linux.intel.com>
Hello:
This series was applied to chrome-platform/linux.git (for-next)
by Greg Kroah-Hartman <gregkh@linuxfoundation.org>:
On Fri, 26 May 2023 16:14:32 +0300 you wrote:
> Hi,
>
> The comment in the first patch is now fixed as requested by Bjorn. No
> other changes compared to v1.
>
> Original message:
>
> [...]
Here is the summary with links:
- [v2,1/2] usb: typec: mux: Clean up mux_fwnode_match()
https://git.kernel.org/chrome-platform/c/4aebc4f89f00
- [v2,2/2] usb: typec: mux: Remove alt mode parameters from the API
https://git.kernel.org/chrome-platform/c/3524fe31538c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-07-10 5:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 13:14 [PATCH v2 0/2] usb: typec: mux: Remove the "svid" device property checks Heikki Krogerus
2023-05-26 13:14 ` [PATCH v2 1/2] usb: typec: mux: Clean up mux_fwnode_match() Heikki Krogerus
2023-05-26 13:14 ` [PATCH v2 2/2] usb: typec: mux: Remove alt mode parameters from the API Heikki Krogerus
2023-07-10 5:39 ` [PATCH v2 0/2] usb: typec: mux: Remove the "svid" device property checks patchwork-bot+chrome-platform
2023-07-10 5:53 ` patchwork-bot+chrome-platform [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=168896839903.3413.16844292204313046489.git-patchwork-notify@kernel.org \
--to=patchwork-bot+chrome-platform@kernel.org \
--cc=andersson@kernel.org \
--cc=chrome-platform@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.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