netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: "Petr Písař" <ppisar@redhat.com>
Cc: <netdev@vger.kernel.org>
Subject: Re: [PATCH] iproute2: bridge: Close file with bridge monitor file
Date: Mon, 30 Sep 2013 21:11:06 -0700	[thread overview]
Message-ID: <20130930211106.6bccd8da@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <1380095145-6618-1-git-send-email-ppisar@redhat.com>

On Wed, 25 Sep 2013 09:45:45 +0200
Petr Písař <ppisar@redhat.com> wrote:

> The `bridge monitor file FILENAME' reads dumped netlink messages from
> a file. But it forgot to close the file after using it. This patch
> fixes it.
> 
> Signed-off-by: Petr Písař <ppisar@redhat.com>

Applied

      reply	other threads:[~2013-10-01  4:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-25  7:45 [PATCH] iproute2: bridge: Close file with bridge monitor file Petr Písař
2013-10-01  4:11 ` Stephen Hemminger [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=20130930211106.6bccd8da@nehalam.linuxnetplumber.net \
    --to=stephen@networkplumber.org \
    --cc=netdev@vger.kernel.org \
    --cc=ppisar@redhat.com \
    /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).