From: David Ahern <dsahern@kernel.org>
To: Yuyang Huang <yuyanghuang@google.com>,
Hangbin Liu <liuhangbin@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Simon Horman" <horms@kernel.org>,
roopa@cumulusnetworks.com, jiri@resnulli.us,
stephen@networkplumber.org, jimictw@google.com, prohr@google.com,
nicolas.dichtel@6wind.com, andrew@lunn.ch,
netdev@vger.kernel.org, "Maciej Żenczykowski" <maze@google.com>,
"Lorenzo Colitti" <lorenzo@google.com>
Subject: Re: [PATCH iproute2-next] iproute2: add 'ip monitor mcaddr' support
Date: Mon, 18 Nov 2024 11:45:24 -0700 [thread overview]
Message-ID: <c97dd18b-8f67-4d22-a088-d73268402261@kernel.org> (raw)
In-Reply-To: <CADXeF1GqzSWYmSFO3v6x7+KTc=Q+U9hUiTd+x5yvZaViSKSkOQ@mail.gmail.com>
On 11/18/24 6:19 AM, Yuyang Huang wrote:
> Thanks for the prompt review feedback.
>
>> No need changes for headers. Stephen will sync the headers.
>
> The patch will not compile without the header changes. I guess that
> means I should put the patch on hold until the kernel change is merged
> and the header changes get synced up to iproute2?
headers in 1 patch; remaining change in a second patch. That allows the
set to be usable and then I can drop the uapi patch after a header sync
and only apply the second one.
next prev parent reply other threads:[~2024-11-18 18:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-17 14:16 [PATCH iproute2-next] iproute2: add 'ip monitor mcaddr' support Yuyang Huang
2024-11-18 12:36 ` Hangbin Liu
2024-11-18 13:19 ` Yuyang Huang
2024-11-18 18:45 ` David Ahern [this message]
2024-11-19 1:06 ` Andrew Lunn
2024-11-19 4:25 ` Yuyang Huang
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=c97dd18b-8f67-4d22-a088-d73268402261@kernel.org \
--to=dsahern@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jimictw@google.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=liuhangbin@gmail.com \
--cc=lorenzo@google.com \
--cc=maze@google.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=pabeni@redhat.com \
--cc=prohr@google.com \
--cc=roopa@cumulusnetworks.com \
--cc=stephen@networkplumber.org \
--cc=yuyanghuang@google.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.