dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Pilcher <arequipeno@gmail.com>
To: Paul Menzel <paulepanter@users.sourceforge.net>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm: EDID quirk improvements
Date: Sat, 11 Aug 2012 10:38:15 -0500	[thread overview]
Message-ID: <50267C67.6080007@gmail.com> (raw)
In-Reply-To: <1344673899.5674.11.camel@mattotaupa>

On 08/11/2012 03:31 AM, Paul Menzel wrote:
> As a side note, could you also mention the patch iteration in the tag,
> that means [PATCH vN] so that I know what is the latest version. That
> would be great.

Can you (or anyone else reading this) point me to how to do this with
git send-email?

> I would submit adding the new quirk flags and the LG quirk as separate
> patches. If it is not too much work, it would be great if you could
> split them up.

Does git provide any facility to make this easier?  As far as I can
tell, the process is to start over with a newly cloned repository,
apply the current patch, manually back out the changes that I want to
separate, commit, manually redo the separate changes, and commit
again.  Is that correct?

> You even added this one from the following commit.
> 
>         commit bc42aabc6a01b92b0f961d65671564e0e1cd7592
>         Author: Adam Jackson <ajax@redhat.com>
>         Date:   Wed May 23 16:26:54 2012 -0400
>         
>             drm/edid/quirks: ViewSonic VA2026w
> 
> I am going to need that quirk. Great!

It's in Linus's tree.

>> +DEFINE_MUTEX(edid_quirk_list_mutex);
>> +
>> +/**
>> + * drm_edid_mfg_format - format an "encoded" EDID manufacturer ID for printing
>> + * @mfg_id: the encoded manufacturer ID
>> + * @buf: destination buffer for the formated manufacturer ID (minimum 7 bytes)
> 
> format*t*ed
> 
> http://www.merriam-webster.com/dictionary/formatted

Thanks for catching that.  I keep finding little typos like that; very
annoying.

>> +
>> +	return count;
>> +}
> 
> Add an empty line here before the next comment?
> 
>>  /*** DDC fetch and block validation ***/

I'm pretty sure I can manage that.  ;-)

>> +MODULE_PARM_DESC(edid_quirks, "See Documentation/EDID/edid_quirks.txt");
> 
> Not all users have access to the Linux source tree, so maybe a small
> overview is still needed? Or even an URL?

I can't think of a way to provide anything useful within the scope of a
parameter description.  Any suggestions?

A URL would be great, but what would it be?  (I don't have a personal
web site, and that doesn't seem really appropriate anyway.)

> Thanks again for that great patch. With the comments addressed above you
> can add my acknowledgment.
> 
> Acked-by: Paul Menzel <paulepanter@users.sourceforge.net>

Thank you for your feedback.

Are you saying that I should add the acked-by?  If so, how?  (You can
probably tell that I'm really struggling with git.)

> I am going to try to test that patch too for a Philips and LG TV [2].

I hope it helps.

-- 
========================================================================
Ian Pilcher                                         arequipeno@gmail.com
"If you're going to shift my paradigm ... at least buy me dinner first."
========================================================================

  reply	other threads:[~2012-08-11 15:38 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-19 19:16 Enhancing EDID quirk functionality Ian Pilcher
2012-04-24  9:07 ` Lars-Peter Clausen
2012-04-24 19:00   ` Ian Pilcher
2012-05-03 18:01     ` Ian Pilcher
2012-05-03 19:42       ` Adam Jackson
2012-05-07 19:50         ` Ian Pilcher
2012-05-07 21:38           ` Adam Jackson
2012-08-10  4:23             ` Ian Pilcher
2012-08-10  4:23               ` [PATCH] drm: EDID quirk improvements Ian Pilcher
2012-08-10 18:44                 ` Ian Pilcher
2012-08-10 18:44                   ` Ian Pilcher
2012-08-11  8:31                     ` Paul Menzel
2012-08-11 15:38                       ` Ian Pilcher [this message]
2012-08-11 19:52                         ` Paul Menzel
2012-08-11 19:37                     ` Paul Menzel
2012-08-12  4:30                       ` [PATCH v3 0/2] Enhanced EDID quirk functionality Ian Pilcher
2012-08-12  4:30                         ` [PATCH v3 1/2] drm: Add user-defined EDID quirks capability Ian Pilcher
2012-08-12 15:39                           ` Paul Menzel
2012-08-12  4:30                         ` [PATCH v3 2/2] drm: Add EDID quirks to disable HDMI audio and InfoFrames Ian Pilcher
2012-08-12 15:45                           ` Paul Menzel
2012-08-12  6:58                         ` [PATCH v3 0/2] Enhanced EDID quirk functionality Paul Menzel
2012-08-12 20:07                           ` [PATCH v4 0/3] " Ian Pilcher
2012-08-12 20:07                             ` [PATCH v4 1/3] drm: Add user-defined EDID quirks capability Ian Pilcher
2012-08-14 15:13                               ` Paul Menzel
2012-08-14 15:45                                 ` Ian Pilcher
2012-08-15  6:41                                   ` Paul Menzel
2012-08-12 20:07                             ` [PATCH v4 2/3] drm: Add EDID quirks to disable HDMI audio and InfoFrames Ian Pilcher
2012-08-12 20:08                             ` [PATCH v4 3/3] drm: Add EDID quirk for LG L246WP Ian Pilcher
2012-09-04 14:52                               ` Paul Menzel
2012-08-12 21:29                             ` [PATCH v4 0/3] Enhanced EDID quirk functionality Christian König
2012-08-12 21:31                             ` Paul Menzel
2012-08-13 14:39                               ` Ian Pilcher

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=50267C67.6080007@gmail.com \
    --to=arequipeno@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=paulepanter@users.sourceforge.net \
    /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