[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1405747256.605.36.camel@jarvis.lan>
Date: Fri, 18 Jul 2014 22:20:56 -0700
From: James Bottomley <James.Bottomley@...senPartnership.com>
To: Nick Krause <xerofoify@...il.com>
Cc: deller@....de, tiwai@...e.de, Jiri Kosina <jkosina@...e.cz>,
Joe Perches <joe@...ches.com>, dave.anglin@...l.net,
linux-parisc@...r.kernel.org,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] parisc: Remove FIXME comment
On Fri, 2014-07-18 at 22:25 -0400, Nick Krause wrote:
> On Fri, Jul 18, 2014 at 5:03 PM, James Bottomley
> <James.Bottomley@...senpartnership.com> wrote:
> > On Fri, 2014-07-18 at 16:37 -0400, Nicholas Krause wrote:
> >> The comment for size of frame not being needed is incorrect , the
> >> function called needs this parameter.
> >
> > Actually, that's not correct. The point of the FIXME is that fram_size
> > is only used in a debug print and could be eliminated since the
> > internals of the function excluding the debugging statements don't use
> > it.
> >
> > James
> >
> >
>
> So I need to need a patch removing the parameter from the function
> and this part of the code?
Well, no, I'm not sure there's any action to take. The FIXME reminds us
that there's no actual use of the frame size in the function body except
for the debugging prints. The parameter could be removed if everyone
who debugs the kernel agrees either to remove the debug code or remove
the frame pointer from the prints, but it's probably not worth bothering
about, which is why it's still there.
James
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists