Received-SPF: softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19;
Date:   Wed, 20 Apr 2022 14:41:21 +0100
From:   Mark Brown <broonie@kernel.org>
To:     Miaoqian Lin <linmq006@gmail.com>
Cc:     Liam Girdwood <lgirdwood@gmail.com>,
        Jaroslav Kysela <perex@perex.cz>,
        Takashi Iwai <tiwai@suse.com>, alsa-devel@alsa-project.org,
        linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ASoC: fsl: Fix error handling in pcm030_fabric_probe
Message-ID: <YmANgcO9BMxp8PLC@sirena.org.uk>
References: <Yh90u+E3RTuGEDWU@sirena.org.uk>
 <20220420021855.8224-1-linmq006@gmail.com>
 <YmAD6MIuKdjgm7Yu@sirena.org.uk>
 <4e3309d9-879f-3385-3e8e-0fa1a31ddd9a@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
        protocol="application/pgp-signature"; boundary="rm+GGDPp5GTQyZKB"
Content-Disposition: inline
In-Reply-To: <4e3309d9-879f-3385-3e8e-0fa1a31ddd9a@gmail.com>
Precedence: bulk


--rm+GGDPp5GTQyZKB
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Wed, Apr 20, 2022 at 09:35:55PM +0800, Miaoqian Lin wrote:
> On 2022/4/20 21:00, Mark Brown wrote:

> >> - rebase on top of commit 559089e0a93d ("vmalloc: replace VM_NO_HUGE_VMAP with VM_ALLOW_HUGE_VMAP")

> > Why rebase on top of that seemingly random commit?  Is there some sort
> > of dependency here?

> Hi, it the head of master in when I made this patch. It's because you pointed out

> that patch v1 doesn't apply against current code. But I am not sure what's the problem.

> So I ensure the codebase is up-to-date. If this patch have no conflict, you can ignore it.

Current code here is my git tree (-next is often a fair approximation) -
if people have been making changes since the merge window then often
code written against mainline won't apply and things need to be based on
people's current work.  You're looking for

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

--rm+GGDPp5GTQyZKB
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmJgDYAACgkQJNaLcl1U
h9Aevwf/ULNqXVQDbV8fuV6Qilw1nnp30Uhxr1swwNI5GZq806ylondesmsA/Bao
KcooPJ6fC01+V2mjTBdS2ixwZnNHBddgTRixaYW52BnFiul+dFi21NiD7K8Japhh
lkk+HGCAOhyBUOrOcSuHIKmof5UuBuzQh5ObwPWW5e7O+2jcy8p/CD5SdSWvrKrL
J9t4dWoBeBFXUnXzIieAbJ2A24P+RSteGoGsOhfbgkBGTxNihe63TSUY5rZYw7LX
0QswaM07k9hUACCJTHamwQTgjRIfMiYLQmgM70iCm4h+DsTcYcthrW5/cgcicvgC
hzJ0B1d6KbYrpQlk23vciyh9mHBQ0g==
=eH5c
-----END PGP SIGNATURE-----

--rm+GGDPp5GTQyZKB--