From: Alexander Aring <alex.aring@gmail.com>
To: Trond.Myklebust@netapp.com
Cc: linux-nfs@vger.kernel.org, netdev@vger.kernel.org,
werner@almesberger.net
Subject: Re: [PATCH] nfs: fix dead code of ipv6_addr_scope
Date: Sat, 21 Dec 2013 09:17:07 +0100 [thread overview]
Message-ID: <20131221081706.GA11689@omega> (raw)
In-Reply-To: <1387600744-11366-1-git-send-email-alex.aring@gmail.com>
Hi,
I saw right now file "./net/sctp/ipv6.c" in function sctp_v6_scope has
the same issue.
- Alex
next prev parent reply other threads:[~2013-12-21 8:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-21 4:39 [PATCH] nfs: fix dead code of ipv6_addr_scope Alexander Aring
2013-12-21 8:17 ` Alexander Aring [this message]
[not found] ` <1387600744-11366-1-git-send-email-alex.aring-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-12-21 12:44 ` Hannes Frederic Sowa
[not found] ` <20131221124440.GG14073-5j1vdhnGyZutBveJljeh2VPnkB77EeZ12LY78lusg7I@public.gmane.org>
2013-12-21 13:32 ` Alexander Aring
2013-12-22 2:30 ` Hannes Frederic Sowa
[not found] ` <20131222023054.GH14073-5j1vdhnGyZutBveJljeh2VPnkB77EeZ12LY78lusg7I@public.gmane.org>
2013-12-22 12:30 ` Alexander Aring
2013-12-22 12:38 ` Hannes Frederic Sowa
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=20131221081706.GA11689@omega \
--to=alex.aring@gmail.com \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=werner@almesberger.net \
/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).