From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Mauro Carvalho Chehab <mchehab@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/1] media: subdev: Replace custom implementation of device_match_fwnode()
Date: Mon, 14 Nov 2022 11:47:38 +0200 [thread overview]
Message-ID: <Y3IOusYrtZgC9BiY@smile.fi.intel.com> (raw)
In-Reply-To: <20220927171618.51971-1-andriy.shevchenko@linux.intel.com>
On Tue, Sep 27, 2022 at 08:16:18PM +0300, Andy Shevchenko wrote:
> Replace custom implementation of the device_match_fwnode().
Sakari, here you are in Cc list and I never have any response on this patch.
Maybe something wrong with emails somewhere?
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2022-11-14 9:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 17:16 [PATCH v1 1/1] media: subdev: Replace custom implementation of device_match_fwnode() Andy Shevchenko
2022-11-14 9:47 ` 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=Y3IOusYrtZgC9BiY@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=tomi.valkeinen@ideasonboard.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox