From: "H. Peter Anvin" <hpa@zytor.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Matt Fleming <matt@console-pimps.org>,
Ingo Molnar <mingo@kernel.org>,
"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] EFI changes for v3.11
Date: Mon, 08 Jul 2013 11:36:12 -0700 [thread overview]
Message-ID: <51DB069C.1010607@zytor.com> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F31C76880@ORSMSX106.amr.corp.intel.com>
On 07/08/2013 10:29 AM, Luck, Tony wrote:
>>> ----------------------------------------------------------------
>>> Tony Luck (1):
>>> [IA64] sim: Add casts to avoid assignment warnings
>>>
>>> arch/ia64/hp/sim/boot/fw-emu.c | 20 ++++++++++----------
>>> 1 file changed, 10 insertions(+), 10 deletions(-)
>>
>> I don't see this commit in Linus' tree so presumably Tony is still
>> seeing these warnings.
>
> Correct - I see 10 warning about "assignment makes pointer from integer"
> when building Linus' tree (HEAD = d2b4a646).
>
> My patch doesn't appear to be in linux-next either (next-20130708).
>
> I had hoped to have this patch follow in the same path that the
> one that changed the types and introduced the warnings took ...
> but since that didn't work perhaps I should just ask Linus to pull
> it from my ia64 tree.
>
I can push it, although it seems a bit odd to me to push an ia64-only
patch through the x86 tree.
Let me know what you prefer.
-hpa
next prev parent reply other threads:[~2013-07-08 18:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-26 12:23 Matt Fleming
2013-07-03 8:19 ` Matt Fleming
2013-07-08 17:29 ` Luck, Tony
2013-07-08 18:36 ` H. Peter Anvin [this message]
2013-07-08 19:02 ` Tony Luck
-- strict thread matches above, loose matches on Subject: below --
2013-06-13 13:46 Matt Fleming
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=51DB069C.1010607@zytor.com \
--to=hpa@zytor.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@console-pimps.org \
--cc=mingo@kernel.org \
--cc=tony.luck@intel.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
all inboxes | Powered by JetHome®