From: Yuanhan Liu <yliu@fridaylinux.org>
To: Kevin Traynor <ktraynor@redhat.com>
Cc: Aaron Conole <aconole@redhat.com>,
stable@dpdk.org,
Alejandro Lucero <alejandro.lucero@netronome.com>,
Ferruh Yigit <ferruh.yigit@intel.com>,
Eelco Chaudron <echaudro@redhat.com>,
Pablo Cascon <pablo.cascon@redhat.com>,
Adrien Mazarguil <adrien.mazarguil@6wind.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-stable] [PATCH 0/2] nfp: support non-root user for the Netronome
Date: Sun, 20 May 2018 15:19:26 +0800 [thread overview]
Message-ID: <20180520071926.pmplwd322rbcrng3@yuanhanliu-NB0.tencent.com> (raw)
In-Reply-To: <ef324f6d-8d5b-942e-72ab-e7e9ec2ab669@redhat.com>
On Mon, May 14, 2018 at 03:23:41PM +0100, Kevin Traynor wrote:
> Ping Yuanhan - can you clarify question below? Also, can you let us know
Hi Kevin,
Sorry for being late: I just have very little time at weekends. I planned
to handle it last week, but I had to do something else.
And to your question: yes, they are not pushed yet: I should have done that
weeks ago though.
I will push them today.
> when you are planning further backports to 17.11 stable branch?
I just want to know do you expect something else to be released in 17.11.3?
If so, could you do a list, just for making sure I don't miss it.
--yliu
>
> thanks,
> Kevin.
>
> On 05/08/2018 10:23 AM, Kevin Traynor wrote:
> > On 05/06/2018 07:34 AM, Yuanhan Liu wrote:
> >> On Mon, Apr 30, 2018 at 07:02:29PM +0100, Kevin Traynor wrote:
> >>> On 04/30/2018 06:20 PM, 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.
> >>>>
> >>>
> >>> Hi Yuanhan, I think we would like to get this into the next 17.11 stable
> >>> release if possible. Not sure when you are merging patches into the tree
> >>> for it?
> >>
> >> Hi,
> >>
> >> I have just applied it to dpdk-stable/17.11. It will be part of 17.11.3
> >> LTS release.
> >>
> >
> > Hi,
> >
> > They don't appear to be on the branch? Maybe you have a private 'next'
> > branch or something in your workflow, but reporting in case something
> > still needs to be pushed.
> >
> > thanks,
> > Kevin.
> >
> >> Thanks.
> >>
> >> --yliu
> >>>
> >>> Kevin.
> >>>
> >>>> 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(-)
> >>>>
> >
next prev parent reply other threads:[~2018-05-20 10:15 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 [this message]
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
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=20180520071926.pmplwd322rbcrng3@yuanhanliu-NB0.tencent.com \
--to=yliu@fridaylinux.org \
--cc=aconole@redhat.com \
--cc=adrien.mazarguil@6wind.com \
--cc=alejandro.lucero@netronome.com \
--cc=echaudro@redhat.com \
--cc=ferruh.yigit@intel.com \
--cc=ktraynor@redhat.com \
--cc=pablo.cascon@redhat.com \
--cc=stable@dpdk.org \
--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).