From: David Miller <davem@davemloft.net>
To: socketcan@hartkopp.net
Cc: mkl@pengutronix.de, netdev@vger.kernel.org
Subject: Re: [PATCH can-next] can: dump stack on protocol bugs
Date: Tue, 19 Mar 2013 09:55:58 -0400 (EDT) [thread overview]
Message-ID: <20130319.095558.766533338565579034.davem@davemloft.net> (raw)
In-Reply-To: <51475446.9000604@hartkopp.net>
From: Oliver Hartkopp <socketcan@hartkopp.net>
Date: Mon, 18 Mar 2013 18:52:06 +0100
> The rework of the kernel hlist implementation "hlist: drop the node parameter
> from iterators" (b67bfe0d42cac56c512dd5da4b1b347a23f4b70a) created some
> fallout in the form of non matching comments and obsolete code.
>
> Additionally to the cleanup this patch adds a WARN() statement to catch the
> caller of the wrong filter removal request.
>
> Signed-off-by: Oliver Hartkopp <socketcan@hartkopp.net>
Applied, thanks.
prev parent reply other threads:[~2013-03-19 13:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-18 17:52 [PATCH can-next] can: dump stack on protocol bugs Oliver Hartkopp
2013-03-19 13:55 ` 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=20130319.095558.766533338565579034.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=socketcan@hartkopp.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).