From: Alexander Viro <viro@math.psu.edu>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fs/super.c stuff (3/10)
Date: Mon, 11 Jun 2001 01:36:15 -0400 (EDT) [thread overview]
Message-ID: <Pine.GSO.4.21.0106110135430.24249-100000@weyl.math.psu.edu> (raw)
In-Reply-To: <Pine.GSO.4.21.0106110134230.24249-100000@weyl.math.psu.edu>
Grr... 4 of 10, that is. Sorry.
On Mon, 11 Jun 2001, Alexander Viro wrote:
> diff -urN S6-pre2-fsync_no_super/include/linux/fs.h S6-pre2-put_super/include/linux/fs.h
> --- S6-pre2-fsync_no_super/include/linux/fs.h Sun Jun 10 18:36:27 2001
> +++ S6-pre2-put_super/include/linux/fs.h Sun Jun 10 18:39:04 2001
> @@ -1320,7 +1320,6 @@
>
> extern struct file_system_type *get_fs_type(const char *name);
> extern struct super_block *get_super(kdev_t);
> -extern void put_super(kdev_t);
> static inline int is_mounted(kdev_t dev)
> {
> struct super_block *sb = get_super(dev);
>
>
>
prev parent reply other threads:[~2001-06-11 5:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-11 5:32 [PATCHes] fs/super.c stuff Alexander Viro
2001-06-11 5:33 ` [PATCH] fs/super.c stuff (1/10) Alexander Viro
2001-06-11 5:33 ` [PATCH] fs/super.c stuff (2/10) Alexander Viro
2001-06-11 5:34 ` [PATCH] fs/super.c stuff (3/10) Alexander Viro
2001-06-11 5:34 ` Alexander Viro
2001-06-11 5:35 ` [PATCH] fs/super.c stuff (5/10) Alexander Viro
2001-06-11 5:37 ` [PATCH] fs/super.c stuff (6/10) Alexander Viro
2001-06-11 5:37 ` [PATCH] fs/super.c stuff (7/10) Alexander Viro
2001-06-11 5:38 ` [PATCH] fs/super.c stuff (8/10) Alexander Viro
2001-06-11 5:39 ` [PATCH] fs/super.c stuff (9/10) Alexander Viro
2001-06-11 5:40 ` [PATCH] fs/super.c stuff (10/10) Alexander Viro
2001-06-11 5:36 ` Alexander Viro [this message]
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=Pine.GSO.4.21.0106110135430.24249-100000@weyl.math.psu.edu \
--to=viro@math.psu.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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).