From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
linux-staging@lists.linux.dev, Kate Hsuan <hpa@redhat.com>,
"kieran.bingham@ideasonboard.com"
<kieran.bingham@ideasonboard.com>
Subject: Re: [GIT PULL] media: atomisp: Changes for 6.10-2
Date: Fri, 26 Apr 2024 20:08:22 +0300 [thread overview]
Message-ID: <Zivfhs29Ra_YyED8@smile.fi.intel.com> (raw)
In-Reply-To: <57b7f59a-8549-44d5-95fd-4402951d4bd2@redhat.com>
On Fri, Apr 26, 2024 at 07:04:10PM +0200, Hans de Goede wrote:
> On 4/26/24 12:15 PM, Mauro Carvalho Chehab wrote:
> > Em Tue, 16 Apr 2024 11:33:51 +0200
> > Hans de Goede <hdegoede@redhat.com> escreveu:
> >
> >> Hi Mauro, Hans,
> >>
> >> Here is a second round of atomisp changes for 6.10,
> >> this pull-request supersedes / replace my
> >> "media: atomisp: Changes for 6.10-1" pull-request.
> >>
> >> Various cleanup patches from Jonathan Bergh and Andy +
> >> a set of patches from me which has been reviewed
> >> by Andy and Kieran.
> >
> > Atomisp patches applied, thanks!
> >
> > I had to do a rebase here first, as it seems some patches were
> > merged already on this series and on the previous one.
> >
> > Please double-check if I picked everything, and rebase your
> > tree on the top of media-stage before the next PR, to avoid
> > potential issues during patch review.
>
> Thank you for merging all the patches.
>
> I have done a rebase of my media-atomisp tree and all patches
> there were skipped as "previously applied commit", so everything
> looks good.
I would recommend to double check with the real diff between two branches
(like old one, possibly rebased on old media tree) and new one.
I remember some (Git versions?) time I got this message while the content
was slightly different, hence from that time I learnt to double check with
the actual diff.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2024-04-26 17:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 9:33 [GIT PULL] media: atomisp: Changes for 6.10-2 Hans de Goede
2024-04-16 10:50 ` [GIT PULL] media: atomisp: Changes for 6.10-2 (#100910) Jenkins
2024-04-26 10:15 ` [GIT PULL] media: atomisp: Changes for 6.10-2 Mauro Carvalho Chehab
2024-04-26 17:04 ` Hans de Goede
2024-04-26 17:08 ` Andy Shevchenko [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=Zivfhs29Ra_YyED8@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=hpa@redhat.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=kieran.bingham@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mchehab@kernel.org \
--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.