From: Marc Kleine-Budde <mkl@pengutronix.de>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, linux-can@vger.kernel.org, kernel@pengutronix.de
Subject: pull-request: can 2013-12-17
Date: Tue, 17 Dec 2013 11:44:47 +0100 [thread overview]
Message-ID: <1387277089-25554-1-git-send-email-mkl@pengutronix.de> (raw)
Hello David,
this is a pull request with two fixes for net/master, the current release
cycle.
It consists of a patch by Alexey Khoroshilov from the Linux Driver Verification
project, which fixes a memory leak in ems_usb's failure patch. And a patch by
me which fixes a memory leak in the peak usb driver.
regards,
Marc
---
The following changes since commit 9bd7d20c45157c175bfd45449e904a404506f99c:
sctp: loading sctp when load sctp_probe (2013-12-16 20:04:27 -0500)
are available in the git repository at:
git://gitorious.org/linux-can/linux-can.git fixes-for-3.13
for you to fetch changes up to 20fb4eb96fb0350d28fc4d7cbfd5506711079592:
can: peak_usb: fix mem leak in pcan_usb_pro_init() (2013-12-17 11:19:33 +0100)
----------------------------------------------------------------
Alexey Khoroshilov (1):
can: ems_usb: fix urb leaks on failure paths
Marc Kleine-Budde (1):
can: peak_usb: fix mem leak in pcan_usb_pro_init()
drivers/net/can/usb/ems_usb.c | 3 ++-
drivers/net/can/usb/peak_usb/pcan_usb_pro.c | 3 +++
2 files changed, 5 insertions(+), 1 deletion(-)
next reply other threads:[~2013-12-17 10:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 10:44 Marc Kleine-Budde [this message]
2013-12-17 10:44 ` [PATCH 1/2] can: ems_usb: fix urb leaks on failure paths Marc Kleine-Budde
2013-12-17 10:44 ` [PATCH 2/2] can: peak_usb: fix mem leak in pcan_usb_pro_init() Marc Kleine-Budde
2013-12-17 22:22 ` pull-request: can 2013-12-17 David Miller
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=1387277089-25554-1-git-send-email-mkl@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=davem@davemloft.net \
--cc=kernel@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--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).