linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Juergen Gross <jgross@suse.com>,
	linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org,
	x86@kernel.org
Cc: hpa@zytor.com, tglx@linutronix.de, mingo@redhat.com
Subject: Re: [PATCH] xen: remove unused hypercall functions
Date: Mon, 20 Aug 2018 19:10:18 -0400	[thread overview]
Message-ID: <80a934d8-d07d-0dc5-b7f9-2aa91bdd6dc3@oracle.com> (raw)
In-Reply-To: <20180820130330.11704-1-jgross@suse.com>

On 08/20/2018 09:03 AM, Juergen Gross wrote:
> Remove Xen hypercall functions which are used nowhere in the kernel.
>
> Signed-off-by: Juergen Gross <jgross@suse.com>
> ---

Applied to for-linus-19b.

-boris


      reply	other threads:[~2018-08-20 23:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-20 13:03 [PATCH] xen: remove unused hypercall functions Juergen Gross
2018-08-20 23:10 ` Boris Ostrovsky [this message]

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=80a934d8-d07d-0dc5-b7f9-2aa91bdd6dc3@oracle.com \
    --to=boris.ostrovsky@oracle.com \
    --cc=hpa@zytor.com \
    --cc=jgross@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).