From: Matthew Thode <prometheanfire@gentoo.org>
To: Richard Yao <ryao@gentoo.org>, Dan Williams <dan.j.williams@intel.com>
Cc: Joe Lawrence <joe.lawrence@stratus.com>,
"Reddy, Sreekanth" <Sreekanth.Reddy@lsi.com>,
"Nandigama, Nagalakshmi" <Nagalakshmi.Nandigama@lsi.com>,
Support <support@lsi.com>,
DL-MPT Fusion Linux <DL-MPTFusionLinux@lsi.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"JBottomley@parallels.com" <JBottomley@parallels.com>,
"kernel@gentoo.org" <kernel@gentoo.org>
Subject: Re: mpt2sas driver barfs when force removing a drive on 3.13.1
Date: Thu, 13 Feb 2014 23:48:17 -0600 [thread overview]
Message-ID: <52FDAE21.7070309@gentoo.org> (raw)
In-Reply-To: <52FBCE6E.50703@gentoo.org>
[-- Attachment #1.1: Type: text/plain, Size: 1720 bytes --]
On 02/12/2014 01:41 PM, Richard Yao wrote:
> On 02/12/2014 02:25 PM, Dan Williams wrote:
>> On Wed, Feb 12, 2014 at 9:41 AM, Richard Yao <ryao@gentoo.org> wrote:
>>> You should use `git send-email` to send the patch to all of the people
>>> listed by get_maintainer.pl:
>>
>> I see nothing wrong with the patch Joe originally submitted:
>> http://marc.info/?l=linux-scsi&m=138609455422179&w=2
>>
>>>
>>> richard@desktop ~/devel/linux $ scripts/get_maintainer.pl --file
>>> drivers/scsi/scsi_transport_sas.c
>>> "James E.J. Bottomley" <JBottomley@parallels.com> (maintainer:SCSI
>>> SUBSYSTEM)
>>> linux-scsi@vger.kernel.org (open list:SCSI SUBSYSTEM)
>>> linux-kernel@vger.kernel.org (open list)
>>>
>>> If I see that James E.J. Bottomley is already on CC for this discussion,
>>> but my recent (and first) experience submitting a patch for another
>>> subsystem was that they are ignored unless this strict procedure is
>>> followed.
>>>
>>> If the maintainer does not respond within a month after doing this, I
>>> suggest informing Linus Torvalds via email that the subsystem maintainer
>>> is non-responsive.
>>>
>>
>> Just re-ping James, he'll get to it...
>>
>
> That was intended as generic advice. Sadly, I don't have a copy of the
> email headers for the original patch submission, so I can't inspect it.
>
> That being said, I am receiving these emails because I suggested Matthew
> to include the Gentoo kernel team alias on the CC list when I advised
> him to send this report upstream.
>
Confirmed that it now works (I luksClosed the device, removed it from
the system, waited a few seconds, readded it and checked dmesg).
--
-- Matthew Thode (prometheanfire)
[-- Attachment #1.2: 0x40AC5AC3.asc --]
[-- Type: application/pgp-keys, Size: 5681 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2014-02-14 5:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-01 2:49 mpt2sas driver barfs when force removing a drive on 3.13.1 Matthew Thode
2014-02-03 14:24 ` Joe Lawrence
2014-02-03 14:24 ` Joe Lawrence
2014-02-12 11:43 ` Reddy, Sreekanth
2014-02-12 16:43 ` Joe Lawrence
2014-02-12 17:41 ` Richard Yao
2014-02-12 19:25 ` Dan Williams
2014-02-12 19:41 ` Richard Yao
2014-02-12 19:46 ` Matthew Thode
2014-02-14 5:48 ` Matthew Thode [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=52FDAE21.7070309@gentoo.org \
--to=prometheanfire@gentoo.org \
--cc=DL-MPTFusionLinux@lsi.com \
--cc=JBottomley@parallels.com \
--cc=Nagalakshmi.Nandigama@lsi.com \
--cc=Sreekanth.Reddy@lsi.com \
--cc=dan.j.williams@intel.com \
--cc=joe.lawrence@stratus.com \
--cc=kernel@gentoo.org \
--cc=linux-scsi@vger.kernel.org \
--cc=ryao@gentoo.org \
--cc=support@lsi.com \
/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.