From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Oliver Freyermuth <o.freyermuth@googlemail.com>
Cc: "Linux Media Mailing List" <linux-media@vger.kernel.org>,
"Mauro Carvalho Chehab" <mchehab@infradead.org>,
"Stefan Brüns" <stefan.bruens@rwth-aachen.de>
Subject: Re: [PATCH RESEND] Revert "media: dvbsky: use just one mutex for serializing device R/W ops"
Date: Fri, 5 Oct 2018 12:30:37 -0300 [thread overview]
Message-ID: <20181005123037.64b9f24c@coco.lan> (raw)
In-Reply-To: <4333a303-c06b-e641-20de-7b51058e0287@googlemail.com>
Em Fri, 5 Oct 2018 16:34:28 +0200
Oliver Freyermuth <o.freyermuth@googlemail.com> escreveu:
> Dear Mauro,
>
> thanks! Just to clarify, the issue I described in https://bugzilla.kernel.org/show_bug.cgi?id=199323
> was on an Intel x86_64 system, with an onboard USB Controller handled by the standard xhci driver,
> so this does not affect RPi alone.
That's weird... I tested such patch here before applying (and it was
tested by someone else, as far as I know), and it worked fine.
Perhaps the x86 bug is related to some recent changes at the USB
subsystem. Dunno.
Anyway, patch revert applied upstream.
Regards,
Mauro
next prev parent reply other threads:[~2018-10-05 22:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-24 20:26 DVBSky S960CI hard broken in 4.18 Oliver Freyermuth
2018-09-30 16:16 ` [Regression] " Oliver Freyermuth
2018-10-05 14:25 ` [PATCH] Revert "media: dvbsky: use just one mutex for serializing device R/W ops" Mauro Carvalho Chehab
2018-10-05 14:25 ` Mauro Carvalho Chehab
2018-10-05 14:26 ` [PATCH RESEND] " Mauro Carvalho Chehab
2018-10-05 14:26 ` Mauro Carvalho Chehab
2018-10-05 14:34 ` Oliver Freyermuth
2018-10-05 15:30 ` Mauro Carvalho Chehab [this message]
2018-10-13 10:37 ` Lars Buerding
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=20181005123037.64b9f24c@coco.lan \
--to=mchehab+samsung@kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=o.freyermuth@googlemail.com \
--cc=stefan.bruens@rwth-aachen.de \
/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.