From: Eric Dumazet <edumazet@google.com>
To: Linux regressions mailing list <regressions@lists.linux.dev>
Cc: "Petr Tesařík" <petr@tesarici.cz>,
"David S. Miller" <davem@davemloft.net>,
"open list" <linux-kernel@vger.kernel.org>,
stable@kernel.org, "Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH 1/1] u64_stats: fix u64_stats_init() for lockdep when used repeatedly in one file
Date: Tue, 2 Apr 2024 15:42:44 +0200 [thread overview]
Message-ID: <CANn89iKfMTGyyMB-x74J5bgzhM1RxSvuNhvXyWWv4DO8MZakSQ@mail.gmail.com> (raw)
In-Reply-To: <72e39571-7122-4f6a-9252-83e663e4b703@leemhuis.info>
On Tue, Apr 2, 2024 at 3:40 PM Linux regression tracking (Thorsten
Leemhuis) <regressions@leemhuis.info> wrote:
>
> Hi. Top-posting for once, to make this easily accessible to everyone.
>
> Hmmm, looks like Petr's patch for a (minor) 6.8 regression didn't make
> any progress in the past two weeks.
>
> Does nobody care? Did nobody merge it because no tree feels really
> appropriate? Or am I missing something obvious and making a fool out of
> myself by asking these questions? :D
It happens, please resend the patch.
next prev parent reply other threads:[~2024-04-02 13:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240306111157.29327-1-petr@tesarici.cz>
[not found] ` <20240311182516.1e2eebd8@meshulam.tesarici.cz>
[not found] ` <CANn89iKQpSaF5KG5=dT_o=WBeZtCiLcN768eUdYvUew-dLbKaA@mail.gmail.com>
[not found] ` <20240311192118.31cfc1fb@meshulam.tesarici.cz>
2024-03-18 14:23 ` [PATCH 1/1] u64_stats: fix u64_stats_init() for lockdep when used repeatedly in one file Linux regression tracking (Thorsten Leemhuis)
2024-04-02 13:40 ` Linux regression tracking (Thorsten Leemhuis)
2024-04-02 13:42 ` Eric Dumazet [this message]
2024-04-02 13:54 ` Eric Dumazet
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=CANn89iKfMTGyyMB-x74J5bgzhM1RxSvuNhvXyWWv4DO8MZakSQ@mail.gmail.com \
--to=edumazet@google.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petr@tesarici.cz \
--cc=regressions@lists.linux.dev \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).