All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: davidm@hpl.hp.com
Cc: davidm@napali.hpl.hp.com, albert@users.sourceforge.net,
	linux-kernel@vger.kernel.org, torvalds@osdl.org, akpm@osdl.org
Subject: Re: [patch] u64 casts
Date: Fri, 27 Feb 2004 23:44:19 -0800	[thread overview]
Message-ID: <20040227234419.7cee9b29.davem@redhat.com> (raw)
In-Reply-To: <16447.58524.257563.252138@napali.hpl.hp.com>

On Fri, 27 Feb 2004 16:45:16 -0800
David Mosberger <davidm@napali.hpl.hp.com> wrote:

> >>>>> On 27 Feb 2004 17:16:53 -0500, Albert Cahalan <albert@users.sourceforge.net> said:
> 
>   Albert> Supposing that this is the case, you may get warnings.
> 
> Well, then do it on your own kernel/system.  I'm not interested in
> spending time on this now, so please don't touch ia64 unless you
> verified that all the other pieces are in place.

Yes, and I already know that trying to do things this way results
in more warnings and more problems on sparc64, as I've tried it.


  parent reply	other threads:[~2004-02-28  7:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-27 20:58 [patch] u64 casts Albert Cahalan
2004-02-28  0:18 ` David Mosberger
2004-02-27 22:16   ` Albert Cahalan
2004-02-28  0:45     ` David Mosberger
2004-02-27 22:53       ` Albert Cahalan
2004-02-28  7:44       ` David S. Miller [this message]
2004-02-28 10:42     ` Jakub Jelinek
2004-02-28 14:46       ` [patch] new version, u64 cast avoidance Albert Cahalan
2004-02-28 23:58         ` Benjamin Herrenschmidt
2004-02-28 23:59           ` Benjamin Herrenschmidt
2004-02-28 22:21             ` Albert Cahalan
2004-02-29  1:08               ` Benjamin Herrenschmidt
2004-02-28 23:49                 ` Albert Cahalan
2004-02-29  3:25                   ` Matt Mackall
2004-02-29  1:01                 ` [patch] 3rd " Albert Cahalan

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=20040227234419.7cee9b29.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=akpm@osdl.org \
    --cc=albert@users.sourceforge.net \
    --cc=davidm@hpl.hp.com \
    --cc=davidm@napali.hpl.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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.