From: Richard Weinberger <richard@nod.at>
To: Christian Brauner <brauner@kernel.org>
Cc: hch <hch@lst.de>, Jan Kara <jack@suse.cz>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
linux-mtd <linux-mtd@lists.infradead.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH 1/2] fs: export sget_dev()
Date: Tue, 29 Aug 2023 18:55:04 +0200 (CEST) [thread overview]
Message-ID: <340229452.1869458.1693328104443.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <20230829-alpinsport-abwerben-4c19ebb9a437@brauner>
----- Ursprüngliche Mail -----
> Von: "Christian Brauner" <brauner@kernel.org>
> An: "hch" <hch@lst.de>, "Jan Kara" <jack@suse.cz>, "richard" <richard@nod.at>
> CC: "Miquel Raynal" <miquel.raynal@bootlin.com>, "Vignesh Raghavendra" <vigneshr@ti.com>, "linux-mtd"
> <linux-mtd@lists.infradead.org>, "linux-fsdevel" <linux-fsdevel@vger.kernel.org>
> Gesendet: Dienstag, 29. August 2023 18:29:16
> Betreff: Re: [PATCH 1/2] fs: export sget_dev()
>> + return sget_fc(fc, super_s_dev_set, super_s_dev_test);
>
> return sget_fc(fc, super_s_dev_test, super_s_dev_set);
>
> Sorry, dumb typo that I had already fixed in tree...
What tree does this patch apply to? linux-next?
I gave it a quick try on Linus' tree but it failed too:
fs/super.c: In function ‘get_tree_bdev’:
fs/super.c:1293:19: error: ‘dev’ undeclared (first use in this function); did you mean ‘bdev’?
s = sget_dev(fc, dev);
^~~
bdev
fs/super.c:1293:19: note: each undeclared identifier is reported only once for each function it appears in
Thanks,
//richard
next prev parent reply other threads:[~2023-08-29 16:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 15:23 [PATCH 0/2] mtd: switch to keying by dev_t Christian Brauner
2023-08-29 15:23 ` [PATCH 1/2] fs: export sget_dev() Christian Brauner
2023-08-29 16:29 ` Christian Brauner
2023-08-29 16:55 ` Richard Weinberger [this message]
2023-08-30 6:13 ` hch
2023-08-30 7:51 ` Christian Brauner
2023-08-30 6:14 ` Christoph Hellwig
2023-08-30 8:05 ` Christian Brauner
2023-08-30 9:38 ` Jan Kara
2023-08-30 9:43 ` Christian Brauner
2023-08-30 10:02 ` Christian Brauner
2023-08-30 10:10 ` Jan Kara
2023-08-29 15:23 ` [PATCH 2/2] mtd: key superblock by device number Christian Brauner
2023-08-30 10:13 ` Jan Kara
2023-08-30 9:50 ` [PATCH 0/2] mtd: switch to keying by dev_t Christian Brauner
2023-08-30 10:15 ` Richard Weinberger
2023-08-30 11:52 ` Christoph Hellwig
2023-08-30 12:19 ` Christian Brauner
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=340229452.1869458.1693328104443.JavaMail.zimbra@nod.at \
--to=richard@nod.at \
--cc=brauner@kernel.org \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--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: 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).