From: bugzilla-daemon@bugzilla.kernel.org
To: backports@vger.kernel.org
Subject: [Bug 51061] brcmsmac crashes and disconnects
Date: Thu, 29 Nov 2012 23:49:24 +0000 (UTC) [thread overview]
Message-ID: <20121129234924.B0B6511FAE1@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-51061-58281@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=51061
--- Comment #3 from Luis R. Rodriguez <mcgrof@gmail.com> 2012-11-29 23:49:24 ---
Thanks for the review and confirmation. Konstantin, Alan, I tried to re-assign
the bug to Arend but bugzilla indicates the Assignee
(backports@vger.kernel.org) or someone with permissions needs to be able to do
this. Not sure if we ever got a password to use for backports@vger.kernel.org
to be able to re-assign bugs via bugzilla that were determined at a later time
are not backport related, I don't think so. Can we or can a few of us get
permissions to reassign bugs? Please note that in practice we have had so far
only 1 reported bug regarding compat-drivers / compat-wireless (back in the
day) that was an actual backport bug as such I suspect as with other bugs that
have been filed before just a heads up that most bugs on drivers that use
compat *will* likely be *real* driver bugs based on upstream linux-stable code.
I am also not sure if it is possible to modify the bug entry to re-assign to
networking for component.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2012-11-29 23:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-51061-58281@https.bugzilla.kernel.org/>
2012-11-29 14:40 ` [Bug 51061] brcmsmac crashes and disconnects bugzilla-daemon
2012-11-29 19:04 ` bugzilla-daemon
2012-11-29 23:13 ` bugzilla-daemon
2012-11-29 23:49 ` bugzilla-daemon [this message]
2012-11-30 0:02 ` bugzilla-daemon
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=20121129234924.B0B6511FAE1@bugzilla.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=backports@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.