From: Madhumitha Prabakaran <madhumithabiw@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Michael Hennerich <Michael.Hennerich@analog.com>,
linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org
Cc: Lars-Peter Clausen <lars@metafoo.de>,
linux-staging@lists.linux.dev, skhan@linuxfoundation.org,
ivan.orlov0322@gmail.com
Subject: Re: [PATCH] Add struct ad9832_platform_data to the include/linux/iio
Date: Sun, 9 Jul 2023 18:40:20 -0500 [thread overview]
Message-ID: <52f47b43-e735-0be9-ebac-e6e099a2dd09@gmail.com> (raw)
In-Reply-To: <20230708154506.01785c65@jic23-huawei>
On 7/8/23 09:45, Jonathan Cameron wrote:
> On Sat, 8 Jul 2023 13:10:29 +0200
> Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
>
>> On Fri, Jul 07, 2023 at 04:15:53PM -0500, Madhumitha Prabakaran wrote:
>>> Add struct ad9832_platform_data to the include/linux/iio
>>> for maintaining code organization and clarity.
>>>
>>> Signed-off-by: Madhumitha Prabakaran <madhumithabiw@gmail.com>
>>> ---
>>> drivers/staging/iio/frequency/ad9832.c | 3 +--
>>> drivers/staging/iio/frequency/ad9832.h | 34 --------------------------
>>> include/linux/iio/frequency/ad9832.h | 30 +++++++++++++++++++++++
>> No, not yet, sorry. Staging drivers should be self-contained, why does
>> this .c file need a .h file at all anyway? It should all just be in the
>> .c file, can you do that instead?
> This is an aged driver so still has definitions that would be included
> from board files, hence the header.
>
> So Madhumitha, if you are looking at getting this driver out of staging
> (which would be great!) then first job is convert it from platform data
> to device tree (or better yet generic firmware bindings using linux/property.h)
Sure, I will take a look and work on convert it from platform data to
generic
firmware bindings.
> A side effect of that is the header would go away as equivalent job would be
> done by the dt-bindings yaml file.
>
> Jonathan
>
>> thanks,
>>
>> greg k-h
prev parent reply other threads:[~2023-07-09 23:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 21:15 [PATCH] Add struct ad9832_platform_data to the include/linux/iio Madhumitha Prabakaran
2023-07-08 11:10 ` Greg Kroah-Hartman
2023-07-08 14:45 ` Jonathan Cameron
2023-07-09 23:40 ` Madhumitha Prabakaran [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=52f47b43-e735-0be9-ebac-e6e099a2dd09@gmail.com \
--to=madhumithabiw@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=gregkh@linuxfoundation.org \
--cc=ivan.orlov0322@gmail.com \
--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=skhan@linuxfoundation.org \
/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