All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bhaskar Chowdhury <unixbhaskar@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, lgirdwood@gmail.com,
	rdunlap@infradead.org, linux-kernel@vger.kernel.org,
	tiwai@suse.com, peter.ujfalusi@gmail.com
Subject: Re: [PATCH] sound: soc: ti: Fix a typo in the file ams-delta.c
Date: Thu, 18 Mar 2021 01:07:35 +0530	[thread overview]
Message-ID: <YFJaf+Q1P1nnvJm/@ArchLinux> (raw)
In-Reply-To: <20210317123411.GA5559@sirena.org.uk>

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

On 12:34 Wed 17 Mar 2021, Mark Brown wrote:
>On Wed, Mar 17, 2021 at 01:50:42PM +0530, Bhaskar Chowdhury wrote:
>>
>> s/functonality/functionality/
>
>Please submit patches using subject lines reflecting the style for the
>subsystem, this makes it easier for people to identify relevant patches.
>Look at what existing commits in the area you're changing are doing and
>make sure your subject lines visually resemble what they're doing.
>There's no need to resubmit to fix this alone.

Thanks, will remind myself next time I will try to do the same. But, I was
trying to be "As explicit as possible" , so the person in charge can struggle less and hover less to understand what it is for. Anyway, will follow.

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

WARNING: multiple messages have this Message-ID (diff)
From: Bhaskar Chowdhury <unixbhaskar@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: peter.ujfalusi@gmail.com, lgirdwood@gmail.com, perex@perex.cz,
	tiwai@suse.com, alsa-devel@alsa-project.org,
	linux-kernel@vger.kernel.org, rdunlap@infradead.org
Subject: Re: [PATCH] sound: soc: ti: Fix a typo in the file ams-delta.c
Date: Thu, 18 Mar 2021 01:07:35 +0530	[thread overview]
Message-ID: <YFJaf+Q1P1nnvJm/@ArchLinux> (raw)
In-Reply-To: <20210317123411.GA5559@sirena.org.uk>

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

On 12:34 Wed 17 Mar 2021, Mark Brown wrote:
>On Wed, Mar 17, 2021 at 01:50:42PM +0530, Bhaskar Chowdhury wrote:
>>
>> s/functonality/functionality/
>
>Please submit patches using subject lines reflecting the style for the
>subsystem, this makes it easier for people to identify relevant patches.
>Look at what existing commits in the area you're changing are doing and
>make sure your subject lines visually resemble what they're doing.
>There's no need to resubmit to fix this alone.

Thanks, will remind myself next time I will try to do the same. But, I was
trying to be "As explicit as possible" , so the person in charge can struggle less and hover less to understand what it is for. Anyway, will follow.

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

  reply	other threads:[~2021-03-17 19:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-17  8:20 [PATCH] sound: soc: ti: Fix a typo in the file ams-delta.c Bhaskar Chowdhury
2021-03-17 12:34 ` Mark Brown
2021-03-17 12:34   ` Mark Brown
2021-03-17 19:37   ` Bhaskar Chowdhury [this message]
2021-03-17 19:37     ` Bhaskar Chowdhury
2021-03-17 13:41 ` Mark Brown

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=YFJaf+Q1P1nnvJm/@ArchLinux \
    --to=unixbhaskar@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter.ujfalusi@gmail.com \
    --cc=rdunlap@infradead.org \
    --cc=tiwai@suse.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 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.