From: Jakub Kicinski <kuba@kernel.org>
To: Donald Hunter <donald.hunter@gmail.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
johannes@sipsolutions.net, razor@blackwall.org
Subject: Re: [PATCH net-next 3/4] netlink: specs: remove implicit structs for SNMP counters
Date: Tue, 6 May 2025 09:10:25 -0700 [thread overview]
Message-ID: <20250506091025.6002377f@kernel.org> (raw)
In-Reply-To: <CAD4GDZyFM0uY9WPPw3DF1F+tsDU=0PwyA1yFvbxVxv3amyfu5g@mail.gmail.com>
On Tue, 6 May 2025 13:50:44 +0100 Donald Hunter wrote:
> On Mon, 5 May 2025 at 18:02, Jakub Kicinski <kuba@kernel.org> wrote:
> >
> > name: reasm-overlaps
> > - type: u64
> > - name: br-boolopt-multi
> > type: struct
> > header: linux/if_bridge.h
>
> The patch does not apply for me, I think due to the above line
> changing in another series.
Oh, my bad, the rt-link C info patch was hiding in my queue between
these and net-next. Will send v2 shortly.
next prev parent reply other threads:[~2025-05-06 16:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-05 17:02 [PATCH net-next 0/4] netlink: specs: remove phantom structs Jakub Kicinski
2025-05-05 17:02 ` [PATCH net-next 1/4] netlink: specs: nl80211: drop structs which are not uAPI Jakub Kicinski
2025-05-06 12:56 ` Donald Hunter
2025-05-05 17:02 ` [PATCH net-next 2/4] netlink: specs: ovs: correct struct names Jakub Kicinski
2025-05-06 12:58 ` Donald Hunter
2025-05-05 17:02 ` [PATCH net-next 3/4] netlink: specs: remove implicit structs for SNMP counters Jakub Kicinski
2025-05-06 12:50 ` Donald Hunter
2025-05-06 16:10 ` Jakub Kicinski [this message]
2025-05-05 17:02 ` [PATCH net-next 4/4] netlink: specs: rt-link: remove implicit structs from devconf Jakub Kicinski
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=20250506091025.6002377f@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.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).