From: David Miller <davem@davemloft.net>
To: greg@kroah.com
Cc: James.Bottomley@HansenPartnership.com,
Nagalakshmi.Nandigama@lsi.com, stable@vger.kernel.org,
gregkh@suse.de, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
alan@lxorguk.ukuu.org.uk, linux-scsi@vger.kernel.org,
Eric.Moore@lsi.com
Subject: Re: [PATCH] mpt2sas: fix non-x86 crash on shutdown
Date: Wed, 04 Jan 2012 14:39:29 -0500 (EST) [thread overview]
Message-ID: <20120104.143929.962116161801444281.davem@davemloft.net> (raw)
In-Reply-To: <20120104192102.GB18214@kroah.com>
From: Greg KH <greg@kroah.com>
Date: Wed, 4 Jan 2012 11:21:02 -0800
> On Wed, Jan 04, 2012 at 09:25:13AM -0600, James Bottomley wrote:
>> From: "nagalakshmi.nandigama@lsi.com" <nagalakshmi.nandigama@lsi.com>
>
> That's not a correct "from" line, sorry. That would create a mess of
> the log. Oh, I see Linus's tree is already a mess here, ugh. Please be
> more careful when accepting patches, otherwise stuff like this causes me
> to have to hand-edit the kernel git logs when I run the "who does what"
> statistic reports...
>
> David, any objection for me taking this patch (left below) instead of
> your original one for the stable tree?
No objection.
next prev parent reply other threads:[~2012-01-04 19:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120103223332.GA4112@kroah.com>
2012-01-03 22:33 ` [50/75] mpt2sas crashes on shutdown Greg KH
2012-01-04 8:53 ` Nandigama, Nagalakshmi
2012-01-04 15:18 ` Greg KH
2012-01-04 15:19 ` James Bottomley
2012-01-04 15:25 ` [PATCH] mpt2sas: fix non-x86 crash " James Bottomley
2012-01-04 19:21 ` Greg KH
2012-01-04 19:39 ` David Miller [this message]
2012-01-05 19:10 ` Patch "mpt2sas: fix non-x86 crash on shutdown" has been added to the 3.0-stable tree gregkh
2012-01-05 19:25 ` Patch "mpt2sas: fix non-x86 crash on shutdown" has been added to the 3.1-stable tree gregkh
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=20120104.143929.962116161801444281.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Eric.Moore@lsi.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=Nagalakshmi.Nandigama@lsi.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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).