From: Stephen Hemminger <stephen@networkplumber.org>
To: David Ahern <dsahern@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2] ip link: Do not call ll_name_to_index when creating a new link
Date: Fri, 25 May 2018 08:21:22 -0700 [thread overview]
Message-ID: <20180525082122.5b4c4740@xeon-e3> (raw)
In-Reply-To: <054faf87-f311-61a1-3c9a-e7d20cac8279@gmail.com>
On Fri, 18 May 2018 17:40:05 -0600
David Ahern <dsahern@gmail.com> wrote:
> On 5/18/18 4:08 PM, Stephen Hemminger wrote:
> >
> > What about just pushing the lookup down to the leaf functions that need it?
> >
>
> That should work as well. You want to re-send a formal patch?
>
I just pushed it up as a formal patch (with your text).
prev parent reply other threads:[~2018-05-25 15:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 22:22 [PATCH iproute2] ip link: Do not call ll_name_to_index when creating a new link dsahern
2018-05-17 22:36 ` Stephen Hemminger
2018-05-17 22:47 ` David Ahern
2018-05-18 0:17 ` David Ahern
2018-05-18 22:08 ` Stephen Hemminger
2018-05-18 23:40 ` David Ahern
2018-05-25 15:21 ` Stephen Hemminger [this message]
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=20180525082122.5b4c4740@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dsahern@gmail.com \
--cc=netdev@vger.kernel.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).