From: Jeff Layton <jlayton@redhat.com>
To: Bhumika Goyal <bhumirks@gmail.com>,
julia.lawall@lip6.fr, trond.myklebust@primarydata.com,
anna.schumaker@netapp.com, bfields@fieldses.org,
davem@davemloft.net, linux-nfs@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 0/4] make function arg and structures as const
Date: Tue, 17 Oct 2017 12:40:27 -0400 [thread overview]
Message-ID: <1508258427.4747.7.camel@redhat.com> (raw)
In-Reply-To: <1508256866-12798-1-git-send-email-bhumirks@gmail.com>
On Tue, 2017-10-17 at 18:14 +0200, Bhumika Goyal wrote:
> Make the function argument as const. After thing change, make
> the cache_detail structures as const.
>
> Bhumika Goyal (4):
> sunrpc: make the function arg as const
> NFS: make cache_detail structures const
> NFSD: make cache_detail structures const
> SUNRPC: make cache_detail structures const
>
> fs/nfs/dns_resolve.c | 2 +-
> fs/nfsd/export.c | 4 ++--
> fs/nfsd/nfs4idmap.c | 4 ++--
> include/linux/sunrpc/cache.h | 2 +-
> net/sunrpc/auth_gss/svcauth_gss.c | 4 ++--
> net/sunrpc/cache.c | 2 +-
> net/sunrpc/svcauth_unix.c | 4 ++--
> 7 files changed, 11 insertions(+), 11 deletions(-)
>
Looks pretty straightforward. You can add this to the set:
Reviewed-by: Jeff Layton <jlayton@redhat.com>
next prev parent reply other threads:[~2017-10-17 16:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 16:14 [PATCH 0/4] make function arg and structures as const Bhumika Goyal
2017-10-17 16:14 ` [PATCH 1/4] sunrpc: make the function arg " Bhumika Goyal
2017-10-17 16:14 ` Bhumika Goyal
2017-10-17 16:14 ` [PATCH 2/4] NFS: make cache_detail structure const Bhumika Goyal
2017-10-17 16:14 ` [PATCH 3/4] NFSD: make cache_detail structures const Bhumika Goyal
2017-10-17 16:14 ` Bhumika Goyal
2017-10-17 16:14 ` [PATCH 4/4] SUNRPC: " Bhumika Goyal
2017-10-17 16:40 ` Jeff Layton [this message]
2017-11-10 2:21 ` [PATCH 0/4] make function arg and structures as const J. Bruce Fields
2017-11-10 2:21 ` J. Bruce Fields
2017-11-10 15:09 ` Anna Schumaker
2017-11-10 15:29 ` J. Bruce Fields
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=1508258427.4747.7.camel@redhat.com \
--to=jlayton@redhat.com \
--cc=anna.schumaker@netapp.com \
--cc=bfields@fieldses.org \
--cc=bhumirks@gmail.com \
--cc=davem@davemloft.net \
--cc=julia.lawall@lip6.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=trond.myklebust@primarydata.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 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.