From: Matthew Wilcox <willy@debian.org>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Christoph Hellwig <hch@lst.de>,
linux-kernel@vger.kernel.org,
kernel-janitor-discuss@lists.sourceforge.net
Subject: Re: [PATCH] change allow_write_access/deny_write_access prototype
Date: Sun, 17 Nov 2002 19:47:42 +0000 [thread overview]
Message-ID: <20021117194742.D7530@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0211171036360.22525-100000@home.transmeta.com>; from torvalds@transmeta.com on Sun, Nov 17, 2002 at 10:39:47AM -0800
On Sun, Nov 17, 2002 at 10:39:47AM -0800, Linus Torvalds wrote:
> Also, I'm going to stop applying the header file cleanups altogether
> unless the people who send them to me check that things compile afterwards
> a lot better.
>
> Arnaldo has been helping a lot in fixing stuff up after the cleanups,
> thanks go to him. The last net.h/fs.h cleanup broke pcm_native.c, for
> example.
I'm quite happy to test that my header cleanups don't break things --
but there are many things which don't currently compile anyway. I try
to enable the things I think my changes will break, but I didn't spot
the isapnp one my pci_dev changes broke. Could I ask that you update
defconfig with your .config again so we can be sure things don't break
_your_ build?
--
Revolutions do not require corporate support.
next prev parent reply other threads:[~2002-11-17 19:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-17 18:31 [PATCH] change allow_write_access/deny_write_access prototype Christoph Hellwig
2002-11-17 18:39 ` Linus Torvalds
2002-11-17 19:47 ` Matthew Wilcox [this message]
2002-11-17 20:16 ` Linus Torvalds
2002-11-17 19:06 ` Alexander Viro
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=20021117194742.D7530@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=hch@lst.de \
--cc=kernel-janitor-discuss@lists.sourceforge.net \
--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 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.