public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Dawid Osuchowski <dawid.osuchowski@linux.intel.com>
To: Matt Vollrath <tactii@gmail.com>, intel-wired-lan@osuosl.org
Cc: stable@vger.kernel.org, Avigail Dahan <avigailx.dahan@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-net v2] e1000e: Unroll PTP in probe error handling
Date: Tue, 14 Apr 2026 10:55:35 +0200	[thread overview]
Message-ID: <01cee873-23d7-43f5-96eb-29826d1c157c@linux.intel.com> (raw)
In-Reply-To: <20260413000325.33379-1-tactii@gmail.com>

On 2026-04-13 2:03 AM, Matt Vollrath wrote:

Hey Matt,

Thanks for the patch!

Apologies but it seems I didn't explain fully where the changelog should 
go, same goes for the Cc: stable as it should be inserted into the 
commit msg as a tag, see example below.

> If probe fails after registering the PTP clock and its delayed work,
> these resources must be released.
> 
> This was not an issue until a 2016 fix moved the e1000e_ptp_init() call
> before the jump to err_register.
> 
> Fixes: aa524b66c5ef ("e1000e: don't modify SYSTIM registers during SIOCSHWTSTAMP ioctl")
> Signed-off-by: Matt Vollrath <tactii@gmail.com>
> Tested-by: Avigail Dahan <avigailx.dahan@intel.com>
> ---

Changelog should go _here_, not below the:

-- 
2.43.0

and should also have the --- afterwards. So using this patch submission 
as an example your commit msg + changelog should look like the following:

If probe fails after registering the PTP clock and its delayed work,
these resources must be released.

This was not an issue until a 2016 fix moved the e1000e_ptp_init() call
before the jump to err_register.

Fixes: aa524b66c5ef ("e1000e: don't modify SYSTIM registers during 
SIOCSHWTSTAMP ioctl")
Cc: stable@vger.kernel.org
Signed-off-by: Matt Vollrath <tactii@gmail.com>
Tested-by: Avigail Dahan <avigailx.dahan@intel.com>
---
Changes:
v2:
* Apply the correct Fixes tag
* Target iwl-net
* Cc stable
---

  drivers/net/ethernet/intel/e1000e/netdev.c | 1 +
  1 file changed, 1 insertion(+)

<snip of the rest of the diff/>

Once again sorry for not saying it more clearly before.

Best regards
~Dawid

  reply	other threads:[~2026-04-14  8:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-13  0:03 [PATCH iwl-net v2] e1000e: Unroll PTP in probe error handling Matt Vollrath
2026-04-14  8:55 ` Dawid Osuchowski [this message]
2026-04-14 17:16   ` [Intel-wired-lan] " Matt Vollrath

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=01cee873-23d7-43f5-96eb-29826d1c157c@linux.intel.com \
    --to=dawid.osuchowski@linux.intel.com \
    --cc=avigailx.dahan@intel.com \
    --cc=intel-wired-lan@osuosl.org \
    --cc=stable@vger.kernel.org \
    --cc=tactii@gmail.com \
    /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