From: David Miller <davem@davemloft.net>
To: tlfalcon@linux.vnet.ibm.com
Cc: netdev@vger.kernel.org, mwb@linux.vnet.ibm.com
Subject: Re: [PATCH net 1/2] ibmvnic: Unmap ibmvnic_statistics structure
Date: Sun, 13 Nov 2016 13:42:46 -0500 (EST) [thread overview]
Message-ID: <20161113.134246.1757938406341670109.davem@davemloft.net> (raw)
In-Reply-To: <1478883646-10760-1-git-send-email-tlfalcon@linux.vnet.ibm.com>
From: Thomas Falcon <tlfalcon@linux.vnet.ibm.com>
Date: Fri, 11 Nov 2016 11:00:45 -0600
> This structure was mapped but never subsequently unmapped.
>
> Signed-off-by: Thomas Falcon <tlfalcon@linux.vnet.ibm.com>
Applied.
prev parent reply other threads:[~2016-11-13 18:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-11 17:00 [PATCH net 1/2] ibmvnic: Unmap ibmvnic_statistics structure Thomas Falcon
2016-11-11 17:00 ` [PATCH net 2/2] ibmvnic: Fix size of debugfs name buffer Thomas Falcon
2016-11-13 18:42 ` David Miller
2016-11-13 18:42 ` 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=20161113.134246.1757938406341670109.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=mwb@linux.vnet.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=tlfalcon@linux.vnet.ibm.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).