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 2
Date: Wed, 2 Oct 2013 17:32:46 +0200 [thread overview]
Message-ID: <20131002153245.GA4273@ulmo.nvidia.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1124 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-20131002 tag is also provided for convenience.
No new conflicts today. i386, x86_64 and ARM default configurations did
build fine. Well, the same issue on i.MX is still there, so I added the
patch on top of today's linux-next tree so others won't have to deal
with it. I'm assuming it will make it into the i.MX tree eventually.
One small change, I have removed Joern's bcon tree as per his request.
Furthermore there's now an rr-cache branch in the tree linked to above
which contains an orphaned branch with the resolutions recorded in the
.git/rr-cache directory. There's also a new script Next/rr-cache which
can be used to setup the .git/rr-cache directory from an rr-cache branch
and manage it using git. In a nutshell: it's a wrapper around git with
extra handling for the "init" command.
As I already mentioned, Mark has volunteered to do the linux-next tree
for tomorrow and the day after that. I should be able to resume doing
them on Monday.
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2013-10-02 15:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-02 15:32 Thierry Reding [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-10-02 9:57 linux-next: Tree for Oct 2 Stephen Rothwell
2019-10-02 4:46 Stephen Rothwell
2018-10-02 9:18 Stephen Rothwell
2015-10-02 5:27 Stephen Rothwell
2014-10-02 10:26 Stephen Rothwell
2012-10-02 6:32 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=20131002153245.GA4273@ulmo.nvidia.com \
--to=thierry.reding@gmail.com \
--cc=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).