From: Mark Brown <broonie@kernel.org>
To: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: linux-next: Tree for Mar 13
Date: Thu, 13 Mar 2014 18:53:25 +0000 [thread overview]
Message-ID: <20140313185325.GF366@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 214 bytes --]
Hi all,
I've uploaded -next for today. There were no new issues today and no
trees needed reverting. This build has been tested with ARM
multi_v7_defconfig and x86 allmodconfig between each merge.
Thanks,
Mark
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2014-03-13 18:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-13 18:53 Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-13 4:13 linux-next: Tree for Mar 13 Stephen Rothwell
2020-03-13 11:03 Stephen Rothwell
2018-03-13 7:33 Stephen Rothwell
2018-03-13 15:57 ` Mike Snitzer
2018-03-13 17:30 ` Randy Dunlap
2018-03-13 19:52 ` Kees Cook
2018-03-13 20:08 ` Stephen Rothwell
[not found] ` <20180313175205.GA15734@light.dominikbrodowski.net>
2018-03-13 20:48 ` Stephen Rothwell
2015-03-13 6:36 Stephen Rothwell
2013-03-13 5:48 Stephen Rothwell
2012-03-13 9:41 Stephen Rothwell
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=20140313185325.GF366@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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).