All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Given <dg@cowlark.com>
To: linux-sparse@vger.kernel.org
Subject: Re: [PATCH 2/15 v2] Unhardcode byte size being 8 bits.
Date: Thu, 18 Dec 2008 17:12:34 +0000	[thread overview]
Message-ID: <494A8482.7030801@cowlark.com> (raw)
In-Reply-To: <20081217190534.24084.94887.stgit@zaytsev.su>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Alexey Zaytsev wrote:
> From: David Given <dg@cowlark.com>
[...]
> Anyway, here is the updated byte size patch.
> David, we still need your sign-off here.
[...]
> diff --git a/compile-i386.c b/compile-i386.c
[...snipped for brevity, you already have the patch...]

Okay:

Signed-off-by: David Given <dg@cowlark.com>

FWIW, I also hereby declare my work in this patch to be in the public
domain, which means you can do what you like with it, including
relicensing it at a future date. Just in case anyone decides to try and
persue a sparse license change.

- --
David Given
dg@cowlark.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAklKhIEACgkQf9E0noFvlzjSxwCgzwIVOjhr7Nu+eccIwR1susN8
+TMAoJujE7dAZgAoPSmtlcfYMeq7QE9T
=iKFi
-----END PGP SIGNATURE-----

      parent reply	other threads:[~2008-12-18 17:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-17 20:05 [PATCH 2/15 v2] Unhardcode byte size being 8 bits Alexey Zaytsev
2008-12-17 23:33 ` David Given
2008-12-18  0:33   ` Alexey Zaytsev
2008-12-18  0:58     ` David Given
2008-12-18  1:24       ` Alexey Zaytsev
2008-12-18  1:10     ` Derek M Jones
2008-12-18  1:52       ` Derek M Jones
2008-12-18  3:11         ` Alexey Zaytsev
2008-12-18 13:05           ` Derek M Jones
2008-12-18 17:07             ` Alexey Zaytsev
2008-12-18 17:12 ` David Given [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=494A8482.7030801@cowlark.com \
    --to=dg@cowlark.com \
    --cc=linux-sparse@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.