From: Lars-Peter Clausen <lars@metafoo.de>
To: "Sharma, Sanjeev" <Sanjeev_Sharma@mentor.com>,
sanjeev sharma <sanjeevsharmaengg@gmail.com>
Cc: "jic23@kernel.org" <jic23@kernel.org>,
gregkh <gregkh@linuxfoundation.org>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
devel <devel@driverdev.osuosl.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging:iio: moved platform_data into include/linux/iio
Date: Mon, 25 Aug 2014 10:08:48 +0200 [thread overview]
Message-ID: <53FAEF10.7010001@metafoo.de> (raw)
In-Reply-To: <FDC088D3B5555644AE135ED28A7ABDE94DF3CC4B@EU-MBX-04.mgc.mentorg.com>
On 08/25/2014 09:17 AM, Sharma, Sanjeev wrote:
> Hello Lars,
>
> As per your suggestion Can I move complete Driver out of staging specially SPI ADC Driver.
Only if they are cleaned up first. All of the drivers that are still in
staging do have issues, otherwise we'd already had moved them. A few of them
are OK codestyle wise, but do have ABI issues which need to be resolved
before they can be moved.
- Lars
>
> Regards
> Sanjeev Sharma
>
> -----Original Message-----
> From: Lars-Peter Clausen [mailto:lars@metafoo.de]
> Sent: Wednesday, August 20, 2014 12:20 PM
> To: sanjeev sharma
> Cc: Sharma, Sanjeev; jic23@kernel.org; gregkh; linux-iio@vger.kernel.org; devel; linux-kernel
> Subject: Re: [PATCH] staging:iio: moved platform_data into include/linux/iio
>
> On 08/20/2014 08:44 AM, sanjeev sharma wrote:
>> Hi,
>>
>> This was the action item(TO-DO). IMO, it make sense to move into
>> include/linux/iio because IIO complete subsystem may take some time.
>
> The code that is in staging is not supposed to 'leak' outside of staging. So either you move the driver as a whole out of staging or leave it there, but do not move individual files of the driver out of staging. The action item is for when the driver is moved out of staging.
>
next prev parent reply other threads:[~2014-08-25 8:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-20 6:41 [PATCH] staging:iio: moved platform_data into include/linux/iio Sanjeev Sharma
2014-08-20 6:36 ` Lars-Peter Clausen
2014-08-20 6:44 ` sanjeev sharma
2014-08-20 6:50 ` Lars-Peter Clausen
2014-08-20 7:02 ` sanjeev sharma
2014-08-20 11:15 ` gregkh
2014-08-21 12:24 ` Sharma, Sanjeev
2014-08-25 7:17 ` Sharma, Sanjeev
2014-08-25 8:08 ` Lars-Peter Clausen [this message]
2014-08-25 11:49 ` Sharma, Sanjeev
2014-08-25 13:32 ` Lars-Peter Clausen
2014-08-26 11:33 ` Sharma, Sanjeev
2014-08-26 17:27 ` Jonathan Cameron
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=53FAEF10.7010001@metafoo.de \
--to=lars@metafoo.de \
--cc=Sanjeev_Sharma@mentor.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sanjeevsharmaengg@gmail.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;
as well as URLs for NNTP newsgroup(s).