From: Jean Delvare <jdelvare@suse.de>
To: Kashyap Desai <kashyap.desai@avagotech.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
"Robin H. Johnson" <robbat2@gentoo.org>,
Adam Radford <aradford@gmail.com>,
Neela Syam Kolli <megaraidlinux@lsi.com>,
linux-scsi@vger.kernel.org, arkadiusz.bubala@open-e.com,
Matthew Garrett <matthew.garrett@nebula.com>,
Sumit Saxena <sumit.saxena@avagotech.com>,
Uday Lingala <uday.lingala@avagotech.com>,
"PDL,MEGARAIDLINUX" <megaraidlinux.pdl@avagotech.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Myron Stowe <myron.stowe@redhat.com>
Subject: RE: megaraid_sas: "FW in FAULT state!!", how to get more debug output? [BKO63661]
Date: Wed, 15 Jul 2015 09:21:55 +0200 [thread overview]
Message-ID: <1436944915.4661.5.camel@chaos.site> (raw)
In-Reply-To: <775bb7e5ecc09c3f042ca8e949b35e5f@mail.gmail.com>
Le Friday 10 July 2015 à 19:46 +0530, Kashyap Desai a écrit :
> >
> > I am about to commit the patch that was successfully tested by the
> > customer on
> > SLES 12, but I'm a bit confused. The upstream patch you referred to is:
> >
> > https://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=for-
> > next&id=6431f5d7c6025f8b007af06ea090de308f7e6881
> > [SCSI] megaraid_sas: megaraid_sas driver init fails in kdump kernel
> >
> > But the patch I used is the one you sent by e-mail on May 28th. It is
> > completely
> > different!
> >
> > So what am I supposed to do? Use the patch you sent (and that was tested
> > by the customer) for SLES 11 SP3 and SLES 12? Or was it just for testing
> > and the proper way of fixing the problem would be to backport the
>>upstream commit?
>
> You can use that patch as valid candidate for upstream submission. Some of
> the MR maintainer (Sumit Saxena) will send that patch. We are just
> organizing other patch series.
> Since SLES already ported patch without commit id, we are fine. I am just
> giving reference that patch which send via email will be send to upstream
> very soon along with other patch set.
OK, thanks for the clarification. The patched SLES 11 SP3 kernel is
currently under testing by the customer, apparently it doesn't work but
I don't have all the details yet. Maybe some more patches need to be
backported because that kernel is older.
--
Jean Delvare
SUSE L3 Support
prev parent reply other threads:[~2015-07-15 7:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <robbat2-20140712T111727-002806026Z@orbis-terrarum.net>
[not found] ` <CAErSpo5+=33byGqCjFCSfTpfKFtSAHRqYLzGF7yf5d18gEmWsQ@mail.gmail.com>
[not found] ` <robbat2-20140712T215640-831385120Z@orbis-terrarum.net>
2015-04-29 17:28 ` megaraid_sas: "FW in FAULT state!!", how to get more debug output? [BKO63661] Bjorn Helgaas
2015-05-28 12:24 ` Bjorn Helgaas
2015-05-28 13:35 ` Kashyap Desai
2015-06-29 13:25 ` Jean Delvare
2015-06-30 10:33 ` Kashyap Desai
2015-07-01 9:20 ` Jean Delvare
2015-07-07 8:44 ` Jean Delvare
2015-07-07 9:18 ` Kashyap Desai
2015-07-10 14:05 ` Jean Delvare
2015-07-10 14:16 ` Kashyap Desai
2015-07-15 7:21 ` Jean Delvare [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=1436944915.4661.5.camel@chaos.site \
--to=jdelvare@suse.de \
--cc=aradford@gmail.com \
--cc=arkadiusz.bubala@open-e.com \
--cc=bhelgaas@google.com \
--cc=kashyap.desai@avagotech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew.garrett@nebula.com \
--cc=megaraidlinux.pdl@avagotech.com \
--cc=megaraidlinux@lsi.com \
--cc=myron.stowe@redhat.com \
--cc=robbat2@gentoo.org \
--cc=sumit.saxena@avagotech.com \
--cc=uday.lingala@avagotech.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 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).