patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: "Stanisław Kardach" <kda@semihalf.com>, "dpdk stable" <stable@dpdk.org>
Subject: Re: please help backporting some patches to stable release 21.11.2
Date: Tue, 28 Jun 2022 15:14:55 +0100	[thread overview]
Message-ID: <80256e4b-a7ea-db42-a3d9-9914e1f1dbea@redhat.com> (raw)
In-Reply-To: <CALVGJW+qWrGQsu0EciKnMTMMA1zk6HLtdhKG6vq_81WjhJ92Ug@mail.gmail.com>

On 27/06/2022 10:15, Stanisław Kardach wrote:
> On Fri, Jun 24, 2022 at 6:31 PM Kevin Traynor <ktraynor@redhat.com> wrote:
>> <snip>
>> c65e343c14  Stanislaw Kardach ci: enable C++ check for Arm and PPC
> This commit is not necessary as C++ checks were added later by:
>    5e437164df buildtools/chkincs: test headers for C++ compatibility
> 

Thanks for checking, will drop from list.


  reply	other threads:[~2022-06-28 14:15 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-24 16:31 Kevin Traynor
2022-06-27  9:15 ` Stanisław Kardach
2022-06-28 14:14   ` Kevin Traynor [this message]
2022-06-27 13:39 ` Rahul Lakkireddy
2022-06-28 14:18   ` Kevin Traynor
2022-06-27 21:15 ` McDaniel, Timothy
2022-06-28 14:13   ` Kevin Traynor
2022-06-28 14:20 ` Kevin Traynor
2022-06-29 10:24 ` Niklas Söderlund
2022-07-01 16:06   ` Kevin Traynor
2022-07-06 20:40 ` luca.boccassi
2022-08-01 13:31 ` McDaniel, Timothy
  -- strict thread matches above, loose matches on Subject: below --
2022-06-21 10:02 Kevin Traynor
2022-06-22  2:57 ` Jiawen Wu
2022-06-22  4:26 ` Gagandeep Singh
2022-06-23 14:08   ` Kevin Traynor
2022-06-22  4:47 ` Zhou, YidingX
2022-06-22  8:40   ` Kalesh Anakkur Purayil
2022-06-22 10:48 ` Niklas Söderlund
2022-06-24 14:17   ` Kevin Traynor
     [not found] ` <62b2851c.1c69fb81.cf480.7398SMTPIN_ADDED_BROKEN@mx.google.com>
2022-06-23 14:05   ` Kevin Traynor
2022-05-10 13:00 Kevin Traynor

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=80256e4b-a7ea-db42-a3d9-9914e1f1dbea@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=kda@semihalf.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).