mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesper Juhl <jesper.juhl@gmail.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com
Subject: Re: [PATCH] i386, nmi: signed vs unsigned mixup
Date: Sun, 20 Nov 2005 02:45:27 +0100	[thread overview]
Message-ID: <9a8748490511191745h6aebd102r91007bc2b84382ff@mail.gmail.com> (raw)
In-Reply-To: <20051119173358.2bf1dbb5.akpm@osdl.org>

On 11/20/05, Andrew Morton <akpm@osdl.org> wrote:
> Jesper Juhl <jesper.juhl@gmail.com> wrote:
> >
> > Ok, so does that mean that, if properly verified, patches for things
> >  that "gcc -Wsigned-compare" flags will be appreciated?
>
> All patches are appreciated, but not all are applied ;)
>
> Sure, go for it - let's see what the patches end up looking like.  We might
> find real bugs in there - I found a bunch of howlers back in 2.3.late.
> That was with `gcc -W' which turns on more than -Wsigned-compare.
>
> Maybe you could prepare a quick overall summary first, see if you can work
> out the overall scope of the problem and then we can take a look at that,
> decide what bits to attack?
>
Sure, I'll do that tomorrow.
All these sign issues all over annoy me :)
I'll try to get a handle on the scope of the thing tomorrow, then send
a mail with what I find, then we can talk about what would be useful
to do.

--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html

  reply	other threads:[~2005-11-20  1:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-19 23:10 Jesper Juhl
2005-11-20  0:28 ` Andrew Morton
2005-11-20  0:30   ` Jesper Juhl
2005-11-20  1:08     ` Andrew Morton
2005-11-20  1:15       ` Jesper Juhl
2005-11-20  1:33         ` Andrew Morton
2005-11-20  1:45           ` Jesper Juhl [this message]
2005-11-21 10:40             ` Jesper Juhl
2005-11-21 20:20               ` Andrew Morton

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=9a8748490511191745h6aebd102r91007bc2b84382ff@mail.gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    /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

all inboxes | Powered by JetHome®