From: "Mukunda,Vijendar" <vijendar.mukunda@amd.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: broonie@kernel.org, alsa-devel@alsa-project.org,
Basavaraj.Hiregoudar@amd.com, Sunilkumar.Dommati@amd.com,
Mario.Limonciello@amd.com, Mastan.Katragadda@amd.com,
arungopal.kondaveeti@amd.com, Vinod Koul <vkoul@kernel.org>,
Bard Liao <yung-chuan.liao@linux.intel.com>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Sanyog Kale <sanyog.r.kale@intel.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] soundwire: export sdw_compute_slave_ports() function
Date: Wed, 8 Feb 2023 12:49:29 +0530 [thread overview]
Message-ID: <f1d1268d-6232-0428-4aef-a002eab6e16d@amd.com> (raw)
In-Reply-To: <Y+NCL1MdgwcuLTLk@infradead.org>
On 08/02/23 12:03, Christoph Hellwig wrote:
> On Wed, Feb 01, 2023 at 10:29:44PM +0530, Vijendar Mukunda wrote:
>> Export sdw_compute_slave_ports() function to use it in another
>> soundwire manager module.
>> Move sdw_transport_data structure to bus header file to export
>> sdw_compute_slave_ports() function.
> You might want to send this along with the actual user.
This is a dependent patch for our soundwire manager driver
patch series. Yesterday we have pushed this patch based on soundwire
git tree. If the patch is not picked, then we will resend this patch
as part of our patch series.
next prev parent reply other threads:[~2023-02-08 7:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 16:59 [PATCH] soundwire: export sdw_compute_slave_ports() function Vijendar Mukunda
2023-02-01 23:21 ` Pierre-Louis Bossart
2023-02-07 6:14 ` Mukunda,Vijendar
2023-02-08 6:33 ` Christoph Hellwig
2023-02-08 7:19 ` Mukunda,Vijendar [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-07 7:16 Vijendar Mukunda
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=f1d1268d-6232-0428-4aef-a002eab6e16d@amd.com \
--to=vijendar.mukunda@amd.com \
--cc=Basavaraj.Hiregoudar@amd.com \
--cc=Mario.Limonciello@amd.com \
--cc=Mastan.Katragadda@amd.com \
--cc=Sunilkumar.Dommati@amd.com \
--cc=alsa-devel@alsa-project.org \
--cc=arungopal.kondaveeti@amd.com \
--cc=broonie@kernel.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=sanyog.r.kale@intel.com \
--cc=vkoul@kernel.org \
--cc=yung-chuan.liao@linux.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