From: Christoph Hellwig <hch@infradead.org>
To: Christoph Hellwig <hch@lst.de>
Cc: William McVicker <willmcvicker@google.com>,
Theodore Ts'o <tytso@mit.edu>,
linux-ext4@vger.kernel.org,
"Stephen E. Baker" <baker.stephen.e@gmail.com>,
adilger.kernel@dilger.ca
Subject: Re: simplify ext4_sb_read_encoding regression
Date: Sat, 15 Apr 2023 22:56:23 -0700 [thread overview]
Message-ID: <ZDuOB8We29IAYR/4@infradead.org> (raw)
In-Reply-To: <20230416054742.GA5427@lst.de>
On Sun, Apr 16, 2023 at 07:47:42AM +0200, Christoph Hellwig wrote:
> We could do that, but it seems a bit ugly. What prevents symbol_request
> from working properly for this case in your setup?
To anwer to myself - I guess we need something else than a plain
EXPORT_SYMBOL for everything that is used by
symbol_request. Which would be a nice cleanly anyway - exports for
symbol_request aren't normal exports and should probably have a clear
marker just to stand out anyway.
next prev parent reply other threads:[~2023-04-16 5:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFDdnB1Rq3vNe_qt_0u+inzOuL4vrGhgbOoQZKBwfBktni=Npw@mail.gmail.com>
2022-05-29 1:24 ` simplify ext4_sb_read_encoding regression Theodore Ts'o
2022-05-29 12:19 ` Theodore Ts'o
2022-05-29 22:49 ` Stephen E. Baker
2022-05-30 1:49 ` Theodore Ts'o
2022-05-30 22:20 ` Stephen E. Baker
2022-05-31 0:16 ` Theodore Ts'o
2022-05-31 1:37 ` Theodore Ts'o
2022-06-02 2:06 ` Stephen E. Baker
2022-06-02 14:47 ` Theodore Ts'o
2023-04-14 23:01 ` William McVicker
2023-04-16 5:47 ` Christoph Hellwig
2023-04-16 5:56 ` Christoph Hellwig [this message]
2023-04-17 3:26 ` Theodore Ts'o
2023-04-17 16:16 ` Will McVicker
2022-05-28 22:55 Stephen E. Baker
2022-05-30 14:21 ` Gabriel Krisman Bertazi
2022-05-30 22:27 ` Stephen E. Baker
2022-05-31 0:56 ` Dave Chinner
2022-05-31 2:39 ` Stephen E. Baker
2022-06-02 17:47 ` Gabriel Krisman Bertazi
2022-06-05 0:11 ` Stephen E. Baker
2022-06-05 3:21 ` Stephen E. Baker
2022-06-05 6:23 ` Gabriel Krisman Bertazi
2022-06-05 13:56 ` Stephen E. Baker
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=ZDuOB8We29IAYR/4@infradead.org \
--to=hch@infradead.org \
--cc=adilger.kernel@dilger.ca \
--cc=baker.stephen.e@gmail.com \
--cc=hch@lst.de \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=willmcvicker@google.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;
as well as URLs for NNTP newsgroup(s).