From: Frank Seidel <frank@f-seidel.de>
To: Rabin Vincent <rabin@rab.in>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Remove unneeded code in sys_getpriority
Date: Sun, 3 Feb 2008 19:10:28 +0100 [thread overview]
Message-ID: <200802031910.28621.frank@f-seidel.de> (raw)
In-Reply-To: <20080203175854.GB3124@ubuntu>
On Sunday 03 February 2008 18:58, Rabin Vincent wrote:
> Do you mean the PRIO_* cases in the switch? They're still independent
> of position after the patch because they don't fall through.
Yes, sure, this is fully correct now. Just if somehting whatsoever
is put ahead touching retval one need to take care of this here.
But as i don't have enough experience to know if this likely at all i'm
fully fine with it. Just wanted to note one should think about if
its worth the change.
Thanks,
Frank
prev parent reply other threads:[~2008-02-03 18:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-03 3:04 [PATCH] Remove unneeded code in sys_getpriority Rabin Vincent
2008-02-03 9:54 ` Frank Seidel
2008-02-03 17:58 ` Rabin Vincent
2008-02-03 18:10 ` Frank Seidel [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=200802031910.28621.frank@f-seidel.de \
--to=frank@f-seidel.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rabin@rab.in \
/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