From: Punit Agrawal <punit1.agrawal@toshiba.co.jp>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, "Brandeburg\,
Jesse" <jesse.brandeburg@intel.com>, "Nguyen\,
Anthony L" <anthony.l.nguyen@intel.com>,
"daichi1.fukui\@toshiba.co.jp" <daichi1.fukui@toshiba.co.jp>,
"nobuhiro1.iwamatsu\@toshiba.co.jp"
<nobuhiro1.iwamatsu@toshiba.co.jp>,
Corinna Vinschen <vinschen@redhat.com>, "Brown\,
Aaron.F" <aaron.f.brown@intel.com>, "Keller\,
Jacob.E" <jacob.e.keller@intel.com>,
"David.S.Miller" <davem@davemloft.net>
Subject: Re: [PATCH v4.4.y, v4.9.y] igb: Remove incorrect "unexpected SYS WRAP" log message
Date: Thu, 25 Feb 2021 09:44:02 +0900 [thread overview]
Message-ID: <87wnuxugbx.fsf@kokedama.swc.toshiba.co.jp> (raw)
In-Reply-To: <20210224085126.45af7b68@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (Jakub Kicinski's message of "Wed, 24 Feb 2021 08:51:26 -0800")
Jakub Kicinski <kuba@kernel.org> writes:
> On Wed, 24 Feb 2021 11:28:59 +0900 Punit Agrawal wrote:
>> > It makes sense to me for htis to apply to those stable trees as well.
>>
>> Thanks Jake.
>>
>> Networking maintainers - It's been a couple of weeks this patch is on
>> the list. Is there anything else that needs to be done for it to be
>> picked up for stable?
>
> Network maintainers only handle stable selection at the time of
> submission (if that). So if you want to request a backport of a commit
> which is already in Linus's tree and wasn't selected you should follow
> the standard stable procedure and submit the request to stable@, CCing
> netdev.
Ah I missed that. Thanks for the pointer - I'll resend the request to
stable with netdev in CC.
next prev parent reply other threads:[~2021-02-25 0:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 1:34 [PATCH v4.4.y, v4.9.y] igb: Remove incorrect "unexpected SYS WRAP" log message Punit Agrawal
2021-02-10 1:46 ` Keller, Jacob E
2021-02-24 2:28 ` Punit Agrawal
[not found] ` <20210224085126.45af7b68@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
2021-02-25 0:44 ` Punit Agrawal [this message]
2021-02-25 0:54 Punit Agrawal
2021-02-25 8:17 ` Greg KH
2021-03-17 0:38 ` Punit Agrawal
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=87wnuxugbx.fsf@kokedama.swc.toshiba.co.jp \
--to=punit1.agrawal@toshiba.co.jp \
--cc=aaron.f.brown@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=daichi1.fukui@toshiba.co.jp \
--cc=davem@davemloft.net \
--cc=jacob.e.keller@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nobuhiro1.iwamatsu@toshiba.co.jp \
--cc=vinschen@redhat.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;
as well as URLs for NNTP newsgroup(s).