From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6399943776789331968 X-Received: by 10.46.8.18 with SMTP id 18mr613990lji.13.1490116968770; Tue, 21 Mar 2017 10:22:48 -0700 (PDT) X-BeenThere: outreachy-kernel@googlegroups.com Received: by 10.46.22.2 with SMTP id w2ls1683348ljd.48.gmail; Tue, 21 Mar 2017 10:22:48 -0700 (PDT) X-Received: by 10.46.8.18 with SMTP id 18mr613988lji.13.1490116968066; Tue, 21 Mar 2017 10:22:48 -0700 (PDT) Return-Path: Received: from mail-lf0-x243.google.com (mail-lf0-x243.google.com. [2a00:1450:4010:c07::243]) by gmr-mx.google.com with ESMTPS id q207si1241503wme.3.2017.03.21.10.22.48 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 21 Mar 2017 10:22:48 -0700 (PDT) Received-SPF: pass (google.com: domain of arushisinghal19971997@gmail.com designates 2a00:1450:4010:c07::243 as permitted sender) client-ip=2a00:1450:4010:c07::243; Authentication-Results: gmr-mx.google.com; dkim=pass header.i=@gmail.com; spf=pass (google.com: domain of arushisinghal19971997@gmail.com designates 2a00:1450:4010:c07::243 as permitted sender) smtp.mailfrom=arushisinghal19971997@gmail.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=gmail.com Received: by mail-lf0-x243.google.com with SMTP id r36so13751966lfi.0 for ; Tue, 21 Mar 2017 10:22:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=IBbniFuJsPQRybWuv2GbsFs/iG3WhWNb+lEYi22ZOHo=; b=jkk6sw6boWNkdU3pT1Hl62smiEZczEh4dA9E59+0+higWjN1Eg8n4NC25646OuW5YH +YuUnVj1QTRv4w/tl1cmzCYdR3orl0OR+aitMMm4YLfXcgtu1hr4pJmEQ7OZqyJwfhav rNgIleQuvzN1PJKgXpMp4CrWM4TRZqEY5HFPfOSz+eV4jE8qsLcpT7tlZEpUf78xamm+ DTfJfuy5nIuUnJKOJ45b5BtZBM9OK3aG9DOGQMBDpzF3rSmRi7IjkvxI+Q6PzsjgdYll A2zYuU6so24T4BsGz3nM1Kx1jo1bE37r9Dhepi7b85M35f/7cy2NIXDeHV91QZh3XIbp T7EQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=IBbniFuJsPQRybWuv2GbsFs/iG3WhWNb+lEYi22ZOHo=; b=gJOEYc9YyO1UgGTsWitmf/+dS6Xa9NeglcxG2yTklH1d2PW11um/tvUWpIxEd3xqPR pr5ysznK4bpIIWxCbKsxjyvJf0pqSP6InvLd9QJv60FCnsOwZdR3b8qo5Ol7J5v+429M dkrxr3LlMLztYCdQ+xuHe59lWRxd28sbkl20VbM6zJKlAyphLzaPTbv2m3UNn5g9bYWa Ec7VC9qTkWyKMrvqalgys0KP5amRuHN4+BrQIUzSvmeZCw/L5SI36r3h73//VjbJdabR SZBCjDimD+nRoxdtGwE6/u6ZV7YK844PYk2Ssx4XqAQ8EFfwhwsy+9dmU/xk2yFNQ6yW XbOw== X-Gm-Message-State: AFeK/H280NAVIQJapjswVvOrPiq1dozcVpHWvFc6Tf7WeIYaBLtpWpsEk7KzzVF88bVQAjdNrb2cV4OEAAR4jg== X-Received: by 10.25.128.87 with SMTP id b84mr4792242lfd.86.1490116967535; Tue, 21 Mar 2017 10:22:47 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.170.69 with HTTP; Tue, 21 Mar 2017 10:22:46 -0700 (PDT) In-Reply-To: <20170321170221.GB2793@d830.WORKGROUP> References: <20170321133021.6737-1-arushisinghal19971997@gmail.com> <20170321160348.GA1859@d830.WORKGROUP> <20170321170221.GB2793@d830.WORKGROUP> From: Arushi Singhal Date: Tue, 21 Mar 2017 22:52:46 +0530 Message-ID: Subject: Re: [Outreachy kernel] [PATCH 0/2] IIO coding tasks To: Alison Schofield Cc: Julia Lawall , Jonathan Cameron , Hartmut Knaack , outreachy-kernel@googlegroups.com, Michael Hennerich , lars@metafoo.de, Greg KH , speakup@linux-speakup.org, driverdevel , linux-kernel@vger.kernel.org, Peter Meerwald-Stadler , linux-iio@vger.kernel.org Content-Type: multipart/alternative; boundary=001a113ebfcc861ba5054b40e47b --001a113ebfcc861ba5054b40e47b Content-Type: text/plain; charset=UTF-8 On Tue, Mar 21, 2017 at 10:32 PM, Alison Schofield 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@gmail.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. 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@googlegroups.com. > > > > To post to this group, send email to > > > outreachy-kernel@googlegroups.com. > > > > To view this discussion on the web visithttps://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@googlegroups.com. > > > To post to this group, send email to outreachy-kernel@googlegroups.com > . > > > To view this discussion on the web visithttps://groups.google. > com/d/msgid/outreachy-kernel/CA%2BXqjF9dVy33Dsv0H2z8x > > > taNeMOW7SQgr4qa4wLwz6xFNVTsUA%40mail.gmail.com. > > > For more options, visit https://groups.google.com/d/optout. > > > > > > > > --001a113ebfcc861ba5054b40e47b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Tue, Mar 21, 2017 at 10:32 PM, Alison Schofield &l= t;amsfield22@gmai= l.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@gmail.com>
> > wrote:
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0On Tue, Mar 21, 2017 at 07:00:17PM +053= 0, Arushi Singhal wrote:
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0> Patchseries of IIO coding tasks > >
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0This wouldn't be a patchset.=C2=A0 = Although they touch the same
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0driver, the changes are unrelated.=C2= =A0 See more below...
> >
> > This I have send as a Patchset because as you have mentioned belo= w 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 change= s and as they
> > should be applied one after other so that's why I have send t= hem as
> > Patchset.
>
> For the IIO patches, it is better to work on the IIO tree, not Greg= 9;s.
> Greg manages staging, not IIO.=C2=A0 The IIO patches should appear in = Greg's
> tree eventually.
>
> julia

We didn't direct applicants to create an iio tree.=C2=A0 At this= point,
it seems more than is necessary.=C2=A0 They can follow the directions in th= e
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 mentio= ned that my [PATCH 2/2] is already being done someone. So how can I make th= e changes of [PATCH 1/2] on top of it as [PATCH 2/2] is not yet applied on = the staging tree.
Please suggest me.
Thanks
=
Arushi
>
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0>
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0> Arushi Singhal (2):
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0staging: ad7759: Repla= ce mlock with driver private lock
> >
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0This one is already been submitted.=C2= =A0 If you have a v2 for it,
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0then v2
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0the original patch.
> >
> > Is it submitted by me only before? And this is not the v2.
> > I have just resed it.
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0staging: iio: ade7759:= Move header content to implementation
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0file
> >
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0This patch is done and applied already.= =C2=A0 See the Coding Task #1
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0notes
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0in the IIO Tasks page.
> >
> > Not at applied I think so.
> > Thanks
> > Arushi
> >
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0alisons
> >
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0>
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0>=C2=A0 drivers/staging/iio/meter/ade7759.c=C2=A0 =C2=A0| 56
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0+++++++++++++++++++++++++++++++++-= -
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0>=C2=A0 drivers/staging/iio/meter/ade7759.h=C2=A0 =C2=A0| 53
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0---------------------------------<= br> > >=C2=A0 =C2=A0 =C2=A0 =C2=A0>=C2=A0 2 files changed, 54 insertio= ns(+), 57 deletions(-)
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0>
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0> --
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0> 2.11.0
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0>
> > > --
> > > You received this message because you are subscribed to the = Google
> > Groups "outreachy-kernel" group.
> > > To unsubscribe from this group and stop receiving emails fro= m it,
> > send an email to outreachy-kernel+unsubscribe@googlegroups.com.<= br> > > > To post to this group, send email to
> > outreachy-ke= rnel@googlegroups.com.
> > > To view this discussion on the web visithttps://groups.google.com/d/msgid/outreac= hy-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 Googl= e Groups
> > "outreachy-kernel" group.
> > To unsubscribe from this group and stop receiving emails from it,= send an
> > email to outreachy-kernel+unsubscribe@googlegroups.com.
> > To post to this group, send email to outreachy-kernel@googlegroups.com.
> > To view this discussion on the web visithttps://groups.google.com/d/msgid/outreachy-= kernel/CA%2BXqjF9dVy33Dsv0H2z8x
> > taNeMOW7SQgr4qa4wLwz6xFNVTsUA%40mail.gmail.com.
> > For more options, visit https://groups.google.com/d/optout.
> >
> >


--001a113ebfcc861ba5054b40e47b--