From: Krzysztof Opasiak <k.opasiak@samsung.com>
To: balbi@ti.com
Cc: 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 18:58:13 +0200 [thread overview]
Message-ID: <560188A5.9010201@samsung.com> (raw)
In-Reply-To: <20150922165324.GA7094@saruman.tx.rr.com>
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.
Best regards,
--
Krzysztof Opasiak
Samsung R&D Institute Poland
Samsung Electronics
next prev parent reply other threads:[~2015-09-22 16:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-22 16:39 [PATCH 1/2] usb: gadget: loopback: fix: Don't share qlen and buflen between instances 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 [this message]
2015-09-22 17:23 ` Felipe Balbi
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=560188A5.9010201@samsung.com \
--to=k.opasiak@samsung.com \
--cc=andrzej.p@samsung.com \
--cc=balbi@ti.com \
--cc=gregkh@linuxfoundation.org \
--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 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.