From: Greg KH <gregkh@linuxfoundation.org>
To: outreachy-kernel@googlegroups.com
Subject: Yet again the patch queue is empty.
Date: Tue, 27 Oct 2015 17:14:27 +0900 [thread overview]
Message-ID: <20151027081427.GC17198@kroah.com> (raw)
Hi all,
I've gone through all submitted patches, with the exception of the time
change patches, as I'll rely on Arnd to handle them.
If you have not gotten an automated email saying your patch was applied,
please rebased against the staging-testing branch of my staging.git tree
on git.kernel.org and resend it, as it's lost from my patch queue.
thanks,
greg k-h
reply other threads:[~2015-10-27 8:14 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=20151027081427.GC17198@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.