From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Kunwu Chan <chentao@kylinos.cn>
Cc: linux@armlinux.org.uk, robh@kernel.org, saravanak@google.com,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] amba: Add dev_is_amba() function and export it for modules
Date: Mon, 23 Sep 2024 14:12:19 +0300 [thread overview]
Message-ID: <ZvFNE7pbwFN28ROF@smile.fi.intel.com> (raw)
In-Reply-To: <ZvFM6yC1EQPS5w_s@smile.fi.intel.com>
On Mon, Sep 23, 2024 at 02:11:40PM +0300, Andy Shevchenko wrote:
> On Mon, Sep 23, 2024 at 05:42:47PM +0800, Kunwu Chan wrote:
> > Add dev_is_amba() function to determine
> > whether the device is a AMBA device.
>
> Thanks, but it needs at least a user to show the conversion.
> I think I suggested in the last discussion to convert all
> straightforward cases (which are not the direct users of the
> given bus type).
Okay, I see now, I was only Cc'ed to the first in the series...
Scratch that comment then, sorry for the noise.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-09-23 11:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-23 9:42 [PATCH 0/2] Add dev_is_amba and replace the usage in platform Kunwu Chan
2024-09-23 9:42 ` [PATCH 1/2] amba: Add dev_is_amba() function and export it for modules Kunwu Chan
2024-09-23 11:11 ` Andy Shevchenko
2024-09-23 11:12 ` Andy Shevchenko [this message]
2024-09-24 22:28 ` Rob Herring
2024-09-24 22:43 ` Russell King (Oracle)
2024-09-30 1:39 ` Kunwu Chan
2024-10-02 2:11 ` Rob Herring
2024-09-23 9:42 ` [PATCH 2/2] of/platform: PCI: Use dev_is_platform/dev_is_amba to identify platform/amba devices Kunwu Chan
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=ZvFNE7pbwFN28ROF@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=chentao@kylinos.cn \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=robh@kernel.org \
--cc=saravanak@google.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;
as well as URLs for NNTP newsgroup(s).