From: patchwork-bot+chrome-platform@kernel.org
To: Ken Lin <ken_lin5@hotmail.com>
Cc: linux-kernel@vger.kernel.org, groeck@chromium.org,
bleung@chromium.org, hverkuil-cisco@xs4all.nl,
mchehab@kernel.org, rekanorman@chromium.org,
sadolfsson@chromium.org, u.kleine-koenig@pengutronix.de,
chrome-platform@lists.linux.dev, linux-media@vger.kernel.org,
rasheed.hsueh@lcfc.corp-partner.google.com
Subject: Re: [1/2] media: platform: cros-ec: Rename conns array for the match table
Date: Mon, 13 Nov 2023 03:42:36 +0000 [thread overview]
Message-ID: <169984695698.27851.12936649022716476866.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <KL1PR01MB38096300BE18095E51FB7A5BAECAA@KL1PR01MB3809.apcprd01.prod.exchangelabs.com>
Hello:
This series was applied to chrome-platform/linux.git (for-next)
by Hans Verkuil <hverkuil-cisco@xs4all.nl>:
On Thu, 5 Oct 2023 09:38:40 +0800 you wrote:
> Rename conns array to port_**_conns, ** is the ports which support cec.
> ex: dibbi_conns support Port D and B will be renamed to port_db_conns.
> Make it much cleaner and readable.
>
> Signed-off-by: Ken Lin <ken_lin5@hotmail.com>
> ---
>
> [...]
Here is the summary with links:
- [1/2] media: platform: cros-ec: Rename conns array for the match table
https://git.kernel.org/chrome-platform/c/678e8d804149
- [2/2] media: platform: cros-ec: Add Taranza to the match table
https://git.kernel.org/chrome-platform/c/cd5c11d5aacd
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-11-13 3:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 1:38 [1/2] media: platform: cros-ec: Rename conns array for the match table Ken Lin
2023-10-05 6:16 ` Uwe Kleine-König
2023-11-13 3:23 ` patchwork-bot+chrome-platform
2023-11-13 3:42 ` 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=169984695698.27851.12936649022716476866.git-patchwork-notify@kernel.org \
--to=patchwork-bot+chrome-platform@kernel.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=groeck@chromium.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=ken_lin5@hotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rasheed.hsueh@lcfc.corp-partner.google.com \
--cc=rekanorman@chromium.org \
--cc=sadolfsson@chromium.org \
--cc=u.kleine-koenig@pengutronix.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).