From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: linux-media@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v1 2/2] media: atomisp: Replace open-coded i2c_find_device_by_fwnode()
Date: Wed, 10 Apr 2024 16:49:53 +0300 [thread overview]
Message-ID: <ZhaZAdUdAwL80Tza@smile.fi.intel.com> (raw)
In-Reply-To: <911d84a7-cb3b-4ca5-86a1-334e7b3f85c6@redhat.com>
On Wed, Apr 10, 2024 at 03:41:15PM +0200, Hans de Goede wrote:
> On 4/10/24 3:35 PM, Andy Shevchenko wrote:
> > On Wed, Apr 10, 2024 at 12:35:29PM +0200, Hans de Goede wrote:
> >> On 3/26/24 9:27 PM, Andy Shevchenko wrote:
...
> >> I'm going to merge this variant into my media-atomisp branch
> >> instead of the orignal.
> >
> > Thanks!
> >
> > This explains why changelog made the commit message.
> > Was it done deliberately?
>
> Oops, no that was by accident. I normally git send-email
> + git am my patches and then git am cuts it off...
>
> I just send out a pull-request with this minor wart in it
> (after testing), so unless there are other reasons to respin
> I guess we'll have to live with it.
You might check the linux-next scripts or ask Stephen if this is an issue.
In any case we will know sooner or later :-)
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2024-04-10 13:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 20:27 [PATCH v1 0/2] media: atomisp: Fix and refactor PMIC I²C discovery Andy Shevchenko
2024-03-26 20:27 ` [PATCH v1 1/2] media: atomisp: Put PMIC device after getting its I²C address Andy Shevchenko
2024-04-10 10:41 ` Hans de Goede
2024-03-26 20:27 ` [PATCH v1 2/2] media: atomisp: Replace open-coded i2c_find_device_by_fwnode() Andy Shevchenko
2024-04-10 10:35 ` Hans de Goede
2024-04-10 13:35 ` Andy Shevchenko
2024-04-10 13:41 ` Hans de Goede
2024-04-10 13:49 ` 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=ZhaZAdUdAwL80Tza@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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.