linux-kernel - RE: [EXT] Re: [PATCH v2] mtd: spi-nor: Fix wrong abbreviation HWCPAS

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 8 Feb 2019 18:43:26 +0000
From:   "Bean Huo (beanhuo)" <beanhuo@...ron.com>
To:     Boris Brezillon <bbrezillon@...nel.org>
CC:     "Tudor.Ambarus@...rochip.com" <Tudor.Ambarus@...rochip.com>,
        "linux-mtd@...ts.infradead.org" <linux-mtd@...ts.infradead.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "marek.vasut@...il.com" <marek.vasut@...il.com>,
        "computersforpeace@...il.com" <computersforpeace@...il.com>,
        "dwmw2@...radead.org" <dwmw2@...radead.org>,
        "richard@....at" <richard@....at>
Subject: RE: [EXT] Re: [PATCH v2] mtd: spi-nor: Fix wrong abbreviation HWCPAS

Hi,Boris 
I sent three times, seems last time is successful. would you check that is correct?

git send-email 0001-mtd-spi-nor-Fix-wrong-abbreviation-HWCPAS.patch
0001-mtd-spi-nor-Fix-wrong-abbreviation-HWCPAS.patch
To whom should the emails be sent (if anyone)? linux-mtd@...ts.infradead.org,Tudor.Ambarus@...rochip.com,bbrezillon@...nel.org,linux-kernel@...r.kernel.org
Message-ID to be used as In-Reply-To for the first email (if any)? 
(mbox) Adding cc: Bean Huo <beanhuo@...ron.com> from line 'From: Bean Huo <beanhuo@...ron.com>'
(body) Adding cc: Bean Huo <beanhuo@...ron.com> from line 'Signed-off-by: Bean Huo <beanhuo@...ron.com>'

From: Bean Huo <beanhuo@...ron.com>
To: linux-mtd@...ts.infradead.org,
        Tudor.Ambarus@...rochip.com,
        bbrezillon@...nel.org,
        linux-kernel@...r.kernel.org
Cc: Bean Huo <beanhuo@...ron.com>
Subject: [PATCH] mtd: spi-nor: Fix wrong abbreviation HWCPAS
Date: Fri,  8 Feb 2019 18:00:12 +0000
Message-Id: <20190208180012.25852-1-beanhuo@...ron.com>
X-Mailer: git-send-email 2.17.1

    The Cc list above has been expanded by additional
    addresses found in the patch commit message. By default
    send-email prompts before sending whenever this occurs.
    This behavior is controlled by the sendemail.confirm
    configuration setting.

    For additional information, run 'git send-email --help'.
    To retain the current behavior, but squelch this message,
    run 'git config --global sendemail.confirm auto'.

Send this email? ([y]es|[n]o|[q]uit|[a]ll): y
OK. Log says:
Sendmail: /usr/sbin/sendmail -i linux-mtd@...ts.infradead.org Tudor.Ambarus@...rochip.com bbrezillon@...nel.org linux-kernel@...r.kernel.org beanhuo@...ron.com
From: Bean Huo <beanhuo@...ron.com>
To: linux-mtd@...ts.infradead.org,
        Tudor.Ambarus@...rochip.com,
        bbrezillon@...nel.org,
        linux-kernel@...r.kernel.org
Cc: Bean Huo <beanhuo@...ron.com>
Subject: [RESEND PATCH v2] mtd: spi-nor: Fix wrong abbreviation HWCPAS
Date: Fri,  8 Feb 2019 18:00:12 +0000
Message-Id: <20190208180012.25852-1-beanhuo@...ron.com>
X-Mailer: git-send-email 2.17.1

Result: OK

>
>Hi Bean,
>
>On Fri, 8 Feb 2019 17:13:52 +0000
>"Bean Huo (beanhuo)" <beanhuo@...ron.com> wrote:
>
>> Hi, Tutor
>> Thanks. unfortunately, it doesn't work on my side. Problem is on our email
>server side, not my local setting.
>> I followed your configuration, then git-email failed.
>
>Can you paste the output of git send-email and the [sendemail] section of
>your .gitconfig so we can check.
>It shouldn't fail, really, because the server shouldn't check the body section of
>your email, and this is where the extra
>
>	From: First Last <foo@....com>
>
>line is placed.
>
>> Please just change my S-o-b to 'Bean Huo (beanhuo) <beanhuo@...ron.com>'
>in my patch to please checkpacth.pl.  It is not huge change.
>
>It's not a problem when an drive-by contributor posts a patch, but if you don't
>patch it that means we'll have to do it manually every time we apply one of your
>patch, so please find a solution.
>
>Thanks,
>
>Boris