From: Thierry Reding <thierry.reding@gmail•com>
To: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Cc: Mark Brown <broonie@kernel•org>
Subject: linux-next: Tree for Oct 9
Date: Wed, 9 Oct 2013 16:14:22 +0200 [thread overview]
Message-ID: <1381328067-1593-1-git-send-email-treding@nvidia.com> (raw)
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-20131009 tag is also provided for convenience.
Gained a few conflicts, but nothing too exciting. x86, ARM, PowerPC and
MIPS default configurations build fine. There were some build failures
unrelated to the merge, most of which I fixed and added as patches on
top of the final merge.
Thierry
next reply other threads:[~2013-10-09 14:14 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-09 14:14 Thierry Reding [this message]
2013-10-09 14:14 ` [PATCH] ipv6: Unbreak build Thierry Reding
2013-10-09 14:41 ` Eric Dumazet
2013-10-10 10:48 ` Thierry Reding
2013-10-09 14:14 ` linux-next: manual merge of the clk tree Thierry Reding
2013-10-09 14:14 ` linux-next: manual merge of the drm-intel tree Thierry Reding
2013-10-09 14:14 ` linux-next: manual merge of the imx-mxs tree Thierry Reding
2013-10-09 16:56 ` Fabio Estevam
2013-10-09 14:14 ` linux-next: manual merge of the mvebu tree Thierry Reding
2013-10-09 14:21 ` Jason Cooper
2013-10-09 14:37 ` Jason Cooper
2013-10-10 10:57 ` Thierry Reding
2013-10-10 11:40 ` Jason Cooper
2013-10-09 15:29 ` linux-next: Tree for Oct 9 Guenter Roeck
2013-10-09 15:44 ` Guenter Roeck
2013-10-09 17:55 ` Guenter Roeck
-- strict thread matches above, loose matches on Subject: below --
2025-10-09 11:45 Mark Brown
2024-10-09 7:20 Stephen Rothwell
2024-10-09 9:04 ` Aithal, Srikanth
2024-10-09 9:14 ` Aithal, Srikanth
2023-10-09 5:17 Stephen Rothwell
2020-10-09 9:14 Stephen Rothwell
2019-10-09 5:09 Stephen Rothwell
2018-10-09 8:02 Stephen Rothwell
2018-10-10 0:50 ` Guenter Roeck
2015-10-09 6:24 Stephen Rothwell
2014-10-09 7:11 Stephen Rothwell
2012-10-09 3: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=1381328067-1593-1-git-send-email-treding@nvidia.com \
--to=thierry.reding@gmail$(echo .)com \
--cc=broonie@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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