From: Stephen Hemminger <shemming@brocade.com>
To: Phil Sutter <phil@nwl.cc>
Cc: <netdev@vger.kernel.org>
Subject: Re: [iproute PATCH v2 0/2] Two cosmetic fixes in tc/m_action.c
Date: Thu, 16 Jun 2016 09:42:59 -0700 [thread overview]
Message-ID: <20160616094259.5448aaf1@xeon-e3> (raw)
In-Reply-To: <1466031039-18411-1-git-send-email-phil@nwl.cc>
On Thu, 16 Jun 2016 00:50:37 +0200
Phil Sutter <phil@nwl.cc> wrote:
> Found these when doing something else. Shouldn't cause any functional
> change.
>
> Changes since v1:
> - Replace patch 1/2 with a better solution as suggested by Stephen
> Hemminger.
>
> Phil Sutter (2):
> tc: m_action: Use C99 style initializers for struct req
> tc: m_action: Drop unused variable nladdr in tc_action_gd()
>
> tc/m_action.c | 50 +++++++++++++++++++++++---------------------------
> 1 file changed, 23 insertions(+), 27 deletions(-)
>
Applied
prev parent reply other threads:[~2016-06-16 16:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 22:50 [iproute PATCH v2 0/2] Two cosmetic fixes in tc/m_action.c Phil Sutter
2016-06-15 22:50 ` [iproute PATCH v2 1/2] tc: m_action: Use C99 style initializers for struct req Phil Sutter
2016-06-15 22:50 ` [iproute PATCH v2 2/2] tc: m_action: Drop unused variable nladdr in tc_action_gd() Phil Sutter
2016-06-16 16:42 ` 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=20160616094259.5448aaf1@xeon-e3 \
--to=shemming@brocade.com \
--cc=netdev@vger.kernel.org \
--cc=phil@nwl.cc \
/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).