From: David Miller <davem@davemloft.net>
To: krzysztof.h1@poczta.fm
Cc: linux-fbdev-devel@lists.sourceforge.net, sparclinux@vger.kernel.org
Subject: Re: [PATCH] p9100: use standard fields for framebuffer physical address and length
Date: Mon, 04 May 2009 14:10:24 -0700 (PDT) [thread overview]
Message-ID: <20090504.141024.206710584.davem@davemloft.net> (raw)
In-Reply-To: <20090504224257.00514552.krzysztof.h1@poczta.fm>
From: Krzysztof Helt <krzysztof.h1@poczta.fm>
Date: Mon, 4 May 2009 22:42:57 +0200
> From: Krzysztof Helt <krzysztof.h1@wp.pl>
>
> Use standard fields fbinfo.fix.smem_start and fbinfo.fix.smem_len
> for physical address and length of framebuffer.
>
> This also fixes output of the 'fbset -i' command - address and length
> of the framebuffer are displayed correctly.
>
> Signed-off-by: Krzysztof Helt <krzysztof.h1@wp.pl>
My objections to the cg3 patch apply here as well.
prev parent reply other threads:[~2009-05-04 21:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-04 20:42 [PATCH] p9100: use standard fields for framebuffer physical address and length Krzysztof Helt
2009-05-04 21:10 ` David Miller [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=20090504.141024.206710584.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=krzysztof.h1@poczta.fm \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=sparclinux@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;
as well as URLs for NNTP newsgroup(s).