From: Arushi Singhal <arushisinghal19971997@gmail.com>
To: Alison Schofield <amsfield22@gmail.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
Hartmut Knaack <knaack.h@gmx.de>,
outreachy-kernel@googlegroups.com,
Michael Hennerich <Michael.Hennerich@analog.com>,
lars@metafoo.de, Greg KH <gregkh@linuxfoundation.org>,
speakup@linux-speakup.org,
driverdevel <devel@driverdev.osuosl.org>,
linux-kernel@vger.kernel.org,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
linux-iio@vger.kernel.org
Subject: Re: [Outreachy kernel] [PATCH 0/2] IIO coding tasks
Date: Tue, 21 Mar 2017 22:06:36 +0530 [thread overview]
Message-ID: <CA+XqjF9dVy33Dsv0H2z8xtaNeMOW7SQgr4qa4wLwz6xFNVTsUA@mail.gmail.com> (raw)
In-Reply-To: <20170321160348.GA1859@d830.WORKGROUP>
[-- Attachment #1: Type: text/plain, Size: 1917 bytes --]
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.
> >
> > 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 visit https://groups.google.com/d/
> msgid/outreachy-kernel/20170321133021.6737-1-
> arushisinghal19971997%40gmail.com.
> > For more options, visit https://groups.google.com/d/optout.
>
[-- Attachment #2: Type: text/html, Size: 3444 bytes --]
next prev parent reply other threads:[~2017-03-21 16:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 13:30 [PATCH 0/2] IIO coding tasks Arushi Singhal
2017-03-21 13:30 ` [PATCH 1/2] staging: ad7759: Replace mlock with driver private lock Arushi Singhal
2017-03-21 13:30 ` [PATCH 2/2] staging: iio: ade7759: Move header content to implementation file Arushi Singhal
2017-03-21 16:03 ` [Outreachy kernel] [PATCH 0/2] IIO coding tasks Alison Schofield
2017-03-21 16:36 ` Arushi Singhal [this message]
2017-03-21 16:39 ` Julia Lawall
2017-03-21 17:02 ` Alison Schofield
2017-03-21 17:09 ` Julia Lawall
2017-03-21 17:22 ` Arushi Singhal
2017-03-21 17:27 ` Julia Lawall
2017-03-21 17:57 ` Jonathan Cameron
2017-03-21 17:33 ` Alison Schofield
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=CA+XqjF9dVy33Dsv0H2z8xtaNeMOW7SQgr4qa4wLwz6xFNVTsUA@mail.gmail.com \
--to=arushisinghal19971997@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=amsfield22@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=outreachy-kernel@googlegroups.com \
--cc=pmeerw@pmeerw.net \
--cc=speakup@linux-speakup.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;
as well as URLs for NNTP newsgroup(s).