[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <173980282988.27803.8804843258021715339.b4-ty@oracle.com>
Date: Mon, 17 Feb 2025 09:34:36 -0500
From: cel@...nel.org
To: Olga Kornievskaia <okorniev@...hat.com>,
Dan Carpenter <dan.carpenter@...aro.org>
Cc: Chuck Lever <chuck.lever@...cle.com>,
Jeff Layton <jlayton@...nel.org>,
Neil Brown <neilb@...e.de>,
Dai Ngo <Dai.Ngo@...cle.com>,
Tom Talpey <tom@...pey.com>,
linux-nfs@...r.kernel.org,
linux-kernel@...r.kernel.org,
kernel-janitors@...r.kernel.org
Subject: Re: [PATCH next] nfsd: Fix a WARN_ONCE() message
From: Chuck Lever <chuck.lever@...cle.com>
On Mon, 17 Feb 2025 10:33:31 +0300, Dan Carpenter wrote:
> The first parameter of WARN_ONCE() is supposed to be the condition but
> it's missing here. This WARN_ONCE() will only print the "xcl_name".
>
>
Squashed into nfsd-next, thanks!
[1/1] nfsd: Fix a WARN_ONCE() message
(no commit info)
--
Chuck Lever
Powered by blists - more mailing lists