[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20200714103536.GC4900@sirena.org.uk>
Date: Tue, 14 Jul 2020 11:35:36 +0100
From: Mark Brown <broonie@...nel.org>
To: qiao mnlife <mnlife.qiao@...il.com>
Cc: "lgirdwood@...il.com" <lgirdwood@...il.com>,
Jaroslav Kysela <perex@...ex.cz>,
open list <linux-kernel@...r.kernel.org>,
"alsa-devel@...a-project.org" <alsa-devel@...a-project.org>,
乔星 <mnlife@...mail.com>
Subject: Re: [PATCH] soc jack: When snd_soc_card_jack_new is not called or
the call fails, calling this function causes a null pointer access
On Fri, Jul 10, 2020 at 02:56:03PM +0000, qiao mnlife wrote:
> ________________________________
> From: mnlife <mnlife@...mail.com>
> Sent: Friday, July 10, 2020 10:45:42 PM
> To: mnlife.qiao@...il.com <mnlife.qiao@...il.com>
> Cc: mnlife <mnlife@...mail.com>
> Subject: [PATCH] When snd_soc_card_jack_new is not called or the call fails, calling this function causes a null pointer access
>
> Signed-off-by: mnlife <mnlife@...mail.com>
This looks good but it's a bit mangled in submission - can you please
try to resend using something closer to the format in
submitting-patches.rst? The changelog should be in the body of the mail
and there should be a patch subject in a similar format to to the other
patches in git.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists