linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: linux-next@vger.kernel.org
Cc: Thierry Reding <thierry.reding@gmail.com>, linux-kernel@vger.kernel.org
Subject: linux-next: Tree for Oct 4
Date: Sat, 5 Oct 2013 23:44:54 +0100	[thread overview]
Message-ID: <20131005224454.GA21581@sirena.org.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 392 bytes --]

Hi all,

Better late than never 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-20131004 tag is also provided for convenience.

Each merge was tested with x86_664 allyesconfig.  A few new conflicts
and build test failures came up along the way - these have all been
reported.

Thanks,
Mark

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

             reply	other threads:[~2013-10-05 22:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-05 22:44 Mark Brown [this message]
2013-10-06 18:13 ` linux-next: Tree for Oct 4 Guenter Roeck
  -- strict thread matches above, loose matches on Subject: below --
2023-10-04  5:21 Stephen Rothwell
2022-10-04 11:05 Stephen Rothwell
2019-10-04  5:59 Stephen Rothwell
2018-10-04  8:34 Stephen Rothwell
2018-10-04 13:46 ` Guenter Roeck
2018-10-04 14:21   ` Geert Uytterhoeven
2018-10-04 23:44     ` Stephen Rothwell
2018-10-05  1:33       ` Guenter Roeck
     [not found]         ` <01c4a73c-7901-2fbb-8f87-95ff21dc5126-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2018-10-05  5:39           ` Stephen Rothwell
     [not found]             ` <20181005153905.126a005e-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2018-10-05 14:27               ` Alexander Duyck
2016-10-04  3:56 Stephen Rothwell
2016-10-04  4:22 ` Stephen Rothwell
2012-10-04  5:33 Stephen Rothwell
2011-10-04  8: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=20131005224454.GA21581@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).