Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Wed, 19 May 2021 15:30:58 +0200
From:   Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To:     Mark Brown <broonie@kernel.org>
Cc:     linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org
Subject: Re: [PATCH 2/3] spi: fix some invalid char occurrences
Message-ID: <20210519153058.71b59658@coco.lan>
In-Reply-To: <20210519131043.GD4224@sirena.org.uk>
References: <e606930c73029f16673849c57acac061dd923866.1621412009.git.mchehab+huawei@kernel.org>
        <ff8d296e1fdcc4f1c6df94434a5720bcedcd0ecf.1621412009.git.mchehab+huawei@kernel.org>
        <20210519131043.GD4224@sirena.org.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

Em Wed, 19 May 2021 14:10:43 +0100
Mark Brown <broonie@kernel.org> escreveu:

> 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 ('=EF=BF=BD'). =20
>=20
> I only have patch 2 here, what's the story with dependencies?

Sorry, I sent three completely independent patches to different
subsystems. It was not supposed to be numerated... meaning that I need to
fix my send scripts ;-)=20

The only thing they have in common is that they touch files using
the REPLACEMENT CHARACTER (U+fffd).

The other two patches are:

	[PATCH 1/3] gpu: drm: replace occurrences of invalid character
	[PATCH 3/3] visorbus: fix a copyright symbol that was bad encoded

Thanks,
Mauro