Linux Renesas SOC kernel development
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: Daniel Scally <djrscally@gmail.com>,
	Heikki Krogerus <heikki.krogerus@linux.intel.com>,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Wolfram Sang <wsa@kernel.org>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	"linux-renesas-soc@vger.kernel.org" 
	<linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH v5 RESEND 1/4] drivers: fwnode: Extend device_get_match_data() to struct bus_type
Date: Thu, 3 Aug 2023 15:12:06 +0300	[thread overview]
Message-ID: <ZMuZlu5W/22ZDKBw@smile.fi.intel.com> (raw)
In-Reply-To: <TYCPR01MB593382D6915A0D4297483B6F8608A@TYCPR01MB5933.jpnprd01.prod.outlook.com>

On Thu, Aug 03, 2023 at 12:05:58PM +0000, Biju Das wrote:
> > Subject: Re: [PATCH v5 RESEND 1/4] drivers: fwnode: Extend
> > device_get_match_data() to struct bus_type
> > 
> > On Thu, Aug 03, 2023 at 11:30:59AM +0100, Biju Das wrote:
> > > Extend device_get_match_data() to buses (for eg: I2C) by adding a
> > > callback device_get_match_data() to struct bus_type() and call this
> > > method as a fallback for generic fwnode based device_get_match_data().
> > 
> > With this resend you were too fast to forgot Sakari's tag...
> 
> In my mailbox, I received Sakari's tag after sending RESEND patch series.
> It may be some race situation with mailboxes.

Right. My point is, give some time before resend even if something is wrong.
Jest reply to your own message to inform people that "the vX is wrong and
I am going to resend it soon",

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2023-08-03 12:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-03 10:30 [PATCH v5 RESEND 0/4] Extend device_get_match_data() to struct bus_type Biju Das
2023-08-03 10:30 ` [PATCH v5 RESEND 1/4] drivers: fwnode: " Biju Das
2023-08-03 12:00   ` Andy Shevchenko
2023-08-03 12:02     ` Sakari Ailus
2023-08-03 12:07       ` Andy Shevchenko
2023-08-03 12:13       ` Biju Das
2023-08-03 12:05     ` Biju Das
2023-08-03 12:12       ` Andy Shevchenko [this message]
2023-08-03 10:31 ` [PATCH v5 RESEND 2/4] i2c: Add i2c_device_get_match_data() callback Biju Das
2023-08-03 12:06   ` Andy Shevchenko
2023-08-03 13:52     ` Biju Das
2023-08-04  4:05       ` Andy Shevchenko
2023-08-03 10:31 ` [PATCH v5 RESEND 3/4] i2c: i2c-core-of: Convert i2c_of_match_device_sysfs() to non-static Biju Das
2023-08-03 12:08   ` Andy Shevchenko
2023-08-03 10:31 ` [PATCH v5 RESEND 4/4] i2c: Extend i2c_device_get_match_data() to support i2c sysfs Biju Das
2023-08-03 12:10   ` Andy Shevchenko
2023-08-03 12:13 ` [PATCH v5 RESEND 0/4] Extend device_get_match_data() to struct bus_type 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=ZMuZlu5W/22ZDKBw@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=djrscally@gmail.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=geert+renesas@glider.be \
    --cc=gregkh@linuxfoundation.org \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=sakari.ailus@linux.intel.com \
    --cc=wsa@kernel.org \
    /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