From: Tejun Heo <htejun@gmail•com>
To: Benjamin Herrenschmidt <benh@kernel•crashing.org>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
linux-ide@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>,
ppc-dev <linuxppc-dev@ozlabs•org>,
albertl@mail•com, Alan Cox <alan@lxorguk•ukuu.org.uk>
Subject: Re: Oops in pata_pdc2027x
Date: Mon, 11 Dec 2006 22:55:59 +0900 [thread overview]
Message-ID: <457D636F.9020806@gmail.com> (raw)
In-Reply-To: <1165651032.1103.123.camel@localhost.localdomain>
Benjamin Herrenschmidt wrote:
> Could that be related to the fix
>
> [PATCH] libata: fix oops with sparsemem
>
> That Arnd Bergmann just posted ? I'm copying it below in case you
> haven't seen it.
Seems to be the same problem to me. I'll reply in the original thread.
Thanks.
--
tejun
prev parent reply other threads:[~2006-12-11 13:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-05 6:01 Oops in pata_pdc2027x Stephen Rothwell
2006-12-06 6:10 ` Albert Lee
2006-12-06 6:21 ` Stephen Rothwell
2006-12-07 3:56 ` Albert Lee
2006-12-07 6:16 ` Stephen Rothwell
2006-12-09 7:57 ` Benjamin Herrenschmidt
2006-12-11 13:55 ` Tejun Heo [this message]
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=457D636F.9020806@gmail.com \
--to=htejun@gmail$(echo .)com \
--cc=alan@lxorguk$(echo .)ukuu.org.uk \
--cc=albertl@mail$(echo .)com \
--cc=benh@kernel$(echo .)crashing.org \
--cc=linux-ide@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
/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