From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_CR_TRAILER, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E0D0DC433DB for ; Thu, 25 Mar 2021 10:48:22 +0000 (UTC) Received: from alsa0.perex.cz (alsa0.perex.cz [77.48.224.243]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 81C3361A2C for ; Thu, 25 Mar 2021 10:48:21 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 81C3361A2C Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=suse.de Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=alsa-devel-bounces@alsa-project.org Received: from alsa1.perex.cz (alsa1.perex.cz [207.180.221.201]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by alsa0.perex.cz (Postfix) with ESMTPS id 1CB521657; Thu, 25 Mar 2021 11:47:29 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz 1CB521657 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1616669299; bh=mf+zJNmvPrW0I5P+Pg0vTdbr1r7zvX4eo6DL3nL7xOY=; h=Date:From:To:Subject:In-Reply-To:References:Cc:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From; b=DVATwGcPM3W1MSOypS9tUprnHJ/qVlHF8EHRkX8v2N/j+rfES6sf36YYV8kigV7fs UbRvYu01Pdwzs0MOG23fPwU50geTSXVZgDx8asy8chAaijZRw0CXRf5zfYfPd7lwXC OGIQUcL2SjTMpGD9O+KyOXdwUmq2/+loF1O3yYMI= Received: from alsa1.perex.cz (localhost.localdomain [127.0.0.1]) by alsa1.perex.cz (Postfix) with ESMTP id 8B420F80257; Thu, 25 Mar 2021 11:47:28 +0100 (CET) Received: by alsa1.perex.cz (Postfix, from userid 50401) id 9B5F7F8025F; Thu, 25 Mar 2021 11:47:26 +0100 (CET) Received: from mx2.suse.de (mx2.suse.de [195.135.220.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by alsa1.perex.cz (Postfix) with ESMTPS id EAEB0F80104 for ; Thu, 25 Mar 2021 11:47:19 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz EAEB0F80104 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id F33B1AA55; Thu, 25 Mar 2021 10:47:18 +0000 (UTC) Date: Thu, 25 Mar 2021 11:47:18 +0100 Message-ID: From: Takashi Iwai To: Bhaskar Chowdhury Subject: Re: [PATCH V3] ALSA: pcm: Fix couple of typos In-Reply-To: <20210325095617.GB32566@debian> References: <20210325090609.10372-1-unixbhaskar@gmail.com> <20210325095617.GB32566@debian> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/25.3 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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 X-BeenThere: alsa-devel@alsa-project.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Alsa-devel mailing list for ALSA developers - http://www.alsa-project.org" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: "Alsa-devel" On Thu, 25 Mar 2021 10:56:39 +0100, Bhaskar Chowdhury wrote: > > 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 > >> --- > >> 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. I meant to try to apply the patch from mail fetched from the ML, not the patch you made from your git tree. Takashi