From: Dan Carpenter <dan.carpenter@oracle.com>
To: NeilBrown <neilb@suse.de>
Cc: kbuild@lists.01.org,
Trond Myklebust <trond.myklebust@hammerspace.com>,
Anna Schumaker <Anna.Schumaker@Netapp.com>,
lkp@intel.com, linux-nfs@vger.kernel.org
Subject: Re: [PATCH/rfc] NFS: introduce NFS namespaces.
Date: Mon, 28 Jun 2021 09:35:47 +0300 [thread overview]
Message-ID: <20210628063547.GN1983@kadam> (raw)
In-Reply-To: <162483925301.7211.5330261248734853509@noble.neil.brown.name>
On Mon, Jun 28, 2021 at 10:14:13AM +1000, NeilBrown wrote:
> On Fri, 25 Jun 2021, Dan Carpenter wrote:
> > Hi NeilBrown,
> >
> > url: https://github.com/0day-ci/linux/commits/NeilBrown/NFS-introduce-NFS-namespaces/20210625-093359
> > base: git://git.linux-nfs.org/projects/trondmy/linux-nfs.git linux-next
> > config: x86_64-randconfig-m001-20210622 (attached as .config)
> > compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
> >
> > If you fix the issue, kindly add following tag as appropriate
> > Reported-by: kernel test robot <lkp@intel.com>
> > Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
>
> I assume this only applies if I fix the issue with a separate patch?
That's stuff the kbuild-bot adds. I just review the bug report and hit
forward.
regards,
dan carpenter
next prev parent reply other threads:[~2021-06-28 6:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-25 1:32 [PATCH/rfc] NFS: introduce NFS namespaces NeilBrown
2021-06-25 13:37 ` Dan Carpenter
2021-06-28 0:14 ` NeilBrown
2021-06-28 6:35 ` Dan Carpenter [this message]
2021-07-01 0:54 ` [PATCH/rfc v2] " NeilBrown
2021-07-01 9:32 ` Daire Byrne
2021-07-01 11:39 ` NeilBrown
2021-07-03 12:45 ` Daire Byrne
2021-07-03 23:03 ` NeilBrown
2021-07-06 16:22 ` Daire Byrne
2021-07-07 1:12 ` NeilBrown
2021-07-07 10:57 ` Daire Byrne
2021-07-07 21:25 ` NeilBrown
2021-07-07 22:21 ` Daire Byrne
2021-07-07 23:18 ` NeilBrown
2021-07-13 12:27 ` Daire Byrne
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=20210628063547.GN1983@kadam \
--to=dan.carpenter@oracle.com \
--cc=Anna.Schumaker@Netapp.com \
--cc=kbuild@lists.01.org \
--cc=linux-nfs@vger.kernel.org \
--cc=lkp@intel.com \
--cc=neilb@suse.de \
--cc=trond.myklebust@hammerspace.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox