From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 16971] New: qla4xxx compile failure on 32-bit PowerPC: missing readq and writeq
Date: Tue, 24 Aug 2010 19:07:49 GMT [thread overview]
Message-ID: <bug-16971-11613@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=16971
Summary: qla4xxx compile failure on 32-bit PowerPC: missing
readq and writeq
Product: IO/Storage
Version: 2.5
Kernel Version: 2.6.36-rc1
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: SCSI
AssignedTo: linux-scsi@vger.kernel.org
ReportedBy: maciej.rutecki@gmail.com
CC: mroos@linux.ee, rjw@sisk.pl, maciej.rutecki@gmail.com
Regression: Yes
Subject : qla4xxx compile failure on 32-bit PowerPC: missing readq and
writeq
Submitter : Meelis Roos <mroos@linux.ee>
Date : 2010-08-19 21:03
Message-ID : alpine.SOC.1.00.1008192359310.19654@math.ut.ee
References : http://marc.info/?l=linux-kernel&m=128225184900892&w=2
This entry is being used for tracking a regression from 2.6.35. Please don't
close it until the problem is fixed in the mainline.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2010-08-24 19:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-24 19:07 bugzilla-daemon [this message]
2010-08-24 19:08 ` [Bug 16971] qla4xxx compile failure on 32-bit PowerPC: missing readq and writeq bugzilla-daemon
2010-08-30 13:46 ` bugzilla-daemon
2010-08-30 15:02 ` bugzilla-daemon
2010-09-22 18:04 ` bugzilla-daemon
2010-10-13 20:19 ` bugzilla-daemon
2010-11-19 20:06 ` bugzilla-daemon
2010-12-05 21:52 ` bugzilla-daemon
2010-12-08 12:08 ` bugzilla-daemon
2010-12-08 16:22 ` 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-16971-11613@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 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.