public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Daniel Scally <djrscally@gmail.com>
Cc: platform-driver-x86@vger.kernel.org,
	linux-kernel@vger.kernel.org, Hans de Goede <hdegoede@redhat.com>,
	Mark Gross <mgross@linux.intel.com>
Subject: Re: [Bug 214453] New: skl_int3472_unregister_clock: kernel NULL pointer dereference (HP Elite x2 1013 G3)
Date: Sat, 9 Oct 2021 10:14:51 +0200	[thread overview]
Message-ID: <YWFPe8yeiYYeYPWy@zn.tnic> (raw)
In-Reply-To: <035a956e-9987-9b26-38a5-8319f69d4b6d@gmail.com>

On Fri, Oct 08, 2021 at 11:18:50PM +0100, Daniel Scally wrote:
> I can patch this - but do I need to do to show that the patch is for
> that specific bug report or anything?

What we do in such cases, usually, is add

Link: https://bugzilla.kernel.org/show_bug.cgi?id=214453

to the commit message, under the SOB chain.

Also, you probably also should give in a Fixes: tag the commit ID of the
patch your fix is for, so that your fix gets automatically backported to
stable.

I.e.:

Fixes: 12-char-sha1-abbrev ("Commit title")
Cc: <stable@vger.kernel.org>

HTH.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

      reply	other threads:[~2021-10-09  8:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-214453-6385@https.bugzilla.kernel.org/>
2021-10-04 16:59 ` [Bug 214453] New: skl_int3472_unregister_clock: kernel NULL pointer dereference (HP Elite x2 1013 G3) Borislav Petkov
2021-10-05 14:44   ` Daniel Scally
2021-10-08 22:18   ` Daniel Scally
2021-10-09  8:14     ` Borislav Petkov [this message]

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=YWFPe8yeiYYeYPWy@zn.tnic \
    --to=bp@alien8.de \
    --cc=djrscally@gmail.com \
    --cc=hdegoede@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgross@linux.intel.com \
    --cc=platform-driver-x86@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox