public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 111731] mpt2sas doesn't get built
Date: Fri, 12 Feb 2016 05:04:01 +0000	[thread overview]
Message-ID: <bug-111731-11613-MG6sHDe6Nk@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-111731-11613@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=111731

biosehn@yahoo.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |biosehn@yahoo.com

--- Comment #1 from biosehn@yahoo.com ---
This related OpenSUSE bugzilla has a patch that resolves the issue. 
https://bugzilla.opensuse.org/show_bug.cgi?id=962694

Per that BZ patch has been sent upstream, so hopefully it will make it into
distributions soon but you can probably solve it manually with that patch to
dracut until dracut itself receives an official update with the patch.

The patch as listed for OpenSUSE doesn't match the line numbers for me on
CentOS7, but searching for the proceeding lines I was able to find where to
patch it manually and it worked, I now have mpt3sas built into my 4.4 initrd
(whereas previously I didn't have either mpt3sas or mpt2sas because my 3.10
only had mpt2sas).

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

      reply	other threads:[~2016-02-12  5:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-02  9:55 [Bug 111731] New: mpt2sas doesn't get built bugzilla-daemon
2016-02-12  5:04 ` bugzilla-daemon [this message]

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-111731-11613-MG6sHDe6Nk@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