From: Peter Zijlstra <peterz@infradead.org>
To: James Hogan <james.hogan@imgtec.com>
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] arch: include/asm/Kbuild: fix preempt.h sort order
Date: Sat, 30 Nov 2013 10:20:31 +0100 [thread overview]
Message-ID: <20131130092031.GG16796@laptop.programming.kicks-ass.net> (raw)
In-Reply-To: <1385736191-31862-1-git-send-email-james.hogan@imgtec.com>
On Fri, Nov 29, 2013 at 02:43:11PM +0000, James Hogan wrote:
> Commit a787870924db (sched, arch: Create asm/preempt.h) added the
> generic asm/preempt.h header, but took no notice of the sort order of
> various architecture's include/asm/Kbuild files. Move preempt.h into the
> correct sort position in files which are mostly already sorted.
Oh, I completely failed to notice they're sorted.
Thanks for fixing it up.
next prev parent reply other threads:[~2013-11-30 9:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-29 14:43 [PATCH] arch: include/asm/Kbuild: fix preempt.h sort order James Hogan
2013-11-30 9:20 ` Peter Zijlstra [this message]
2013-11-30 9:20 ` Peter Zijlstra
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=20131130092031.GG16796@laptop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=james.hogan@imgtec.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox