25.03.2021 10:42, Vladimir Sementsov-Ogievskiy wrote:
25.03.2021 00:13, no-re...@patchew.org wrote:
Patchew URL: 
https://patchew.org/QEMU/20210324205132.464899-1-vsement...@virtuozzo.com/



Hi,

This series seems to have some coding style problems. See output below for
more information:

Type: series
Message-id: 20210324205132.464899-1-vsement...@virtuozzo.com
Subject: [PATCH v4 00/11] 64bit block-layer: part II

=== TEST SCRIPT BEGIN ===
#!/bin/bash
git rev-parse base > /dev/null || exit 0
git config --local diff.renamelimit 0
git config --local diff.renames True
git config --local diff.algorithm histogram
./scripts/checkpatch.pl --mailback base..
=== TEST SCRIPT END ===

Updating 3c8cf5a9c21ff8782164d1def7f44bd888713384
 From https://github.com/patchew-project/qemu
  - [tag update]      patchew/20210323221539.3532660-1-cr...@redhat.com -> 
patchew/20210323221539.3532660-1-cr...@redhat.com
  * [new tag]         patchew/20210324205132.464899-1-vsement...@virtuozzo.com 
-> patchew/20210324205132.464899-1-vsement...@virtuozzo.com
Switched to a new branch 'test'
bed608a block/io: allow 64bit discard requests
9b3b5c7 block: use int64_t instead of int in driver discard handlers
9d5776f block: make BlockLimits::max_pdiscard 64bit
1dc4bab block/io: allow 64bit write-zeroes requests
05ca540 block: use int64_t instead of int in driver write_zeroes handlers
5864b0d block: make BlockLimits::max_pwrite_zeroes 64bit
9698c13 block: use int64_t instead of uint64_t in copy_range driver handlers
4e60566 block: use int64_t instead of uint64_t in driver write handlers
8aa3af1 block: use int64_t instead of uint64_t in driver read handlers
fc695f9 qcow2: check request on vmstate save/load path
a13a9ef block/io: bring request check to bdrv_co_{read, write}v_vmstate

=== OUTPUT BEGIN ===
1/11 Checking commit a13a9efd128c (block/io: bring request check to 
bdrv_co_{read, write}v_vmstate)
ERROR: Author email address is mangled by the mailing list
#2:
Author: Vladimir Sementsov-Ogievskiy via <qemu-devel@nongnu.org>

That's a strange false-positive.

Look at 1/11: it's not mangled in any way. Looking at the source I see clean 
"From:" header:

   From: Vladimir Sementsov-Ogievskiy <vsement...@virtuozzo.com>

And there is no any "Author" in the message source at all. "qemu-devel" is 
noted only in Cc: list.


Hmm, but if look at mail on patchew, 
https://patchew.org/QEMU/20210324205132.464899-1-vsement...@virtuozzo.com/20210324205132.464899-2-vsement...@virtuozzo.com/
yes it is mangled..

I hope everyone who is in CC (as me) gets this email not-mangled.

--
Best regards,
Vladimir

Reply via email to