DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Christian Ehrhardt <christian.ehrhardt@canonical.com>,
	David Marchand <david.marchand@redhat.com>,
	"stable@dpdk.org" <stable@dpdk.org>,
	Chenbo Xia <chenbo.xia@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: please help backporting some patches to stable release 19.11.11
Date: Thu, 2 Dec 2021 21:18:01 +0100	[thread overview]
Message-ID: <2790f1a6-a391-4f1d-6149-d1342bf94104@redhat.com> (raw)
In-Reply-To: <CAATJJ0+ndH8WxJUisy4aJhxX3=o+K_KjGqCdJzp7tKOwtFs0yw@mail.gmail.com>

Hi Christian,

On 12/2/21 14:45, Christian Ehrhardt wrote:
> On Tue, Nov 30, 2021 at 5:56 PM <christian.ehrhardt@canonical.com> wrote:
>>
>> Hi commit authors (and maintainers),
>>
>> Despite being selected by the DPDK maintenance tool ./devtools/git-log-fixes.sh
>> I didn't apply following commits from DPDK main to 19.11
>> stable branch, as conflicts or build errors occur.
>>
>> Can authors check your patches in the following list and either:
>>      - Backport your patches to the 19.11 branch, or
>>      - Indicate that the patch should not be backported
>>
>> Please do either of the above by December the 14th 2021 (More time than
>> usual as backports get harder).
> 
> Sorry, but to meet some deadlines by test/verification I need to reduce the
> time for backports to make it into -rc1 to the 9th of December.
> 
> That still is 7 days out from now and still longer than usual.
> 
> 
>> You can find the a temporary work-in-progress branch of the coming 19.11.11
>> release at:
>>      https://github.com/cpaelzer/dpdk-stable-queue
>> It is recommended to backport on top of that to minimize further conflicts or
>> misunderstandings.
>>
>> Some notes on stable backports:
>>
>> A backport should contain a reference to the DPDK main branch commit
>> in it's commit message in the following fashion:
>>      [ upstream commit <commit's dpdk main branch SHA-1 checksum> ]
>>
>> For example:
>>      https://git.dpdk.org/dpdk-stable/commit/?h=18.11&id=d90e6ae6f936ecdc2fd3811ff9f26aec7f3c06eb
>>
>> When sending the backported patch, please indicate the target branch in the
>> subject line, as we have multiple branches, for example:
>>      [PATCH 19.11] foo/bar: fix baz
>>
>> With git format-patch, this can be achieved by appending the parameter:
>>      --subject-prefix='PATCH 19.11'
>>
>> Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".
>>
>> FYI, branch 19.11 is located at tree:
>>     https://git.dpdk.org/dpdk-stable
>>
>> Thanks.
>>
>> Christian Ehrhardt <christian.ehrhardt@canonical.com>
>>
>> ---
>>

...

>> b72099be7f  David Marchand   net/virtio-user: fix init when using existing tap
This commit should not be backported.
We deliberately omitted adding the Fixes tag and Cc'ing stable@dpdk.org
so that it is not automatically backported.

Regards,
Maxime


       reply	other threads:[~2021-12-02 20:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20211130165621.2467243-1-christian.ehrhardt@canonical.com>
     [not found] ` <CAATJJ0+ndH8WxJUisy4aJhxX3=o+K_KjGqCdJzp7tKOwtFs0yw@mail.gmail.com>
2021-12-02 20:18   ` Maxime Coquelin [this message]
2021-12-03  6:22     ` Christian Ehrhardt

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=2790f1a6-a391-4f1d-6149-d1342bf94104@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=chenbo.xia@intel.com \
    --cc=christian.ehrhardt@canonical.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --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).