From: Ferruh Yigit <firstname.lastname@example.org> To: Luca Boccassi <email@example.com> Cc: dpdk stable <firstname.lastname@example.org> Subject: Re: [dpdk-stable] please help backporting some patches to stable release 19.11.3 Date: Fri, 5 Jun 2020 13:49:50 +0100 Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> On 5/27/2020 11:14 AM, email@example.com wrote: > Hi commit authors (and maintainers), > > I didn't apply following commits from DPDK master 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 June the 3rd. > > > Some notes on stable backports: > > A backport should contain a reference to the DPDK master branch commit > in it's commit message in the following fashion: > [ upstream commit <commit's dpdk master 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 "firstname.lastname@example.org" but not "email@example.com". > > FYI, branch 19.11 is located at tree: > https://git.dpdk.org/dpdk-stable > > Thanks. > > Luca Boccassi > <...> > 867b49d17a Ferruh Yigit ring: fix build for gcc O1 optimization Hi Luca, The fix is not applicable for 19.11, we can ignore it. 'lib/librte_ring/rte_ring_peek.h' has been added for 20.05 and this patch fixes it.
next prev parent reply index Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <firstname.lastname@example.org> 2020-05-28 9:29 ` Wei Hu (Xavier) 2020-05-28 16:35 ` Luca Boccassi 2020-05-29 3:38 ` Wei Hu (Xavier) 2020-06-05 12:49 ` Ferruh Yigit [this message] 2020-05-27 16:10 Luca Boccassi 2020-06-03 8:48 ` Luca Boccassi
Reply instructions: You may reply publically 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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.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
patches for DPDK stable branches Archives are clonable: git clone --mirror http://inbox.dpdk.org/stable/0 stable/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 stable stable/ http://inbox.dpdk.org/stable \ email@example.com public-inbox-index stable Newsgroup available over NNTP: nntp://inbox.dpdk.org/inbox.dpdk.stable AGPL code for this site: git clone https://public-inbox.org/ public-inbox