From: Jens Axboe <axboe-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org>
To: Gabriel Krisman Bertazi
<krisman-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>,
tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org
Cc: cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
khazhy-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org,
kernel-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org
Subject: Re: [PATCH v2 0/2] Fixes to blkg_conf_prep
Date: Mon, 26 Oct 2020 07:58:09 -0600 [thread overview]
Message-ID: <73a3223b-2a92-49ae-e985-13399d8bf86e@kernel.dk> (raw)
In-Reply-To: <20201022205842.1739739-1-krisman-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
On 10/22/20 2:58 PM, Gabriel Krisman Bertazi wrote:
> Hi Tejun,
>
> In addition to addressing your comments the previously submitted fix to
> pre-allocate the radix node on blkg_conf_prep, this series fixes a small
> memleak on the same function.
Applied, thanks.
--
Jens Axboe
prev parent reply other threads:[~2020-10-26 13:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 20:58 [PATCH v2 0/2] Fixes to blkg_conf_prep Gabriel Krisman Bertazi
[not found] ` <20201022205842.1739739-1-krisman-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
2020-10-22 20:58 ` [PATCH v2 1/2] blk-cgroup: Fix memleak on error path Gabriel Krisman Bertazi
[not found] ` <20201022205842.1739739-2-krisman-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
2020-10-26 13:54 ` Tejun Heo
2020-10-22 20:58 ` [PATCH v2 2/2] blk-cgroup: Pre-allocate tree node on blkg_conf_prep Gabriel Krisman Bertazi
[not found] ` <20201022205842.1739739-3-krisman-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
2020-10-26 13:55 ` Tejun Heo
2020-10-26 13:58 ` Jens Axboe [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=73a3223b-2a92-49ae-e985-13399d8bf86e@kernel.dk \
--to=axboe-tswwg44o7x1aa/9udqfwiw@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=kernel-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org \
--cc=khazhy-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
--cc=krisman-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org \
--cc=tj-DgEjT+Ai2ygdnm+yROfE0A@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.