All of lore.kernel.org
 help / color / mirror / Atom feed
From: richardcochran@gmail.com (Richard Cochran)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH net-next 0/2] cpsw: fix resource leak for v3.8
Date: Sat,  3 Nov 2012 09:25:28 +0100	[thread overview]
Message-ID: <cover.1351930782.git.richardcochran@gmail.com> (raw)

While looking at the idea of removing all of the register offsets in
the CPSW's device tree, I noticed that the driver would be leaking IO
mappings. Although this is, strictly speaking, a bug fix, still it can
wait to appear in v3.8, since there is no way to use the driver in
v3.7 (or earlier) anyhow.

Thanks,
Richard


Richard Cochran (2):
  cpsw: rename register banks to match the reference manual, part 2
  cpsw: fix leaking IO mappings

 drivers/net/ethernet/ti/cpsw.c |   39 +++++++++++++++++++--------------------
 1 files changed, 19 insertions(+), 20 deletions(-)

-- 
1.7.2.5

WARNING: multiple messages have this Message-ID (diff)
From: Richard Cochran <richardcochran@gmail.com>
To: <netdev@vger.kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
	David Miller <davem@davemloft.net>,
	Cyril Chemparathy <cyril@ti.com>,
	Mugunthan V N <mugunthanvnm@ti.com>,
	Vaibhav Hiremath <hvaibhav@ti.com>
Subject: [PATCH net-next 0/2] cpsw: fix resource leak for v3.8
Date: Sat,  3 Nov 2012 09:25:28 +0100	[thread overview]
Message-ID: <cover.1351930782.git.richardcochran@gmail.com> (raw)

While looking at the idea of removing all of the register offsets in
the CPSW's device tree, I noticed that the driver would be leaking IO
mappings. Although this is, strictly speaking, a bug fix, still it can
wait to appear in v3.8, since there is no way to use the driver in
v3.7 (or earlier) anyhow.

Thanks,
Richard


Richard Cochran (2):
  cpsw: rename register banks to match the reference manual, part 2
  cpsw: fix leaking IO mappings

 drivers/net/ethernet/ti/cpsw.c |   39 +++++++++++++++++++--------------------
 1 files changed, 19 insertions(+), 20 deletions(-)

-- 
1.7.2.5

             reply	other threads:[~2012-11-03  8:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-03  8:25 Richard Cochran [this message]
2012-11-03  8:25 ` [PATCH net-next 0/2] cpsw: fix resource leak for v3.8 Richard Cochran
2012-11-03  8:25 ` [PATCH net-next 1/2] cpsw: rename register banks to match the reference manual, part 2 Richard Cochran
2012-11-03  8:25   ` Richard Cochran
2012-11-03  8:25 ` [PATCH net-next 2/2] cpsw: fix leaking IO mappings Richard Cochran
2012-11-03  8:25   ` Richard Cochran
2012-11-04 13:23   ` Cyril Chemparathy
2012-11-04 13:23     ` Cyril Chemparathy
2012-11-04 15:16     ` Richard Cochran
2012-11-04 15:16       ` Richard Cochran
2012-11-03 19:38 ` [PATCH net-next 0/2] cpsw: fix resource leak for v3.8 David Miller
2012-11-03 19:38   ` David Miller
2012-11-05  8:40 ` N, Mugunthan V
2012-11-05  8:40   ` N, Mugunthan V

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=cover.1351930782.git.richardcochran@gmail.com \
    --to=richardcochran@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.