netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: xemul@openvz.org
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 2/2][BRIDGE]: Consolidate error paths in br_add_bridge().
Date: Sun, 04 May 2008 17:58:16 -0700 (PDT)	[thread overview]
Message-ID: <20080504.175816.31670485.davem@davemloft.net> (raw)
In-Reply-To: <481D5C71.9000005@openvz.org>

From: Pavel Emelyanov <xemul@openvz.org>
Date: Sun, 04 May 2008 10:49:21 +0400

> This actually had to be merged with the patch #1, but I decided
> not to mix two changes in one patch.
> 
> There are already two calls to free_netdev() in there, so merge
> them into one.
> 
> Signed-off-by: Pavel Emelyanov <xemul@openvz.org>

Looks good, applied.

      reply	other threads:[~2008-05-05  0:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-04  6:49 [PATCH 2/2][BRIDGE]: Consolidate error paths in br_add_bridge() Pavel Emelyanov
2008-05-05  0:58 ` 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=20080504.175816.31670485.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=xemul@openvz.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).