From: Alison Schofield <amsfield22@gmail.com>
To: outreachy-kernel@googlegroups.com
Subject: Where are your IIO patches
Date: Mon, 20 Mar 2017 15:47:26 -0700 [thread overview]
Message-ID: <20170320224725.GA6223@d830.WORKGROUP> (raw)
This got a bit buried on a thread from Aishwarya, so I'm going to
send as a new message. Aishwarya had some further clean up to do
in the IIO driver just submitted and was wondering when the changed
files would appear in the staging-testing tree.
Jonathan applies the IIO patches to his IIO tree. He periodically
pushes it to Greg's staging tree.
The push|pull is "iminent". If you are wanting to do further work in
a driver you recently submitted to IIO, I suggest waiting until you
see the emails from Greg saying your patch has been applied to
staging-testing. Then you can update your tree and work on top of the
latest/greatest files.
Questions, please ask,
alisons
reply other threads:[~2017-03-20 22:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20170320224725.GA6223@d830.WORKGROUP \
--to=amsfield22@gmail.com \
--cc=outreachy-kernel@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.