All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Kevin Traynor <ktraynor@redhat.com>,
	Elena Agostini <eagostini@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH] gpu/cuda: missing slash in libcuda.so path
Date: Tue, 08 Mar 2022 15:29:54 +0100	[thread overview]
Message-ID: <5293210.0WQXIW03uk@thomas> (raw)
In-Reply-To: <DM6PR12MB4107A49DC5A155EE820A901FCD099@DM6PR12MB4107.namprd12.prod.outlook.com>

08/03/2022 15:24, Elena Agostini:
> Yes please
> 
> Thanks
> EA
> 
> From: Kevin Traynor <ktraynor@redhat.com>
> 
> 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.


I forgot the Fixes: line and Cc: stable@dpdk.org

Elena, please remind to add such lines next time,
it makes the process more automatic.





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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-01 19:42 [PATCH] gpu/cuda: missing slash in libcuda.so path eagostini
2022-03-07 21:47 ` Thomas Monjalon
2022-03-08 14:24   ` Kevin Traynor
2022-03-08 14:24     ` Elena Agostini
2022-03-08 14:29       ` Thomas Monjalon [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=5293210.0WQXIW03uk@thomas \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=eagostini@nvidia.com \
    --cc=ktraynor@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.