From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Kunwu Chan <kunwu.chan@linux.dev>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
krzk@kernel.org, andi.shyti@kernel.org, robh@kernel.org,
gregkh@linuxfoundation.org, suzuki.poulose@arm.com,
linux-kernel@vger.kernel.org, Kunwu Chan <chentao@kylinos.cn>
Subject: Re: [PATCH] amba: make amba_bustype constant
Date: Wed, 4 Sep 2024 14:58:36 +0100 [thread overview]
Message-ID: <ZthnjPjPB+6cMf9w@shell.armlinux.org.uk> (raw)
In-Reply-To: <65c80deb-21e1-44eb-87c9-c7cdd36d77cd@linux.dev>
On Thu, Aug 29, 2024 at 09:31:29AM +0800, Kunwu Chan wrote:
> Thanks for the reply.
> On 2024/8/28 21:17, Andy Shevchenko wrote:
> > On Wed, Aug 28, 2024 at 10:51:54AM +0800, Kunwu Chan wrote:
> > > On 2024/8/27 21:37, Andy Shevchenko wrote:
> > > > On Tue, Aug 27, 2024 at 03:45:31PM +0800, Kunwu Chan wrote:
> > > > > On 2024/8/26 18:40, Andy Shevchenko wrote:
> > > > > > On Mon, Aug 26, 2024 at 06:08:11PM +0800, Kunwu Chan wrote:
> > ...
> >
> > > > > > Make it patch series:
> > > > > > 1) patch that introduces exported function called dev_is_amba() (1 patch)
> > > Done.
> > > > > > 2) convert user-by-user (N patches)
> > > I've no idea about how to modify, such as in iommu.c:
> > Oh, crap. Yes, this need more thinking.
> > Anyway, Russell is okay with your initial patch, the rest can be done
> > separately. For now probably we can leave it exported for this only case.
> >
> Anyway, thanks for the suggestion, i'll introduce the dev_is_amba function
>
> and add the Suggested tag for you.
>
> If you have a better idea and need me to do it, you can always contact me.
General policy is not to add stuff that doesn't have any users. From
what I can see from briefly reading this discussion, and looking at
the patches submitted to me, the dev_is_amba() patch adds a helper,
but as yet there are no users - and not even any patches on a mailing
list to make use of this helper. Therefore, I won't be applying that
patch.
Good idea, but it needs users...
Please note that I likely won't be reading further discussion (see
my signature below, and I'm having the same op on the other eye -
which is the only eye suitable for screen work at the moment -
this Friday.)
--
*** please note that I probably will only be occasionally responsive
*** for an unknown period of time due to recent eye surgery making
*** reading quite difficult.
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2024-09-04 13:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-23 6:42 [PATCH] amba: make amba_bustype constant Kunwu Chan
2024-08-23 13:48 ` Andy Shevchenko
2024-08-26 8:20 ` Kunwu Chan
2024-08-26 10:08 ` Kunwu Chan
2024-08-26 10:40 ` Andy Shevchenko
2024-08-27 7:45 ` Kunwu Chan
2024-08-27 13:37 ` Andy Shevchenko
2024-08-28 2:51 ` Kunwu Chan
2024-08-28 13:17 ` Andy Shevchenko
2024-08-29 1:31 ` Kunwu Chan
2024-09-04 13:58 ` Russell King (Oracle) [this message]
2024-09-04 14:07 ` Andy Shevchenko
2024-09-05 8:51 ` Kunwu Chan
2024-08-27 13:46 ` Russell King (Oracle)
2024-08-28 3:00 ` 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=ZthnjPjPB+6cMf9w@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andi.shyti@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=chentao@kylinos.cn \
--cc=gregkh@linuxfoundation.org \
--cc=krzk@kernel.org \
--cc=kunwu.chan@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=suzuki.poulose@arm.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