From: John Kacur <jkacur@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org, Jon Masters <jcm@redhat.com>,
linux-rt-users@vger.kernel.org,
Clark Williams <williams@redhat.com>
Subject: Re: [PATCH -rt] Updates-from-Jon-Masters-for-hwlat_detector.c.patch
Date: Tue, 3 Nov 2009 14:50:22 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.00.0911031444090.6542@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.2.00.0911031413230.12138@localhost.localdomain>
On Tue, 3 Nov 2009, Thomas Gleixner wrote:
> On Mon, 2 Nov 2009, John Kacur wrote:
> > Updated patch just adds the error checking from Jon Masters then,
> > patched against -rt.
>
> Can you please inline patches ?
>
> @@ -607,7 +607,11 @@ static ssize_t debug_enable_fwrite(stru
> if (!enabled)
> goto unlock;
> enabled = 0;
> - stop_kthread();
> + err = stop_kthread();
> + if (0 != err) {
>
> Eeew !
Yeah, I saw that too and thought it a bit ugly. However, my goal was only
to make sure that the latest version of Jon's hwlat patch got into -rt, so
I didn't think it was my place to "fix" his style.
Note - even the much hated checkpatch program doesn't balk at that.
However that is hardly an authority.
If you read the introduction to "Expert C Programming - Deep C Secrets",
they mention that some programmers write
if (3==i)
instead of
if (i==3)
because if you mistakenly only type one '=', then the compiler can
complain about it, instead of silently assigning 3 to i.
I can only guess that is the sort of idea / habit that Jon got that style
from.
John
next prev parent reply other threads:[~2009-11-03 13:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-22 22:12 [PATCH -rt] Updates-from-Jon-Masters-for-hwlat_detector.c.patch John Kacur
2009-11-02 15:43 ` Thomas Gleixner
2009-11-02 19:46 ` John Kacur
2009-11-03 13:15 ` Thomas Gleixner
2009-11-03 13:50 ` John Kacur [this message]
2009-11-03 15:17 ` Jon Masters
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=alpine.LFD.2.00.0911031444090.6542@localhost.localdomain \
--to=jkacur@redhat.com \
--cc=jcm@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=williams@redhat.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