All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: "Liao, Bard" <bard.liao@intel.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
	"Kale, Sanyog R" <sanyog.r.kale@intel.com>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Subject: Re: [PATCH v2 0/2] soundwire: use {u32|u16}p_replace_bits
Date: Fri, 18 Sep 2020 17:50:12 +0530	[thread overview]
Message-ID: <20200918122012.GT2968@vkoul-mobl> (raw)
In-Reply-To: <DM6PR11MB40749F64E911CF7E430C740EFF3F0@DM6PR11MB4074.namprd11.prod.outlook.com>

On 18-09-20, 12:10, Liao, Bard wrote:
> 
> On 9/17/2020 8:01 PM, Vinod Koul wrote:
> > This is v2 of the series to fix usage of FIELD_PREP and use
> > {u32|u16}p_replace_bits.
> >
> > v1 used u32_replace_bits but looks like it might be removed so use the
> > {u32|u16}p_replace_bits() instead. Also this helped to find that one
> > instance in intel driver should have used u16p_replace_bits() so that is
> > fixed too
> >
> > Vinod Koul (2):
> > soundwire: cadence: use u32p_replace_bits
> > soundwire: intel: use {u32|u16}p_replace_bits
> >
> > drivers/soundwire/cadence_master.c | 21 ++++++++++-----------
> > drivers/soundwire/intel.c | 14 +++++++-------
> > 2 files changed, 17 insertions(+), 18 deletions(-)
> 
> Tested it on a Intel platform. So
> 
> Tested-by: Bard Liao <yung-chuan.liao@linux.intel.com>

Thanks Bard, applied now

-- 
~Vinod

  reply	other threads:[~2020-09-18 12:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-18 12:10 [PATCH v2 0/2] soundwire: use {u32|u16}p_replace_bits Liao, Bard
2020-09-18 12:20 ` Vinod Koul [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-09-17 12:01 Vinod Koul

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=20200918122012.GT2968@vkoul-mobl \
    --to=vkoul@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=bard.liao@intel.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=sanyog.r.kale@intel.com \
    --cc=srinivas.kandagatla@linaro.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 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.