public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Joshua Washington <joshwash@google.com>
Cc: stable@vger.kernel.org, Ankit Garg <nktgrg@google.com>,
	Jordan Rhee <jordanrhee@google.com>,
	Harshitha Ramamurthy <hramamurthy@google.com>,
	Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH 6.6.y] gve: defer interrupt enabling until NAPI registration
Date: Tue, 17 Feb 2026 12:01:06 +0100	[thread overview]
Message-ID: <2026021745-sweep-dioxide-a823@gregkh> (raw)
In-Reply-To: <CALuQH+Xsai9RWAwinJ6uG6Q9a_ocyaLrq2LtjY=6oVgFctK52w@mail.gmail.com>

On Mon, Feb 16, 2026 at 11:00:01AM -0800, Joshua Washington wrote:
> Hello,
> 
> I was also wondering if the way I'd sent the patches was okay, with
> major.minory.y patches for each of the stable kernels, or if I should
> send them differently in V2. Lore seems to have grouped all 4 patches
> into a series, which seemed a bit odd to me, but was probably related
> to the fact that I'd only used a single send-email command.

Either is fine, that's the least of our worries when taking stable
backports :)

thanks,

greg k-h

      reply	other threads:[~2026-02-17 11:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-13 21:16 [PATCH 5.10.y] gve: defer interrupt enabling until NAPI registration Joshua Washington
2026-02-13 21:17 ` [PATCH 5.15.y] " Joshua Washington
2026-02-13 21:17 ` [PATCH 6.1.y] " Joshua Washington
2026-02-13 21:17 ` [PATCH 6.6.y] " Joshua Washington
2026-02-16  9:58   ` Greg KH
2026-02-16 18:41     ` Joshua Washington
2026-02-16 19:00       ` Joshua Washington
2026-02-17 11:01         ` Greg KH [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=2026021745-sweep-dioxide-a823@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=hramamurthy@google.com \
    --cc=jordanrhee@google.com \
    --cc=joshwash@google.com \
    --cc=nktgrg@google.com \
    --cc=pabeni@redhat.com \
    --cc=stable@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