All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Ball <cjb@laptop.org>
To: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
Cc: linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] viafb: kill lcd_panel_id
Date: Sun, 13 Mar 2011 16:07:42 +0000	[thread overview]
Message-ID: <m3hbb7xaup.fsf@pullcord.laptop.org> (raw)
In-Reply-To: <1299964979-3391-2-git-send-email-FlorianSchandinat@gmx.de> (Florian Tobias Schandinat's message of "Sat, 12 Mar 2011 21:22:56 +0000")

Hi Florian,

On Sat, Mar 12 2011, Florian Tobias Schandinat wrote:
> This patch removes all internal uses of another mostly artificial
> value. It does duplicate the information of the maximum resolution and
> it is not flexible as only a few resolutions exist. Hence it is better
> to remove it and clean the mess up.
> No runtime change expected.
>
> Signed-off-by: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>

We're passing viafb_lcd_panel_id at boot-time on OLPC XO-1.5.
Won't this break boot for us, and anyone else who needs to use it?

Thanks,

- Chris.
-- 
Chris Ball   <cjb@laptop.org>   <http://printf.net/>
One Laptop Per Child

WARNING: multiple messages have this Message-ID (diff)
From: Chris Ball <cjb@laptop.org>
To: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
Cc: linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] viafb: kill lcd_panel_id
Date: Sun, 13 Mar 2011 12:07:42 -0400	[thread overview]
Message-ID: <m3hbb7xaup.fsf@pullcord.laptop.org> (raw)
In-Reply-To: <1299964979-3391-2-git-send-email-FlorianSchandinat@gmx.de> (Florian Tobias Schandinat's message of "Sat, 12 Mar 2011 21:22:56 +0000")

Hi Florian,

On Sat, Mar 12 2011, Florian Tobias Schandinat wrote:
> This patch removes all internal uses of another mostly artificial
> value. It does duplicate the information of the maximum resolution and
> it is not flexible as only a few resolutions exist. Hence it is better
> to remove it and clean the mess up.
> No runtime change expected.
>
> Signed-off-by: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>

We're passing viafb_lcd_panel_id at boot-time on OLPC XO-1.5.
Won't this break boot for us, and anyone else who needs to use it?

Thanks,

- Chris.
-- 
Chris Ball   <cjb@laptop.org>   <http://printf.net/>
One Laptop Per Child

  reply	other threads:[~2011-03-13 16:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-12 21:22 viafb cleanup patches Florian Tobias Schandinat
2011-03-12 21:22 ` [PATCH 1/4] viafb: kill lcd_panel_id Florian Tobias Schandinat
2011-03-12 21:22   ` Florian Tobias Schandinat
2011-03-13 16:07   ` Chris Ball [this message]
2011-03-13 16:07     ` Chris Ball
2011-03-13 17:15     ` Florian Tobias Schandinat
2011-03-13 17:15       ` Florian Tobias Schandinat
2011-03-14  0:05       ` Chris Ball
2011-03-14  0:05         ` Chris Ball
2011-03-12 21:22 ` [PATCH 2/4] viafb: remove unused data_mode and device_type Florian Tobias Schandinat
2011-03-12 21:22 ` [PATCH 3/4] viafb: strip some structures Florian Tobias Schandinat
2011-03-12 21:22   ` Florian Tobias Schandinat
2011-03-12 21:22 ` [PATCH 4/4] viafb: factor lcd scaling parameters out Florian Tobias Schandinat

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=m3hbb7xaup.fsf@pullcord.laptop.org \
    --to=cjb@laptop.org \
    --cc=FlorianSchandinat@gmx.de \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@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.