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

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.

Cheers,
Ben.


  reply	other threads:[~2006-11-09 22:35 UTC|newest]

Thread overview: 8+ 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 [this message]
2006-11-10  5:48     ` Greg KH
2006-11-10  9:44       ` Benjamin Herrenschmidt
2006-11-13  5:17       ` Paul Mackerras
2006-11-13  6:07         ` Benjamin Herrenschmidt
  -- strict thread matches above, loose matches on Subject: below --
2006-11-10  6:58 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=1163111737.4982.40.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=akpm@osdl.org \
    --cc=cornelia.huck@de.ibm.com \
    --cc=greg@kroah.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 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.