From: "Chen, Rong A" <rong.a.chen@intel.com>
To: "Joe Perches" <joe@perches.com>,
"kernel test robot" <lkp@intel.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
linux-serial <linux-serial@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>
Cc: kbuild-all@lists.01.org, Jiri Slaby <jirislaby@kernel.org>
Subject: Re: [kbuild-all] Re: [PATCH] MAINTAINERS: Update DW 8250 UART maintainership
Date: Mon, 20 Jun 2022 11:17:43 +0800 [thread overview]
Message-ID: <7c01c4f8-1826-8769-c3d3-309a9d23f113@intel.com> (raw)
In-Reply-To: <7690845ccf9597e8cdc560a674a1b8e79a10f680.camel@perches.com>
On 6/18/2022 4:17 AM, Joe Perches wrote:
> On Sat, 2022-06-18 at 04:09 +0800, kernel test robot wrote:
>> Hi "Ilpo,
>>
>> Thank you for the patch! Yet something to improve:
>>
>> [auto build test ERROR on linus/master]
>> [also build test ERROR on v5.19-rc2 next-20220617]
>> [If your patch is applied to the wrong git tree, kindly drop us a note.
>> And when submitting patch, we suggest to use '--base' as documented in
>> https://git-scm.com/docs/git-format-patch]
>>
>> url: https://github.com/intel-lab-lkp/linux/commits/Ilpo-J-rvinen/MAINTAINERS-Update-DW-8250-UART-maintainership/20220617-174145
>> base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 47700948a4abb4a5ae13ef943ff682a7f327547a
>> reproduce: make htmldocs
>>
>> If you fix the issue, kindly add following tag where applicable
>> Reported-by: kernel test robot <lkp@intel.com>
>>
>> All errors (new ones prefixed by >>):
>>
>>>> 'utf-8' codec can't decode byte 0xe4 in position 1396: invalid continuation byte
>
> ?
>
> false positive?
Hi,
I tried to apply the patch, and I can reproduce the error by 'make
htmldocs':
$ wget -q -O -
https://lore.kernel.org/lkml/be58b398-71ff-7c12-1bf1-a09181d9c80@linux.intel.com/raw
| git apply -v
$ git --no-pager diff
diff --git a/MAINTAINERS b/MAINTAINERS
index f52543aedd61e..3d64756814f09 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -19247,8 +19247,9 @@ F:
Documentation/devicetree/bindings/gpio/snps,creg-gpio.txt
F: drivers/gpio/gpio-creg-snps.c
SYNOPSYS DESIGNWARE 8250 UART DRIVER
+M: Ilpo Jrvinen <ilpo.jarvinen@linux.intel.com>
R: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
-S: Maintained
+S: Supported
F: drivers/tty/serial/8250/8250_dw.c
F: drivers/tty/serial/8250/8250_dwlib.*
F: drivers/tty/serial/8250/8250_lpss.c
It seems the special character 'ä' in name 'Ilpo Järvinen' was parsed
wrongly.
Best Regards,
Rong Chen
next prev parent reply other threads:[~2022-06-20 3:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 9:39 [PATCH] MAINTAINERS: Update DW 8250 UART maintainership Ilpo Järvinen
2022-06-17 9:45 ` Greg Kroah-Hartman
2022-06-17 10:21 ` Andy Shevchenko
2022-06-17 9:47 ` Andy Shevchenko
2022-06-17 20:09 ` kernel test robot
2022-06-17 20:17 ` Joe Perches
2022-06-17 20:17 ` Joe Perches
2022-06-20 3:17 ` Chen, Rong A [this message]
2022-06-20 6:12 ` [kbuild-all] " Ilpo Järvinen
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=7c01c4f8-1826-8769-c3d3-309a9d23f113@intel.com \
--to=rong.a.chen@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jirislaby@kernel.org \
--cc=joe@perches.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=lkp@intel.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.