All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Fricke <sebastian.fricke@collabora.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: linux-media@vger.kernel.org
Subject: Re: [GIT PULL FOR 6.9] Various Mediatek VCodec fixes
Date: Mon, 25 Mar 2024 18:37:25 +0100	[thread overview]
Message-ID: <20240325173725.ydxv7o2xqgzpdtqm@basti-XPS-13-9310> (raw)
In-Reply-To: <73de97e4-a9ce-4e46-8718-7e51936a66c3@xs4all.nl>

Hey Hans,
>>
>> On 25.03.2024 10:30, Hans Verkuil wrote:
>>> Hi Sebastian,
>>>
>>> Are these fixes for v6.9 or can these be merged for v6.10?
>>
>> I was hoping for them to land in 6.9 but if that doesn't work that is
>> fine for me as well.
>>
>>>
>>> Not all of these patches have a 'Fixes' tag, perhaps they should have it?
>>
>> No the tags are correct, do you want me to strictly only mix patches
>> with fixes tags or only patches without fixes tags?
>
>That's why I asked: if you want that all these patches go to v6.9, then I can
>apply them to our fixes branch and they will be passed on to Linus for
>6.9, but in that case it would be good to have Fixes tags.
>
>If all patches are OK to be merged for 6.10, then I can just apply them
>to our staging tree.
>
>Finally, if some are for 6.9 and some for 6.10 (presumably those patches
>without the Fixes tag), then I can split it up myself.
>
>In any case, I need to know what you want.

Alright, then please add all of them to 6.9, the two without the fixes
tags are not critical but that enable normal functionality, so I'd call
them important enough.

>
>Regards,
>
>	Hans

Greetings,
Sebastian

      reply	other threads:[~2024-03-25 17:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-15 13:25 [GIT PULL FOR 6.9] Various Mediatek VCodec fixes Sebastian Fricke
2024-03-15 13:56 ` [GIT PULL FOR 6.9] Various Mediatek VCodec fixes (#99936) Jenkins
2024-03-25  9:30 ` [GIT PULL FOR 6.9] Various Mediatek VCodec fixes Hans Verkuil
2024-03-25 15:44   ` Sebastian Fricke
2024-03-25 16:25     ` Hans Verkuil
2024-03-25 17:37       ` Sebastian Fricke [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=20240325173725.ydxv7o2xqgzpdtqm@basti-XPS-13-9310 \
    --to=sebastian.fricke@collabora.com \
    --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 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.