From: "Nick Warne" <nick@ukfsn.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Typo in fs/smbfs/file.c
Date: Sat, 12 Jun 2004 10:15:55 +0100 [thread overview]
Message-ID: <40CAD7DB.3188.17917F3D@localhost> (raw)
I reported this sometime back, and it appears it's not so much of a
typo, but GCC allows both in some cases - but not _my_ GCC.
http://lkml.org/lkml/2004/3/14/53
I have to change to upper case 'Z' every new build to get it to build
clean.
Nick
--
"When you're chewing on life's gristle,
Don't grumble, Give a whistle..."
next reply other threads:[~2004-06-12 9:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-12 9:15 Nick Warne [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-11 21:14 Typo in fs/smbfs/file.c Bernhard Wesely
2004-06-11 21:53 ` Jörn Engel
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=40CAD7DB.3188.17917F3D@localhost \
--to=nick@ukfsn.org \
--cc=linux-kernel@vger.kernel.org \
/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