From: "H. Peter Anvin" <hpa@zytor.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Andi Kleen <andi@firstfloor.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Remove __visible from asmlinkage for 3.15
Date: Thu, 01 May 2014 22:38:24 -0700 [thread overview]
Message-ID: <53632F50.9010506@zytor.com> (raw)
In-Reply-To: <CA+55aFwc5znv-mqSX9nwVWNoXRUekoTiia4vgLgxauQcVZD15w@mail.gmail.com>
On 05/01/2014 05:52 PM, Linus Torvalds wrote:
> On Thu, May 1, 2014 at 3:44 PM, Andi Kleen <andi@firstfloor.org> wrote:
>> This is the earlier patchkit based on Linus original feedback.
>> It should be merged for 3.15 to finally quell the asmlinkage warnings
>> that are visible in various configurations.
>
> Ack, looks good to me. I'm assuming I'll get this through the -tip
> tree, otherwise holler and I'll pick it up directly, but it's not like
> there is any major hurry.
>
How about I put it into tip/urgent, but for next week's pull so it gets
some time to cook first...
-hpa
next prev parent reply other threads:[~2014-05-02 5:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-01 22:44 Remove __visible from asmlinkage for 3.15 Andi Kleen
2014-05-01 22:44 ` [PATCH 1/3] Revert "lto: Make asmlinkage __visible" Andi Kleen
2014-05-05 23:12 ` [tip:x86/urgent] asmlinkage: " tip-bot for Andi Kleen
2014-05-01 22:44 ` [PATCH 2/3] asmlinkage, x86: Add explicit __visible to arch/x86/* Andi Kleen
2014-05-05 23:12 ` [tip:x86/urgent] asmlinkage, x86: Add explicit __visible to arch/ x86/* tip-bot for Andi Kleen
2014-05-01 22:44 ` [PATCH 3/3] asmlinkage: Add explicit __visible to drivers/*, lib/*, kernel/* Andi Kleen
2014-05-05 23:12 ` [tip:x86/urgent] " tip-bot for Andi Kleen
2014-05-02 0:52 ` Remove __visible from asmlinkage for 3.15 Linus Torvalds
2014-05-02 5:38 ` H. Peter Anvin [this message]
2014-05-02 16:12 ` Linus Torvalds
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=53632F50.9010506@zytor.com \
--to=hpa@zytor.com \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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