From: David Miller <davem@davemloft.net>
To: colin.king@canonical.com
Cc: kuznet@ms2.inr.ac.ru, yoshfuji@linux-ipv6.org,
netdev@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ipv6: use ARRAY_SIZE for array sizing calculation on array seg6_action_table
Date: Tue, 09 Jan 2018 11:41:10 -0500 (EST) [thread overview]
Message-ID: <20180109.114110.846074032577787600.davem@davemloft.net> (raw)
In-Reply-To: <20180107235026.8387-1-colin.king@canonical.com>
From: Colin King <colin.king@canonical.com>
Date: Sun, 7 Jan 2018 23:50:26 +0000
> From: Colin Ian King <colin.king@canonical.com>
>
> Use the ARRAY_SIZE macro on array seg6_action_table to determine size of
> the array. Improvement suggested by coccinelle.
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
Applied to net-next.
prev parent reply other threads:[~2018-01-09 16:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-07 23:50 [PATCH] ipv6: use ARRAY_SIZE for array sizing calculation on array seg6_action_table Colin King
2018-01-09 16:41 ` David Miller [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=20180109.114110.846074032577787600.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=colin.king@canonical.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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).