From: bugme-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 10730] New: build issue #503 for v2.6.26-rc2-433-gf26a398 : undefined reference to `request_firmware'
Date: Sat, 17 May 2008 03:06:12 -0700 (PDT) [thread overview]
Message-ID: <bug-10730-11613@http.bugzilla.kernel.org/> (raw)
http://bugzilla.kernel.org/show_bug.cgi?id=10730
Summary: build issue #503 for v2.6.26-rc2-433-gf26a398 :
undefined reference to `request_firmware'
Product: SCSI Drivers
Version: 2.5
KernelVersion: 2.6.26-rc2-433-gf26a398
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Other
AssignedTo: scsi_drivers-other@kernel-bugs.osdl.org
ReportedBy: rjw@sisk.pl
OtherBugsDependingO 10492
nThis:
Regression: 1
Subject : build issue #503 for v2.6.26-rc2-433-gf26a398 : undefined
reference to `request_firmware'
Submitter : Toralf Förster <toralf.foerster@gmx.de>
Date : 2008-05-16 17:06
References : http://marc.info/?l=linux-kernel&m=121095777616792&w=4
This entry is being used for tracking a regression from 2.6.25. Please don't
close it until the problem is fixed in the mainline.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2008-05-17 10:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-17 10:06 bugme-daemon [this message]
2008-06-10 13:27 ` [Bug 10730] build issue #503 for v2.6.26-rc2-433-gf26a398 : undefined reference to `request_firmware' bugme-daemon
2008-07-04 21:40 ` bugme-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-10730-11613@http.bugzilla.kernel.org/ \
--to=bugme-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;
as well as URLs for NNTP newsgroup(s).