From: Trond Myklebust <trondmy@hammerspace.com>
To: "paulmck@kernel.org" <paulmck@kernel.org>,
"madhuparnabhowmik04@gmail.com" <madhuparnabhowmik04@gmail.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"kbuild-all@lists.01.org" <kbuild-all@lists.01.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"rcu@vger.kernel.org" <rcu@vger.kernel.org>,
"joel@joelfernandes.org" <joel@joelfernandes.org>,
"linux-kernel-mentees@lists.linuxfoundation.org"
<linux-kernel-mentees@lists.linuxfoundation.org>,
"anna.schumaker@netapp.com" <anna.schumaker@netapp.com>
Subject: Re: [Linux-kernel-mentees] [PATCH] fs: nfs: dir.c: Fix sparse error
Date: Thu, 12 Dec 2019 13:45:29 +0000 [thread overview]
Message-ID: <5614739335088d3e9baff43b752df04b84a8ad14.camel@hammerspace.com> (raw)
In-Reply-To: <20191212041406.GT2889@paulmck-ThinkPad-P72>
On Wed, 2019-12-11 at 20:14 -0800, Paul E. McKenney wrote:
> On Wed, Dec 11, 2019 at 01:18:42PM +0530,
> madhuparnabhowmik04@gmail.com wrote:
> > This build error is because the macro list_tail_rcu() is
> > not yet present in the mainline kernel.
> >
> > This patch is dependent on the patch :
> > https://lore.kernel.org/linux-kernel-mentees/CAF65HP2SC89k9HJZfcLgeOMRPBKRyasCMiLo2gZgBKycjHuU6A@mail.gmail.com/T/#t
>
> If the NFS folks are OK with it, I would be happy to take it in -rcu,
> where the list_tail_rcu() patch is currently located.
>
> Thanx, Paul
That would be fine with me.
Cheers
Trond
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
next prev parent reply other threads:[~2019-12-12 18:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 5:46 [Linux-kernel-mentees] [PATCH] fs: nfs: dir.c: Fix sparse error madhuparnabhowmik04
2019-12-11 1:01 ` kbuild test robot
2019-12-11 7:48 ` madhuparnabhowmik04
2019-12-12 4:14 ` Paul E. McKenney
2019-12-12 13:45 ` Trond Myklebust [this message]
2019-12-12 18:03 ` Paul E. McKenney
2019-12-12 19:48 ` Madhuparna Bhowmik
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=5614739335088d3e9baff43b752df04b84a8ad14.camel@hammerspace.com \
--to=trondmy@hammerspace.com \
--cc=anna.schumaker@netapp.com \
--cc=joel@joelfernandes.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=madhuparnabhowmik04@gmail.com \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.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).