From: Al Viro <viro@ZenIV.linux.org.uk>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Harvey Harrison <harvey.harrison@gmail.com>, linux-next@vger.kernel.org
Subject: Re: [PATCH 3/3] proc: make grab_header static
Date: Fri, 18 Jul 2008 00:23:28 +0100 [thread overview]
Message-ID: <20080717232328.GO28946@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20080717150950.5d721d90.akpm@linux-foundation.org>
On Thu, Jul 17, 2008 at 03:09:50PM -0700, Andrew Morton wrote:
> On Thu, 17 Jul 2008 14:22:35 -0700
> Harvey Harrison <harvey.harrison@gmail.com> wrote:
>
> > fs/proc/proc_sysctl.c:69:25: warning: symbol 'grab_header' was not declared. Should it be static?
> urgh. We need to do something here.
>
> People are dumping large hunks of 2.6.28 material into linux-next
> during the merge window. This screws me up because I haven't merged
> into 2.6.27 yet, and my patch queue is based on linux-next. And I
> _have_ to do that, because lots of the git trees haven't merged into
> mainline yet.
FWIW, you are slightly misreading the situation - it *is* my fault, but
in a different way. What's happening is not development going into that
branch - it's untangling a huge pile of pending patches into sequence.
And yes, it should've gone public as-is a couple of weeks ago ;-/
next prev parent reply other threads:[~2008-07-17 23:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-17 21:22 [PATCH 3/3] proc: make grab_header static Harvey Harrison
2008-07-17 22:09 ` Andrew Morton
2008-07-17 22:15 ` Harvey Harrison
2008-07-17 22:38 ` Andrew Morton
2008-07-17 23:23 ` Al Viro [this message]
2008-07-17 23:36 ` Andrew Morton
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=20080717232328.GO28946@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=harvey.harrison@gmail.com \
--cc=linux-next@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 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.