From: Stephen Hemminger <stephen@networkplumber.org>
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: Alexander Aring <aring@mojatatu.com>,
yotamg@mellanox.com, xiyou.wangcong@gmail.com, jiri@resnulli.us,
netdev@vger.kernel.org
Subject: Re: [PATCH iproute2 2/4] tc: m_ife: print IEEE ethertype format
Date: Mon, 28 Aug 2017 15:37:34 -0700 [thread overview]
Message-ID: <20170828153734.4b32fa02@xeon-e3> (raw)
In-Reply-To: <ff74308c-2fe9-7c73-6215-8a269ea1be5e@mojatatu.com>
On Mon, 28 Aug 2017 18:18:04 -0400
Jamal Hadi Salim <jhs@mojatatu.com> wrote:
> Alex,
>
> I think we should get rid of these fprintfs instead of fixing them.
> They were originally intended to be debug outputs.
>
> cheers,
> jamal
>
> On 17-08-28 03:07 PM, Alexander Aring wrote:
> > This patch uses the usually IEEE format to display an ethertype which is
> > 4-digits and every digit in upper case.
> >
> > Signed-off-by: Alexander Aring <aring@mojatatu.com>
> > ---
> > tc/m_ife.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/tc/m_ife.c b/tc/m_ife.c
> > index e05e2276..7b57130e 100644
> > --- a/tc/m_ife.c
> > +++ b/tc/m_ife.c
> > @@ -125,7 +125,7 @@ static int parse_ife(struct action_util *a, int *argc_p, char ***argv_p,
> > NEXT_ARG();
> > if (get_u16(&ife_type, *argv, 0))
> > invarg("ife type is invalid", *argv);
> > - fprintf(stderr, "IFE type 0x%x\n", ife_type);
> > + fprintf(stderr, "IFE type 0x%04X\n", ife_type);
> > user_type = 1;
> > } else if (matches(*argv, "dst") == 0) {
> > NEXT_ARG();
> >
>
For iproute commands the show output is supposed to match the corresponding set inputs.
next prev parent reply other threads:[~2017-08-28 22:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 19:07 [PATCH iproute2 0/4] tc: m_ife: handle IFE ethertype value Alexander Aring
2017-08-28 19:07 ` [PATCH iproute2 1/4] tc: m_ife: allow ife type to zero Alexander Aring
2017-08-28 19:34 ` Stephen Hemminger
2017-08-28 22:16 ` Jamal Hadi Salim
2017-08-28 19:07 ` [PATCH iproute2 2/4] tc: m_ife: print IEEE ethertype format Alexander Aring
2017-08-28 19:33 ` Stephen Hemminger
2017-08-28 22:18 ` Jamal Hadi Salim
2017-08-28 22:37 ` Stephen Hemminger [this message]
2017-08-28 22:56 ` Jamal Hadi Salim
2017-08-28 19:07 ` [PATCH iproute2 3/4] tc: m_ife: report about kernels default type Alexander Aring
2017-08-28 22:18 ` Jamal Hadi Salim
2017-08-28 19:07 ` [PATCH iproute2 4/4] man: tc-ife: add default type note Alexander Aring
2017-08-28 22:19 ` Jamal Hadi Salim
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=20170828153734.4b32fa02@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=aring@mojatatu.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=xiyou.wangcong@gmail.com \
--cc=yotamg@mellanox.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 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).