linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: Maneesh Soni <maneesh@in.ibm.com>
Cc: Sachin Sant <sachinp@in.ibm.com>,
	Russell King <rmk+lkml@arm.linux.org.uk>,
	Sharyathi Nagesh <sharyath@in.ibm.com>,
	linux-kernel@vger.kernel.org,
	Arjan van de Ven <arjan@infradead.org>,
	Vivek Goyal <vgoyal@in.ibm.com>
Subject: Re: Bug while executing : cat /proc/iomem on 2.6.17-rc1/rc2
Date: Sat, 13 May 2006 07:56:26 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0605130755040.3866@g5.osdl.org> (raw)
In-Reply-To: <20060513103047.GA28366@in.ibm.com>



On Sat, 13 May 2006, Maneesh Soni wrote:
> 
> Backing out 
> 
> http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=10dbe196a8da6b3196881269c6639c0ec11c36cb
> 
> solves this problem for me. This patch adds memory more than 4G to /proc/iomem
> but without 64-bit fields for struct resource it ends up in confusing 
> iomem_resource list. I think this patch needs the core 64-bit struct resource
> related changes also.

Yeah, let's revert that for now. I don't think the people involved 
realized how it was dependent on the 64-bit struct resource changes.

Thanks,

		Linus

      reply	other threads:[~2006-05-13 14:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-25 10:43 Bug while executing : cat /proc/iomem on 2.6.17-rc1/rc2 Sachin Sant
2006-04-25 10:48 ` Arjan van de Ven
2006-05-11  7:27   ` Sharyathi Nagesh
2006-05-11  7:32     ` Russell King
2006-05-11  8:38       ` Sachin Sant
2006-05-13 10:30         ` Maneesh Soni
2006-05-13 14:56           ` Linus Torvalds [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=Pine.LNX.4.64.0605130755040.3866@g5.osdl.org \
    --to=torvalds@osdl.org \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maneesh@in.ibm.com \
    --cc=rmk+lkml@arm.linux.org.uk \
    --cc=sachinp@in.ibm.com \
    --cc=sharyath@in.ibm.com \
    --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;
as well as URLs for NNTP newsgroup(s).