From: bugzilla-daemon@bugzilla.kernel.org
To: backports@vger.kernel.org
Subject: [Bug 55971] redefined error in 2.6.32-279.22.1.el6.x86_64 kernel
Date: Wed, 3 Apr 2013 21:15:50 +0000 (UTC) [thread overview]
Message-ID: <20130403211550.0728C11FB08@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-55971-58281@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=55971
--- Comment #3 from Andy Gospodarek <andy@greyhouse.net> 2013-04-03 21:15:49 ---
Created an attachment (id=97241)
--> (https://bugzilla.kernel.org/attachment.cgi?id=97241)
Initial fix for 6.3 update kernel
This has not been tested other than to be sure it compiles. I'll post to the
list once I receive confirmation that it works for the reporter.
--
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:[~2013-04-03 21:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-30 7:32 [Bug 55971] New: redefined error in 2.6.32-279.22.1.el6.x86_64 kernel bugzilla-daemon
2013-03-31 0:58 ` [Bug 55971] " bugzilla-daemon
2013-04-03 14:31 ` bugzilla-daemon
2013-04-03 21:15 ` bugzilla-daemon [this message]
2013-04-03 21:16 ` 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=20130403211550.0728C11FB08@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox