All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luis Chamberlain <mcgrof@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: axboe@kernel.dk, sth@linux.ibm.com, hoeppner@linux.ibm.com,
	hca@linux.ibm.com, gor@linux.ibm.com, agordeev@linux.ibm.com,
	borntraeger@linux.ibm.com, linux-block@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] block: annotate bdev_disk_changed() deprecation with a symbol namespace
Date: Mon, 27 Mar 2023 16:08:52 -0700	[thread overview]
Message-ID: <ZCIiBHyrzDoTJPXT@bombadil.infradead.org> (raw)
In-Reply-To: <ZCIgavqUnw0Z3A3t@bombadil.infradead.org>

On Mon, Mar 27, 2023 at 04:02:02PM -0700, Luis Chamberlain wrote:
> On Mon, Mar 27, 2023 at 03:16:39PM -0700, Christoph Hellwig wrote:
> > What I'd really want is something like an
> > 
> > EXPORT_SYMBOL_FOR(bdev_disk_changed, loop, CONFIG_BLK_DEV_LOOP);
> > EXPORT_SYMBOL_FOR(bdev_disk_changed, dasd_kmod, CONFIG_DASD);
> > 
> > Which ensures that the symbol lookup only succeeds for loop.ko and
> > dasd_kmod.ko, and that the export only happens if the relevant
> > symbols are set.
> 
> I think that could be done, sure.

BTW is anyone aware of similar exports which are stuck in this way?

  Luis

  reply	other threads:[~2023-03-27 23:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-27 18:44 [PATCH] block: annotate bdev_disk_changed() deprecation with a symbol namespace Luis Chamberlain
2023-03-27 22:16 ` Christoph Hellwig
2023-03-27 23:02   ` Luis Chamberlain
2023-03-27 23:08     ` Luis Chamberlain [this message]
2023-03-27 23:20       ` 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=ZCIiBHyrzDoTJPXT@bombadil.infradead.org \
    --to=mcgrof@kernel.org \
    --cc=agordeev@linux.ibm.com \
    --cc=axboe@kernel.dk \
    --cc=borntraeger@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=hch@infradead.org \
    --cc=hoeppner@linux.ibm.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sth@linux.ibm.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.