[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <10EF084D-7EC6-493D-98D1-26B70E67771D@jic23.retrosnub.co.uk>
Date: Tue, 21 Mar 2017 17:57:22 +0000
From: Jonathan Cameron <jic23@...23.retrosnub.co.uk>
To: Julia Lawall <julia.lawall@...6.fr>,
Arushi Singhal <arushisinghal19971997@...il.com>
CC: Alison Schofield <amsfield22@...il.com>,
Jonathan Cameron <jic23@...nel.org>,
Hartmut Knaack <knaack.h@....de>,
outreachy-kernel@...glegroups.com,
Michael Hennerich <Michael.Hennerich@...log.com>,
lars@...afoo.de, Greg KH <gregkh@...uxfoundation.org>,
speakup@...ux-speakup.org,
driverdevel <devel@...verdev.osuosl.org>,
linux-kernel@...r.kernel.org,
Peter Meerwald-Stadler <pmeerw@...erw.net>,
linux-iio@...r.kernel.org
Subject: Re: [Outreachy kernel] [PATCH 0/2] IIO coding tasks
On 21 March 2017 17:27:02 GMT+00:00, Julia Lawall <julia.lawall@...6.fr> wrote:
>
>
>On Tue, 21 Mar 2017, Arushi Singhal wrote:
>
>>
>>
>> On Tue, Mar 21, 2017 at 10:32 PM, Alison Schofield
><amsfield22@...il.com>
>> wrote:
>> On Tue, Mar 21, 2017 at 05:39:38PM +0100, Julia Lawall wrote:
>> >
>> >
>> > On Tue, 21 Mar 2017, Arushi Singhal wrote:
>> >
>> > > On Tue, Mar 21, 2017 at 9:33 PM, Alison Schofield
>> <amsfield22@...il.com>
>> > > wrote:
>> > > On Tue, Mar 21, 2017 at 07:00:17PM +0530, Arushi
>> Singhal wrote:
>> > > > Patchseries of IIO coding tasks
>> > >
>> > > This wouldn't be a patchset. Although they touch the
>> same
>> > > driver, the changes are unrelated. See more below...
>> > >
>> > > This I have send as a Patchset because as you have
>mentioned
>> below that the
>> > > [PATCH 2/2] was already done before by someone but I think
>> so it is not yet
>> > > applied in the Greg's tree yet.So I have done both the
>> changes and as they
>> > > should be applied one after other so that's why I have send
>> them as
>> > > Patchset.
>> >
>> > For the IIO patches, it is better to work on the IIO tree,
>not
>> Greg's.
>> > Greg manages staging, not IIO. The IIO patches should appear
>> in Greg's
>> > tree eventually.
>> >
>> > julia
>>
>> We didn't direct applicants to create an iio tree. At this
>> point,
>> it seems more than is necessary. They can follow the
>directions
>> in the
>> task descriptions and avoid the collisions.
>>
>> Of course, they are welcome to create a tree to iio/testing.
>>
>> (IMHO it's more overhead/busy work and maybe not the best use
>> of time in the home stretch of the application period.)
>>
>> alisons
>>
>>
>> Hi Alison
>> As you have mentioned that my [PATCH 2/2] is already being done
>someone. So
>> how can I make the changes of [PATCH 1/2] on top of it as [PATCH 2/2]
>is not
>> yet applied on the staging tree.
>
>Make a patch that applies to the current state of the IIO tree. Just
>clone that one like you cloned the staging one.
>
>julia
>
Slight amendment,. Normally would be the togreg branch which doesn't rebase.
With all the current churn might be best to use the testing branch and i will fix up any issues if i
have to rebase as result of build tests.
Will.send Greg a pull later anyway, so should be less difference after he pulls that.
J
>> Please suggest me.
>> Thanks
>> Arushi
>> >
>> > > >
>> > > > Arushi Singhal (2):
>> > > > staging: ad7759: Replace mlock with driver
>private
>> lock
>> > >
>> > > This one is already been submitted. If you have a v2
>> for it,
>> > > then v2
>> > > the original patch.
>> > >
>> > > Is it submitted by me only before? And this is not the v2.
>> > > I have just resed it.
>> > > > staging: iio: ade7759: Move header content to
>> implementation
>> > > file
>> > >
>> > > This patch is done and applied already. See the
>> Coding Task #1
>> > > notes
>> > > in the IIO Tasks page.
>> > >
>> > > Not at applied I think so.
>> > > Thanks
>> > > Arushi
>> > >
>> > > alisons
>> > >
>> > > >
>> > > > drivers/staging/iio/meter/ade7759.c | 56
>> > > +++++++++++++++++++++++++++++++++--
>> > > > drivers/staging/iio/meter/ade7759.h | 53
>> > > ---------------------------------
>> > > > 2 files changed, 54 insertions(+), 57 deletions(-)
>> > > >
>> > > > --
>> > > > 2.11.0
>> > > >
>> > > > --
>> > > > You received this message because you are subscribed to
>> the Google
>> > > Groups "outreachy-kernel" group.
>> > > > To unsubscribe from this group and stop receiving emails
>> from it,
>> > > send an email to
>> outreachy-kernel+unsubscribe@...glegroups.com.
>> > > > To post to this group, send email to
>> > > outreachy-kernel@...glegroups.com.
>> > > > To view this discussion on the
>webvisithttps://groups.google.com/d/msgid/outreachy-kernel/20170321133021.6737
>> -1-ar
>> > > ushisinghal19971997%40gmail.com.
>> > > > For more options, visit
>> https://groups.google.com/d/optout.
>> > >
>> > >
>> > > --
>> > > You received this message because you are subscribed to the
>> Google Groups
>> > > "outreachy-kernel" group.
>> > > To unsubscribe from this group and stop receiving emails
>> from it, send an
>> > > email to outreachy-kernel+unsubscribe@...glegroups.com.
>> > > To post to this group, send email to
>> outreachy-kernel@...glegroups.com.
>> > > To view this discussion on the
>webvisithttps://groups.google.com/d/msgid/outreachy-kernel/CA%2BXqjF9dVy33Dsv0
>> H2z8x
>> > > taNeMOW7SQgr4qa4wLwz6xFNVTsUA%40mail.gmail.com.
>> > > For more options, visit https://groups.google.com/d/optout.
>> > >
>> > >
>>
>>
>>
>>
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Powered by blists - more mailing lists