mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: H Hartley Sweeten <hartleys@visionengravers.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problem with /proc/iomem on ARM
Date: Wed, 1 Jul 2009 19:55:02 +0200	[thread overview]
Message-ID: <ac3eb2510907011055r5d5f06c1k754e52ebae88efab@mail.gmail.com> (raw)
In-Reply-To: <BD79186B4FD85F4B8E60E381CAEE190901A13822@mi8nycmail19.Mi8.com>

On Wed, Jul 1, 2009 at 19:32, H Hartley
Sweeten<hartleys@visionengravers.com> wrote:
> I just noticed a problem with /proc/iomem on my ARM system
> that I think was introduced by your patch:
>
> commit 1d559e29138834bbcdf34ac072232bf543bfc4e0
> Author: Kay Sievers <kay.sievers@vrfy.org>
> Date:   Tue Jan 6 10:44:43 2009 -0800
>
>    arm: struct device - replace bus_id with dev_name(), dev_set_name()
>
>    Cc: Russell King <rmk@arm.linux.org.uk>
>    Signed-off-by: Kay Sievers <kay.sievers@vrfy.org>
>    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>

> This was seen with kernel 2.6.30.  I havn't looked at /proc/iomem for
> a while so I'm not sure when this first started.

Are you sure, 8a577ffc75d9194fe8cdb7479236f2081c26ca1f isn't in your tree?

After all, it seems like this should be fixed in arm somewhere, not to
copy and store internal driver core pointers, but use the device
itself to retrieve the values.

Thanks,
Kay

  reply	other threads:[~2009-07-01 17:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-01 17:32 H Hartley Sweeten
2009-07-01 17:55 ` Kay Sievers [this message]
2009-07-01 18:01   ` H Hartley Sweeten
2009-07-01 18:12     ` Kay Sievers
2009-07-01 18:24       ` H Hartley Sweeten
2009-07-01 18:46         ` Kay Sievers
2009-07-08 22:09           ` H Hartley Sweeten

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=ac3eb2510907011055r5d5f06c1k754e52ebae88efab@mail.gmail.com \
    --to=kay.sievers@vrfy.org \
    --cc=hartleys@visionengravers.com \
    --cc=linux-kernel@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
all inboxes | Powered by JetHome®