Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bowers, AndrewX <andrewx.bowers@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH v3 net-next 2/7] ipeh: Move generic EH functions to exthdrs_common.c
Date: Thu, 22 Aug 2019 17:13:54 +0000	[thread overview]
Message-ID: <faa4b599286e4a76898078e59fa42af5@intel.com> (raw)
In-Reply-To: <1566254665-5200-3-git-send-email-tom@herbertland.com>

> -----Original Message-----
> From: Intel-wired-lan [mailto:intel-wired-lan-bounces at osuosl.org] On
> Behalf Of Tom Herbert
> Sent: Monday, August 19, 2019 3:44 PM
> To: Intel-wired-lan at lists.osuosl.org
> Cc: Tom Herbert <tom@herbertland.com>; Tom Herbert
> <tom@quantonium.net>
> Subject: [Intel-wired-lan] [PATCH v3 net-next 2/7] ipeh: Move generic EH
> functions to exthdrs_common.c
> 
> From: Tom Herbert <tom@quantonium.net>
> 
> Move generic functions in exthdrs.c to new exthdrs_common.c so that
> exthdrs.c only contains functions that are specific to IPv6 processing, and
> exthdrs_common.c contains functions that are generic. These functions
> include those that will be used with IPv4 extension headers.
> Generic extension header related functions are prefixed by ipeh_.
> 
> Fix kbuild issue.
> 
> Reported-by: kbuild test robot <lkp@intel.com>
> Signed-off-by: Tom Herbert <tom@herbertland.com>
> ---
>  include/net/ipeh.h        |  12 ++++
>  include/net/ipv6.h        |   9 ---
>  net/dccp/ipv6.c           |   2 +-
>  net/ipv6/Kconfig          |   4 ++
>  net/ipv6/Makefile         |   1 +
>  net/ipv6/calipso.c        |   6 +-
>  net/ipv6/exthdrs.c        | 138 --------------------------------------------
>  net/ipv6/exthdrs_common.c | 144
> ++++++++++++++++++++++++++++++++++++++++++++++
>  net/ipv6/ipv6_sockglue.c  |   2 +-
>  net/ipv6/raw.c            |   2 +-
>  net/ipv6/tcp_ipv6.c       |   2 +-
>  net/ipv6/udp.c            |   2 +-
>  net/l2tp/l2tp_ip6.c       |   2 +-
>  net/sctp/ipv6.c           |   2 +-
>  14 files changed, 171 insertions(+), 157 deletions(-)  create mode 100644
> net/ipv6/exthdrs_common.c

Tested-by: Andrew Bowers <andrewx.bowers@intel.com>



  reply	other threads:[~2019-08-22 17:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-19 22:44 [Intel-wired-lan] [PATCH v3 net-next 0/7] ipv6: Extension header infrastructure Tom Herbert
2019-08-19 22:44 ` [Intel-wired-lan] [PATCH v3 net-next 1/7] ipeh: Create exthdrs_options.c and ipeh.h Tom Herbert
2019-08-22 17:13   ` Bowers, AndrewX
2019-08-19 22:44 ` [Intel-wired-lan] [PATCH v3 net-next 2/7] ipeh: Move generic EH functions to exthdrs_common.c Tom Herbert
2019-08-22 17:13   ` Bowers, AndrewX [this message]
2019-08-19 22:44 ` [Intel-wired-lan] [PATCH v3 net-next 3/7] ipeh: Generic TLV parser Tom Herbert
2019-08-22 17:17   ` Bowers, AndrewX
2019-08-19 22:44 ` [Intel-wired-lan] [PATCH v3 net-next 4/7] ip6tlvs: Registration of TLV handlers and parameters Tom Herbert
2019-08-22 17:17   ` Bowers, AndrewX
2019-08-19 22:44 ` [Intel-wired-lan] [PATCH v3 net-next 5/7] ip6tlvs: Add TX parameters Tom Herbert
2019-08-22 17:18   ` Bowers, AndrewX
2019-08-19 22:44 ` [Intel-wired-lan] [PATCH v3 net-next 6/7] ip6tlvs: Add netlink interface Tom Herbert
2019-08-22 17:18   ` Bowers, AndrewX
2019-08-19 22:44 ` [Intel-wired-lan] [PATCH v3 net-next 7/7] ip6tlvs: Validation of TX Destination and Hop-by-Hop options Tom Herbert
2019-08-22 17:19   ` Bowers, AndrewX

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=faa4b599286e4a76898078e59fa42af5@intel.com \
    --to=andrewx.bowers@intel.com \
    --cc=intel-wired-lan@osuosl.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