From: Lee Jones <lee@kernel.org>
To: Naresh Solanki <naresh.solanki@9elements.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] mfd: max5970: Rename driver and remove wildcard
Date: Mon, 22 May 2023 08:11:43 +0100 [thread overview]
Message-ID: <20230522071143.GO404509@google.com> (raw)
In-Reply-To: <14badbda-9f27-bd5d-bd59-5515c9824886@9elements.com>
On Thu, 18 May 2023, Naresh Solanki wrote:
> Hi Lee,
>
> On 18-05-2023 03:44 pm, Lee Jones wrote:
> > On Thu, 27 Apr 2023, Naresh Solanki wrote:
> >
> > > The previous version of this driver included wildcards in file names
> > > and descriptions. This patch renames the driver to only support MAX5970
> > > and MAX5978, which are the only chips that the driver actually supports.
> >
> > So multiple devices are supported:
> >
> > MAX5970 ... AND
> > MAX5978 ... thus
> > MAX597X ... does make sense, no?
> > What are you trying to achieve?
> Understood. It is important to note that there are indeed other unrelated
> chips in addition to MAX5970 and MAX5978. Examples include MAX5971, which is
> a Single-Port, 40W, IEEE 802.3af/at PSE Controller with Integrated MOSFET,
> and MAX5974A, an Active-Clamped, Spread-Spectrum, Current-Mode PWM
> Controller, among others.
>
> With this change, the intention is to be specific about the chips the driver
> supports. Instead of using wildcards or a broad "MAX597X" designation, the
> patch aims to exclusively support the MAX5970 and MAX5978 chips.
It's a tricky situation when engineers/marketing people name devices in
a nonsensical manner. However, "max5970" just as misleading in this
context as "max597x", thus the patch doesn't improve anything. It's
more of a maneuver side-ways.
> > > Signed-off-by: Naresh Solanki <Naresh.Solanki@9elements.com>
> > > ---
> > > drivers/mfd/Kconfig | 4 ++--
> > > drivers/mfd/simple-mfd-i2c.c | 18 +++++++++---------
> > > include/linux/mfd/{max597x.h => max5970.h} | 16 ++++++++--------
> > > 3 files changed, 19 insertions(+), 19 deletions(-)
> > > rename include/linux/mfd/{max597x.h => max5970.h} (92%)
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2023-05-22 7:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 11:30 [PATCH 1/2] mfd: max5970: Rename driver and remove wildcard Naresh Solanki
2023-04-27 11:30 ` [PATCH 2/2] regulator: " Naresh Solanki
2023-04-30 15:58 ` Mark Brown
2023-06-02 8:15 ` Lee Jones
2023-05-04 10:05 ` [PATCH 1/2] mfd: " Naresh Solanki
2023-05-10 13:46 ` Lee Jones
2023-05-18 10:14 ` Lee Jones
2023-05-18 13:44 ` Naresh Solanki
2023-05-22 7:11 ` Lee Jones [this message]
2023-05-24 9:53 ` Naresh Solanki
2023-06-08 17:57 ` [GIT PULL] Immutable branch between MFD and Regulator due for the v6.5 merge window Lee Jones
-- strict thread matches above, loose matches on Subject: below --
2023-04-27 10:22 [PATCH 1/2] mfd: max5970: Rename driver and remove wildcard Naresh Solanki
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=20230522071143.GO404509@google.com \
--to=lee@kernel.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=naresh.solanki@9elements.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.