netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: kumaran.4353@gmail.com
Cc: kuznet@ms2.inr.ac.ru, jmorris@namei.org, kaber@trash.net,
	netdev@vger.kernel.org
Subject: Re: [PATCH v2] net IPv6: Remove unnecessary argument of ndisc_send_ns and ndisc_send_na
Date: Mon, 14 Apr 2014 13:22:01 -0400 (EDT)	[thread overview]
Message-ID: <20140414.132201.372297856628816549.davem@davemloft.net> (raw)
In-Reply-To: <534B5EAB.9050803@gmail.com>

From: Balakumaran Kannan <kumaran.4353@gmail.com>
Date: Mon, 14 Apr 2014 09:36:03 +0530

> The 'neigh' argument of 'ndisc_send_ns' and 'ndisc_send_na' are not used in
> these functions. So this argument could be removed.
> 
> And a minor change of 'optlen' assignment in those functions. the compound
> addition and assignment operator is not needed as 'optlen' value is always
> zero.
> 
> Signed-off-by: Balakumaran Kannan <kumaran.4353@gmail.com>
> ---
> I am not sure whether 'neigh' argument is intentional or planned for any
> future use. If you find this is unnecessary, this patch could be considered.
> 
> And ndisc_send_na is used as a function pointer in ipv6_stub. This may affect
> anybody using this structure. But with default configuration built, I didn't
> get any error or warning. Kindly consider this scenario also.
> 
> Please ignore the previous patch as it doesn't have optlen modification in
> ndisc_send_na

I really don't like this change, and furthermore this breaks the build
as Hideaki YOSHIFUJI pointed out.  Drivers use the ipv6_stub methods and
you thus have to update all of the ones that use the ->ndisc_*().

      reply	other threads:[~2014-04-14 17:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-14  4:06 [PATCH v2] net IPv6: Remove unnecessary argument of ndisc_send_ns and ndisc_send_na Balakumaran Kannan
2014-04-14 17:22 ` 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=20140414.132201.372297856628816549.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=jmorris@namei.org \
    --cc=kaber@trash.net \
    --cc=kumaran.4353@gmail.com \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=netdev@vger.kernel.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).