From: Christoph Hellwig <hch@infradead.org>
To: Kieran Bingham <kieranbingham@gmail.com>
Cc: Marco Stornelli <marco.stornelli@gmail.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linux Embedded <linux-embedded@vger.kernel.org>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
Tim Bird <tim.bird@am.sony.com>
Subject: Re: [PATCH 15/16] pramfs: test module
Date: Wed, 13 Oct 2010 07:23:51 -0400 [thread overview]
Message-ID: <20101013112351.GA16422@infradead.org> (raw)
In-Reply-To: <4CB301E4.40405@gmail.com>
On Mon, Oct 11, 2010 at 01:24:04PM +0100, Kieran Bingham wrote:
> >@@ -0,0 +1,49 @@
> >+/*
> >+ * FILE NAME fs/pramfs/namei.c
> FILE NAME != namei.c
Yes, that's why you should never do such filename comments which are not
only utterly prone to be out of data, but also 100% useless.
prev parent reply other threads:[~2010-10-13 11:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-10 16:37 [PATCH 15/16] pramfs: test module Marco Stornelli
2010-10-10 16:57 ` Randy Dunlap
2010-10-11 7:08 ` Marco Stornelli
2010-10-11 12:24 ` Kieran Bingham
2010-10-13 11:23 ` Christoph Hellwig [this message]
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=20101013112351.GA16422@infradead.org \
--to=hch@infradead.org \
--cc=kieranbingham@gmail.com \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.stornelli@gmail.com \
--cc=tim.bird@am.sony.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;
as well as URLs for NNTP newsgroup(s).