From: gregkh <gregkh@linuxfoundation.org>
To: sanjeev sharma <sanjeevsharmaengg@gmail.com>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
Sanjeev Sharma <sanjeev_sharma@mentor.com>,
jic23@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: Wed, 20 Aug 2014 06:15:37 -0500 [thread overview]
Message-ID: <20140820111537.GA12663@kroah.com> (raw)
In-Reply-To: <CAGUYZuQwKMG0OFt_gJVPTj3EWin68Jg3jzD9T_Rje-UroOCf=g@mail.gmail.com>
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Wed, Aug 20, 2014 at 12:32:52PM +0530, sanjeev sharma wrote:
> Hi,
>
> I have only moved some header files because other header files are already
> present there and these are only pending files which is not moved outside the
> staging directory.
>
> @Greg:What is your though on this ?
Lars-Peter is correct, don't "leak" files from staging. Take the time
to work on fixing up these drivers correctly so they can be moved out of
staging instead of just doing simple file moves which do nothing.
greg k-h
next prev parent reply other threads:[~2014-08-20 11:16 UTC|newest]
Thread overview: 11+ 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
[not found] ` <CAGUYZuSENkSjoA9U0E8MQKp0a1J3moE8p8NYAzfiZ+BpxND4Aw@mail.gmail.com>
2014-08-20 6:50 ` Lars-Peter Clausen
[not found] ` <CAGUYZuQwKMG0OFt_gJVPTj3EWin68Jg3jzD9T_Rje-UroOCf=g@mail.gmail.com>
2014-08-20 11:15 ` gregkh [this message]
2014-08-21 12:24 ` Sharma, Sanjeev
2014-08-25 7:17 ` Sharma, Sanjeev
2014-08-25 8:08 ` Lars-Peter Clausen
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=20140820111537.GA12663@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sanjeev_sharma@mentor.com \
--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