From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Kieran Bingham <kieran.bingham@ideasonboard.com>,
Mauro Carvalho Chehab <mchehab@s-opensource.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Edgar Thier <info@edgarthier.net>
Subject: Re: a 4.16 kernel with Debian 9.4 "stretch" causes a log explosion
Date: Wed, 25 Apr 2018 03:37:05 +0300 [thread overview]
Message-ID: <13495678.ygx19VKxpQ@avalon> (raw)
In-Reply-To: <alpine.DEB.2.20.1804112130030.25028@axis700.grange>
Hi Guennadi,
On Wednesday, 11 April 2018 22:33:43 EEST Guennadi Liakhovetski wrote:
> On Wed, 11 Apr 2018, Kieran Bingham wrote:
> > On 11/04/18 18:06, Guennadi Liakhovetski wrote:
> > <snip>
> >
> >>>>> Just figured out this commit
> >>>>>
> >>>>> From: Edgar Thier <info@edgarthier.net>
> >>>>> Date: Thu, 12 Oct 2017 03:54:17 -0400
> >>>>> Subject: [PATCH] media: uvcvideo: Apply flags from device to actual
> >>>>> properties
> >>>>>
> >>>>> as the culprit. Without it everything is back to normal.
> >>>>
> >>>> I've already investigated and fixed this:
> >>>>
> >>>> Please apply:
> >>>> https://patchwork.kernel.org/patch/10299735/
> >>
> >> Great, thanks! That seems to fix my problem.
> >
> > Fantastic. I'm glad it helped.
> >
> > - Can I call that a Tested-by: ? :-D
>
> Now you officially can - I replied to the patch.
Thank you. I've picked the tag and sent a pull request to Mauro.
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2018-04-25 0:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 9:56 a 4.16 kernel with Debian 9.4 "stretch" causes a log explosion Guennadi Liakhovetski
2018-04-11 16:17 ` Kieran Bingham
2018-04-11 16:21 ` Kieran Bingham
2018-04-11 17:06 ` Guennadi Liakhovetski
2018-04-11 18:15 ` Kieran Bingham
2018-04-11 19:33 ` Guennadi Liakhovetski
2018-04-25 0:37 ` Laurent Pinchart [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=13495678.ygx19VKxpQ@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=g.liakhovetski@gmx.de \
--cc=info@edgarthier.net \
--cc=kieran.bingham@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@s-opensource.com \
/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