From: Greg KH <gregkh@linuxfoundation.org>
To: outreachy-kernel@googlegroups.com
Subject: Caught up on Outreachy patches again
Date: Sun, 9 Oct 2016 17:29:29 +0200 [thread overview]
Message-ID: <20161009152929.GA29937@kroah.com> (raw)
Hi all,
I've now caught up on all submitted outreachy kernel patches, with the
exception of a few iio patches that I think the iio maintainer will be
reviewing and handling in a few days.
If I have missed anything that anyone has submitted (i.e. you did not
either get an email from my patch system saying the patch was applied,
or an email from a reviewer saying something needed to be fixed), please
consider the patch lost and resend it.
thanks,
greg k-h
next reply other threads:[~2016-10-09 15:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-09 15:29 Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-03-09 18:41 Caught up on Outreachy patches, again Greg KH
2017-03-12 14:31 Greg KH
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=20161009152929.GA29937@kroah.com \
--to=gregkh@linuxfoundation.org \
--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.