From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-staging@lists.linux.dev, Kate Hsuan <hpa@redhat.com>
Subject: Re: [GIT PULL] media: atomisp: Changes for 6.8-1
Date: Thu, 1 Feb 2024 14:20:31 +0100 [thread overview]
Message-ID: <20240201142031.34b89978@coco.lan> (raw)
In-Reply-To: <3d0d2d3e-f991-4261-83f8-e4fd813e0804@redhat.com>
Em Thu, 1 Feb 2024 13:33:08 +0100
Hans de Goede <hdegoede@redhat.com> escreveu:
> Hi,
>
> On 2/1/24 13:18, Mauro Carvalho Chehab wrote:
> > Em Thu, 1 Feb 2024 12:46:19 +0100
> > Hans de Goede <hdegoede@redhat.com> escreveu:
> >
> >> Hi,
> >>
> >> On 2/1/24 07:10, Mauro Carvalho Chehab wrote:
> >>> Em Sun, 31 Dec 2023 11:39:18 +0100
> >>> Hans de Goede <hdegoede@redhat.com> escreveu:
> >>>
> >>>> Hi Mauro,
> >>>>
> >>>> Here are the atomisp changes for 6.8.
> >>>>
> >>>> My patches in this set been posted on the list, but only a couple of
> >>>> minutes ago, leaving pretty much zero time for review. Sorry about that,
> >>>> with the holidays the timing did not work out very well.
> >>>>
> >>>> If you don't want to take this pull-request because of this it
> >>>> would be good if you can at least take the patches up to
> >>>> the "media: atomisp: Fix spelling mistake in ia_css_acc_types.h"
> >>>> change. There are only 2 unreviewed patches from me in that
> >>>> set, which fix the atomisp driver not working at all with
> >>>> the latest media_stage/master code. And the rest of the patches
> >>>> in that set are from others and have been reviewed by me.
> >>>
> >>> We typically close the media merge window at -rc6. As I was also
> >>> in vacations during those weeks, this PR was merged today for 6.9.
> >>
> >> No problem, I know I was late with submitting this PR.
> >>
> >>> Indeed the first two patches seem to be needed to fix an issue on 6.8.
> >>> Could you please send them to stable after their arrival at linux-next?
> >>
> >> I'm not sure what you mean with send them to stable ?
> >>
> >> 6.8 is not released yet, so these need to be send to Linus this
> >> cycle. What is the process for media bugfixes for the current
> >> kernel cycle ?
> >
> > Heh, sorry, somehow I was thinking on 6.7 :-)
> >
> > If the bug only happens on 6.8, I can just cherry-pick the two patches
> > on my fixes branch.
>
> I believe you only need:
>
> "media: atomisp: Adjust for v4l2_subdev_state handling changes in 6.8"
>
> And as the subject says, that is a fix for 6.8, 6.7 is fine AFAIK.
Ok, patch cherry-picked to the fixes branch. I'll send it together
with the other pending patches after they arrive to linux-next
(so likely next week).
Thanks,
Mauro
prev parent reply other threads:[~2024-02-01 13:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-31 10:39 [GIT PULL] media: atomisp: Changes for 6.8-1 Hans de Goede
2023-12-31 11:37 ` [GIT PULL] media: atomisp: Changes for 6.8-1 (#98381) Jenkins
2024-02-01 6:10 ` [GIT PULL] media: atomisp: Changes for 6.8-1 Mauro Carvalho Chehab
2024-02-01 11:46 ` Hans de Goede
2024-02-01 12:18 ` Mauro Carvalho Chehab
2024-02-01 12:33 ` Hans de Goede
2024-02-01 13:20 ` 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=20240201142031.34b89978@coco.lan \
--to=mchehab@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=hpa@redhat.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=sakari.ailus@linux.intel.com \
/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.