From: vadim4j@gmail.com
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Vadim Kochan <vadim4j@gmail.com>, netdev@vger.kernel.org
Subject: Re: [PATCH iproute2 0/2] lib names: Refactoring and cleanups
Date: Wed, 10 Dec 2014 17:10:29 +0200 [thread overview]
Message-ID: <20141210151029.GA18451@angus-think.wlc.globallogic.com> (raw)
In-Reply-To: <20141209203856.491322c0@urahara>
On Tue, Dec 09, 2014 at 08:38:56PM -0800, Stephen Hemminger wrote:
> On Sat, 6 Dec 2014 04:05:10 +0200
> Vadim Kochan <vadim4j@gmail.com> wrote:
>
> > Some cleanups and refactoring in lib/rt_names.c:
> >
> > #1 Replaced using of /etc/iproute2 path by CONFDIR define
> > when initializing tables of group names.
> >
> > #2 Added helper to have one func for parsing id and names from
> > db files.
> >
> > Vadim Kochan (2):
> > lib names: Use CONFDIR for specify 'group' file path
> > lib names: Add helper func for parse id and name from file
> >
> > lib/rt_names.c | 70 +++++++++++++++++++++++++++++++++-------------------------
> > 1 file changed, 40 insertions(+), 30 deletions(-)
> >
>
> Both applied
Hi Stephen,
I see a warning (after 'make clean && make') about using 'const' in lib/rt_names.c:
static const char * rtnl_rtscope_tab[256] = {
"global",
};
which came with PATCH with a subject:
"lib names: Add helper func for parse id and name from file" (f00073e8b)
but in the PATCH version which was sent by me in email I did not see this.
Why it was needed ?
Regards,
Vadim
next prev parent reply other threads:[~2014-12-10 15:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-06 2:05 [PATCH iproute2 0/2] lib names: Refactoring and cleanups Vadim Kochan
2014-12-06 2:05 ` [PATCH iproute2 1/2] lib names: Use CONFDIR for specify 'group' file path Vadim Kochan
2014-12-06 2:05 ` [PATCH iproute2 2/2] lib names: Add helper func for parse id and name from file Vadim Kochan
2014-12-10 4:38 ` [PATCH iproute2 0/2] lib names: Refactoring and cleanups Stephen Hemminger
2014-12-10 15:10 ` vadim4j [this message]
2014-12-10 23:46 ` Stephen Hemminger
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=20141210151029.GA18451@angus-think.wlc.globallogic.com \
--to=vadim4j@gmail.com \
--cc=netdev@vger.kernel.org \
--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