public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Cornelia Huck <cornelia.huck@de.ibm.com>,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	Len Brown <len.brown@intel.com>, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH 0/2] Add dev_sysdata and use it for ACPI
Date: Fri, 10 Nov 2006 14:48:46 +0900	[thread overview]
Message-ID: <20061110054846.GA9137@kroah.com> (raw)
In-Reply-To: <1163111737.4982.40.camel@localhost.localdomain>

On Fri, Nov 10, 2006 at 09:35:37AM +1100, Benjamin Herrenschmidt wrote:
> On Thu, 2006-11-09 at 17:04 +0100, Cornelia Huck wrote:
> > On Thu, 09 Nov 2006 11:45:21 +1100,
> > Benjamin Herrenschmidt <benh@au1.ibm.com> wrote:
> > 
> > >  - Add a dev_sysdata structure to struct device whose content is arch
> > > specific. It will allow architectures like powerpc, arm, i386, ... who
> > > need different types of DMA ops for busses and other kind of auxilliary
> > > data for devices in general (numa node id, firmware data, etc...) to put
> > > them in there, without bloating all architectures. The patch adds an
> > > empty definition for the structure to all architectures.
> > 
> > I like this. If we could move the dma stuff in there, we could get rid
> > of it on s390 where it is just bloat we drag around...
> > 
> > (Maybe dev_archdata would be a better name, since the definition is
> > architecture specific?)
> 
> Hrm... I wonder why I posted from my IBM address :-) I have no firm
> preference on the name of the structure. So far, I had no feedback on
> that patch at all appart from yours though.
> 
> Andrew, Greg ? Is that something you would take for 2.6.20 ? I need to
> know wether I should rework my patches to use that or stick to my hacks
> involving hijacking firmware_data.

Sorry, I'm in Japan this week, and access to email is limited.

I like this change, but I like the dev_archdata name better.  It lets
people know who owns the pointer much better.

Care to respin these patches with this change?

And yes, I don't see a problem with such a change like this for 2.6.20,
it's pretty simple.

thanks,

greg k-h

  reply	other threads:[~2006-11-10  8:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-09  0:45 [PATCH 0/2] Add dev_sysdata and use it for ACPI Benjamin Herrenschmidt
2006-11-09 16:04 ` Cornelia Huck
2006-11-09 22:35   ` Benjamin Herrenschmidt
2006-11-10  5:48     ` Greg KH [this message]
2006-11-10  9:44       ` Benjamin Herrenschmidt
2006-11-13  5:17       ` Paul Mackerras
2006-11-13  6:07         ` Benjamin Herrenschmidt

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=20061110054846.GA9137@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@osdl.org \
    --cc=benh@kernel.crashing.org \
    --cc=cornelia.huck@de.ibm.com \
    --cc=len.brown@intel.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