From: Greg KH <greg@kroah.com>
To: Mark Lord <lkml@rtr.ca>
Cc: Adrian Bunk <bunk@stusta.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Sid Boyce <g3vbv@blueyonder.co.uk>, Pavel Machek <pavel@ucw.cz>,
Marcel Holtmann <marcel@holtmann.org>,
linux-pm@lists.osdl.org, maxk@qualcomm.com,
bluez-devel@lists.sourceforge.net, Matt Mackall <mpm@selenic.com>,
Johannes Berg <johannes@sipsolutions.net>,
Albert Hopkins <kernel@marduk.letterboxes.org>,
Ayaz Abdulla <aabdulla@nvidia.com>, Jeff Garzik <jeff@garzik.org>,
netdev@vger.kernel.org
Subject: Re: [1/6] 2.6.21-rc2: known regressions
Date: Sun, 4 Mar 2007 20:34:43 -0800 [thread overview]
Message-ID: <20070305043443.GA29158@kroah.com> (raw)
In-Reply-To: <45EB961D.6030808@rtr.ca>
On Sun, Mar 04, 2007 at 11:01:33PM -0500, Mark Lord wrote:
> Adrian Bunk wrote:
> >
> >Subject : Bluetooth RFComm locks up the machine (device_move() related)
> >References : http://lkml.org/lkml/2007/3/4/64
> >Submitter : Mark Lord <lkml@rtr.ca>
> >Caused-By : Marcel Holtmann <marcel@holtmann.org>
> > commit c1a3313698895d8ad4760f98642007bf236af2e8
> >Status : unknown
>
> A 2-line patch exists for fs/sysfs/dir.c to address this.
> Waiting on Greg to apply it or substitute something prettier. ;)
I want to see if Marcel agrees with it, as he did the original patch in
that area.
thanks,
greg k-h
next prev parent reply other threads:[~2007-03-05 4:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0702272105220.12485@woody.linux-foundation.org>
2007-03-05 1:50 ` [1/6] 2.6.21-rc2: known regressions Adrian Bunk
2007-03-05 2:26 ` Andrew Morton
2007-03-05 3:35 ` Greg KH
2007-03-06 0:55 ` Johannes Berg
2007-03-05 4:01 ` Mark Lord
2007-03-05 4:34 ` Greg KH [this message]
2007-03-05 12:42 ` Marcel Holtmann
2007-03-07 11:06 ` Jeff Garzik
2007-03-07 22:17 ` Albert Hopkins
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=20070305043443.GA29158@kroah.com \
--to=greg@kroah.com \
--cc=aabdulla@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=bunk@stusta.de \
--cc=g3vbv@blueyonder.co.uk \
--cc=jeff@garzik.org \
--cc=johannes@sipsolutions.net \
--cc=kernel@marduk.letterboxes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.org \
--cc=lkml@rtr.ca \
--cc=marcel@holtmann.org \
--cc=maxk@qualcomm.com \
--cc=mpm@selenic.com \
--cc=netdev@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).