From: Mark Brown <broonie@kernel.org>
To: qiao mnlife <mnlife.qiao@gmail.com>
Cc: "lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"Jaroslav Kysela" <perex@perex.cz>,
"open list" <linux-kernel@vger.kernel.org>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
乔星 <mnlife@foxmail.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
Date: Tue, 14 Jul 2020 11:35:36 +0100 [thread overview]
Message-ID: <20200714103536.GC4900@sirena.org.uk> (raw)
In-Reply-To: <DM6PR12MB4122CBAFE14C28D7302272E3F9650@DM6PR12MB4122.namprd12.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 739 bytes --]
On Fri, Jul 10, 2020 at 02:56:03PM +0000, qiao mnlife wrote:
> ________________________________
> From: mnlife <mnlife@foxmail.com>
> Sent: Friday, July 10, 2020 10:45:42 PM
> To: mnlife.qiao@gmail.com <mnlife.qiao@gmail.com>
> Cc: mnlife <mnlife@foxmail.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@foxmail.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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
parent reply other threads:[~2020-07-14 10:35 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <DM6PR12MB4122CBAFE14C28D7302272E3F9650@DM6PR12MB4122.namprd12.prod.outlook.com>]
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=20200714103536.GC4900@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mnlife.qiao@gmail.com \
--cc=mnlife@foxmail.com \
--cc=perex@perex.cz \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®