archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <>
To: Ido Schimmel <>,
Subject: Re: [PATCH net] ipv4: Fix route deletion when nexthop info is not specified
Date: Fri, 25 Nov 2022 11:07:15 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi, this is your Linux kernel regression tracker.

On 24.11.22 22:09, Ido Schimmel wrote:
> When the kernel receives a route deletion request from user space it
> tries to delete a route that matches the route attributes specified in
> the request.
> [...]
 > Cc:
> Reported-by: Jonas Gorski <>

Many thx for taking care of this. There is one small thing to improve,
please add the following tags here:


To explain: Linus[1] and others considered proper link tags in cases
like important, as they allow anyone to look into the backstory weeks or
years from now. That why they should be placed here, as outlined by the
documentation[2]. I care personally, because these tags make my
regression tracking efforts a whole lot easier, as they allow my
tracking bot 'regzbot' to automatically connect reports with patches
posted or committed to fix tracked regressions.

Apropos regzbot, let me tell regzbot to monitor this thread:

#regzbot ^backmonitor:

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)

P.S.: As the Linux kernel's regression tracker I deal with a lot of
reports and sometimes miss something important when writing mails like
this. If that's the case here, don't hesitate to tell me in a public
reply, it's in everyone's interest to set the public record straight.

[1] for details, see:

[2] see Documentation/process/submitting-patches.rst
( and

  parent reply	other threads:[~2022-11-25 10:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-24 21:09 [PATCH net] ipv4: Fix route deletion when nexthop info is not specified Ido Schimmel
2022-11-24 21:25 ` Nikolay Aleksandrov
2022-11-25  3:52 ` David Ahern
2022-11-25 10:07 ` Thorsten Leemhuis [this message]
2022-11-29  1:00 ` patchwork-bot+netdevbpf

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \ \

* 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).