From: Christoph Hellwig <hch@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Evgeniy Dushistov <dushistov@mail.ru>,
Steven <stevenaaus@yahoo.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH]: ufs: fix symlink creation on ufs2
Date: Thu, 10 Jan 2008 08:40:41 +0000 [thread overview]
Message-ID: <20080110084040.GD10745@infradead.org> (raw)
In-Reply-To: <20080109235148.d5896897.akpm@linux-foundation.org>
On Wed, Jan 09, 2008 at 11:51:48PM -0800, Andrew Morton wrote:
> > +++ b/fs/ufs/super.c
> > @@ -131,6 +131,8 @@ static void ufs_print_super_stuff(struct super_block *sb,
> > printk(KERN_INFO" cs_nffree(Num of free frags): %llu\n",
> > (unsigned long long)
> > fs64_to_cpu(sb, usb3->fs_un1.fs_u2.cs_nffree));
> > + printk(KERN_INFO" fs_maxsymlinklen: %u\n",
> > + usb3->fs_un2.fs_44.fs_maxsymlinklen);
>
> I assume this needs conversion via fs32_to_cpu() before we print it.
Yes, it does. I wish people would run sparse before submitting patches :P
next prev parent reply other threads:[~2008-01-10 8:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-02 20:47 [PATCH]: ufs: fix symlink creation on ufs2 Evgeniy Dushistov
2008-01-10 7:51 ` Andrew Morton
2008-01-10 8:40 ` Christoph Hellwig [this message]
2008-01-10 8:44 ` Al 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=20080110084040.GD10745@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=dushistov@mail.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=stevenaaus@yahoo.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.