From: Bhaskar Chowdhury <unixbhaskar@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, lars@metafoo.de,
linux-kernel@vger.kernel.org, tiwai@suse.com,
gustavoars@kernel.org, huawei@kernel.org,
mirq-linux@rere.qmqm.pl, broonie@kernel.org,
rdunlap@infradead.org
Subject: Re: [PATCH V3] ALSA: pcm: Fix couple of typos
Date: Thu, 25 Mar 2021 15:26:39 +0530 [thread overview]
Message-ID: <20210325095617.GB32566@debian> (raw)
In-Reply-To: <s5ho8f7mv5k.wl-tiwai@suse.de>
[-- Attachment #1: Type: text/plain, Size: 1555 bytes --]
On 10:37 Thu 25 Mar 2021, Takashi Iwai wrote:
>On Thu, 25 Mar 2021 10:06:09 +0100,
>Bhaskar Chowdhury wrote:
>>
>> s/unconditonally/unconditionally/
>> s/succesful/successful/
>>
>> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
>> ---
>> Changes from V2:
>> Takashi pointed out that the patch was not applicable due to some unwanted
>> stuff get into it. Resending it with the new patch creation.
>
>Hrm, still not applicable. Can you apply the patch from your own post
>via git-am in your side?
>
Here is what I do for this specific case :
✔ ~/git-linux/linux-next [patch L|✔]
15:18 $ sed -i 's/unconditonally/unconditionally/' sound/core/pcm_native.c
✔ ~/git-linux/linux-next [patch L|✚ 1]
15:19 $ sed -i 's/succesful/successful/' sound/core/pcm_native.c
✔ ~/git-linux/linux-next [patch L|✚ 1]
15:19 $ git add .
✔ ~/git-linux/linux-next [patch L|●1]
15:19 $ git ci "Fix some patch error"
[patch 88d5af187dbb] Fix some patch error
1 file changed, 2 insertions(+), 2 deletions(-)
15:21 $ git_fetch_single_file.sh sound/core/pcm_native.c
Looks alright!✔ ~/git-linux/linux-next [patch L|●1]
15:21 $ git add .
✔ ~/git-linux/linux-next [patch L|●1]
15:21 $ git ci "Bring for patch"
[patch 352e1ce8dacf] Bring for patch
1 file changed, 2 insertions(+), 2 deletions(-)
✔ ~/git-linux/linux-next [patch L|✔]
15:22 $ git apply --verbose 0001-Made-patche-for-this.patch
Checking patch sound/core/pcm_native.c...
Applied patch sound/core/pcm_native.c cleanly.
>
>Takashi
[-- 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: Takashi Iwai <tiwai@suse.de>
Cc: perex@perex.cz, tiwai@suse.com, broonie@kernel.org,
mirq-linux@rere.qmqm.pl, lars@metafoo.de, gustavoars@kernel.org,
huawei@kernel.org, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org, rdunlap@infradead.org
Subject: Re: [PATCH V3] ALSA: pcm: Fix couple of typos
Date: Thu, 25 Mar 2021 15:26:39 +0530 [thread overview]
Message-ID: <20210325095617.GB32566@debian> (raw)
In-Reply-To: <s5ho8f7mv5k.wl-tiwai@suse.de>
[-- Attachment #1: Type: text/plain, Size: 1555 bytes --]
On 10:37 Thu 25 Mar 2021, Takashi Iwai wrote:
>On Thu, 25 Mar 2021 10:06:09 +0100,
>Bhaskar Chowdhury wrote:
>>
>> s/unconditonally/unconditionally/
>> s/succesful/successful/
>>
>> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
>> ---
>> Changes from V2:
>> Takashi pointed out that the patch was not applicable due to some unwanted
>> stuff get into it. Resending it with the new patch creation.
>
>Hrm, still not applicable. Can you apply the patch from your own post
>via git-am in your side?
>
Here is what I do for this specific case :
✔ ~/git-linux/linux-next [patch L|✔]
15:18 $ sed -i 's/unconditonally/unconditionally/' sound/core/pcm_native.c
✔ ~/git-linux/linux-next [patch L|✚ 1]
15:19 $ sed -i 's/succesful/successful/' sound/core/pcm_native.c
✔ ~/git-linux/linux-next [patch L|✚ 1]
15:19 $ git add .
✔ ~/git-linux/linux-next [patch L|●1]
15:19 $ git ci "Fix some patch error"
[patch 88d5af187dbb] Fix some patch error
1 file changed, 2 insertions(+), 2 deletions(-)
15:21 $ git_fetch_single_file.sh sound/core/pcm_native.c
Looks alright!✔ ~/git-linux/linux-next [patch L|●1]
15:21 $ git add .
✔ ~/git-linux/linux-next [patch L|●1]
15:21 $ git ci "Bring for patch"
[patch 352e1ce8dacf] Bring for patch
1 file changed, 2 insertions(+), 2 deletions(-)
✔ ~/git-linux/linux-next [patch L|✔]
15:22 $ git apply --verbose 0001-Made-patche-for-this.patch
Checking patch sound/core/pcm_native.c...
Applied patch sound/core/pcm_native.c cleanly.
>
>Takashi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-03-25 9:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 9:06 [PATCH V3] ALSA: pcm: Fix couple of typos Bhaskar Chowdhury
2021-03-25 9:37 ` Takashi Iwai
2021-03-25 9:37 ` Takashi Iwai
2021-03-25 9:56 ` Bhaskar Chowdhury [this message]
2021-03-25 9:56 ` Bhaskar Chowdhury
2021-03-25 10:47 ` Takashi Iwai
2021-03-25 10:47 ` Takashi Iwai
2021-03-25 12:07 ` Bhaskar Chowdhury
2021-03-25 12:07 ` Bhaskar Chowdhury
2021-03-25 16:35 ` Randy Dunlap
2021-03-26 6:53 ` Bhaskar Chowdhury
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=20210325095617.GB32566@debian \
--to=unixbhaskar@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=gustavoars@kernel.org \
--cc=huawei@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mirq-linux@rere.qmqm.pl \
--cc=rdunlap@infradead.org \
--cc=tiwai@suse.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 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.