public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Jaswinder Singh Rajput <jaswinder@kernel.org>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	"H. Peter Anvin" <hpa@kernel.org>,
	x86 maintainers <x86@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -tip] x86: entry_32.S fix compiling warnings
Date: Sat, 14 Mar 2009 08:14:15 +0100	[thread overview]
Message-ID: <20090314071415.GB22381@elte.hu> (raw)
In-Reply-To: <1237012693.18733.3.camel@ht.satnam>


* Jaswinder Singh Rajput <jaswinder@kernel.org> wrote:

> Hello Ingo,
> 
> Are these looks OK to you:
> 
> Subject: [PATCH] x86: entry_32.S fix compiling warnings
> 
> Fixed:
>  arch/x86/kernel/entry_32.S:446: Warning: 00000000080001d1 shortened to 00000000000001d1
>  arch/x86/kernel/entry_32.S:457: Warning: 000000000800feff shortened to 000000000000feff
>  arch/x86/kernel/entry_32.S:527: Warning: 00000000080001d1 shortened to 00000000000001d1
>  arch/x86/kernel/entry_32.S:541: Warning: 000000000800feff shortened to 000000000000feff
>  arch/x86/kernel/entry_32.S:676: Warning: 0000000008000091 shortened to 0000000000000091

ah, indeed - that's TIF_SYSCALL_FTRACE.

It's in fact faster to check 32 bit mask not a 16 bit mask.

Applied, thanks.

	Ingo

  reply	other threads:[~2009-03-14  7:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-14  6:38 [PATCH -tip] x86: entry_32.S fix compiling warnings Jaswinder Singh Rajput
2009-03-14  7:14 ` Ingo Molnar [this message]
2009-03-14  7:18 ` [tip:tracing/syscalls] x86: entry_32.S fix compile warnings - fix work mask bit width Jaswinder Singh Rajput
2009-03-14  8:13   ` Cyrill Gorcunov
2009-03-14  8:29     ` Jaswinder Singh Rajput
2009-03-14  8:45 ` Jaswinder Singh Rajput

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=20090314071415.GB22381@elte.hu \
    --to=mingo@elte.hu \
    --cc=fweisbec@gmail.com \
    --cc=hpa@kernel.org \
    --cc=jaswinder@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=x86@kernel.org \
    /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