From: David Miller <davem@davemloft.net>
To: vinay.yadav@chelsio.com
Cc: netdev@vger.kernel.org, kuba@kernel.org, edumazet@google.com,
borisp@mellanox.com, secdev@chelsio.com
Subject: Re: [PATCH net-next] crypto/chtls: Fix compile error when CONFIG_IPV6 is disabled
Date: Wed, 03 Jun 2020 10:46:54 -0700 (PDT) [thread overview]
Message-ID: <20200603.104654.509090864511244400.davem@davemloft.net> (raw)
In-Reply-To: <20200603103317.653-1-vinay.yadav@chelsio.com>
From: Vinay Kumar Yadav <vinay.yadav@chelsio.com>
Date: Wed, 3 Jun 2020 16:03:17 +0530
> @@ -102,19 +100,24 @@ static struct net_device *chtls_find_netdev(struct chtls_dev *cdev,
> return ndev;
> ndev = ip_dev_find(&init_net, inet_sk(sk)->inet_rcv_saddr);
> break;
> +#if IS_ENABLED(CONFIG_IPV6)
> case PF_INET6:
> + struct net_device *temp;
> + int addr_type;
> +
You never, ever, compiled this code.
next prev parent reply other threads:[~2020-06-03 17:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 10:33 [PATCH net-next] crypto/chtls: Fix compile error when CONFIG_IPV6 is disabled Vinay Kumar Yadav
2020-06-03 13:03 ` kernel test robot
2020-06-03 14:11 ` kernel test robot
2020-06-03 17:46 ` David Miller [this message]
2020-06-04 3:28 ` kernel test robot
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=20200603.104654.509090864511244400.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=borisp@mellanox.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=secdev@chelsio.com \
--cc=vinay.yadav@chelsio.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).