From: bluez-devel-owner@lists.sourceforge.net
To: bluez-devel-owner@lists.sourceforge.net
Subject: Bluez-devel post from bunk@stusta.de requires approval
Date: Tue, 13 Mar 2007 05:50:14 -0700 [thread overview]
Message-ID: <mailman.197539.1173790214.20110.bluez-devel@lists.sourceforge.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 399 bytes --]
As list administrator, your authorization is requested for the
following mailing list posting:
List: Bluez-devel@lists.sourceforge.net
From: bunk@stusta.de
Subject: [2/6] 2.6.21-rc3: known regressions
Reason: Too many recipients to the message
At your convenience, visit:
https://lists.sourceforge.net/lists/admindb/bluez-devel
to approve or deny the request.
[-- Attachment #2: Type: message/rfc822, Size: 2980 bytes --]
From: Adrian Bunk <bunk@stusta.de>
To: Linus Torvalds <torvalds@linux-foundation.org>, Andrew Morton <akpm@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, Len Brown <lenb@kernel.org>, davem@davemloft.net, kuznet@ms2.inr.ac.ru, pekkas@netcore.fi, jmorris@namei.org, yoshfuji@linux-ipv6.org, kaber@coreworks.de, netdev@vger.kernel.org, Pavel Machek <pavel@ucw.cz>, Marcel Holtmann <marcel@holtmann.org>, maxk@qualcomm.com, bluez-devel@lists.sf.net, Albert Hopkins <kernel@marduk.letterboxes.org>, Ayaz Abdulla <aabdulla@nvidia.com>, jgarzik@pobox.com
Subject: [2/6] 2.6.21-rc3: known regressions
Date: Tue, 13 Mar 2007 13:50:03 +0100
Message-ID: <20070313125003.GS18731@stusta.de>
This email lists some known regressions in Linus' tree compared to 2.6.20.
If you find your name in the Cc header, you are either submitter of one
of the bugs, maintainer of an affectected subsystem or driver, a patch
of you caused a breakage or I'm considering you in any other way
possibly involved with one or more of these issues.
Due to the huge amount of recipients, please trim the Cc when answering.
Subject : ipv6 crash
References : http://lkml.org/lkml/2007/3/10/2
Submitter : Len Brown <lenb@kernel.org>
Status : unknown
Subject : ThinkPad X60: bluetooth hardlocks
References : http://lkml.org/lkml/2007/3/2/85
Submitter : Pavel Machek <pavel@ucw.cz>
Handled-By : Marcel Holtmann <marcel@holtmann.org>
Status : unknown
Subject : forcedeth: skb_over_panic
References : http://bugzilla.kernel.org/show_bug.cgi?id=8058
Submitter : Albert Hopkins <kernel@marduk.letterboxes.org>
Handled-By : Ayaz Abdulla <aabdulla@nvidia.com>
Status : problem is being debugged
[-- Attachment #3: Type: message/rfc822, Size: 617 bytes --]
From: bluez-devel-request@lists.sourceforge.net
Subject: confirm 8304fa7a3a71c5e87ad5b5253f1388fa2673619f
If you reply to this message, keeping the Subject: header intact,
Mailman will discard the held message. Do this if the message is
spam. If you reply to this message and include an Approved: header
with the list password in it, the message will be approved for posting
to the list. The Approved: header can also appear in the first line
of the body of the reply.
next reply other threads:[~2007-03-13 12:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-13 12:50 bluez-devel-owner [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-01-09 5:51 Bluez-devel post from bunk@stusta.de requires approval bluez-devel-owner
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=mailman.197539.1173790214.20110.bluez-devel@lists.sourceforge.net \
--to=bluez-devel-owner@lists.sourceforge.net \
/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