From: Sean Young <sean@mess.org>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: linux-media@vger.kernel.org
Subject: Re: [GIT PULL FOR v6.7] Minor rc fixes
Date: Wed, 11 Oct 2023 14:40:22 +0100 [thread overview]
Message-ID: <ZSalxiDPtztvdW0x@gofer.mess.org> (raw)
In-Reply-To: <3faae6db-140a-4eb0-a72e-4d2a82e281ec@xs4all.nl>
On Wed, Oct 11, 2023 at 02:58:19PM +0200, Hans Verkuil wrote:
> On 09/10/2023 09:41, Sean Young wrote:
> > The following changes since commit 73835b514160dc548f7d77c6cd7fe6a8629d3406:
> >
> > media: imon: fix access to invalid resource for the second interface (2023-10-07 10:55:48 +0200)
> >
> > are available in the Git repository at:
> >
> > git://linuxtv.org/syoung/media_tree.git tags/v6.7c
> >
> > for you to fetch changes up to faf2b9954d9c9fdbac48e4b1d45d5ba2d3f10e52:
> >
> > media: lirc: drop trailing space from scancode transmit (2023-10-09 08:22:14 +0100)
> >
> > ----------------------------------------------------------------
> > v6.7c
> >
> > ----------------------------------------------------------------
> > Sean Young (2):
> > media: sharp: fix sharp encoding
> > media: lirc: drop trailing space from scancode transmit
> >
> > drivers/media/rc/ir-sharp-decoder.c | 8 +++++---
> > drivers/media/rc/lirc_dev.c | 6 +++++-
> > 2 files changed, 10 insertions(+), 4 deletions(-)
>
> These two patches have a Cc to stable, but no Fixes: tag.
I've added the fixes tags and retagged the v6.7c tag in my repo.
> Can you provide Fixes tags for these two patches? I can add them
> manually.
I should have fully read your message before retagging, my bad. What do
you want me to do now? The patches haven't changed, just the commit
messages.
Sean
next prev parent reply other threads:[~2023-10-11 13:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 7:41 [GIT PULL FOR v6.7] Minor rc fixes Sean Young
2023-10-09 8:09 ` [GIT PULL FOR v6.7] Minor rc fixes (#95641) Jenkins
2023-10-11 12:58 ` [GIT PULL FOR v6.7] Minor rc fixes Hans Verkuil
2023-10-11 13:40 ` Sean Young [this message]
2023-10-11 13:51 ` Hans Verkuil
2023-10-11 14:53 ` Sean Young
2023-10-11 14:55 ` Hans Verkuil
2023-10-11 15:06 ` Sean Young
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=ZSalxiDPtztvdW0x@gofer.mess.org \
--to=sean@mess.org \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@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