mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Arjan van de Ven <arjan@infradead.org>,
	vgoyal@in.ibm.com,
	linux kernel mailing list <linux-kernel@vger.kernel.org>,
	Fastboot mailing list <fastboot@lists.osdl.org>,
	Morton Andrew Morton <akpm@osdl.org>,
	gregkh@suse.de
Subject: Re: [RFC][PATCH] Expanding the size of "start" and "end" field in "struct resource"
Date: Wed, 15 Mar 2006 13:37:57 -0700	[thread overview]
Message-ID: <m1slpjfnq2.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <006E591F-5F82-4B79-8D1A-581B6AF00185@kernel.crashing.org> (Kumar Gala's message of "Wed, 15 Mar 2006 14:28:42 -0600")

Kumar Gala <galak@kernel.crashing.org> writes:

> Warnings primarily, however I think some places have assumptions  about size
> that have to be looked at.

Ok.  So nothing too bad just a thorough audit.  Although any driver that
has a real problem with a 64bit type is already broken on every 64bit
arch.

And we do need the 64bit type so we can handle 64bit pci resources on
x86 and ppc32 at some point.

Eric

  reply	other threads:[~2006-03-15 20:39 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-15 19:31 Vivek Goyal
2006-03-15 19:48 ` Kumar Gala
2006-03-15 19:57 ` Arjan van de Ven
2006-03-15 20:01   ` Kumar Gala
2006-03-15 20:10     ` Kumar Gala
2006-03-15 20:13     ` Eric W. Biederman
2006-03-15 20:28       ` Kumar Gala
2006-03-15 20:37         ` Eric W. Biederman [this message]
2006-03-15 20:32       ` Vivek Goyal
2006-03-15 20:58         ` Eric W. Biederman
2006-03-15 21:57   ` David S. Miller
2006-03-15 20:53 ` Benjamin LaHaise
2006-03-15 21:05   ` Kumar Gala
2006-03-15 21:13     ` Benjamin LaHaise
2006-03-15 21:29       ` Eric W. Biederman
2006-03-15 21:28         ` Benjamin LaHaise
2006-03-15 21:50           ` Eric W. Biederman
2006-03-15 22:13             ` Andrew Morton
2006-03-15 22:18               ` David S. Miller
2006-03-15 21:59           ` Eric W. Biederman
2006-03-15 22:07             ` Benjamin LaHaise
2006-03-16 14:45               ` Eric W. Biederman
2006-03-15 21:30       ` Kumar Gala
2006-03-15 21:35         ` hackmiester / Hunter Fuller
2006-03-15 21:31       ` Eric W. Biederman
2006-03-15 21:15     ` Eric W. Biederman
2006-03-15 21:26     ` linux-os (Dick Johnson)
2006-03-15 21:37       ` Eric W. Biederman
2006-03-15 22:08 ` Greg KH

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=m1slpjfnq2.fsf@ebiederm.dsl.xmission.com \
    --to=ebiederm@xmission.com \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=fastboot@lists.osdl.org \
    --cc=galak@kernel.crashing.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vgoyal@in.ibm.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®