Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Agrawal, Akshu" <Akshu.Agrawal@amd.com>
To: Mark Brown <broonie@kernel.org>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org, lgirdwood@gmail.com
Subject: Re: [PATCH 0/1] Use of shared resource in designware
Date: Mon, 19 Feb 2018 09:26:16 +0530	[thread overview]
Message-ID: <bb4dfe21-18f2-f17f-7371-e6a19ddb58bd@amd.com> (raw)
In-Reply-To: <20180216114754.GD5886@sirena.org.uk>



On 2/16/2018 5:17 PM, Mark Brown wrote:
> On Fri, Feb 16, 2018 at 01:13:28PM +0530, Akshu Agrawal wrote:
>> This patch will allow the driver to map same registers
>> to multiple instances of driver.
>>
>> It is useful when playback and capture have same regsiters
>> and are required to be present on separate cpu dais.
> 
> Please don't send cover letters for single patches, if there is anything
> that needs saying put it in the changelog of the patch or after the ---
> if it's administrative stuff.  This reduces mail volume and ensures that
> any important information is recorded in the changelog rather than being
> lost.
> 
Got it. The reason for making a cover letter was to let you all know 
that its dependent on "Add devm_ioremap_shared_resource()"
patch. https://patchwork.kernel.org/patch/10177127/

      reply	other threads:[~2018-02-19  3:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-16  7:43 [PATCH 0/1] Use of shared resource in designware Akshu Agrawal
2018-02-16  7:43 ` [PATCH 1/1] ASoC: dwc: Use devm_ioremap_shared_resource Akshu Agrawal
2018-02-16 11:47 ` [PATCH 0/1] Use of shared resource in designware Mark Brown
2018-02-19  3:56   ` Agrawal, Akshu [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=bb4dfe21-18f2-f17f-7371-e6a19ddb58bd@amd.com \
    --to=akshu.agrawal@amd.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=tiwai@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox