From: David Miller <davem@davemloft.net>
To: wferi@niif.hu
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 0/2] Re: spurious netconsole: network logging stopped messages
Date: Thu, 06 Jan 2011 11:30:46 -0800 (PST) [thread overview]
Message-ID: <20110106.113046.246528563.davem@davemloft.net> (raw)
In-Reply-To: <cover.1294326001.git.wferi@niif.hu>
From: Ferenc Wagner <wferi@niif.hu>
Date: Thu, 6 Jan 2011 16:11:18 +0100
> Hi,
>
> I've been running with these two patches for a couple of days now.
> I don't understand the bridge case: why should netconsole stop logging
> on a bridge device which lost a slave? Or does NETDEV_BONDING_DESLAVE
> mean something else?
>
> Anyway, I think the first patch fixes a real bug and the second makes
> the kernel message clearer, independently of its cause.
Both applied, thank you.
prev parent reply other threads:[~2011-01-06 19:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-03 16:57 spurious netconsole: network logging stopped messages Ferenc Wagner
2011-01-06 15:11 ` [PATCH 0/2] " Ferenc Wagner
2011-01-06 15:11 ` [PATCH 1/2] netconsole: don't announce stopping if nothing happened Ferenc Wagner
2011-01-06 15:11 ` [PATCH 2/2] netconsole: clarify stopping message Ferenc Wagner
2011-01-06 19:30 ` 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=20110106.113046.246528563.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=wferi@niif.hu \
/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).