grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH] Remove nested functions from disk and file read hooks
Date: Tue, 26 Feb 2013 22:57:40 +0100	[thread overview]
Message-ID: <512D2FD4.8040300@gmail.com> (raw)
In-Reply-To: <20130121121430.GB4066@riva.dynamic.greenend.org.uk>

[-- Attachment #1: Type: text/plain, Size: 928 bytes --]


On 21.01.2013 13:14, Colin Watson wrote:

> Part seven.  This particular patch in the set loses some of the
> compressed-kernel size we'd gained from earlier patches, but it's still
> a good bit smaller than when I started on this work so I'm not worried.
> Note that, as a general pattern, I have intentionally not zeroed out
> read_hook_data after calling code using a read hook; this is because (a)
> the code that calls read hooks only checks whether read_hook is NULL,
> (b) every function that sets read_hook to something non-NULL naturally
> also sets read_hook_data if it cares about its value, and (c) avoiding
> the extra code to zero read_hook_data makes a few bytes of difference to
> the size of compressed core images.


There are some possible improvements that we've discussed on IRC.
Apparently you didn't have time to implement them. They can come in
separately later if needed. Go ahead.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]

      reply	other threads:[~2013-02-26 21:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-21 12:14 [PATCH] Remove nested functions from disk and file read hooks Colin Watson
2013-02-26 21:57 ` Vladimir 'φ-coder/phcoder' Serbinenko [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=512D2FD4.8040300@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 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).