All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
	Hans Verkuil <hverkuil-cisco@xs4all.nl>,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	Andy Shevchenko <andriy.shevchenko@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 11:15:33 +0100	[thread overview]
Message-ID: <20240426111533.2b717d57@sal.lan> (raw)
In-Reply-To: <5f89adf7-23e3-4966-ac50-838335b13207@redhat.com>

Hi Hans,

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.

Regards,
Mauro

  parent reply	other threads:[~2024-04-26 10:15 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 ` Mauro Carvalho Chehab [this message]
2024-04-26 17:04   ` [GIT PULL] media: atomisp: Changes for 6.10-2 Hans de Goede
2024-04-26 17:08     ` Andy Shevchenko

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=20240426111533.2b717d57@sal.lan \
    --to=mchehab@kernel.org \
    --cc=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=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.