DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: Srikanth Yalavarthi <syalavarthi@marvell.com>
Cc: David Marchand <david.marchand@redhat.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	 Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
	"thomas@monjalon.net" <thomas@monjalon.net>,
	 Prince Takkar <ptakkar@marvell.com>
Subject: Re: [EXT] [PATCH] ml/cnxk: don't export internal headers
Date: Wed, 18 Oct 2023 19:51:43 +0530	[thread overview]
Message-ID: <CALBAE1M0GonutafHVsoJpYmMrRgApaU3AuNkX7CO=2gafPCYzg@mail.gmail.com> (raw)
In-Reply-To: <DS0PR18MB55027C14DD836B9D06AC3BE4AED5A@DS0PR18MB5502.namprd18.prod.outlook.com>

On Wed, Oct 18, 2023 at 3:03 PM Srikanth Yalavarthi
<syalavarthi@marvell.com> wrote:
>
> > -----Original Message-----
> > From: David Marchand <david.marchand@redhat.com>
> > Sent: 18 October 2023 14:46
> > To: dev@dpdk.org
> > Cc: Jerin Jacob Kollanukkaran <jerinj@marvell.com>; thomas@monjalon.net;
> > Srikanth Yalavarthi <syalavarthi@marvell.com>; Prince Takkar
> > <ptakkar@marvell.com>
> > Subject: [EXT] [PATCH] ml/cnxk: don't export internal headers
> >
> > External Email
> >
> > ----------------------------------------------------------------------
> > driver_sdk_headers is used to expose headers that may be used by external
> > drivers.
> > Don't export ml/cnxk internal headers.
> >
> > Fixes: fe83ffd9ec2e ("ml/cnxk: add skeleton")
> >
> > Signed-off-by: David Marchand <david.marchand@redhat.com>
>
> Acked-by: Srikanth Yalavarthi <syalavarthi@marvell.com>

Applied to dpdk-next-net-mrvl/for-next-net. Thanks

      reply	other threads:[~2023-10-18 14:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-18  9:15 David Marchand
2023-10-18  9:33 ` [EXT] " Srikanth Yalavarthi
2023-10-18 14:21   ` Jerin Jacob [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='CALBAE1M0GonutafHVsoJpYmMrRgApaU3AuNkX7CO=2gafPCYzg@mail.gmail.com' \
    --to=jerinjacobk@gmail.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=ptakkar@marvell.com \
    --cc=syalavarthi@marvell.com \
    --cc=thomas@monjalon.net \
    /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).