From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Khalid Masum <khalid.masum.92@gmail.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Cc: Vinod Koul <vkoul@kernel.org>,
Bard Liao <yung-chuan.liao@linux.intel.com>,
Sanyog Kale <sanyog.r.kale@intel.com>
Subject: Re: [PATCH v2 linux-next] Remove Unnecessary TODO
Date: Wed, 17 Aug 2022 08:31:20 +0200 [thread overview]
Message-ID: <a92f5041-9630-66ee-1757-4b58bdaabe90@linux.intel.com> (raw)
In-Reply-To: <20220816175954.5259-1-khalid.masum.92@gmail.com>
On 8/16/22 19:59, Khalid Masum wrote:
> The capabilities enabled for multi-link are required as part of the
> programming sequences, even when a stream uses a single link we still
> use the syncArm/syncGo sequences. Therefore the TODO is no longer
> necessary.
>
> Suggested-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
> Signed-off-by: Khalid Masum <khalid.masum.92@gmail.com>
the title of your patch should be something like
soundwire: intel: remove unnecessary TODO
so that the patch scope and context is clearly identified.
> ---
> Previous discussions:
> - v1 Link: https://lore.kernel.org/lkml/20220814080416.7531-1-khalid.masum.92@gmail.com/
>
> Changes since v1:
> - Remove the todo, leave rest of the code as is
> - Update commit message
>
> drivers/soundwire/bus.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/soundwire/bus.c b/drivers/soundwire/bus.c
> index 8d4000664fa3..18158825a6d8 100644
> --- a/drivers/soundwire/bus.c
> +++ b/drivers/soundwire/bus.c
> @@ -75,7 +75,6 @@ int sdw_bus_master_add(struct sdw_bus *bus, struct device *parent,
>
> /*
> * Initialize multi_link flag
> - * TODO: populate this flag by reading property from FW node
> */
> bus->multi_link = false;
> if (bus->ops->read_prop) {
next prev parent reply other threads:[~2022-08-17 6:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 17:59 [PATCH v2 linux-next] Remove Unnecessary TODO Khalid Masum
2022-08-17 6:31 ` Pierre-Louis Bossart [this message]
2022-08-17 7:25 ` Khalid Masum
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=a92f5041-9630-66ee-1757-4b58bdaabe90@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=khalid.masum.92@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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