From: Jacob Keller <jacob.e.keller@intel.com>
To: David Ahern <dsahern@gmail.com>,
Parav Pandit <parav@mellanox.com>,
netdev@vger.kernel.org
Cc: stephen@networkplumber.org, dsahern@kernel.org, jiri@mellanox.com
Subject: Re: [PATCH net-next iproute2 1/2] Update devlink kernel header
Date: Thu, 5 Mar 2020 16:55:21 -0800 [thread overview]
Message-ID: <1517e035-8be1-d66b-92cb-727abdc36cd7@intel.com> (raw)
In-Reply-To: <3281568c-72d3-2c02-adc3-4e3008cdf4ec@gmail.com>
On 3/5/2020 4:43 PM, David Ahern wrote:
> On 3/5/20 5:42 PM, Jacob Keller wrote:
>> This hunk doesn't seem relevant to the patch and isn't mentioned in the
>> subject or description.
>
> it was a sync of the header file. I drop those changes and do full uapi
> sync for iproute2 and then apply patches.
>
Makes sense. Thanks for the explanation.
next prev parent reply other threads:[~2020-03-06 0:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 4:06 [PATCH net-next iproute2 0/2] devlink: Introduce devlink port flavour virtual Parav Pandit
2020-03-04 4:06 ` [PATCH net-next iproute2 1/2] Update devlink kernel header Parav Pandit
2020-03-06 0:42 ` Jacob Keller
2020-03-06 0:43 ` David Ahern
2020-03-06 0:55 ` Jacob Keller [this message]
2020-03-06 0:44 ` Jacob Keller
2020-03-04 4:06 ` [PATCH net-next iproute2 2/2] devlink: Introduce devlink port flavour virtual Parav Pandit
2020-03-04 19:48 ` David Ahern
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=1517e035-8be1-d66b-92cb-727abdc36cd7@intel.com \
--to=jacob.e.keller@intel.com \
--cc=dsahern@gmail.com \
--cc=dsahern@kernel.org \
--cc=jiri@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=parav@mellanox.com \
--cc=stephen@networkplumber.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).