From: Vinicius Costa Gomes <vinicius.gomes@intel.com>
To: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>,
Sasha Neftin <sasha.neftin@intel.com>
Cc: vinschen@redhat.com, naamax.meir@linux.intel.com,
intel-wired-lan@lists.osuosl.org,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
hkelam@marvell.com, anthony.l.nguyen@intel.com, "Lifshits,
Vitaly" <vitaly.lifshits@intel.com>,
"Ruinskiy, Dima" <dima.ruinskiy@intel.com>
Subject: Re: [Intel-wired-lan] 6.10; regression; bisected - commit 86167183a17e cause info msg "trying to register non-static key"
Date: Wed, 05 Jun 2024 15:03:47 -0700 [thread overview]
Message-ID: <87le3jujwc.fsf@intel.com> (raw)
In-Reply-To: <CABXGCsPAdzVnSpT65NkMTi=jS1c0-bz=2XjnZWUkOxhrnkpgEQ@mail.gmail.com>
Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com> writes:
> On Tue, May 21, 2024 at 10:34 AM Sasha Neftin <sasha.neftin@intel.com> wrote:
>>
>> Any thought? Revert?
>>
>
> Sorry for the noise. Is there any solution?
Sasha has provided the revert[1], so it's on its way to be fixed.
[1] https://lore.kernel.org/intel-wired-lan/20240529051307.3094901-1-sasha.neftin@intel.com/
>
> --
> Best Regards,
> Mike Gavrilov.
Cheers,
--
Vinicius
WARNING: multiple messages have this Message-ID (diff)
From: Vinicius Costa Gomes <vinicius.gomes@intel.com>
To: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>,
Sasha Neftin <sasha.neftin@intel.com>
Cc: Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
vinschen@redhat.com, hkelam@marvell.com,
naamax.meir@linux.intel.com, anthony.l.nguyen@intel.com,
"Ruinskiy, Dima" <dima.ruinskiy@intel.com>,
"Lifshits, Vitaly" <vitaly.lifshits@intel.com>,
intel-wired-lan@lists.osuosl.org
Subject: Re: [Intel-wired-lan] 6.10; regression; bisected - commit 86167183a17e cause info msg "trying to register non-static key"
Date: Wed, 05 Jun 2024 15:03:47 -0700 [thread overview]
Message-ID: <87le3jujwc.fsf@intel.com> (raw)
In-Reply-To: <CABXGCsPAdzVnSpT65NkMTi=jS1c0-bz=2XjnZWUkOxhrnkpgEQ@mail.gmail.com>
Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com> writes:
> On Tue, May 21, 2024 at 10:34 AM Sasha Neftin <sasha.neftin@intel.com> wrote:
>>
>> Any thought? Revert?
>>
>
> Sorry for the noise. Is there any solution?
Sasha has provided the revert[1], so it's on its way to be fixed.
[1] https://lore.kernel.org/intel-wired-lan/20240529051307.3094901-1-sasha.neftin@intel.com/
>
> --
> Best Regards,
> Mike Gavrilov.
Cheers,
--
Vinicius
next prev parent reply other threads:[~2024-06-05 22:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 10:25 6.10;regression;bisected - commit 86167183a17e cause info msg "trying to register non-static key" Mikhail Gavrilov
2024-05-17 21:05 ` [Intel-wired-lan] 6.10; regression; bisected " Vinicius Costa Gomes
2024-05-17 21:05 ` 6.10;regression;bisected " Vinicius Costa Gomes
2024-05-21 5:34 ` [Intel-wired-lan] 6.10; regression; bisected " Sasha Neftin
2024-05-21 5:34 ` Sasha Neftin
2024-06-05 12:09 ` Mikhail Gavrilov
2024-06-05 12:09 ` Mikhail Gavrilov
2024-06-05 22:03 ` Vinicius Costa Gomes [this message]
2024-06-05 22:03 ` Vinicius Costa Gomes
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=87le3jujwc.fsf@intel.com \
--to=vinicius.gomes@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=dima.ruinskiy@intel.com \
--cc=hkelam@marvell.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikhail.v.gavrilov@gmail.com \
--cc=naamax.meir@linux.intel.com \
--cc=sasha.neftin@intel.com \
--cc=vinschen@redhat.com \
--cc=vitaly.lifshits@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.