public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <monstr@monstr.eu>
To: graeme.smecher@mail.mcgill.ca
Cc: linux-kernel@vger.kernel.org, microblaze-uclinux@itee.uq.edu.au
Subject: Re: [PATCH] microblaze: Add dev_archdata node accessors
Date: Wed, 25 Nov 2009 20:00:00 +0100	[thread overview]
Message-ID: <4B0D7EB0.8090604@monstr.eu> (raw)
In-Reply-To: <1259175422-4628-1-git-send-email-graeme.smecher@mail.mcgill.ca>

graeme.smecher@mail.mcgill.ca wrote:
> From: Graeme Smecher <graeme.smecher@mail.mcgill.ca>
> 
> This syncs microblaze with powerpc and sparc architectures, which gained the
> same accessors in Commit 3f3b1632022fcc8317fa3b3c1236471415b3a6b8.

I have the same patch in my next branch. Will be add to mainline soon.

Thanks,
Michal

> 
> Signed-off-by: Graeme Smecher <graeme.smecher@mail.mcgill.ca>
> ---
>  arch/microblaze/include/asm/device.h |   12 ++++++++++++
>  1 files changed, 12 insertions(+), 0 deletions(-)
> 
> diff --git a/arch/microblaze/include/asm/device.h b/arch/microblaze/include/asm/device.h
> index 30286db..b8f654d 100644
> --- a/arch/microblaze/include/asm/device.h
> +++ b/arch/microblaze/include/asm/device.h
> @@ -16,6 +16,18 @@ struct dev_archdata {
>  	struct device_node	*of_node;
>  };
>  
> +static inline void dev_archdata_set_node(struct dev_archdata *ad,
> +					 struct device_node *np)
> +{
> +	ad->of_node = np;
> +}
> +
> +static inline struct device_node *
> +dev_archdata_get_node(const struct dev_archdata *ad)
> +{
> +	return ad->of_node;
> +}
> +
>  struct pdev_archdata {
>  };
>  


-- 
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian

      reply	other threads:[~2009-11-25 19:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-25 18:57 [PATCH] microblaze: Add dev_archdata node accessors graeme.smecher
2009-11-25 19:00 ` Michal Simek [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=4B0D7EB0.8090604@monstr.eu \
    --to=monstr@monstr.eu \
    --cc=graeme.smecher@mail.mcgill.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=microblaze-uclinux@itee.uq.edu.au \
    /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