From: David Miller <davem@davemloft.net>
To: mkl@pengutronix.de
Cc: netdev@vger.kernel.org, linux-can@vger.kernel.org
Subject: Re: pull-request: can 2013-04-09
Date: Tue, 09 Apr 2013 13:25:24 -0400 (EDT) [thread overview]
Message-ID: <20130409.132524.1748863572087326219.davem@davemloft.net> (raw)
In-Reply-To: <1365495215-12081-1-git-send-email-mkl@pengutronix.de>
From: Marc Kleine-Budde <mkl@pengutronix.de>
Date: Tue, 9 Apr 2013 10:13:34 +0200
> here's a fix for the v3.9 release cycle, if not too late:
>
> Wei Yongjun contributes a patch for the can-gw protocoll. The patch fixes the
> memory allocated with kmem_cache_alloc(), is now freed using kmem_cache_free(),
> not kfree().
Pulled, thanks Marc.
prev parent reply other threads:[~2013-04-09 17:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 8:13 pull-request: can 2013-04-09 Marc Kleine-Budde
2013-04-09 8:13 ` [PATCH] can: gw: use kmem_cache_free() instead of kfree() Marc Kleine-Budde
2013-04-09 17:25 ` 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=20130409.132524.1748863572087326219.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.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).