From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH] transparent file reader
Date: Sun, 14 Mar 2010 14:44:11 +0100 [thread overview]
Message-ID: <4B9CE82B.8070106@gmail.com> (raw)
In-Reply-To: <201002282238.48753.szymon@janc.net.pl>
[-- Attachment #1: Type: text/plain, Size: 1792 bytes --]
Szymon Janc wrote:
> Dnia wtorek 16 luty 2010 o 19:16:19 Vladimir 'φ-coder/phcoder' Serbinenko
> napisał(a):
>
>
>> I like the patch however few comments:
>> 1) How are filters ordered?
>> 2) How would I selectively disable a filter. E.g. for hexdump or when
>> payload expects compressed data?
>>
>> +/* Registered filters list. */
>> +static grub_io_filter_t grub_io_filter_list = NULL;
>> +
>> +void grub_io_register(grub_io_filter_t filter)
>> +{
>> + filter->next = grub_io_filter_list;
>> + grub_io_filter_list = filter;
>> +}
>> +
>>
>> list.h can be used for this.
>>
>
> Attached is new version, changes since previous one:
> - use list.h
> - filter registration is priority based
> - filter can be disabled for next open by grub_io_filter_disable()
>
> Interface could be simpler if make it only transparent/non-transparent but
> this is somewhat less flexible. Yet, is it really needed?
>
>
First of all I would prefer not_easily_seekable part to be a separate
patches so it would be easier to pinpoint bugs by bisecting.
+ .prio = 1,
This should be macroifyed e.g
GRUB_IOFILTER_PRIO_COMPRESSOR
grub_io_register, grub_io_unregister and grub_io_filter_disable must be inlined. Last one has to be splitted into grub_io_filter_disable and grub_io_filter_disable_all to avoid special case with "". va_arg in grub_io_filter_disable doesn't justify itself (one can always make 2 calls, especially if function would be inlined
> ------------------------------------------------------------------------
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 293 bytes --]
next prev parent reply other threads:[~2010-03-14 13:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-16 18:06 [PATCH] transparent file reader Szymon Janc
2010-02-16 18:16 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-02-16 19:12 ` Szymon Janc
2010-02-28 21:38 ` Szymon Janc
2010-03-14 13:44 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2010-02-16 19:38 ` Seth Goldberg
2010-02-16 20:00 ` Szymon Janc
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=4B9CE82B.8070106@gmail.com \
--to=phcoder@gmail.com \
--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.