From: David Miller <davem@davemloft.net>
To: wg@grandegger.com
Cc: netdev@vger.kernel.org, Socketcan-core@lists.berlios.de,
kurt.van.dijck@eia.be
Subject: Re: [PATCH] can: sja1000: fix bug using library functions for skb allocation
Date: Mon, 26 Oct 2009 17:34:06 -0700 (PDT) [thread overview]
Message-ID: <20091026.173406.101747247.davem@davemloft.net> (raw)
In-Reply-To: <4AE5C444.9030804@grandegger.com>
From: Wolfgang Grandegger <wg@grandegger.com>
Date: Mon, 26 Oct 2009 16:46:12 +0100
> Commit 7b6856a0 "can: provide library functions for skb allocation"
> did not properly remove two lines of the SJA1000 driver resulting in
> a 'skb_over_panic' when calling skb_put, as reported by Kurt.
>
> Signed-off-by: Kurt Van Dijck <kurt.van.dijck@eia.be>
> Signed-off-by: Wolfgang Grandegger <wg@grandegger.com>
Applied, thanks.
prev parent reply other threads:[~2009-10-27 0:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 15:46 [PATCH] can: sja1000: fix bug using library functions for skb allocation Wolfgang Grandegger
2009-10-27 0:34 ` 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=20091026.173406.101747247.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Socketcan-core@lists.berlios.de \
--cc=kurt.van.dijck@eia.be \
--cc=netdev@vger.kernel.org \
--cc=wg@grandegger.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).