From: Andrew Morton <akpm@linux-foundation.org>
To: David Brownell <david-b@pacbell.net>
Cc: linux-mtd@lists.infradead.org, rjw@sisk.pl, devzero@web.de,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
lenb@kernel.org, greg@kroah.com, linux-ide@vger.kernel.org,
alan@lxorguk.ukuu.org.uk
Subject: Re: some minor issues with 2.6.25-rc6-git7-default
Date: Thu, 27 Mar 2008 13:41:50 -0700 [thread overview]
Message-ID: <20080327134150.5f79dc0b.akpm@linux-foundation.org> (raw)
In-Reply-To: <200803271222.41579.david-b@pacbell.net>
On Thu, 27 Mar 2008 12:22:41 -0700
David Brownell <david-b@pacbell.net> wrote:
> On Tuesday 25 March 2008, Andrew Morton wrote:
> >
> > > > Mar 23 09:17:02 opensuse103 kernel: physmap-flash: probe of physmap-flash.0 failed with error -12
> >
> > There are many physmap-flashes in the tree. __Is this one
> > drivers/mtd/maps/physmap.c?
>
> And there's a regression in mtd/maps/phsymap.c which should
> be resolved before 2.6.25 ships ... on some platforms it
> newly likes to oops on reboot.
I don't appear to have anything which touches physmap.c here.
> I don't have a URL for that patch, but ISTR it's been
> posted both to LKML and to linux-MTD. (That doesn't
> include less-good versions I've seen too.) If needed,
> I can dig it up, but I've been thinking this should have
> a signoff from MTD folk.
Yes, please dig it out and let's look at it.
next prev parent reply other threads:[~2008-03-27 20:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <212011377@web.de>
[not found] ` <200803260010.25327.rjw@sisk.pl>
2008-03-25 23:42 ` some minor issues with 2.6.25-rc6-git7-default Andrew Morton
2008-03-27 19:22 ` David Brownell
2008-03-27 20:41 ` Andrew Morton [this message]
2008-03-27 21:18 ` David Brownell
2008-03-26 19:48 devzero
2008-03-26 20:13 ` Randy Dunlap
2008-03-27 19:16 ` David Brownell
-- strict thread matches above, loose matches on Subject: below --
2008-03-26 20:51 devzero
2008-03-26 21:04 ` Randy Dunlap
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=20080327134150.5f79dc0b.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=david-b@pacbell.net \
--cc=devzero@web.de \
--cc=greg@kroah.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=rjw@sisk.pl \
/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).