patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Alejandro Lucero <alejandro.lucero@netronome.com>
To: Luca Boccassi <bluca@debian.org>
Cc: Aaron Conole <aconole@redhat.com>,
	stable@dpdk.org,  Ferruh Yigit <ferruh.yigit@intel.com>,
	Yuanhan Liu <yliu@fridaylinux.org>,
	 Eelco Chaudron <echaudro@redhat.com>,
	Pablo Cascon <pablo.cascon@redhat.com>,
	 Kevin Traynor <ktraynor@redhat.com>,
	Adrien Mazarguil <adrien.mazarguil@6wind.com>
Subject: Re: [dpdk-stable] [PATCH 0/2] nfp: support non-root user for the Netronome
Date: Thu, 3 May 2018 13:25:11 +0100	[thread overview]
Message-ID: <CAD+H991arrx0zvozbqxWzF-Gw2zGkAPz1t4tPsSXETFoqiNujA@mail.gmail.com> (raw)
In-Reply-To: <1525343408.23337.51.camel@debian.org>

This fixes can not be applied to master because that code was changed and
it is not there anymore.

So it these fixes are going to be applied just to stable versions.

On Thu, May 3, 2018 at 11:30 AM, Luca Boccassi <bluca@debian.org> wrote:

> On Tue, 2018-05-01 at 11:36 +0100, Luca Boccassi wrote:
> > On Mon, 2018-04-30 at 13:20 -0400, Aaron Conole wrote:
> > > Even when trying to use the Netronome cards via VFIO, there is a
> > > lock file being requested, which requires root access.  This series
> > > fixes an issue with the nfp driver lock release always releasing
> > > 'nfp0' (which isn't a bug in practice for other reasons) as well
> > > as allowing the lock file location to be configured by the
> > > application
> > > or user via the HOME environment variable (similar to other
> > > resources
> > > in the DPDK framework).
> > >
> > > This series is only applicable to the stable tree because the nfp
> > > driver is completely rewritten for later versions of DPDK.
> > >
> > > Aaron Conole (2):
> > >   nfp: unlink the appropriate lock file
> > >   nfp: allow for non-root user
> > >
> > >  drivers/net/nfp/nfp_nfpu.c | 25 +++++++++++++++++++++----
> > >  1 file changed, 21 insertions(+), 4 deletions(-)
> >
> > Series applied to 18.02, thanks.
>
> I just noticed this is not in dpdk/master yet, is it scheduled for a
> later release?
>
> --
> Kind regards,
> Luca Boccassi
>

  reply	other threads:[~2018-05-03 12:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-30 17:20 Aaron Conole
2018-04-30 17:20 ` [dpdk-stable] [PATCH 1/2] nfp: unlink the appropriate lock file Aaron Conole
2018-04-30 17:20 ` [dpdk-stable] [PATCH 2/2] nfp: allow for non-root user Aaron Conole
2018-05-08 13:09   ` Eelco Chaudron
2018-05-08 13:20     ` Aaron Conole
2018-05-09 17:05   ` Alejandro Lucero
2018-05-09 17:53     ` Aaron Conole
2018-05-09 19:44       ` Alejandro Lucero
2018-05-10 12:00         ` Alejandro Lucero
2018-04-30 18:02 ` [dpdk-stable] [PATCH 0/2] nfp: support non-root user for the Netronome Kevin Traynor
2018-05-06  6:34   ` Yuanhan Liu
2018-05-08  9:23     ` Kevin Traynor
2018-05-14 14:23       ` Kevin Traynor
2018-05-20  7:19         ` Yuanhan Liu
2018-05-22 10:45           ` Kevin Traynor
2018-05-01 10:36 ` Luca Boccassi
2018-05-03 10:30   ` Luca Boccassi
2018-05-03 12:25     ` Alejandro Lucero [this message]
2018-05-03 12:57       ` Luca Boccassi

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=CAD+H991arrx0zvozbqxWzF-Gw2zGkAPz1t4tPsSXETFoqiNujA@mail.gmail.com \
    --to=alejandro.lucero@netronome.com \
    --cc=aconole@redhat.com \
    --cc=adrien.mazarguil@6wind.com \
    --cc=bluca@debian.org \
    --cc=echaudro@redhat.com \
    --cc=ferruh.yigit@intel.com \
    --cc=ktraynor@redhat.com \
    --cc=pablo.cascon@redhat.com \
    --cc=stable@dpdk.org \
    --cc=yliu@fridaylinux.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).