linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	netdev@vger.kernel.org
Subject: Re: linux-next: Tree for Apr 12
Date: Fri, 13 Apr 2012 13:11:45 +0100	[thread overview]
Message-ID: <20120413131145.1fd00f1d@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <20120412142415.564710b8.akpm@linux-foundation.org>

On Thu, 12 Apr 2012 14:24:15 -0700
Andrew Morton <akpm@linux-foundation.org> wrote:

> On Thu, 12 Apr 2012 14:59:31 +1000
> Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> 
> > I have created today's linux-next tree at
> > git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> 
> This isn't working for me.  Some time between April 3 and April 12
> someone merged something into the non-mm part of linux-next which broke
> ssh.

You are getting further than me  - on 32bit -next of the 12th explodes
with random userspace crashes in init or similar early code.

Alan

  reply	other threads:[~2012-04-13 12:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-12  4:59 linux-next: Tree for Apr 12 Stephen Rothwell
2012-04-12 21:24 ` Andrew Morton
2012-04-13 12:11   ` Alan Cox [this message]
2012-06-04 22:04   ` Andrew Morton
2012-06-04 22:46     ` Eric Paris
2012-06-05  2:42       ` Eric Paris
2012-06-05 19:50         ` Andrew Morton
2013-04-12  6:19 Stephen Rothwell
2016-04-12  4:34 Stephen Rothwell
2017-04-12  7:35 Stephen Rothwell
2018-04-12  3:21 Stephen Rothwell
2019-04-12  8:17 Stephen Rothwell
2020-04-12  3:54 Stephen Rothwell
2021-04-12 13:01 Stephen Rothwell
2022-04-12  5:50 Stephen Rothwell
2023-04-12  4:50 Stephen Rothwell
2024-04-12  7:09 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=20120413131145.1fd00f1d@pyramind.ukuu.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).