From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 83391] Oops on sd_mod
Date: Thu, 28 Aug 2014 13:52:29 +0000 [thread overview]
Message-ID: <bug-83391-11613-mc3BqdTTr9@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-83391-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=83391
Jeff Moyer <jmoyer@redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jmoyer@redhat.com
--- Comment #3 from Jeff Moyer <jmoyer@redhat.com> ---
This is a vendor kernel. You should file a bug report with Red Hat here:
https://bugzilla.redhat.com/enter_bug.cgi?product=Red%20Hat%20Enterprise%20Linux%206
First, though, you should update to a newer kernel... that one is several years
old.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-08-28 13:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 2:32 [Bug 83391] New: Oops on sd_mod bugzilla-daemon
2014-08-28 3:19 ` [Bug 83391] " bugzilla-daemon
2014-08-28 7:55 ` bugzilla-daemon
2014-08-28 13:52 ` bugzilla-daemon [this message]
2014-08-29 1:18 ` bugzilla-daemon
2014-08-29 1:19 ` 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=bug-83391-11613-mc3BqdTTr9@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-scsi@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