public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: <jgross@suse.com>, <xen-devel@lists.xenproject.org>,
	<konrad.wilk@oracle.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Make bind_interdomain_evtchn_to_irq() public
Date: Wed, 13 Aug 2014 10:53:19 +0100	[thread overview]
Message-ID: <53EB358F.9040001@citrix.com> (raw)
In-Reply-To: <1407851024-18936-1-git-send-email-jgross@suse.com>

On 12/08/14 14:43, jgross@suse.com wrote:
> From: Juergen Gross <jgross@suse.com>
> 
> bind_interdomain_evtchn_to_irq() is currently a private function. It is used
> only by bind_interdomain_evtchn_to_irqhandler() to register an irq-handler for
> an event channel.
> 
> By making it public it is possible to use e.g. threaded interrupts with
> interdomain event channels.

Acked-by: David Vrabel <david.vrabel@citrix.com>

But can you change the subject/commit message to:

    xen/events: support threaded irqs for interdomain event channels

    Export bind_interdomain_evtchn_to_irq() so drivers can use threaded
    interrupt handlers with:

     irq = bind_interdomain_evtchn_to_irq(remote_dom, remote_port);
     if (irq < 0)
         /* error */
     ret = request_threaded_irq(...);

Since your pvscsi series depends on this you will want to add this to
that series to be merged via the scsi tree.

David


  parent reply	other threads:[~2014-08-13  9:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-12 13:43 [PATCH] Make bind_interdomain_evtchn_to_irq() public jgross
2014-08-13  9:29 ` [Xen-devel] " David Vrabel
2014-08-13  9:43   ` Juergen Gross
2014-08-13  9:54     ` David Vrabel
2014-08-13 10:04       ` Juergen Gross
2014-08-13  9:53 ` David Vrabel [this message]
2014-08-13 10:04   ` Juergen Gross

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=53EB358F.9040001@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=jgross@suse.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.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