All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Linux Arch list <linux-arch@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>, Greg KH <greg@kroah.com>
Subject: Re: [PATCH] add dev_archdata to struct device
Date: Sat, 11 Nov 2006 07:43:43 +0100	[thread overview]
Message-ID: <200611110743.43829.ak@suse.de> (raw)
In-Reply-To: <1163225919.4982.219.camel@localhost.localdomain>

On Saturday 11 November 2006 07:18, Benjamin Herrenschmidt wrote:
> Add arch specific dev_archdata to struct device
> 
> Adds an arch specific struct dev_arch to struct device. This enables
> architecture to add specific fields to every device in the system, like
> DMA operation pointers, NUMA node ID, firmware specific data, etc...

Fine by me from the x86 side.

-Andi

  reply	other threads:[~2006-11-11  6:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-11  6:18 [PATCH] add dev_archdata to struct device Benjamin Herrenschmidt
2006-11-11  6:43 ` Andi Kleen [this message]
2006-11-13  9:29 ` David Howells
2006-11-13 18:30 ` patch driver-core-add-dev_archdata-to-struct-device.patch added to gregkh-2.6 tree gregkh

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=200611110743.43829.ak@suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=benh@kernel.crashing.org \
    --cc=greg@kroah.com \
    --cc=linux-arch@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.