All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Fleming <matt.fleming@intel.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Borislav Petkov <bp@alien8.de>, X86 ML <x86@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>, Borislav Petkov <bp@suse.de>,
	Matthew Garrett <matthew.garrett@nebula.com>
Subject: Re: [PATCH] x86, efi: Fix a build warning
Date: Thu, 25 Apr 2013 08:19:05 +0100	[thread overview]
Message-ID: <5178D8E9.7020102@intel.com> (raw)
In-Reply-To: <20130425065529.GD7806@gmail.com>

On 25/04/13 07:55, Ingo Molnar wrote:
> It's a basic cleanliness and robustness issue: we generally avoid type 
> casts in the kernel, because type casts override compile-time type checks 
> and are easy to get wrong. They are also ugly.
> 
> So in generaly we try to use the right type for the data structure, which 
> matches its usage (and standardize functions/methods around that type) - 
> then no cast is needed.

Yeah, I'm not advocating using casts, I was just saying "Oh, x86-64
avoids requiring the caller of efi_call_phys* to perform the cast by
doing it in the definition of efi_call*. That's why this is only
affecting 32-bit."

Cleaning this up would be nice. I think at this point, I'll apply
Borislav's patch, and fix all this casting after v3.9 is released, since
instead of just changing query_variable_info, we might as well change
everything in efi_runtime_service_t so that it's consistent.

  reply	other threads:[~2013-04-25  7:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-24 10:09 [PATCH] x86, efi: Fix a build warning Borislav Petkov
2013-04-24 10:29 ` Matt Fleming
2013-04-24 10:56 ` Ingo Molnar
2013-04-24 11:17   ` Matt Fleming
2013-04-24 13:20     ` Borislav Petkov
2013-04-25  6:55     ` Ingo Molnar
2013-04-25  7:19       ` Matt Fleming [this message]
2013-04-25  8:14         ` Ingo Molnar
2013-04-25 10:47         ` Borislav Petkov
2013-04-25 11:40           ` 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=5178D8E9.7020102@intel.com \
    --to=matt.fleming@intel.com \
    --cc=bp@alien8.de \
    --cc=bp@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew.garrett@nebula.com \
    --cc=mingo@kernel.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 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.