From: Greg KH <gregkh@linuxfoundation.org>
To: "Samuel Iglesias Gonsálvez" <siglesias@igalia.com>
Cc: Lv Yunlong <lyl2019@mail.ustc.edu.cn>,
jens.taprogge@taprogge.org,
industrypack-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ipack/carriers/tpci200: Fix a double free in tpci200_pci_probe
Date: Thu, 27 May 2021 14:39:05 +0200 [thread overview]
Message-ID: <YK+S6agat0rGUNI9@kroah.com> (raw)
In-Reply-To: <c00938c1e634340663e145b51c5989bd4a20f326.camel@igalia.com>
On Wed, May 26, 2021 at 12:04:28PM +0200, Samuel Iglesias Gonsálvez wrote:
> Hi Lv,
>
> Thanks for the patch!
>
> Patch is,
>
> Acked-by: Samuel Iglesias Gonsalvez <siglesias@igalia.com>
>
> Greg, Would you mind picking this patch series through your char-misc
> tree?
Sure, will do.
prev parent reply other threads:[~2021-05-27 12:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 9:32 [PATCH] ipack/carriers/tpci200: Fix a double free in tpci200_pci_probe Lv Yunlong
2021-05-26 10:04 ` Samuel Iglesias Gonsálvez
2021-05-27 12:39 ` Greg KH [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=YK+S6agat0rGUNI9@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=industrypack-devel@lists.sourceforge.net \
--cc=jens.taprogge@taprogge.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lyl2019@mail.ustc.edu.cn \
--cc=siglesias@igalia.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).