From: Randy Dunlap <randy.dunlap@oracle.com>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
hsweeten@visionengravers.com, linux-mtd@lists.infradead.org,
Kernel Testers List <kernel-testers@vger.kernel.org>,
dwmw2@infradead.org, Maciej Rutecki <maciej.rutecki@gmail.com>
Subject: Re: [Bug #15729] BUG: physmap modprobe & rmmod
Date: Mon, 19 Apr 2010 21:58:37 -0700 [thread overview]
Message-ID: <20100419215837.d4a9b01d.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20100420045301.GF19957@pengutronix.de>
On Tue, 20 Apr 2010 06:53:01 +0200 Wolfram Sang wrote:
> On Tue, Apr 20, 2010 at 05:19:23AM +0200, Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a summary report
> > of recent regressions.
> >
> > The following bug entry is on the current list of known regressions
> > from 2.6.33. Please verify if it still should be listed and let the tracking team
> > know (either way).
> >
> >
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15729
> > Subject : BUG: physmap modprobe & rmmod
> > Submitter : Randy Dunlap <randy.dunlap@oracle.com>
> > Date : 2010-04-02 20:40 (18 days old)
> > Message-ID : <20100402134058.c4682716.randy.dunlap@oracle.com>
> > References : http://marc.info/?l=linux-kernel&m=127024096210230&w=2
>
> Patch is here:
>
> https://patchwork.kernel.org/patch/90497/
Thanks.
> I'd ack it if I still had the original mail :)
I already replied with
Tested-by: Randy Dunlap <randy.dunlap@oracle.com>
> CCing linux-mtd and some more people, so it can get picked up.
---
~Randy
prev parent reply other threads:[~2010-04-20 4:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <deuQKFRcc0B.A.3EG.BRSzLB@tosh>
[not found] ` <YeFfFNFyTSF.A.MFH.fRSzLB@tosh>
2010-04-20 4:53 ` [Bug #15729] BUG: physmap modprobe & rmmod Wolfram Sang
2010-04-20 4:58 ` Randy Dunlap [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=20100419215837.d4a9b01d.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=dwmw2@infradead.org \
--cc=hsweeten@visionengravers.com \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=maciej.rutecki@gmail.com \
--cc=rjw@sisk.pl \
--cc=w.sang@pengutronix.de \
/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