From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: chenweilong <chenweilong@huawei.com>
Cc: yangyicong@hisilicon.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, wsa@kernel.org,
f.fainelli@gmail.com, jarkko.nikula@linux.intel.com,
jdelvare@suse.de, william.zhang@broadcom.com, jsd@semihalf.com,
conor.dooley@microchip.com, phil.edworthy@renesas.com,
tharunkumar.pasumarthi@microchip.com, semen.protsenko@linaro.org,
kfting@nuvoton.com, linux-i2c@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH next v9 1/4] i2c: hisi: Add initial device tree support
Date: Tue, 1 Nov 2022 16:43:31 +0200 [thread overview]
Message-ID: <Y2Ewk5i/PAS87fa8@smile.fi.intel.com> (raw)
In-Reply-To: <d96beadb-5693-6c73-8fee-3ac3b4cb9a44@huawei.com>
On Tue, Nov 01, 2022 at 03:23:29PM +0800, chenweilong wrote:
> On 2022/10/31 23:42, Andy Shevchenko wrote:
...
> Thanks very much for your detailed explanation.
You're welcome!
> By the way, is it valuable to make a cleanup for the legacy not-up-to-dated drivers?
>
> There's lots of of_match_ptr or ACPI_PTR...
Not on per se basis, only if there is a series which does something more useful
than that. E.g. enabling PRP0001 trick for discrete component drivers that may
be used on more than a single architecture.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2022-11-01 14:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-29 11:59 [PATCH next v9 1/4] i2c: hisi: Add initial device tree support Weilong Chen
2022-10-29 11:59 ` [PATCH next v9 2/4] dt-bindings: i2c: add entry for hisilicon,ascend910-i2c Weilong Chen
2022-10-30 22:01 ` [PATCH next v9 1/4] i2c: hisi: Add initial device tree support Andy Shevchenko
2022-10-31 1:57 ` chenweilong
2022-10-31 15:42 ` Andy Shevchenko
2022-11-01 7:23 ` chenweilong
2022-11-01 14:43 ` 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=Y2Ewk5i/PAS87fa8@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=chenweilong@huawei.com \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=jdelvare@suse.de \
--cc=jsd@semihalf.com \
--cc=kfting@nuvoton.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phil.edworthy@renesas.com \
--cc=robh+dt@kernel.org \
--cc=semen.protsenko@linaro.org \
--cc=tharunkumar.pasumarthi@microchip.com \
--cc=william.zhang@broadcom.com \
--cc=wsa@kernel.org \
--cc=yangyicong@hisilicon.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.