From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: linux-sh@vger.kernel.org
Subject: Re: Suggested patches for merging
Date: Thu, 23 Jul 2020 17:56:24 +0000 [thread overview]
Message-ID: <113e68d5-f322-ca48-0fd3-659161e94fa9@physik.fu-berlin.de> (raw)
In-Reply-To: <8538a950-8e21-29c7-dd0e-fa6e49e2bcef@physik.fu-berlin.de>
Hi Rich!
On 7/23/20 7:52 PM, Rich Felker wrote:
> Have you checked my for-next? It already has all of these except the
> new seccomp series.
I haven't checked yet as last time I did a check-out the connection
was rather slow to me.
Might be better if you get a tree on kernel.org.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2020-07-23 17:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 7:11 Suggested patches for merging John Paul Adrian Glaubitz
2020-07-21 3:16 ` Rich Felker
2020-07-23 12:34 ` John Paul Adrian Glaubitz
2020-07-23 17:52 ` Rich Felker
2020-07-23 17:56 ` John Paul Adrian Glaubitz [this message]
2020-07-23 18:02 ` Rich Felker
2020-07-23 18:04 ` John Paul Adrian Glaubitz
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=113e68d5-f322-ca48-0fd3-659161e94fa9@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=linux-sh@vger.kernel.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).