From: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
To: miles.chen-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org,
Robin Murphy <robin.murphy-5wv7dgnIgG8@public.gmane.org>
Cc: wsd_upstream-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
Subject: Re: [PATCH] lib/dma-debug.c: fix memory leakage
Date: Fri, 23 Feb 2018 00:03:29 +0100 [thread overview]
Message-ID: <20180222230329.GA2820@lst.de> (raw)
In-Reply-To: <6df7e9bd-2203-0692-97e4-8c6434304b0f-5wv7dgnIgG8@public.gmane.org> <1519298540-3071-1-git-send-email-miles.chen-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
Thanks, applied to the dma mapping tree for 4.16, including the Fixes
tag.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: miles.chen@mediatek.com, Robin Murphy <robin.murphy@arm.com>
Cc: Christoph Hellwig <hch@lst.de>,
Marek Szyprowski <m.szyprowski@samsung.com>,
linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
linux-mediatek@lists.infradead.org, wsd_upstream@mediatek.com
Subject: Re: [PATCH] lib/dma-debug.c: fix memory leakage
Date: Fri, 23 Feb 2018 00:03:29 +0100 [thread overview]
Message-ID: <20180222230329.GA2820@lst.de> (raw)
In-Reply-To: <6df7e9bd-2203-0692-97e4-8c6434304b0f@arm.com> <1519298540-3071-1-git-send-email-miles.chen@mediatek.com>
Thanks, applied to the dma mapping tree for 4.16, including the Fixes
tag.
next prev parent reply other threads:[~2018-02-22 23:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 11:22 [PATCH] lib/dma-debug.c: fix memory leakage miles.chen-NuS5LvNUpcJWk0Htik3J/w
2018-02-22 11:22 ` miles.chen
[not found] ` <1519298540-3071-1-git-send-email-miles.chen-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2018-02-22 14:04 ` Robin Murphy
2018-02-22 14:04 ` Robin Murphy
2018-02-22 23:03 ` Christoph Hellwig [this message]
2018-02-22 23:03 ` Christoph Hellwig
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=20180222230329.GA2820@lst.de \
--to=hch-jcswghmuv9g@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=miles.chen-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org \
--cc=robin.murphy-5wv7dgnIgG8@public.gmane.org \
--cc=wsd_upstream-NuS5LvNUpcJWk0Htik3J/w@public.gmane.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.