From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Sean Young <sean@mess.org>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH 0/4] Cleanups of rc keymaps
Date: Thu, 25 Jun 2026 15:33:05 +0200 [thread overview]
Message-ID: <20260625153305.6cf6d597@localhost> (raw)
In-Reply-To: <cover.1782300922.git.sean@mess.org>
On Wed, 24 Jun 2026 12:39:16 +0100
Sean Young <sean@mess.org> wrote:
> I've written a tool for media-ci which checks rc-keymap submissions.
> This tool found some trivial issues.
>
> Sean Young (4):
> media: keymaps: Remove obsolete RC_MAP_RC5_TV keymap define
> media: keymaps: Remove obsolete RC_MAP_HAUPPAUGE_NEW keymap define
> media: keymaps: Ensure module name matches RC_MAP_VIDEOMATE_K100
> media: dt-bindings: rc: Sync keymap list with latest list
>
> Documentation/devicetree/bindings/media/rc.yaml | 4 ++--
> drivers/media/rc/keymaps/Makefile | 2 +-
> .../rc/keymaps/{rc-videomate-m1f.c => rc-videomate-k100.c} | 2 +-
> include/media/rc-map.h | 2 --
> 4 files changed, 4 insertions(+), 6 deletions(-)
> rename drivers/media/rc/keymaps/{rc-videomate-m1f.c => rc-videomate-k100.c} (97%)
>
Makes sense to me. For the entire series:
Acked-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
--
Thanks,
Mauro
prev parent reply other threads:[~2026-06-25 13:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-24 11:39 [PATCH 0/4] Cleanups of rc keymaps Sean Young
2026-06-24 11:39 ` [PATCH 1/4] media: keymaps: Remove obsolete RC_MAP_RC5_TV keymap define Sean Young
2026-06-24 11:39 ` [PATCH] media: rc-core: Ensure that keymaps are sorted Sean Young
2026-06-24 11:39 ` [PATCH 2/4] media: keymaps: Remove obsolete RC_MAP_HAUPPAUGE_NEW keymap define Sean Young
2026-06-24 11:39 ` [PATCH 3/4] media: keymaps: Ensure module name matches RC_MAP_VIDEOMATE_K100 Sean Young
2026-06-24 11:39 ` [PATCH 4/4] media: dt-bindings: rc: Sync keymap list with latest list Sean Young
2026-06-25 13:33 ` Mauro Carvalho Chehab [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=20260625153305.6cf6d597@localhost \
--to=mchehab+huawei@kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=sean@mess.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.