From: Stephen Hemminger <stephen@networkplumber.org>
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: davem@davemloft.net, kuba@kernel.org, edumazet@google.com,
pabeni@redhat.com, jiri@resnulli.us, xiyou.wangcong@gmail.com,
netdev@vger.kernel.org, dsahern@gmail.com,
pctammela@mojatatu.com, victor@mojatatu.com
Subject: Re: [PATCH net-next 1/5] net/sched: Remove uapi support for rsvp classifier
Date: Sat, 23 Dec 2023 09:16:57 -0800 [thread overview]
Message-ID: <20231223091657.498a1595@hermes.local> (raw)
In-Reply-To: <20231223140154.1319084-2-jhs@mojatatu.com>
On Sat, 23 Dec 2023 09:01:50 -0500
Jamal Hadi Salim <jhs@mojatatu.com> wrote:
> diff --git a/tools/include/uapi/linux/pkt_cls.h b/tools/include/uapi/linux/pkt_cls.h
> index 3faee0199a9b..82eccb6a4994 100644
> --- a/tools/include/uapi/linux/pkt_cls.h
> +++ b/tools/include/uapi/linux/pkt_cls.h
> @@ -204,37 +204,6 @@ struct tc_u32_pcnt {
>
Seems like a mistake for kernel source tree to include two copies of same file.
Shouldn't there be an automated make rule to update?
next prev parent reply other threads:[~2023-12-23 17:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-23 14:01 [PATCH net-next 0/5] net/sched: Remove UAPI support for retired TC qdiscs and classifiers Jamal Hadi Salim
2023-12-23 14:01 ` [PATCH net-next 1/5] net/sched: Remove uapi support for rsvp classifier Jamal Hadi Salim
2023-12-23 17:16 ` Stephen Hemminger [this message]
2023-12-23 21:15 ` Jamal Hadi Salim
2024-01-01 18:56 ` Cong Wang
2023-12-23 14:01 ` [PATCH net-next 2/5] net/sched: Remove uapi support for tcindex classifier Jamal Hadi Salim
2023-12-23 14:01 ` [PATCH net-next 3/5] net/sched: Remove uapi support for dsmark qdisc Jamal Hadi Salim
2023-12-23 14:01 ` [PATCH net-next 4/5] net/sched: Remove uapi support for ATM qdisc Jamal Hadi Salim
2023-12-23 14:01 ` [PATCH net-next 5/5] net/sched: Remove uapi support for CBQ qdisc Jamal Hadi Salim
2024-01-01 18:58 ` [PATCH net-next 0/5] net/sched: Remove UAPI support for retired TC qdiscs and classifiers Cong Wang
2024-01-02 14:30 ` 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:
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=20231223091657.498a1595@hermes.local \
--to=stephen@networkplumber.org \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=edumazet@google.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pctammela@mojatatu.com \
--cc=victor@mojatatu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox