From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Matt Mackall <mpm@selenic.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.1-rc1-tiny1 tree for small systems
Date: Fri, 9 Jan 2004 18:15:14 -0200 [thread overview]
Message-ID: <20040109201514.GG18853@conectiva.com.br> (raw)
In-Reply-To: <m1wu82i6tm.fsf@ebiederm.dsl.xmission.com>
Em Thu, Jan 08, 2004 at 12:22:29PM -0700, Eric W. Biederman escreveu:
> Matt Mackall <mpm@selenic.com> writes:
>
> > On Sun, Jan 04, 2004 at 05:00:49PM -0700, Eric W. Biederman wrote:
> > > On the side of useless ugly. But interesting in what I had to touch
> > > the following patch is a first crude stab at removing block device
> > > support from the kernel.
> >
> > This looks good. If you can send me a version with
> > /BLOCK_DEVICE/BLOCK/, etc., I'll put it in.
>
> Ok. I have just had a chance to clean some things up. Attached
> is my latest and hopefully clean set up diffs against 2.6.1-rc1-tiny1
> diff -uNr -X linux-ignore-files linux-2.6.1-rc1-tiny1.compile-fixes/include/linux/fs.h linux-2.6.1-rc1-tiny1.config-block/include/linux/fs.h
> --- linux-2.6.1-rc1-tiny1.compile-fixes/include/linux/fs.h Sun Jan 4 00:03:57 2004
> +++ linux-2.6.1-rc1-tiny1.config-block/include/linux/fs.h Thu Jan 8 11:29:14 2004
> @@ -1210,7 +1214,11 @@
> extern void sync_supers(void);
> extern void sync_filesystems(int wait);
> extern void emergency_sync(void);
> +#ifdef CONFIG_bLOCK
^
|
|
|
|
oops :)
next prev parent reply other threads:[~2004-01-09 20:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-03 3:08 Matt Mackall
2004-01-04 7:42 ` Eric W. Biederman
2004-01-04 8:40 ` Matt Mackall
2004-01-04 16:02 ` Eric W. Biederman
2004-01-05 0:00 ` Eric W. Biederman
2004-01-05 0:34 ` viro
2004-01-05 4:34 ` Eric W. Biederman
[not found] ` <20040105170938.GY18208@waste.org>
2004-01-08 19:22 ` Eric W. Biederman
2004-01-09 20:15 ` Arnaldo Carvalho de Melo [this message]
2004-01-10 21:49 ` Matt Mackall
2004-01-08 21:04 ` bill davidsen
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=20040109201514.GG18853@conectiva.com.br \
--to=acme@conectiva.com.br \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.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
Powered by JetHome