From: Mark Brown <broonie@kernel.org>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org
Subject: Re: [PATCH 2/3] spi: fix some invalid char occurrences
Date: Wed, 19 May 2021 14:10:43 +0100 [thread overview]
Message-ID: <20210519131043.GD4224@sirena.org.uk> (raw)
In-Reply-To: <ff8d296e1fdcc4f1c6df94434a5720bcedcd0ecf.1621412009.git.mchehab+huawei@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 293 bytes --]
On Wed, May 19, 2021 at 10:15:36AM +0200, Mauro Carvalho Chehab wrote:
> One of the author names got an invalid char, probably due to
> a bad charset conversion, being replaced by the
> REPLACEMENT CHARACTER U+fffd ('�').
I only have patch 2 here, what's the story with dependencies?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-05-19 13:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 8:15 [PATCH 1/3] gpu: drm: replace occurrences of invalid character Mauro Carvalho Chehab
2021-05-19 8:15 ` Mauro Carvalho Chehab
2021-05-19 8:15 ` Mauro Carvalho Chehab
2021-05-19 8:15 ` [Intel-gfx] " Mauro Carvalho Chehab
2021-05-19 8:15 ` [PATCH 2/3] spi: fix some invalid char occurrences Mauro Carvalho Chehab
2021-05-19 13:10 ` Mark Brown [this message]
2021-05-19 13:30 ` Mauro Carvalho Chehab
2021-05-19 8:15 ` [PATCH 3/3] visorbus: fix a copyright symbol that was bad encoded Mauro Carvalho Chehab
2021-05-19 15:56 ` [PATCH 1/3] gpu: drm: replace occurrences of invalid character Randy Dunlap
2021-05-19 15:56 ` Randy Dunlap
2021-05-19 15:56 ` Randy Dunlap
2021-05-19 15:56 ` [Intel-gfx] " Randy Dunlap
2021-05-19 16:40 ` Alex Deucher
2021-05-19 16:40 ` Alex Deucher
2021-05-19 16:40 ` Alex Deucher
2021-05-19 16:40 ` [Intel-gfx] " Alex Deucher
2021-05-20 21:08 ` (subset) " Mark Brown
2021-05-20 21:08 ` Mark Brown
2021-05-20 21:08 ` Mark Brown
2021-05-20 21:08 ` [Intel-gfx] " Mark Brown
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=20210519131043.GD4224@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
/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.