From: Daniel Vetter <daniel@ffwll.ch>
To: "Stefan Brüns" <stefan.bruens@rwth-aachen.de>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 3/6] drm/edid: new drm_edid_block_checksum helper function V3
Date: Mon, 1 Dec 2014 17:21:25 +0100 [thread overview]
Message-ID: <20141201162125.GY32117@phenom.ffwll.local> (raw)
In-Reply-To: <d5291eb6-37ab-4038-96f9-707a79b9b96b@HUB1.rwth-ad.de>
On Sun, Nov 30, 2014 at 07:57:43PM +0100, Stefan Brüns wrote:
> The function will also be used by a later patch, so factor it out.
>
> V2: make raw_edid const, define/declare before first use
> V3: fix erroneuos removal of csum variable
>
> Signed-off-by: Stefan Brüns <stefan.bruens@rwth-aachen.de>
> Reviewed-by: Jani Nikula <jani.nikula@intel.com>
Ok, merged the first three patches from this series to my drm patch pile
branch. I'll send a pull for that to Dave for 3.19 I think, but might miss
for 3.20.
Thanks, Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-12-01 16:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1417373866-15440-1-git-send-email-stefan.bruens@rwth-aachen.de>
2014-11-30 18:57 ` [PATCH 1/6] drm/edid: move drm_edid_is_zero to top, make edid argument const Stefan Brüns
2014-11-30 18:57 ` [PATCH 2/6] drm/edid: shorten log output in case of all zeroes edid block Stefan Brüns
2014-11-30 18:57 ` [PATCH 3/6] drm/edid: new drm_edid_block_checksum helper function V3 Stefan Brüns
2014-12-01 16:21 ` Daniel Vetter [this message]
2014-11-30 18:57 ` [PATCH 4/6] drm/edid: calculate address of current extension block only once Stefan Brüns
2014-11-30 18:57 ` [PATCH 5/6] drm/edid: add drm_edid_dump helper function Stefan Brüns
2014-11-30 18:57 ` [PATCH 6/6] drm/edid: Tighten checksum conditions for CEA blocks Stefan Brüns
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=20141201162125.GY32117@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox