public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Greg KH <greg@kroah•com>
Cc: Kay Sievers <kay.sievers@vrfy•org>,
	Sachin Sant <sachinp@in•ibm.com>,
	linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>,
	Heiko Carstens <heiko.carstens@de•ibm.com>,
	linux-s390@vger•kernel.org
Subject: Re: [-next Jan 18] Boot failure on s390 with DEVTMPFS=y
Date: Wed, 20 Jan 2010 10:49:16 +1100	[thread overview]
Message-ID: <20100120104916.e1a2653e.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20100119211422.GA10319@kroah.com>

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

Hi Greg,

On Tue, 19 Jan 2010 13:14:22 -0800 Greg KH <greg@kroah•com> wrote:
>
> On Mon, Jan 18, 2010 at 03:31:09PM +0100, Kay Sievers wrote:
> > 
> > Heiko Carstens posted a simple patch to work around the issue that
> > s390 write-protects the string, the option parser tries to modify.
> > When Greg has pick it up, this should be fixed.
> 
> Yes, I've now queued it up in my trees.

Great.  Another one bites the dust :-)
-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/

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

  reply	other threads:[~2010-01-19 23:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-18  8:57 linux-next: Tree for January 18 Stephen Rothwell
2010-01-18 14:21 ` [-next Jan 18] Boot failure on s390 with DEVTMPFS=y Sachin Sant
2010-01-18 14:31   ` Kay Sievers
2010-01-19 21:14     ` Greg KH
2010-01-19 23:49       ` Stephen Rothwell [this message]
2010-01-18 23:44 ` linux-next: Tree for January 18 (pci + pm) Randy Dunlap
2010-01-19 23:04   ` Rafael J. Wysocki
2010-01-20  4:39     ` Jesse Barnes
2010-01-20  5:20       ` Stephen Rothwell
2010-01-20 16:53     ` Randy Dunlap
2010-01-28 16:33     ` Randy Dunlap
2010-01-28 19:04       ` Jesse Barnes

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=20100120104916.e1a2653e.sfr@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=greg@kroah$(echo .)com \
    --cc=heiko.carstens@de$(echo .)ibm.com \
    --cc=kay.sievers@vrfy$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=linux-s390@vger$(echo .)kernel.org \
    --cc=sachinp@in$(echo .)ibm.com \
    /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