From: Felipe Balbi <balbi@ti.com>
To: Krzysztof Opasiak <k.opasiak@samsung.com>
Cc: <balbi@ti.com>, <gregkh@linuxfoundation.org>,
<linux-kernel@vger.kernel.org>, <andrzej.p@samsung.com>,
<stable@vger.kernel.org>
Subject: Re: [PATCH 1/2] usb: gadget: loopback: fix: Don't share qlen and buflen between instances
Date: Tue, 22 Sep 2015 12:23:02 -0500 [thread overview]
Message-ID: <20150922172302.GB7094@saruman.tx.rr.com> (raw)
In-Reply-To: <560188A5.9010201@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 961 bytes --]
On Tue, Sep 22, 2015 at 06:58:13PM +0200, Krzysztof Opasiak wrote:
>
>
> On 09/22/2015 06:53 PM, Felipe Balbi wrote:
> >On Tue, Sep 22, 2015 at 06:39:26PM +0200, Krzysztof Opasiak wrote:
> >>Each instance of loopback function may have different qlen
> >>and buflen attributes values. When linking function to
> >>configuration those values had been assigned to global
> >>variables. Linking other instance to config overwrites those
> >>values.
> >>
> >>This commit moves those values to f_loopback structure
> >>to avoid overwriting. Now each function has its own instance
> >>of those values.
> >>
> >>Cc: <stable@vger.kernel.org> # 3.10+
> >>Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>
> >
> >looks like you missed linux-usb on both patches. Care to resend ?
> >
>
> Sorry, just send v2 without reading your email because I have found some mem
> leak. I will resend v2 with cc to linux-usb.
Thanks :-)
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-09-22 17:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-22 16:39 Krzysztof Opasiak
2015-09-22 16:39 ` [PATCH 2/2] usb: gadget: loopback: Fix looping back logic implementation Krzysztof Opasiak
2015-09-22 16:53 ` [PATCH 1/2] usb: gadget: loopback: fix: Don't share qlen and buflen between instances Felipe Balbi
2015-09-22 16:58 ` Krzysztof Opasiak
2015-09-22 17:23 ` Felipe Balbi [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=20150922172302.GB7094@saruman.tx.rr.com \
--to=balbi@ti.com \
--cc=andrzej.p@samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=k.opasiak@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®