From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: Anatoly Burakov <anatoly.burakov@intel.com>,
dev@dpdk.org, Neil Horman <nhorman@tuxdriver.com>,
John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>
Subject: Re: [PATCH v2] doc: add deprecation notice for memory hotplug changes
Date: Wed, 7 Feb 2018 15:41:39 +0530 [thread overview]
Message-ID: <20180207101138.GB22174@jerin> (raw)
In-Reply-To: <20180205114742.GC19776@bricha3-MOBL3.ger.corp.intel.com>
-----Original Message-----
> Date: Mon, 5 Feb 2018 11:47:42 +0000
> From: Bruce Richardson <bruce.richardson@intel.com>
> To: Anatoly Burakov <anatoly.burakov@intel.com>
> CC: dev@dpdk.org, Neil Horman <nhorman@tuxdriver.com>, John McNamara
> <john.mcnamara@intel.com>, Marko Kovacevic <marko.kovacevic@intel.com>
> Subject: Re: [dpdk-dev] [PATCH v2] doc: add deprecation notice for memory
> hotplug changes
> User-Agent: Mutt/1.9.1 (2017-09-22)
>
> On Thu, Jan 18, 2018 at 10:32:28AM +0000, Anatoly Burakov wrote:
> > Due to coming changes outlined in memory hotplug RFC, there will
> > be several API/ABI changes.
> >
> > Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
> > ---
> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
>
next prev parent reply other threads:[~2018-02-07 10:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 17:17 [PATCH] doc: add deprecation notice for physmem layout function Anatoly Burakov
2018-01-18 9:55 ` Burakov, Anatoly
2018-01-18 10:32 ` [PATCH v2] doc: add deprecation notice for memory hotplug changes Anatoly Burakov
2018-01-23 10:36 ` Mcnamara, John
2018-02-05 11:47 ` Bruce Richardson
2018-02-07 10:11 ` Jerin Jacob [this message]
2018-02-14 14:48 ` Thomas Monjalon
2018-02-12 15:58 ` Jonas Pfefferle
2018-02-13 0:24 ` Yongseok Koh
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=20180207101138.GB22174@jerin \
--to=jerin.jacob@caviumnetworks.com \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=nhorman@tuxdriver.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.