From: Carsten Emde <C.Emde@osadl.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Nicholas Mc Guire <der.herr@hofr.at>,
Thomas Gleixner <tglx@linutronix.de>,
RT-users <linux-rt-users@vger.kernel.org>
Subject: Re: [PATCH 0/1] Re: [PATCH RT] latency-hist: mostly checkpatch cleanup
Date: Fri, 14 Feb 2014 21:33:31 +0100 [thread overview]
Message-ID: <52FE7D9B.5060301@osadl.org> (raw)
In-Reply-To: <52FE728F.3060908@linutronix.de>
On 02/14/2014 08:46 PM, Sebastian Andrzej Siewior wrote:
> On 02/14/2014 06:16 PM, Carsten Emde wrote:
>> you submitted a patch of a patch - it's not funny and very difficult to read.
>> I allowed myself to transform it to a normal separate patch on top of the one
>> that you patched. It can be merged lateron.
>> Isn't this better? (We always did it this way.)
> Yes, we always did that way. This time it is different.
> I received 20 patches from Nicholas dealing with checkpatch issues. It
> contained code changes like fixes of white space and other changes that
> fall into the category cosmetic - code change at all. Others change the
> body of the patch because checkpatch did not like a twice the same
> person in a signed-of-by line or Toasted-by was not a valid tag and so
> on.
> I did not want any of this patches to extend unnecessary the -RT queue
> so I want them merged right in the first patch where the problem occurs.
> I also did not want to deal with fallout when I merge the
> patches back into the original and a following patch does no longer
> apply. So I asked Nicholas do it this way.
> This patch did a little more because it replaced NR_CPUS with something
> else and therefore I considered it important enough to send it to the
> mailing list. The other will be mentioned in the announcement email
> will be part of the incremental patch.
Ok.
@@ -161,11 +161,11 @@ void notrace latency_hist(int latency_ty
{
struct hist_data *my_hist;
#if defined(CONFIG_WAKEUP_LATENCY_HIST) || \
- defined(CONFIG_MISSED_TIMER_OFFSETS_HIST)
+ defined(CONFIG_MISSED_TIMER_OFFSETS_HIST)
struct maxlatproc_data *mp = NULL;
#endif
- if (cpu < 0 || cpu >= NR_CPUS || latency_type < 0 ||
+ if (!cpu_possible(cpu) || latency_type < 0 ||
latency_type >= MAX_LATENCY_TYPE)
return;
Acked-by: Carsten Emde <C.Emde@osadl.org>
prev parent reply other threads:[~2014-02-14 20:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 17:16 [PATCH 0/1] Re: [PATCH RT] latency-hist: mostly checkpatch cleanup Carsten Emde
2014-02-14 17:16 ` [PATCH 1/1] From: Nicholas Mc Guire <der.herr@hofr.at> Carsten Emde
2014-02-14 19:46 ` [PATCH 0/1] Re: [PATCH RT] latency-hist: mostly checkpatch cleanup Sebastian Andrzej Siewior
2014-02-14 20:33 ` Carsten Emde [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=52FE7D9B.5060301@osadl.org \
--to=c.emde@osadl.org \
--cc=bigeasy@linutronix.de \
--cc=der.herr@hofr.at \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglx@linutronix.de \
/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.