From: rct@gherkin.frus.com (Bob Tracy)
To: linux-kernel@vger.kernel.org
Subject: [PATCH] linux/fs/ufs/namei.c
Date: Thu, 11 Sep 2003 09:03:43 -0500 (CDT) [thread overview]
Message-ID: <20030911140343.28348DBDB@gherkin.frus.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 758 bytes --]
The attached patch fixes a compilation problem (syntax) that
arises when using the recommended minimum (according to
linux/Documentation/Changes) gcc-2.95.3 compiler to build
2.6.0-test5. Would have found this sooner, but my
Slackware 8.0 laptop has been in use at a remote location
for the past several months :-).
<old_fart_mode><gasoline><match>
Don't much care for whatever C language standard revision
that allows this kind of sloppiness. However, gcc-3.2.2
handles it just fine.
</match></gasoline></old_fart_mode>
--
-----------------------------------------------------------------------
Bob Tracy WTO + WIPO = DMCA? http://www.anti-dmca.org
rct@frus.com
-----------------------------------------------------------------------
[-- Attachment #2: patch00t5_ufs --]
[-- Type: text/plain, Size: 503 bytes --]
--- linux/fs/ufs/namei.c.orig Wed Sep 10 10:23:03 2003
+++ linux/fs/ufs/namei.c Wed Sep 10 21:45:30 2003
@@ -113,10 +113,11 @@
static int ufs_mknod (struct inode * dir, struct dentry *dentry, int mode, dev_t rdev)
{
struct inode * inode;
+ int err;
if (!old_valid_dev(rdev))
return -EINVAL;
inode = ufs_new_inode(dir, mode);
- int err = PTR_ERR(inode);
+ err = PTR_ERR(inode);
if (!IS_ERR(inode)) {
init_special_inode(inode, mode, rdev);
/* NOTE: that'll go when we get wide dev_t */
reply other threads:[~2003-09-11 14:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030911140343.28348DBDB@gherkin.frus.com \
--to=rct@gherkin.frus.com \
--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;
as well as URLs for NNTP newsgroup(s).