From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Daniel Axtens <dja@axtens.net>
Cc: Greg KH <greg@kroah.com>,
Dave Stevenson <linux-media@destevenson.freeserve.co.uk>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: uvcvideo logging kernel warnings on device disconnect
Date: Mon, 17 Apr 2017 15:57:35 +0300 [thread overview]
Message-ID: <1742096.L6mokpMOAb@avalon> (raw)
In-Reply-To: <87r30rv2ay.fsf@possimpible.ozlabs.ibm.com>
Hi Daniel,
On Monday 17 Apr 2017 18:57:57 Daniel Axtens wrote:
> Hi,
>
> >> > I hate to pester, but wondered if you had found anything obvious.
> >> > I really do appreciate you taking the time to look.
> >>
> >> Sorry, I haven't had the chance and now will not be able to until
> >> January....
> >
> > Did you mean January 2017 or 2018 ? :-)
>
> I stumbled across this problem independently, and with the help of some
> of the info on this thread (especially yavta), I have what I think is a
> solution: https://patchwork.kernel.org/patch/9683663/
Thank you for that !
I've reviewed your patch. Greg, there's a question for you in my reply, could
you have a look when you'll have time ?
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2017-04-17 12:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-08 12:31 uvcvideo logging kernel warnings on device disconnect Dave Stevenson
2016-12-08 23:09 ` Laurent Pinchart
2016-12-09 7:25 ` Greg KH
2016-12-09 8:59 ` Laurent Pinchart
2016-12-09 9:11 ` Greg KH
2016-12-09 9:14 ` Laurent Pinchart
2016-12-09 9:43 ` Greg KH
2016-12-20 11:19 ` Dave Stevenson
2016-12-21 9:59 ` Greg KH
2017-04-16 11:11 ` Laurent Pinchart
2017-04-17 8:57 ` Daniel Axtens
2017-04-17 12:57 ` Laurent Pinchart [this message]
2017-04-30 16:19 ` Greg KH
2017-04-30 16:20 ` Greg KH
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=1742096.L6mokpMOAb@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=dja@axtens.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@destevenson.freeserve.co.uk \
--cc=linux-media@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.