All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: netdev@vger.kernel.org
Subject: Re: [net-next:master 35/53] net/ipv6/route.c:400:13: sparse: invalid assignment: ^=
Date: Tue, 23 Oct 2012 10:58:10 +0200	[thread overview]
Message-ID: <50865C22.1090503@6wind.com> (raw)
In-Reply-To: <508653b5.7Vy7DCd02KcUpUab%fengguang.wu@intel.com>

Le 23/10/2012 10:22, Fengguang Wu a écrit :
> Hi Nicolas,
>
> FYI, there are new sparse warnings show up in
>
> tree:   git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git master
> head:   598e74f32c6dd4b3dd0ed382c889be07a7c6cbc0
> commit: 51ebd3181572af8d5076808dab2682d800f6da5d [35/53] ipv6: add support of equal cost multipath (ECMP)
Right, I will send a patch.


Thank you,
Nicolas

  reply	other threads:[~2012-10-23  8:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-23  8:22 [net-next:master 35/53] net/ipv6/route.c:400:13: sparse: invalid assignment: ^= Fengguang Wu
2012-10-23  8:58 ` Nicolas Dichtel [this message]
2012-10-23  9:35 ` [PATCH net-next] ipv6: fix sparse warnings in rt6_info_hash_nhsfn() Nicolas Dichtel
2012-10-23 17:06   ` David Miller

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=50865C22.1090503@6wind.com \
    --to=nicolas.dichtel@6wind.com \
    --cc=fengguang.wu@intel.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.