All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Jamal Hadi Salim <jhs@mojatatu.com>, xiyou.wangcong@gmail.com
Cc: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
	Davide Caratti <dcaratti@redhat.com>,
	netdev@vger.kernel.org, jiri@resnulli.us, pabeni@redhat.com,
	wizhao@redhat.com, lucien.xin@gmail.com
Subject: Re: [RFC net-next 2/2] act_mirred: use the backlog for nested calls to mirred ingress
Date: Mon, 9 Jan 2023 10:39:40 -0800	[thread overview]
Message-ID: <20230109103940.52e6bf42@kernel.org> (raw)
In-Reply-To: <CAM0EoMkSqNAvuNSce=f5bmmy4ZRnteJ6CQZpSmUiZ+UKTUL27A@mail.gmail.com>

On Mon, 9 Jan 2023 10:59:49 -0500 Jamal Hadi Salim wrote:
> Sorry, I thought it was addressing the issue we discussed last time.
> Lets discuss in our monthly meeting.

When is your meeting? One could consider this patch as a fix and it
looks kinda "obviously correct", so the need for delays and discussions
is a bit lost on me.

Cong, WDYT?

Reminder: please don't top post and trim your replies.

  reply	other threads:[~2023-01-09 18:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-20 18:25 [RFC net-next 1/2] net/sched: act_mirred: better wording on protection against excessive stack growth Davide Caratti
2022-12-20 18:25 ` [RFC net-next 2/2] act_mirred: use the backlog for nested calls to mirred ingress Davide Caratti
2022-12-26 16:03   ` Jamal Hadi Salim
2023-01-05 17:08     ` Marcelo Ricardo Leitner
2023-01-09 15:59       ` Jamal Hadi Salim
2023-01-09 18:39         ` Jakub Kicinski [this message]
2023-01-09 20:46           ` Jamal Hadi Salim
2023-01-11 14:26             ` Marcelo Ricardo Leitner

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=20230109103940.52e6bf42@kernel.org \
    --to=kuba@kernel.org \
    --cc=dcaratti@redhat.com \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=lucien.xin@gmail.com \
    --cc=marcelo.leitner@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=wizhao@redhat.com \
    --cc=xiyou.wangcong@gmail.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.