From: Al Viro <viro@zeniv.linux.org.uk>
To: Christoph Hellwig <hch@lst.de>
Cc: akpm@linux-foundation.org, x86@kernel.org,
linux-alpha@vger.kernel.org, linux-m68k@lists.linux-m68k.org,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH] net: unexport csum_and_copy_{from,to}_user
Date: Tue, 17 May 2022 22:05:42 +0000 [thread overview]
Message-ID: <YoQcNkB6R/E3vf51@zeniv-ca.linux.org.uk> (raw)
In-Reply-To: <20220421070440.1282704-1-hch@lst.de>
On Thu, Apr 21, 2022 at 09:04:40AM +0200, Christoph Hellwig wrote:
> csum_and_copy_from_user and csum_and_copy_to_user are exported by
> a few architectures, but not actually used in modular code. Drop
> the exports.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Acked-by: Al Viro <viro@zeniv.linux.org.uk>
Not sure which tree should it go through - Arnd's, perhaps?
WARNING: multiple messages have this Message-ID (diff)
From: Al Viro <viro@zeniv.linux.org.uk>
To: Christoph Hellwig <hch@lst.de>
Cc: netdev@vger.kernel.org, x86@kernel.org,
linux-kernel@vger.kernel.org, linux-m68k@lists.linux-m68k.org,
linux-alpha@vger.kernel.org, akpm@linux-foundation.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] net: unexport csum_and_copy_{from,to}_user
Date: Tue, 17 May 2022 22:05:42 +0000 [thread overview]
Message-ID: <YoQcNkB6R/E3vf51@zeniv-ca.linux.org.uk> (raw)
In-Reply-To: <20220421070440.1282704-1-hch@lst.de>
On Thu, Apr 21, 2022 at 09:04:40AM +0200, Christoph Hellwig wrote:
> csum_and_copy_from_user and csum_and_copy_to_user are exported by
> a few architectures, but not actually used in modular code. Drop
> the exports.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Acked-by: Al Viro <viro@zeniv.linux.org.uk>
Not sure which tree should it go through - Arnd's, perhaps?
next prev parent reply other threads:[~2022-05-17 22:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 7:04 [PATCH] net: unexport csum_and_copy_{from,to}_user Christoph Hellwig
2022-04-21 7:04 ` Christoph Hellwig
2022-04-22 22:57 ` Jakub Kicinski
2022-04-22 22:57 ` Jakub Kicinski
2022-04-23 8:05 ` Geert Uytterhoeven
2022-04-23 8:05 ` Geert Uytterhoeven
2022-04-23 8:05 ` Geert Uytterhoeven
2022-04-23 9:47 ` Arnd Bergmann
2022-04-23 9:47 ` Arnd Bergmann
2022-04-23 13:42 ` Michael Ellerman
2022-04-23 13:42 ` Michael Ellerman
2022-05-17 22:05 ` Al Viro [this message]
2022-05-17 22:05 ` Al Viro
2022-05-18 0:39 ` Michael Ellerman
2022-05-18 0:39 ` Michael Ellerman
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=YoQcNkB6R/E3vf51@zeniv-ca.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=x86@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.