From: Vivek Goyal <vgoyal@redhat.com>
To: Kashyap Desai <kashyap.desai@avagotech.com>
Cc: Tomas Henzl <thenzl@redhat.com>,
"Elliott, Robert (Server Storage)" <Elliott@hp.com>,
Sumit Saxena <sumit.saxena@avagotech.com>,
linux-scsi@vger.kernel.org,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Christoph Hellwig <hch@infradead.org>,
jbottomley@parallels.com, aradford <aradford@gmail.com>,
Michal Schmidt <mschmidt@redhat.com>,
amirv@mellanox.com, Jens Axboe <axboe@kernel.dk>,
scameron@beardog.cce.hp.com
Subject: Re: [PATCH 04/11] megaraid_sas : Firmware crash dump feature support
Date: Thu, 11 Sep 2014 13:02:42 -0400 [thread overview]
Message-ID: <20140911170242.GB17140@redhat.com> (raw)
In-Reply-To: <CAHsXFKH2REAYauW5=Tp=eqaeBxve6rZU3ocXcnpVg2P=72VTQw@mail.gmail.com>
On Thu, Sep 11, 2014 at 10:09:27PM +0530, Kashyap Desai wrote:
[..]
> > OK, just keep in mind that the is_kdump_kernel() is not yet in mainline.
>
> Sure I read that part, but when I check kernel source I found
> is_kdump_kernel() is available.
>
> http://lxr.free-electrons.com/source/include/linux/crash_dump.h#L55
> Let's do one thing - We will submit a separate patch for this to avoid
> any confusion.
is_kdump_kernel() has been there for long time just that it was not
exported. Now a patch is sitting in dave miller's tree to export it
and make it available to drivers.
Thanks
Vivek
next prev parent reply other threads:[~2014-09-11 17:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-06 13:25 [PATCH 04/11] megaraid_sas : Firmware crash dump feature support Sumit.Saxena
2014-09-09 15:54 ` Tomas Henzl
2014-09-09 16:18 ` Elliott, Robert (Server Storage)
2014-09-10 10:08 ` Tomas Henzl
2014-09-10 12:12 ` Sumit Saxena
2014-09-10 15:06 ` Elliott, Robert (Server Storage)
2014-09-10 15:28 ` Tomas Henzl
2014-09-10 15:46 ` Vivek Goyal
2014-09-11 9:02 ` Kashyap Desai
2014-09-11 11:20 ` Tomas Henzl
2014-09-11 16:39 ` Kashyap Desai
2014-09-11 17:02 ` Vivek Goyal [this message]
2014-09-11 18:58 ` Tomas Henzl
2014-09-11 19:11 ` Kashyap Desai
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=20140911170242.GB17140@redhat.com \
--to=vgoyal@redhat.com \
--cc=Elliott@hp.com \
--cc=amirv@mellanox.com \
--cc=aradford@gmail.com \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=jbottomley@parallels.com \
--cc=kashyap.desai@avagotech.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mschmidt@redhat.com \
--cc=scameron@beardog.cce.hp.com \
--cc=sumit.saxena@avagotech.com \
--cc=thenzl@redhat.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.