From: Andrew Morton <akpm@linux-foundation.org>
To: Marcin Slusarz <marcin.slusarz@gmail.com>
Cc: linux-kernel@vger.kernel.org, bfennema@falcon.csc.calpoly.edu,
jack@suse.cz
Subject: Re: [PATCH 1/5] udf: remove wrong prototype of udf_readdir
Date: Fri, 21 Dec 2007 16:21:17 -0800 [thread overview]
Message-ID: <20071221162117.faa3d16d.akpm@linux-foundation.org> (raw)
In-Reply-To: <20071221155453.GA8575@joi>
On Fri, 21 Dec 2007 16:55:03 +0100
Marcin Slusarz <marcin.slusarz@gmail.com> wrote:
> sparse generated:
> fs/udf/dir.c:78:5: warning: symbol 'udf_readdir' was not declared. Should it be static?
> there are 2 different prototypes of udf_readdir - remove them and move
> code around to make it still compile
Drat. I just applied six udf patches from you and now we have a new patch
series of only five with no indication what changed.
I guess I really do need to apply my backlog in reverse time order.
next prev parent reply other threads:[~2007-12-22 0:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-21 15:55 [PATCH 1/5] udf: remove wrong prototype of udf_readdir Marcin Slusarz
2007-12-22 0:21 ` Andrew Morton [this message]
2007-12-22 9:00 ` Marcin Slusarz
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=20071221162117.faa3d16d.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bfennema@falcon.csc.calpoly.edu \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=marcin.slusarz@gmail.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.