DPDK patches and discussions
 help / color / mirror / Atom feed
From: Elena Agostini <eagostini@nvidia.com>
To: Kevin Traynor <ktraynor@redhat.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>
Subject: Re: [PATCH] gpu/cuda: missing slash in libcuda.so path
Date: Tue, 8 Mar 2022 14:24:58 +0000	[thread overview]
Message-ID: <DM6PR12MB4107A49DC5A155EE820A901FCD099@DM6PR12MB4107.namprd12.prod.outlook.com> (raw)
In-Reply-To: <578d369e-a3d9-5e05-df91-7e87fa078f9c@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 933 bytes --]

Yes please

Thanks
EA

From: Kevin Traynor <ktraynor@redhat.com>
Date: Tuesday, 8 March 2022 at 15:24
To: Elena Agostini <eagostini@nvidia.com>
Cc: dev@dpdk.org <dev@dpdk.org>, NBU-Contact-Thomas Monjalon (EXTERNAL) <thomas@monjalon.net>
Subject: Re: [PATCH] gpu/cuda: missing slash in libcuda.so path
External email: Use caution opening links or attachments


Hi Elena,

On 07/03/2022 21:47, Thomas Monjalon wrote:
> 01/03/2022 20:42, eagostini@nvidia.com:
>> From: Elena Agostini <eagostini@nvidia.com>
>>
>> Signed-off-by: Elena Agostini <eagostini@nvidia.com>
>
> Applied with this title and commit log:
>
>      gpu/cuda: fix dependency loading path
>
>      A slash was missing in libcuda.so path for dlopen.
>
>
>

This seems like a good candidate for backport to LTS, so I added it to
the queue for 21.11.1.

Please let me know if you do *not* want it backported 21.11.1.

thanks,
Kevin.

[-- Attachment #2: Type: text/html, Size: 3536 bytes --]

  reply	other threads:[~2022-03-08 14:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-01 19:42 eagostini
2022-03-07 21:47 ` Thomas Monjalon
2022-03-08 14:24   ` Kevin Traynor
2022-03-08 14:24     ` Elena Agostini [this message]
2022-03-08 14:29       ` Thomas Monjalon

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=DM6PR12MB4107A49DC5A155EE820A901FCD099@DM6PR12MB4107.namprd12.prod.outlook.com \
    --to=eagostini@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=ktraynor@redhat.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).