From: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
To: David Marchand <david.marchand@redhat.com>,
Kevin Traynor <ktraynor@redhat.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Cc: dpdk stable <stable@dpdk.org>
Subject: RE: [EXT] Re: please help backporting some patches to stable release 21.11.1
Date: Thu, 10 Mar 2022 13:35:03 +0000 [thread overview]
Message-ID: <CO1PR18MB47142A371EC3C10FD764ED99CB0B9@CO1PR18MB4714.namprd18.prod.outlook.com> (raw)
In-Reply-To: <CAJFAV8wORq6rrsq1ovtJKy7+UWRHoAh1huENL3f9y5gLsferwg@mail.gmail.com>
Ack. Thanks David for a cross check.
Regards,
Gowrishankar
> -----Original Message-----
> From: David Marchand <david.marchand@redhat.com>
> Sent: Thursday, March 10, 2022 6:52 PM
> To: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>; Kevin
> Traynor <ktraynor@redhat.com>; Jerin Jacob Kollanukkaran
> <jerinj@marvell.com>
> Cc: dpdk stable <stable@dpdk.org>
> Subject: [EXT] Re: please help backporting some patches to stable release
> 21.11.1
>
> External Email
>
> ----------------------------------------------------------------------
> On Tue, Mar 8, 2022 at 3:51 PM Kevin Traynor <ktraynor@redhat.com>
> wrote:
> >
> > Reminder of patches that need author rebase for 21.11.1 :-)
> > > 315d14d705 Gowrishankar Muthukrishnan event/cnxk: fix memory leaks
>
> The Fixes: tag looks wrong to me.
> This fix should be pointing at 8bdbae66b299 ("event/cnxk: add external clock
> support for timer").
> Hence it is irrelevant to 21.11.
>
>
> --
> David Marchand
prev parent reply other threads:[~2022-03-10 13:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 11:21 Kevin Traynor
2022-03-08 14:51 ` Kevin Traynor
2022-03-10 13:22 ` David Marchand
2022-03-10 13:27 ` Kevin Traynor
2022-03-10 13:35 ` Gowrishankar Muthukrishnan [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=CO1PR18MB47142A371EC3C10FD764ED99CB0B9@CO1PR18MB4714.namprd18.prod.outlook.com \
--to=gmuthukrishn@marvell.com \
--cc=david.marchand@redhat.com \
--cc=jerinj@marvell.com \
--cc=ktraynor@redhat.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).