From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: Ira Weiny <ira.weiny@intel.com>
Cc: Davidlohr Bueso <dave@stgolabs.net>, <dan.j.williams@intel.com>,
<dave.jiang@intel.com>, <alison.schofield@intel.com>,
<vishal.l.verma@intel.com>, <bwidawsk@kernel.org>,
<a.manzanares@samsung.com>, <linux-kernel@vger.kernel.org>,
<linux-cxl@vger.kernel.org>
Subject: Re: [PATCH 2/2] cxl/mbox: Wire up basic irq support
Date: Mon, 17 Oct 2022 11:08:56 +0100 [thread overview]
Message-ID: <20221017110856.00001dee@huawei.com> (raw)
In-Reply-To: <Y0yAX1fTCHhKKzeb@iweiny-desk3>
On Sun, 16 Oct 2022 15:06:23 -0700
Ira Weiny <ira.weiny@intel.com> wrote:
> On Fri, Oct 14, 2022 at 12:49:30PM -0700, Davidlohr Bueso wrote:
> > This adds support for mailbox interrupts, which are needed, for
> > example, for background completion handling.
> >
> > Signed-off-by: Davidlohr Bueso <dave@stgolabs.net>
> > ---
...
> > + IRQF_SHARED, "mailbox", cxlds))
> > + dev_dbg(dev, "Mailbox irq (%d) supported", irq);
> > + }
> > +
> > return 0;
> > }
> >
> > @@ -441,7 +464,9 @@ struct cxl_irq_cap {
> > int (*get_max_msgnum)(struct cxl_dev_state *cxlds);
> > };
> >
> > -static const struct cxl_irq_cap cxl_irq_cap_table[] = { NULL };
> > +static const struct cxl_irq_cap cxl_irq_cap_table[] = {
Trivial patch mangling point but better to have the NULL on separate line
in previous patch to reduce the diff here.
> > + { "mailbox", cxl_pci_mbox_get_max_msgnum }
trailing comma needed as we definitely expect to add more entries!
> > +};
> >
> > static void cxl_pci_free_irq_vectors(void *data)
> > {
> > --
> > 2.37.3
> >
prev parent reply other threads:[~2022-10-17 10:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 19:49 [PATCH v2 0/2] cxl: Add basic MSI/MSI-X support Davidlohr Bueso
2022-10-14 19:49 ` [PATCH 1/2] cxl/pci: Add generic MSI/MSI-X interrupt support Davidlohr Bueso
2022-10-16 22:10 ` Ira Weiny
2022-10-17 0:37 ` Davidlohr Bueso
2022-10-17 10:06 ` Jonathan Cameron
2022-10-14 19:49 ` [PATCH 2/2] cxl/mbox: Wire up basic irq support Davidlohr Bueso
2022-10-16 22:06 ` Ira Weiny
2022-10-17 10:08 ` Jonathan Cameron [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=20221017110856.00001dee@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=a.manzanares@samsung.com \
--cc=alison.schofield@intel.com \
--cc=bwidawsk@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vishal.l.verma@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