patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: David Christensen <drc@linux.vnet.ibm.com>
Cc: stable@dpdk.org, chaozhu@linux.vnet.ibm.com
Subject: Re: [dpdk-stable] [PATCH 18.11] Succeed Chao Zhu as maintainer of EAL for IBM POWER
Date: Tue, 02 Apr 2019 01:26:32 +0200	[thread overview]
Message-ID: <1813562.H5Kv1hlH7T@xps> (raw)
In-Reply-To: <e1f8865d-7f09-9ea2-73d2-160b59c040bf@linux.vnet.ibm.com>

02/04/2019 01:12, David Christensen:
> > I see you want this update to be done in LTS releases.
> > For such need, you just have to add "Cc: stable@dpdk.org"
> > in the commit log of the first patch.
> > We avoid sending patches for a specific version.
> 
> Should I submit a v2 of the original patch, adding the CC?

No, that's fine I'll add it.



      reply	other threads:[~2019-04-01 23:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-01 18:56 David Christensen
2019-04-01 20:20 ` Thomas Monjalon
2019-04-01 23:12   ` David Christensen
2019-04-01 23:26     ` Thomas Monjalon [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=1813562.H5Kv1hlH7T@xps \
    --to=thomas@monjalon.net \
    --cc=chaozhu@linux.vnet.ibm.com \
    --cc=drc@linux.vnet.ibm.com \
    --cc=stable@dpdk.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).