netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: David Miller <davem@davemloft.net>
Cc: den@openvz.org, netdev@vger.kernel.org, yoshfuji@linux-ipv6.org
Subject: Re: [PATCH]: Fix for recently introduced rawv6 bug.
Date: Thu, 12 Jun 2008 23:05:53 +0100	[thread overview]
Message-ID: <20080612220553.GJ28946@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20080612.144933.184241072.davem@davemloft.net>

On Thu, Jun 12, 2008 at 02:49:33PM -0700, David Miller wrote:
> 
> Al Viro noticed that we have two assignments to
> rawv6_prot.destroy, fix below with more details in
> the commit message.
> 
> I'll commit this to net-2.6 and push to Linus.

ACK.  Why does ->destroy() return int, BTW?  All in-tree instances return 0
and AFAICS there's nothing caller could possibly do in case of error anyway...

  reply	other threads:[~2008-06-12 22:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-12 21:49 [PATCH]: Fix for recently introduced rawv6 bug David Miller
2008-06-12 22:05 ` Al Viro [this message]
2008-06-12 22:23   ` David Miller
2008-06-12 23:17 ` YOSHIFUJI Hideaki / 吉藤英明

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=20080612220553.GJ28946@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=davem@davemloft.net \
    --cc=den@openvz.org \
    --cc=netdev@vger.kernel.org \
    --cc=yoshfuji@linux-ipv6.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).