linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sedat Dilek <sedat.dilek@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: linux-next <linux-next@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Mark Brown <broonie@kernel.org>
Subject: Re: linux-next: Tree for Oct 23
Date: Thu, 24 Oct 2013 09:20:53 +0200	[thread overview]
Message-ID: <CA+icZUUUauzttknp3nK=hE=88gHrz6aC8AsbYR2W_1Uqo8nz8g@mail.gmail.com> (raw)
In-Reply-To: <1382541202-6614-1-git-send-email-treding@nvidia.com>

On Wed, Oct 23, 2013 at 5:13 PM, Thierry Reding
<thierry.reding@gmail.com> wrote:
> 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
>

WebGit URL?

Browsing "https://gitorious.org/thierryreding" gives me a...

"This Git object is too large to be displayed in the browser

Consider cloning the repository locally and look at the object there"

Thierry, you were talking about moving to a <kernel.org> address, what happened?

- Sedat -


> A next-20131023 tag is also provided for convenience.
>
> No new conflicts. I've fixed various build failures, so 32-bit and 64-bit
> allmodconfigs build fine on x86. ARM and x86 default configurations also
> build fine. Most of the patches to fix the build failures have been sent
> to the respective maintainers.
>
> Thierry
> --
> To unsubscribe from this list: send the line "unsubscribe linux-next" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2013-10-24  7:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-23 15:13 linux-next: Tree for Oct 23 Thierry Reding
2013-10-23 20:01 ` Guenter Roeck
2013-10-24  7:20 ` Sedat Dilek [this message]
2013-10-24  7:41   ` Thierry Reding
  -- strict thread matches above, loose matches on Subject: below --
2023-10-23  5:58 Stephen Rothwell
2020-10-23  2:34 Stephen Rothwell
2019-10-23  4:55 Stephen Rothwell
2019-10-23  6:05 ` Shaokun Zhang
2019-10-23  6:44   ` Geert Uytterhoeven
2019-10-23  6:56     ` Randy Dunlap
2019-10-23  6:57     ` Shaokun Zhang
2019-10-23 15:46   ` Mark Salyzyn
2019-10-23 20:45     ` Stephen Rothwell
2014-10-23  4:21 Stephen Rothwell
2014-10-23 12:47 ` Stephen Rothwell
2012-10-23  4:19 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='CA+icZUUUauzttknp3nK=hE=88gHrz6aC8AsbYR2W_1Uqo8nz8g@mail.gmail.com' \
    --to=sedat.dilek@gmail.com \
    --cc=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).