From: Tudor Gheorghiu <tudor.reda@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: "Nam Cao" <namcao@linutronix.de>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
linux-iio@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org, "Nuno Sá" <nuno.sa@analog.com>
Subject: Re: [PATCH] staging: iio: frequency: rename macros
Date: Mon, 7 Oct 2024 18:46:05 +0300 [thread overview]
Message-ID: <ZwQCPY7tmMg7ciVZ@redaops> (raw)
In-Reply-To: <20241006122712.2cff065c@jic23-huawei>
On Sun, Oct 06, 2024 at 12:27:12PM +0100, Jonathan Cameron wrote:
>
> Hmm. If you really want to clean this up, then these macros shouldn't
> exist at all. They are legacy of ancient IIO code style and some slightly
> ropey code even then (which is why it's in staging!)
>
> Right option is to use the read_raw callbacks in conjunction with the
> info_mask_* bitmaps that indicate which attributes the IIO core should create.
> There are some corners in here such as PHASESYMBOL for which we've
> never fixed on an ABI and that might need custom attributes, but even
> then these macros probably wouldn't be involved.
>
Hi Jonathan!
Thank you so much for your input!
I understand, so this is not as simple as just renaming the macros,
there is actually a lot more to modify in order to make this driver up
to date with modern standards. I will leave this for the original driver
developers.
> So I'd don't mind 'fixing' checkpatch or the code, but I'd
> rather we fixed the drivers up properly.
As for this, it is somewhat unrelated to the actual driver (I didn't
even consider this initially). That is why I submitted a different patch:
https://lore.kernel.org/all/20241002133418.7924-2-tudor.reda@gmail.com/
Thanks again,
Tudor
prev parent reply other threads:[~2024-10-07 15:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 20:24 [PATCH] staging: iio: frequency: rename macros Tudor Gheorghiu
2024-10-01 22:54 ` Nam Cao
2024-10-02 2:49 ` Tudor Gheorghiu
2024-10-02 6:06 ` Nam Cao
2024-10-06 11:27 ` Jonathan Cameron
2024-10-07 15:46 ` Tudor Gheorghiu [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=ZwQCPY7tmMg7ciVZ@redaops \
--to=tudor.reda@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=namcao@linutronix.de \
--cc=nuno.sa@analog.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