From: Greg KH <gregkh@linuxfoundation.org>
To: Nipun Gupta <nipun.gupta@amd.com>
Cc: maz@kernel.org, tglx@linutronix.de, jgg@ziepe.ca,
linux-kernel@vger.kernel.org, git@amd.com,
harpreet.anand@amd.com, pieter.jansen-van-vuuren@amd.com,
nikhil.agarwal@amd.com, michal.simek@amd.com,
abhijit.gangurde@amd.com, srivatsa@csail.mit.edu
Subject: Re: [PATCH v8 2/2] add wrapper msi allocation API and export msi functions
Date: Fri, 23 Feb 2024 12:21:04 +0100 [thread overview]
Message-ID: <2024022340-reversion-detonator-f229@gregkh> (raw)
In-Reply-To: <20240223092447.65564-2-nipun.gupta@amd.com>
On Fri, Feb 23, 2024 at 02:54:47PM +0530, Nipun Gupta wrote:
> MSI functions can be for allocation and free can be directly
> used by the device drivers without any wrapper provided by
> bus drivers. So export these MSI functions.
>
> Also, add a wrapper API to allocate MSIs providing only the
> number of IRQ's rather than range for simpler driver usage.
Why is this patch 2/2? Don't add wrappers that no one uses, otherwise
we will just delete them again :(
thanks,
greg k-h
next prev parent reply other threads:[~2024-02-23 11:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 9:24 [PATCH v8 1/2] cdx: add MSI support for CDX bus Nipun Gupta
2024-02-23 9:24 ` [PATCH v8 2/2] add wrapper msi allocation API and export msi functions Nipun Gupta
2024-02-23 9:53 ` Thomas Gleixner
2024-02-23 10:00 ` [tip: irq/msi] genirq/msi: Export MSI allocation/free functions and provide a conveniance wrapper tip-bot2 for Nipun Gupta
2024-02-23 11:21 ` Greg KH [this message]
[not found] ` <CH3PR12MB9193A635BC7952495469B2C5E8552@CH3PR12MB9193.namprd12.prod.outlook.com>
2024-02-23 12:39 ` [PATCH v8 2/2] add wrapper msi allocation API and export msi functions Greg KH
2024-02-23 9:50 ` [PATCH v8 1/2] cdx: add MSI support for CDX bus Thomas Gleixner
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=2024022340-reversion-detonator-f229@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=abhijit.gangurde@amd.com \
--cc=git@amd.com \
--cc=harpreet.anand@amd.com \
--cc=jgg@ziepe.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=michal.simek@amd.com \
--cc=nikhil.agarwal@amd.com \
--cc=nipun.gupta@amd.com \
--cc=pieter.jansen-van-vuuren@amd.com \
--cc=srivatsa@csail.mit.edu \
--cc=tglx@linutronix.de \
/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.