From: Mark Brown <broonie@kernel.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: linux-next: Tree for Oct 11
Date: Sat, 12 Oct 2013 18:21:50 +0100 [thread overview]
Message-ID: <20131012172150.GN2443@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 396 bytes --]
Hi all,
I've uploaded today's linux-next tree to the master branch of the
repository below:
git://gitorious.org/thierryreding/linux-next.git
A next-20131011 tag is also provided for convenience.
There was one new conflict which has been reported, each merge builds
fine with x86 allmodconfig. A few cross tree integration fixes are
still being carried but nothing new.
Thanks,
Mark
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2013-10-12 17:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-12 17:21 Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-11 7:00 linux-next: Tree for Oct 11 Stephen Rothwell
2023-10-11 6:25 Stephen Rothwell
2022-10-11 1:49 Stephen Rothwell
2021-10-11 7:37 Stephen Rothwell
2019-10-11 4:05 Stephen Rothwell
2018-10-11 5:23 Stephen Rothwell
2018-10-11 13:27 ` Guenter Roeck
2016-10-11 3:06 Stephen Rothwell
2012-10-11 3:06 Stephen Rothwell
2011-10-11 9:11 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=20131012172150.GN2443@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=thierry.reding@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox