From: Sasha Levin <sashal@kernel.org>
To: Pavel Machek <pavel@denx.de>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Olga Kornievskaia <kolga@netapp.com>,
Anna Schumaker <Anna.Schumaker@netapp.com>,
trond.myklebust@hammerspace.com, linux-nfs@vger.kernel.org
Subject: Re: [PATCH AUTOSEL 4.9 5/7] NFSv4 expose nfs_parse_server_name function
Date: Fri, 11 Feb 2022 09:49:20 -0500 [thread overview]
Message-ID: <YgZ3cPY6l5qp3D6G@sashalap> (raw)
In-Reply-To: <20220206221907.GA26066@duo.ucw.cz>
On Sun, Feb 06, 2022 at 11:19:08PM +0100, Pavel Machek wrote:
>Hi!
>
>> From: Olga Kornievskaia <kolga@netapp.com>
>>
>> [ Upstream commit f5b27cc6761e27ee6387a24df1a99ca77b360fea ]
>>
>> Make nfs_parse_server_name available outside of nfs4namespace.c.
>
>I don't think this makes sense for 4.9-stable. Noone uses the new
>export.
I'll drop it, thanks!
--
Thanks,
Sasha
next prev parent reply other threads:[~2022-02-11 14:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 20:36 [PATCH AUTOSEL 4.9 1/7] NFSv4 only print the label when its queried Sasha Levin
2022-02-03 20:36 ` [PATCH AUTOSEL 4.9 2/7] nfs: nfs4clinet: check the return value of kstrdup() Sasha Levin
2022-02-03 20:36 ` [PATCH AUTOSEL 4.9 3/7] netfilter: nf_conntrack_netbios_ns: fix helper module alias Sasha Levin
2022-02-06 22:17 ` Pavel Machek
2022-02-03 20:36 ` [PATCH AUTOSEL 4.9 4/7] NFSv4 remove zero number of fs_locations entries error check Sasha Levin
2022-02-03 20:36 ` [PATCH AUTOSEL 4.9 5/7] NFSv4 expose nfs_parse_server_name function Sasha Levin
2022-02-06 22:19 ` Pavel Machek
2022-02-11 14:49 ` Sasha Levin [this message]
2022-02-03 20:36 ` [PATCH AUTOSEL 4.9 6/7] scsi: target: iscsi: Make sure the np under each tpg is unique Sasha Levin
2022-02-03 20:36 ` [PATCH AUTOSEL 4.9 7/7] usb: dwc2: gadget: don't try to disable ep0 in dwc2_hsotg_suspend Sasha Levin
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=YgZ3cPY6l5qp3D6G@sashalap \
--to=sashal@kernel.org \
--cc=Anna.Schumaker@netapp.com \
--cc=kolga@netapp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=pavel@denx.de \
--cc=stable@vger.kernel.org \
--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
all inboxes | Powered by JetHome®