From: "Vesa Jääskeläinen" <chaac@nic.fi>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: vesafb terminal for testing.
Date: Tue, 16 Aug 2005 00:05:49 +0300 [thread overview]
Message-ID: <430103AD.1090800@nic.fi> (raw)
In-Reply-To: <87zmrjxge4.fsf@student.han.nl>
Marco Gerards wrote:
> Some comments on the patch:
>
>> 2005-08-14 Vesa Jaaskelainen <chaac@nic.fi>
>>
>> + * DISTLIST: Added term/i386/pc/vesafb.c
>> + * term/i386/pc/vesafb: New file.
>
> Can you please split this up to the generic framebuffer terminal? The
> terminal for framebuffers should be generic and the videodrivers
> should be arch specific. Or do you want to do that later?
I'll do that later. Let's first test this beast out and when it works
then design the actual video driver. I have tried to make framebuffer
code as separate as I could have in this point.
> You forgot the ".c" on the last line.
Already fixed. Actually I noticed that typo when I first sent the patch.
>> +
>> +2005-08-14 Vesa Jaaskelainen <chaac@nic.fi>
>> +
>> * DISTLIST: Added include/grub/i386/pc/vbe.h.
>
> Why two changelog entries? I do not see this change anywhere in the
> patch.
Before making that patch I committed some fixes to DISTLIST and that was
last entry in Changelog before starting to migrate my patch to newest
GRUB. Date on those two patches were identical so diff got "confused"
about those.
>> +static void
>> +*real2pm(grub_vbe_farptr_t ptr)
>
> The * is a part of the type, can you put it on the previous line?
Sure. It seems that I already spotted that one :)
> There are some long lines, can you please make them shorter so
> the maximal line length is 78 characters?
Hmm... I made another scan for those. Still I left some of those there
because in my opinion it is much more readable in that way. But splitted
some lines.
> You sometimes use C++ style comments. Can you change your comments so
> they match the style described in the GCS:
> http://www.gnu.org/prep/standards/html_node/Comments.html#Comments
I think there should not be anymore C++ style comments. It's hard to
stay away from ooooold habits :)
Fortunely I found GNU indentation mode from my editor :)... It makes
this a bit easier.
I will scan the code once more and then commit a bit different version
to CVS as Okuji asked to commit it to there for easier testing.
next prev parent reply other threads:[~2005-08-15 21:10 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-14 11:52 vesafb terminal for testing Vesa Jääskeläinen
2005-08-14 14:48 ` Yoshinori K. Okuji
2005-08-14 15:45 ` Vesa Jääskeläinen
2005-08-14 16:47 ` Vladimir Serbinenko
2005-08-14 19:25 ` Yoshinori K. Okuji
2005-08-15 15:23 ` Vincent Pelletier
2005-08-15 16:06 ` Vladimir Serbinenko
2005-08-15 17:02 ` Marco Gerards
2005-08-15 17:19 ` Yoshinori K. Okuji
2005-08-15 17:41 ` Marco Gerards
2005-08-15 18:55 ` Yoshinori K. Okuji
2005-08-15 20:54 ` Marco Gerards
2005-08-15 21:44 ` Vesa Jääskeläinen
2005-08-16 6:47 ` Vincent Pelletier
2005-08-16 10:20 ` Marco Gerards
2005-08-15 17:07 ` Marco Gerards
2005-08-16 6:54 ` Vincent Pelletier
2005-08-14 21:48 ` Vesa Jääskeläinen
2005-08-14 22:19 ` Yoshinori K. Okuji
2005-08-15 15:52 ` Vesa Jääskeläinen
2005-08-15 16:13 ` Yoshinori K. Okuji
2005-08-15 15:42 ` Vladimir Serbinenko
2005-08-19 0:48 ` Yoshinori K. Okuji
2005-09-18 21:03 ` Vesa Jääskeläinen
2005-09-19 19:00 ` Yoshinori K. Okuji
2005-09-19 23:11 ` Vesa Jääskeläinen
2005-09-20 17:13 ` Yoshinori K. Okuji
2005-08-15 17:24 ` Marco Gerards
2005-08-15 21:05 ` Vesa Jääskeläinen [this message]
2005-08-15 21:21 ` Marco Gerards
2005-08-15 21:39 ` Vesa Jääskeläinen
2005-08-16 10:04 ` Marco Gerards
2005-08-16 18:36 ` Vesa Jääskeläinen
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=430103AD.1090800@nic.fi \
--to=chaac@nic.fi \
--cc=grub-devel@gnu.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.