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 17
Date: Fri, 18 Oct 2013 01:38:47 +0100 [thread overview]
Message-ID: <20131018003847.GH2443@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 337 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-20131017 tag is also provided for convenience.
One new conflict today but otherwise uneventful. x86_64 allmodconfigs
build after each merge but no other build tests were done.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2013-10-18 0:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 0:38 Mark Brown [this message]
2013-10-18 7:45 ` linux-next: Tree for Oct 17 Olof Johansson
2013-10-18 8:22 ` Thierry Reding
2013-10-18 16:22 ` Kevin Hilman
2013-10-18 17:01 ` Kevin Hilman
2013-10-18 17:55 ` Olof Johansson
2013-10-18 11:33 ` Guenter Roeck
2013-10-18 18:08 ` linux-next: Tree for Oct 17 (pinctrl-single.c) Randy Dunlap
2013-10-18 19:43 ` Linus Walleij
2013-10-18 23:39 ` Tony Lindgren
2013-10-18 23:41 ` Randy Dunlap
2013-10-18 23:49 ` Tony Lindgren
2013-10-19 0:39 ` Tony Lindgren
2013-10-19 0:41 ` Randy Dunlap
2013-10-18 18:14 ` linux-next: Tree for Oct 17 (drm: panel-simple) Randy Dunlap
-- strict thread matches above, loose matches on Subject: below --
2023-10-17 4:12 linux-next: Tree for Oct 17 Stephen Rothwell
2022-10-17 1:22 Stephen Rothwell
2019-10-17 4:26 Stephen Rothwell
2018-10-17 6:06 Stephen Rothwell
2016-10-17 2:09 Stephen Rothwell
2014-10-17 3:34 Stephen Rothwell
2012-10-17 2:43 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=20131018003847.GH2443@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;
as well as URLs for NNTP newsgroup(s).