From: Andi Kleen <andi@firstfloor•org>
To: Amir Vadai <amirv@mellanox•com>
Cc: "David S. Miller" <davem@davemloft•net>,
Andrew Morton <akpm@linux-foundation•org>,
Vivek Goyal <vgoyal@redhat•com>,
netdev@vger•kernel.org, Or Gerlitz <ogerlitz@mellanox•com>,
Yevgeny Petrilin <yevgenyp@mellanox•com>
Subject: Re: [PATCH net-next 0/3] Make is_kdump_kernel() accessible from modules
Date: Sun, 27 Jul 2014 17:48:32 -0700 [thread overview]
Message-ID: <877g2y9ulb.fsf@tassilo.jf.intel.com> (raw)
In-Reply-To: <1406473156-4077-1-git-send-email-amirv@mellanox.com> (Amir Vadai's message of "Sun, 27 Jul 2014 17:59:13 +0300")
Amir Vadai <amirv@mellanox•com> writes:
> Hi,
>
> I'm sending this patchset to net-next because it touches a commit [1] that was
> applied lately to net-next.
It would be better to have a generic function for "run with small
memory", that can be also triggered in other ways, e.g. a sysctl or
a boot opion, with kdump just another user.
There are low memory cases which are not kdump.
-Andi
--
ak@linux•intel.com -- Speaking for myself only
next prev parent reply other threads:[~2014-07-28 0:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-27 14:59 [PATCH net-next 0/3] Make is_kdump_kernel() accessible from modules Amir Vadai
2014-07-27 14:59 ` [PATCH net-next 1/3] crash_dump: " Amir Vadai
2014-07-27 14:59 ` [PATCH net-next 2/3] net/mlx4: Use is_kdump_kernel() to detect kdump kernel Amir Vadai
2014-07-27 14:59 ` [PATCH net-next 3/3] net/bnx2x: " Amir Vadai
2014-07-28 0:48 ` Andi Kleen [this message]
2014-07-28 12:26 ` [PATCH net-next 0/3] Make is_kdump_kernel() accessible from modules Vivek Goyal
2014-07-29 23:46 ` David Miller
2014-07-30 12:35 ` Vivek Goyal
2014-07-31 6:51 ` Amir Vadai
2014-07-31 13:07 ` Vivek Goyal
2014-07-31 19:22 ` David Miller
2014-08-01 12:44 ` Vivek Goyal
2014-08-06 8:10 ` Amir Vadai
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=877g2y9ulb.fsf@tassilo.jf.intel.com \
--to=andi@firstfloor$(echo .)org \
--cc=akpm@linux-foundation$(echo .)org \
--cc=amirv@mellanox$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=netdev@vger$(echo .)kernel.org \
--cc=ogerlitz@mellanox$(echo .)com \
--cc=vgoyal@redhat$(echo .)com \
--cc=yevgenyp@mellanox$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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