From: Segher Boessenkool <segher@kernel.crashing.org>
To: Christoph Hellwig <hch@lst.de>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
aneesh.kumar@linux.ibm.com
Subject: Re: [PATCH] powerpc: remove the __kernel_io_end export
Date: Mon, 29 Apr 2019 06:57:06 -0500 [thread overview]
Message-ID: <20190429115706.GO8599@gate.crashing.org> (raw)
In-Reply-To: <20190429115241.12621-1-hch@lst.de>
On Mon, Apr 29, 2019 at 06:52:41AM -0500, Christoph Hellwig wrote:
> This export was added in this merge window, but without any actual
> user, or justification for a modular user.
Hi Christoph,
> -unsigned long __kernel_io_end;
> EXPORT_SYMBOL(__kernel_io_end);
Does that work? Don't you need to remove that second line, as well?
Segher
next prev parent reply other threads:[~2019-04-29 12:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 11:52 [PATCH] powerpc: remove the __kernel_io_end export Christoph Hellwig
2019-04-29 11:57 ` Segher Boessenkool [this message]
2019-04-29 12:00 ` Christoph Hellwig
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=20190429115706.GO8599@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).