Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Peter Große" <pegro@friiks.de>
To: Przemek Kitszel <przemyslaw.kitszel@intel.com>
Cc: Paul Menzel <pmenzel@molgen.mpg.de>,
	<intel-wired-lan@lists.osuosl.org>,
	Tony Nguyen <anthony.l.nguyen@intel.com>,
	<netdev@vger.kernel.org>
Subject: Re: [Intel-wired-lan] [PATCH iwl-net v2] i40e: Fix handling changed priv flags
Date: Thu, 31 Oct 2024 17:11:33 +0100	[thread overview]
Message-ID: <20241031171133.00001507@friiks.de> (raw)
In-Reply-To: <2d6b0d54-57d3-4f3b-833c-8490aa63490d@intel.com>

Am Thu, 31 Oct 2024 08:34:36 +0100
schrieb Przemek Kitszel <przemyslaw.kitszel@intel.com>:

> >> Fixes: 70756d0a4727 ("i40e: Use DECLARE_BITMAP for flags and 
> >> hw_features fields in i40e_pf")
> >> Signed-off-by: Peter Große <pegro@friiks.de>  
> 
> Both the code change and the Fixes: tag are correct, thank you!
> Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>

Great to hear :)

Would this be material for stable?

I hope to avoid building my own kernel and just use a hwe kernel of Ubuntu.


> BTW, we obey netdev rules on IWL ML - next revision only after 24-48h
> and send as standalone series (instead of In-reply-to) - no need to
> repost this time of course

Sorry, I'm new to submitting patches here.

Is there anything else I need to do?

Kind regards
Peter


  reply	other threads:[~2024-10-31 16:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-30 16:06 [Intel-wired-lan] [PATCH iwl-net] i40e: Fix handling changed priv flags pegro
2024-10-30 16:34 ` Paul Menzel
2024-10-30 16:38   ` Paul Menzel
2024-10-30 17:22     ` [Intel-wired-lan] [PATCH iwl-net v2] " pegro
2024-10-30 17:35       ` Paul Menzel
2024-10-31  7:34         ` Przemek Kitszel
2024-10-31 16:11           ` Peter Große [this message]
2024-11-04 12:11             ` Przemek Kitszel
2024-11-07 15:16       ` Pucha, HimasekharX Reddy

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=20241031171133.00001507@friiks.de \
    --to=pegro@friiks.de \
    --cc=anthony.l.nguyen@intel.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=netdev@vger.kernel.org \
    --cc=pmenzel@molgen.mpg.de \
    --cc=przemyslaw.kitszel@intel.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