From: Andrzej Pietrasiewicz <andrzej.p@samsung.com>
To: John Stultz <john.stultz@linaro.org>, Al Viro <viro@zeniv.linux.org.uk>
Cc: Felipe Balbi <balbi@ti.com>,
Krzysztof Opasiak <k.opasiak@samsung.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Michal Nazarewicz <mina86@mina86.com>,
Robert Baldyga <r.baldyga@samsung.com>,
lkml <linux-kernel@vger.kernel.org>,
linux-usb@vger.kernel.org
Subject: Re: Locking issues w/ functionfs gadget and aio?
Date: Wed, 01 Jul 2015 11:59:51 +0200 [thread overview]
Message-ID: <5593BA17.9020400@samsung.com> (raw)
In-Reply-To: <CALAqxLWnprYpkP8xUOk=ACboyze9CEHcok+RCrUktUm1wfbGpw@mail.gmail.com>
W dniu 22.06.2015 o 19:20, John Stultz pisze:
> On Sat, Jun 20, 2015 at 10:24 PM, Al Viro <viro@zeniv.linux.org.uk> wrote:
>> On Fri, Jun 12, 2015 at 05:51:12PM -0700, John Stultz wrote:
>>
>>> I'm not super sure what the right fix is, but if do something like the
>>> following (sorry, whitespace corrupted via copy/paste), I don't seem
>>> to run into the problem.
>>
>> Looks sane. Which tree would you prefer it to go through, vfs or usb?
>> BTW, in either case you'd need Signed-off-by: on that patch...
>
> Heh. I assumed my hack would be the wrong thing, but if there's no
> better suggestion, I'm happy to submit it.
>
> I have no strong preference of which tree it goes through, but I'd
> like for Andrzej to weigh in to make sure he agrees.
>
I have no preference of which tree it goes through either.
As far as the changes themselves are concerned, they have
been reviewed by Robert, whose desk is next to mine and
I trust his opinion.
Thanks,
AP
prev parent reply other threads:[~2015-07-01 10:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-09 1:14 Locking issues w/ functionfs gadget and aio? John Stultz
2015-06-13 0:51 ` John Stultz
2015-06-21 5:24 ` Al Viro
2015-06-22 17:20 ` John Stultz
2015-07-01 9:59 ` Andrzej Pietrasiewicz [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=5593BA17.9020400@samsung.com \
--to=andrzej.p@samsung.com \
--cc=balbi@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=john.stultz@linaro.org \
--cc=k.opasiak@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mina86@mina86.com \
--cc=r.baldyga@samsung.com \
--cc=viro@zeniv.linux.org.uk \
/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