All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH 1/4] video: add fb_edid_add_monspecs for parsing
Date: Mon, 01 Nov 2010 17:42:17 +0000	[thread overview]
Message-ID: <20101101104217.1eb8ff0b.akpm@linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1010281427240.1257@axis700.grange>

On Mon, 1 Nov 2010 16:57:00 +0100 (CET) Guennadi Liakhovetski <g.liakhovetski@gmx.de> wrote:

> Hi Andrew
> 
> On Thu, 28 Oct 2010, Andrew Morton wrote:
> 
> > On Thu, 28 Oct 2010 14:34:44 +0200 (CEST)
> > Guennadi Liakhovetski <g.liakhovetski@gmx.de> wrote:
> > 
> > > From: Erik Gilling <konkers@android.com>
> 
> Thanks for your comments. My plan is to add my S-o-b to this patch from 
> Erik, but otherwise leave it unchanged, because that's what the 2nd patch 
> in this series is for - for fixes and improvements. So, I'll address all 
> your comments in it, is this ok with you?
> 

Yes, that's OK.

It's unusual to do things this way - normally I'd just clump Erik's
patch and your changes to it into a single commit.  So we end up with
something which can be more effectively reviewed and a cleaner kernel
history.

But that's not a terribly important thing - if for some particular
reason you want to do it this way then that's OK by me.

      parent reply	other threads:[~2010-11-01 17:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-28 12:34 [PATCH 1/4] video: add fb_edid_add_monspecs for parsing extended Guennadi Liakhovetski
2010-10-28 23:17 ` [PATCH 1/4] video: add fb_edid_add_monspecs for parsing Andrew Morton
2010-10-28 23:23 ` Andrew Morton
2010-10-28 23:45 ` [PATCH 1/4] video: add fb_edid_add_monspecs for parsing extended edid information Paul Mundt
2010-11-01 15:57 ` [PATCH 1/4] video: add fb_edid_add_monspecs for parsing extended Guennadi Liakhovetski
2010-11-01 17:42 ` Andrew Morton [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=20101101104217.1eb8ff0b.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --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 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.