From: Josh Triplett <josht@linux.vnet.ibm.com>
To: David Given <dg@cowlark.com>
Cc: linux-sparse@vger.kernel.org
Subject: Re: Updated byte size patch
Date: Mon, 07 Jul 2008 11:02:50 -0700 [thread overview]
Message-ID: <1215453770.3003.32.camel@josh-work.beaverton.ibm.com> (raw)
In-Reply-To: <487019DF.10907@cowlark.com>
On Sun, 2008-07-06 at 02:03 +0100, David Given wrote:
> Turns out that I'd missed one place where there was a hardcoded 8 in the
> last patch, so here's an updated version.
I do still have some concerns about the potential performance loss, but
it seems unlikely to cause a serious problem. I have *serious* doubts
that Sparse will ever successfully handle a system without 8-bit bytes.
However, I will merge this patch. I do need a signoff, though.
- Josh Triplett
prev parent reply other threads:[~2008-07-07 18:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-06 1:03 Updated byte size patch David Given
2008-07-07 18:02 ` Josh Triplett [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=1215453770.3003.32.camel@josh-work.beaverton.ibm.com \
--to=josht@linux.vnet.ibm.com \
--cc=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 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).