From: Kevin Traynor <ktraynor@redhat.com>
To: Muhammad Bilal <m.bilal@emumba.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] Compilation failed for Patches intended for previous releases
Date: Wed, 15 Apr 2020 11:47:32 +0100 [thread overview]
Message-ID: <98cd9076-a237-111f-3716-facec0cc78c8@redhat.com> (raw)
In-Reply-To: <CAOFC0T2FcFw-QZUvF2tXCiC4pAHoQSSVPeJPssb0Hsqg18DxUQ@mail.gmail.com>
On 13/04/2020 15:25, Muhammad Bilal wrote:
> About 2 weeks ago, I submitted a patch for a Bug 364, Intended for
> 18.11 branch. The compilation on patchwork failed, whereas it is
> compiled successfully on my local system. I think this might have
> happened because Patch was tested on a Master branch instead of an
> 18.11 branch.
> My question is how should we submit a patch for the 18.11 branch.
>
Hi, it is documented here:
http://doc.dpdk.org/guides/contributing/patches.html#backporting-patches-for-stable-releases
Key points being, it should be sent to stable@dpdk.org and *not*
dev@dpdk.org and it should have the target branch(es) in the subject.
> Patch address = http://patches.dpdk.org/patch/66978/
> Bugzilla ID: 364
>
> Regards,
> Muhammad Bilal
>
prev parent reply other threads:[~2020-04-15 10:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 14:25 Muhammad Bilal
2020-04-15 10:47 ` Kevin Traynor [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=98cd9076-a237-111f-3716-facec0cc78c8@redhat.com \
--to=ktraynor@redhat.com \
--cc=dev@dpdk.org \
--cc=m.bilal@emumba.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 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).