From: Jakub Kicinski <kuba@kernel.org>
To: Chuck Lever <cel@kernel.org>
Cc: Chuck Lever <chuck.lever@oracle.com>,
netdev@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: Re: [PATCH RFC] tools: ynl: Add source files for nfsd netlink protocol
Date: Thu, 5 Oct 2023 07:50:21 -0700 [thread overview]
Message-ID: <20231005075021.0da40d7d@kernel.org> (raw)
In-Reply-To: <169651139213.16787.3812644920847558917.stgit@klimt.1015granger.net>
On Thu, 05 Oct 2023 09:10:38 -0400 Chuck Lever wrote:
> Should I include this with the nfsd netlink protocol patches already
> in nfsd-next, or do you want to take it after those have been merged?
Either way works, I don't see any conflicts right now.
Worst case we'll have a minor conflict on the Makefile.
Note that you should probably also add an entry for nfsd to
tools/net/ynl/Makefile.deps in case there are discrepancies
between the system headers and new uAPI extensions.
next prev parent reply other threads:[~2023-10-05 15:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 13:10 [PATCH RFC] tools: ynl: Add source files for nfsd netlink protocol Chuck Lever
2023-10-05 14:50 ` Jakub Kicinski [this message]
2023-10-05 15:00 ` Chuck Lever III
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=20231005075021.0da40d7d@kernel.org \
--to=kuba@kernel.org \
--cc=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=netdev@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 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.