From: Tejun Heo <htejun@gmail.com>
To: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Gabriel C <nix.or.die@googlemail.com>,
Stefan Richter <stefanr@s5r6.in-berlin.de>,
Jan Engelhardt <jengelh@linux01.gwdg.de>,
Satyam Sharma <satyam.sharma@gmail.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
Kay Sievers <kay.sievers@gmail.com>,
Cornelia Huck <cornelia.huck@de.ibm.com>,
Vitaly Bordug <vitb@kernel.crashing.org>,
Takashi Iwai <tiwai@suse.de>, Ingo Molnar <mingo@elte.hu>,
linux-fsdevel@vger.kernel.org, Doug Chapman <doug.chapman@hp.com>,
Vasily Tarasov <vtaras@openvz.org>,
Thierry MERLE <thierry.merle@free.fr>,
v4l-dvb-maintainer@linuxtv.org,
"Dwaine P. Garden" <dwainegarden@rogers.com>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Adrian Bunk <bunk@stusta.de>
Subject: Re: 2.6.23-rc1: known regressions with patches
Date: Tue, 24 Jul 2007 15:21:10 +0900 [thread overview]
Message-ID: <46A59A56.6000001@gmail.com> (raw)
In-Reply-To: <46A47940.7030801@googlemail.com>
Michal Piotrowski wrote:
> Subject : Oops while modprobing phy fixed module
> References : http://lkml.org/lkml/2007/7/14/63
> Last known good : ?
> Submitter : Gabriel C <nix.or.die@googlemail.com>
> Caused-By : Tejun Heo <htejun@gmail.com>
> commit 3007e997de91ec59af39a3f9c91595b31ae6e08b
> Handled-By : Satyam Sharma <satyam.sharma@gmail.com>
> Tejun Heo <htejun@gmail.com>
> Vitaly Bordug <vitb@kernel.crashing.org>
> Patch1 : http://lkml.org/lkml/2007/7/18/506
> Status : patch available
Patch is in mainline. Commit a1da4dfe35bc36c3bc9716d995c85b7983c38a76.
Thanks.
--
tejun
next prev parent reply other threads:[~2007-07-24 6:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 9:47 2.6.23-rc1: known regressions with patches Michal Piotrowski
2007-07-23 10:25 ` Ingo Molnar
2007-07-23 22:59 ` Greg KH
2007-07-24 21:57 ` Michal Piotrowski
2007-07-24 6:21 ` Tejun Heo [this message]
2007-07-26 9:10 ` [bug] SLUB & freeing locks [was: Re: 2.6.23-rc1: known regressions with patches] Ingo Molnar
2007-07-26 9:26 ` Peter Zijlstra
2007-07-26 9:32 ` Peter Zijlstra
2007-07-26 10:50 ` Ingo Molnar
2007-07-26 17:47 ` Christoph Lameter
2007-07-26 11:08 ` Pekka Enberg
2007-07-26 11:11 ` Peter Zijlstra
2007-07-26 17:51 ` Christoph Lameter
2007-07-26 18:01 ` [PATCH] slub: add lock debugging check Peter Zijlstra
2007-07-26 17:47 ` [bug] SLUB & freeing locks [was: Re: 2.6.23-rc1: known regressions with patches] Christoph Lameter
2007-07-26 18:04 ` Peter Zijlstra
2007-07-26 18:10 ` Christoph Lameter
2007-07-26 18:17 ` Peter Zijlstra
2007-07-26 18:54 ` [PATCH] slub: fix bug in slub debug support Peter Zijlstra
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=46A59A56.6000001@gmail.com \
--to=htejun@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bunk@stusta.de \
--cc=cornelia.huck@de.ibm.com \
--cc=doug.chapman@hp.com \
--cc=dwainegarden@rogers.com \
--cc=gregkh@suse.de \
--cc=jengelh@linux01.gwdg.de \
--cc=kay.sievers@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=mingo@elte.hu \
--cc=nix.or.die@googlemail.com \
--cc=satyam.sharma@gmail.com \
--cc=stefanr@s5r6.in-berlin.de \
--cc=thierry.merle@free.fr \
--cc=tiwai@suse.de \
--cc=torvalds@linux-foundation.org \
--cc=v4l-dvb-maintainer@linuxtv.org \
--cc=vitb@kernel.crashing.org \
--cc=vtaras@openvz.org \
/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