From: Jan Kara <jack@suse.cz> To: Christoph Hellwig <hch@lst.de> Cc: Andrew Morton <akpm@linux-foundation.org>, Miquel Raynal <miquel.raynal@bootlin.com>, Richard Weinberger <richard@nod.at>, Vignesh Raghavendra <vigneshr@ti.com>, Jan Kara <jack@suse.cz>, linux-mtd@lists.infradead.org, linux-fsdevel@vger.kernel.org, linux-mm@kvack.org Subject: Re: [PATCH 1/5] mm: export bdi_unregister Date: Fri, 22 Oct 2021 10:41:49 +0200 [thread overview] Message-ID: <20211022084149.GB1026@quack2.suse.cz> (raw) In-Reply-To: <20211021124441.668816-2-hch@lst.de> On Thu 21-10-21 14:44:37, Christoph Hellwig wrote: > To wind down the magic auto-unregister semantics we'll need to push this > into modular code. > > Signed-off-by: Christoph Hellwig <hch@lst.de> Looks good. Feel free to add: Reviewed-by: Jan Kara <jack@suse.cz> Honza > --- > mm/backing-dev.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/mm/backing-dev.c b/mm/backing-dev.c > index 4a9d4e27d0d9b..8a46a0a4b72fa 100644 > --- a/mm/backing-dev.c > +++ b/mm/backing-dev.c > @@ -958,6 +958,7 @@ void bdi_unregister(struct backing_dev_info *bdi) > bdi->owner = NULL; > } > } > +EXPORT_SYMBOL(bdi_unregister); > > static void release_bdi(struct kref *ref) > { > -- > 2.30.2 > -- Jan Kara <jack@suse.com> SUSE Labs, CR
WARNING: multiple messages have this Message-ID (diff)
From: Jan Kara <jack@suse.cz> To: Christoph Hellwig <hch@lst.de> Cc: Andrew Morton <akpm@linux-foundation.org>, Miquel Raynal <miquel.raynal@bootlin.com>, Richard Weinberger <richard@nod.at>, Vignesh Raghavendra <vigneshr@ti.com>, Jan Kara <jack@suse.cz>, linux-mtd@lists.infradead.org, linux-fsdevel@vger.kernel.org, linux-mm@kvack.org Subject: Re: [PATCH 1/5] mm: export bdi_unregister Date: Fri, 22 Oct 2021 10:41:49 +0200 [thread overview] Message-ID: <20211022084149.GB1026@quack2.suse.cz> (raw) In-Reply-To: <20211021124441.668816-2-hch@lst.de> On Thu 21-10-21 14:44:37, Christoph Hellwig wrote: > To wind down the magic auto-unregister semantics we'll need to push this > into modular code. > > Signed-off-by: Christoph Hellwig <hch@lst.de> Looks good. Feel free to add: Reviewed-by: Jan Kara <jack@suse.cz> Honza > --- > mm/backing-dev.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/mm/backing-dev.c b/mm/backing-dev.c > index 4a9d4e27d0d9b..8a46a0a4b72fa 100644 > --- a/mm/backing-dev.c > +++ b/mm/backing-dev.c > @@ -958,6 +958,7 @@ void bdi_unregister(struct backing_dev_info *bdi) > bdi->owner = NULL; > } > } > +EXPORT_SYMBOL(bdi_unregister); > > static void release_bdi(struct kref *ref) > { > -- > 2.30.2 > -- Jan Kara <jack@suse.com> SUSE Labs, CR ______________________________________________________ Linux MTD discussion mailing list http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2021-10-22 8:41 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-21 12:44 simplify bdi unregistation Christoph Hellwig 2021-10-21 12:44 ` Christoph Hellwig 2021-10-21 12:44 ` [PATCH 1/5] mm: export bdi_unregister Christoph Hellwig 2021-10-21 12:44 ` Christoph Hellwig 2021-10-22 8:41 ` Jan Kara [this message] 2021-10-22 8:41 ` Jan Kara 2021-10-21 12:44 ` [PATCH 2/5] mtd: call bdi_unregister explicitly Christoph Hellwig 2021-10-21 12:44 ` Christoph Hellwig 2021-10-22 8:43 ` Jan Kara 2021-10-22 8:43 ` Jan Kara 2021-10-21 12:44 ` [PATCH 3/5] fs: explicitly unregister per-superblock BDIs Christoph Hellwig 2021-10-21 12:44 ` Christoph Hellwig 2021-10-22 8:48 ` Jan Kara 2021-10-22 8:48 ` Jan Kara 2021-10-21 12:44 ` [PATCH 4/5] mm: don't automatically unregister bdis Christoph Hellwig 2021-10-21 12:44 ` Christoph Hellwig 2021-10-22 8:51 ` Jan Kara 2021-10-22 8:51 ` Jan Kara 2021-10-21 12:44 ` [PATCH 5/5] mm: simplify bdi refcounting Christoph Hellwig 2021-10-21 12:44 ` Christoph Hellwig 2021-10-22 9:02 ` Jan Kara 2021-10-22 9:02 ` Jan Kara 2021-10-27 7:42 ` Christoph Hellwig 2021-10-27 7:42 ` Christoph Hellwig 2021-10-27 9:47 ` Jan Kara 2021-10-27 9:47 ` Jan Kara
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=20211022084149.GB1026@quack2.suse.cz \ --to=jack@suse.cz \ --cc=akpm@linux-foundation.org \ --cc=hch@lst.de \ --cc=linux-fsdevel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=linux-mtd@lists.infradead.org \ --cc=miquel.raynal@bootlin.com \ --cc=richard@nod.at \ --cc=vigneshr@ti.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: linkBe 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.