From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH] video: udlfb: Fix read EDID timeout
Date: Thu, 09 Nov 2017 13:49:46 +0000 [thread overview]
Message-ID: <2766267.J9nXlqQIcI@amdc3058> (raw)
In-Reply-To: <20171102110216.fw4gqa6zkhsofl3o@lenoch>
On Thursday, November 02, 2017 12:02:16 PM Ladislav Michl wrote:
> While usb_control_msg function expects timeout in miliseconds, a value
> of HZ is used. Replace it with USB_CTRL_GET_TIMEOUT and also fix error
> message which looks like:
> udlfb: Read EDID byte 78 failed err ffffff92
> as error is either negative errno or number of bytes transferred use %d
> format specifier.
>
> Retuned EDID is in second byte, so return error when less than two bytes
> are received.
>
> Fixes: 18dffdf8913a ("staging: udlfb: enhance EDID and mode handling support")
>
> Signed-off-by: Ladislav Michl <ladis@linux-mips.org>
Patch queued for 4.15, thanks.
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics
prev parent reply other threads:[~2017-11-09 13:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 11:02 [PATCH] video: udlfb: Fix read EDID timeout Ladislav Michl
2017-11-09 13:49 ` Bartlomiej Zolnierkiewicz [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=2766267.J9nXlqQIcI@amdc3058 \
--to=b.zolnierkie@samsung.com \
--cc=linux-fbdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox