All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Kiper <daniel.kiper@oracle.com>
To: david.vrabel@citrix.com
Cc: jeremy@goop.org, matt.fleming@intel.com, ian.campbell@citrix.com,
	stefano.stabellini@eu.citrix.com, andrew.cooper3@citrix.com,
	x86@kernel.org, linux-kernel@vger.kernel.org, mingo@redhat.com,
	jbeulich@suse.com, hpa@zytor.com, xen-devel@lists.xenproject.org,
	boris.ostrovsky@oracle.com, tglx@linutronix.de
Subject: Re: [PATCH v2 1/2] xen: Silence compiler warnings
Date: Mon, 28 Jul 2014 14:38:23 -0700 (PDT)	[thread overview]
Message-ID: <963f7cc9-3f46-44f6-8fe1-e25fae83c722__27464.3180695877$1406583646$gmane$org@default> (raw)

David,

> On 12/07/14 22:09, Daniel Kiper wrote:
> > Add inline keyword to silence the following compiler
> > warnings if xen_efi_probe() is not used:
>
> The title and should be:
>
>     xen: make stub xen_efi_probe() static inline
>
>     Empty stub functions in headers should be inline or the compiler
>     will warn that it is unused.
>
> Do you want this to go via the Xen tree or the EFI one?

Thanks for your comment but as I can see it was
taken by Matt and now it is a part of tip.

Daniel

             reply	other threads:[~2014-07-28 21:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-28 21:38 Daniel Kiper [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-07-28 21:38 [PATCH v2 1/2] xen: Silence compiler warnings Daniel Kiper
2014-07-12 21:09 [PATCH v2 0/2] " Daniel Kiper
2014-07-12 21:09 ` [PATCH v2 1/2] " Daniel Kiper
2014-07-13  9:59   ` Konrad Rzeszutek Wilk
2014-07-13  9:59   ` Konrad Rzeszutek Wilk
2014-07-28 13:11   ` David Vrabel
2014-07-28 13:11     ` David Vrabel
2014-07-12 21:09 ` Daniel Kiper

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='963f7cc9-3f46-44f6-8fe1-e25fae83c722__27464.3180695877$1406583646$gmane$org@default' \
    --to=daniel.kiper@oracle.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=hpa@zytor.com \
    --cc=ian.campbell@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt.fleming@intel.com \
    --cc=mingo@redhat.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    --cc=xen-devel@lists.xenproject.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.