From: "George Spelvin" <linux@sciencehorizons.net>
To: geert@linux-m68k.org, linux@sciencehorizons.net
Cc: arnd@arndb.de, bot@kernelci.org,
kernel-build-reports@lists.linaro.org,
linux-kernel@vger.kernel.org
Subject: Re: next build: 143 builds: 1 failed, 142 passed, 1 error, 22 warnings (next-20160801)
Date: 4 Aug 2016 10:49:01 -0400 [thread overview]
Message-ID: <20160804144901.12765.qmail@ns.sciencehorizons.net> (raw)
In-Reply-To: <CAMuHMdWwN_fbLwBvHqndawKvwVDUeZ=MbQAaeHLaEUchnhetBQ@mail.gmail.com>
> As these patches were meant for generic non-m68k code, I didn't plan
> to take them through my tree.
Well, that explains everything. Sorry for letting it fall through the
cracks. I assumed that since you send pull requests to Linus regularly,
you'd send it directly.
That's why I only acked the patch rather than did anything with it.
So, who wants to send it now?
next prev parent reply other threads:[~2016-08-04 14:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <579ee2e6.68adc20a.8208b.b5be@mx.google.com>
2016-08-01 13:17 ` Arnd Bergmann
2016-08-01 13:36 ` Mark Brown
2016-08-01 14:57 ` George Spelvin
2016-08-04 13:36 ` Geert Uytterhoeven
2016-08-04 14:49 ` George Spelvin [this message]
2016-08-04 14:58 ` Geert Uytterhoeven
2016-08-02 18:55 ` Kevin Hilman
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=20160804144901.12765.qmail@ns.sciencehorizons.net \
--to=linux@sciencehorizons.net \
--cc=arnd@arndb.de \
--cc=bot@kernelci.org \
--cc=geert@linux-m68k.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®