From: Mark Salyzyn <salyzyn@android.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, kernel-team@android.com, "Yavuz,
Tuba" <tuba@ece.ufl.edu>,
Felipe Balbi <felipe.balbi@linux.intel.com>,
stable <stable@vger.kernel.org>, Felipe Balbi <balbi@ti.com>,
linux-usb@vger.kernel.org
Subject: Re: USB: gadget: f_midi: fixing a possible double-free in f_midi
Date: Tue, 20 Aug 2019 14:13:51 -0700 [thread overview]
Message-ID: <c96a0121-eb12-9449-44eb-0d2e09ccef92@android.com> (raw)
In-Reply-To: <20190820201515.GA20068@kroah.com>
On 8/20/19 1:15 PM, Greg Kroah-Hartman wrote:
> No signed-off-by from you?
>
> Anyway, this is already in the 4.4.y queue and will be in the next
> release.
>
> thanks,
>
> greg k-h
Ok, thanks! I will stand down.
-- Mark
prev parent reply other threads:[~2019-08-20 21:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 17:45 USB: gadget: f_midi: fixing a possible double-free in f_midi Mark Salyzyn
2019-08-20 20:15 ` Greg Kroah-Hartman
2019-08-20 21:13 ` Mark Salyzyn [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=c96a0121-eb12-9449-44eb-0d2e09ccef92@android.com \
--to=salyzyn@android.com \
--cc=balbi@ti.com \
--cc=felipe.balbi@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tuba@ece.ufl.edu \
/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