All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Vijendar Mukunda <Vijendar.Mukunda@amd.com>
Cc: alsa-devel@alsa-project.org, tiwai@suse.de, lgirdwood@gmail.com,
	perex@perex.cz, Alexander.Deucher@amd.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: amd: added error checks in dma driver
Date: Mon, 4 Dec 2017 17:54:19 +0000	[thread overview]
Message-ID: <20171204175419.kejdshqwqgg6lswv@sirena.org.uk> (raw)
In-Reply-To: <1512400584-28170-1-git-send-email-Vijendar.Mukunda@amd.com>

[-- Attachment #1: Type: text/plain, Size: 333 bytes --]

On Mon, Dec 04, 2017 at 08:46:24PM +0530, Vijendar Mukunda wrote:
> added additional error checks in acp dma driver
> v2: printed error codes for acp init & acp deinit
> failure cases.

Don't include noise like inter-version changelogs in commit messages,
add them after the --- if they're important as covered in
SubmittingPatches.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Vijendar Mukunda <Vijendar.Mukunda@amd.com>
Cc: alsa-devel@alsa-project.org, tiwai@suse.de, lgirdwood@gmail.com,
	linux-kernel@vger.kernel.org, Alexander.Deucher@amd.com
Subject: Re: [PATCH] ASoC: amd: added error checks in dma driver
Date: Mon, 4 Dec 2017 17:54:19 +0000	[thread overview]
Message-ID: <20171204175419.kejdshqwqgg6lswv@sirena.org.uk> (raw)
In-Reply-To: <1512400584-28170-1-git-send-email-Vijendar.Mukunda@amd.com>


[-- Attachment #1.1: Type: text/plain, Size: 333 bytes --]

On Mon, Dec 04, 2017 at 08:46:24PM +0530, Vijendar Mukunda wrote:
> added additional error checks in acp dma driver
> v2: printed error codes for acp init & acp deinit
> failure cases.

Don't include noise like inter-version changelogs in commit messages,
add them after the --- if they're important as covered in
SubmittingPatches.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2017-12-04 17:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-04 15:16 [PATCH] ASoC: amd: added error checks in dma driver Vijendar Mukunda
2017-12-04 15:16 ` Vijendar Mukunda
2017-12-04 17:54 ` Mark Brown [this message]
2017-12-04 17:54   ` Mark Brown
2017-12-04 18:49 ` Applied "ASoC: amd: added error checks in dma driver" to the asoc tree Mark Brown
2017-12-04 18:49   ` Mark Brown
  -- strict thread matches above, loose matches on Subject: below --
2017-11-28  4:43 [PATCH] ASoC: amd: added error checks in dma driver Vijendar Mukunda
2017-11-28  4:43 ` Vijendar Mukunda
2017-11-28 11:52 ` Mark Brown
2017-11-28 11:52   ` Mark Brown
2017-11-30  5:29   ` Mukunda,Vijendar
2017-11-23 16:30 Vijendar Mukunda
2017-11-23 16:30 ` Vijendar Mukunda
2017-11-23 16:59 ` Guenter Roeck
2017-11-23 17:29   ` Mark Brown
2017-11-24 11:07     ` Mukunda,Vijendar
2017-11-24  8:11       ` Guenter Roeck
2017-11-24 14:19         ` Mukunda,Vijendar

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=20171204175419.kejdshqwqgg6lswv@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=Alexander.Deucher@amd.com \
    --cc=Vijendar.Mukunda@amd.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --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 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.