All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Ruslan Bilovol <ruslan.bilovol@ti.com>
Cc: linux-omap@vger.kernel.org, linux@arm.linux.org.uk,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 0/3] ARM: OMAP2+: Export SoC information to userspace using SoC infrastructure
Date: Mon, 8 Apr 2013 16:27:19 -0700	[thread overview]
Message-ID: <20130408232718.GE10155@atomide.com> (raw)
In-Reply-To: <1360842924-32429-1-git-send-email-ruslan.bilovol@ti.com>

* Ruslan Bilovol <ruslan.bilovol@ti.com> [130214 03:59]:
> Hi,
> 
> This patch series is an attempt to export some OMAP SoC
> information (like name, revision etc.) to userspace.
> The first patch does some unification of OMAP SoC
> information representation in current sources.
> Second patch adds exactly needed changes using
> exists in Linux kernel SoC infrastructure.

Thanks for your patience with these patches,
applying into omap-for-v3.10/soc.

Tony
 
> -----------------------------------------
> v4:
> - Moved common part of late init into common function  in additional
>   separate patch
> - rebased on top of 'omap-for-v3.9/soc' branch of tmlind/linux-omap tree
> 
> -----------------------------------------
> v3:
> - reduced number of lines changed in the first patch (reusing
>   existent code)
> 
> -----------------------------------------
> v2:
> - changed cpu_* -> soc_* variable names
> - rebased on top of 'omap-for-v3.9/soc' branch of tmlind/linux-omap tree
> 
> 
> Ruslan Bilovol (3):
>   ARM: OMAP2+: Move common part of late init into common function
>   ARM: OMAP2+: SoC name and revision unification
>   ARM: OMAP2+: Export SoC information to userspace
> 
>  arch/arm/mach-omap2/common.h |    8 ++++
>  arch/arm/mach-omap2/id.c     |   95 ++++++++++++++++++++++++++++++++++++++----
>  arch/arm/mach-omap2/io.c     |   34 +++++++--------
>  arch/arm/plat-omap/Kconfig   |    1 +
>  4 files changed, 112 insertions(+), 26 deletions(-)
> 
> -- 
> 1.7.9.5
> 

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/3] ARM: OMAP2+: Export SoC information to userspace using SoC infrastructure
Date: Mon, 8 Apr 2013 16:27:19 -0700	[thread overview]
Message-ID: <20130408232718.GE10155@atomide.com> (raw)
In-Reply-To: <1360842924-32429-1-git-send-email-ruslan.bilovol@ti.com>

* Ruslan Bilovol <ruslan.bilovol@ti.com> [130214 03:59]:
> Hi,
> 
> This patch series is an attempt to export some OMAP SoC
> information (like name, revision etc.) to userspace.
> The first patch does some unification of OMAP SoC
> information representation in current sources.
> Second patch adds exactly needed changes using
> exists in Linux kernel SoC infrastructure.

Thanks for your patience with these patches,
applying into omap-for-v3.10/soc.

Tony
 
> -----------------------------------------
> v4:
> - Moved common part of late init into common function  in additional
>   separate patch
> - rebased on top of 'omap-for-v3.9/soc' branch of tmlind/linux-omap tree
> 
> -----------------------------------------
> v3:
> - reduced number of lines changed in the first patch (reusing
>   existent code)
> 
> -----------------------------------------
> v2:
> - changed cpu_* -> soc_* variable names
> - rebased on top of 'omap-for-v3.9/soc' branch of tmlind/linux-omap tree
> 
> 
> Ruslan Bilovol (3):
>   ARM: OMAP2+: Move common part of late init into common function
>   ARM: OMAP2+: SoC name and revision unification
>   ARM: OMAP2+: Export SoC information to userspace
> 
>  arch/arm/mach-omap2/common.h |    8 ++++
>  arch/arm/mach-omap2/id.c     |   95 ++++++++++++++++++++++++++++++++++++++----
>  arch/arm/mach-omap2/io.c     |   34 +++++++--------
>  arch/arm/plat-omap/Kconfig   |    1 +
>  4 files changed, 112 insertions(+), 26 deletions(-)
> 
> -- 
> 1.7.9.5
> 

WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Ruslan Bilovol <ruslan.bilovol@ti.com>
Cc: linux@arm.linux.org.uk, linux-arm-kernel@lists.infradead.org,
	linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/3] ARM: OMAP2+: Export SoC information to userspace using SoC infrastructure
Date: Mon, 8 Apr 2013 16:27:19 -0700	[thread overview]
Message-ID: <20130408232718.GE10155@atomide.com> (raw)
In-Reply-To: <1360842924-32429-1-git-send-email-ruslan.bilovol@ti.com>

* Ruslan Bilovol <ruslan.bilovol@ti.com> [130214 03:59]:
> Hi,
> 
> This patch series is an attempt to export some OMAP SoC
> information (like name, revision etc.) to userspace.
> The first patch does some unification of OMAP SoC
> information representation in current sources.
> Second patch adds exactly needed changes using
> exists in Linux kernel SoC infrastructure.

Thanks for your patience with these patches,
applying into omap-for-v3.10/soc.

Tony
 
> -----------------------------------------
> v4:
> - Moved common part of late init into common function  in additional
>   separate patch
> - rebased on top of 'omap-for-v3.9/soc' branch of tmlind/linux-omap tree
> 
> -----------------------------------------
> v3:
> - reduced number of lines changed in the first patch (reusing
>   existent code)
> 
> -----------------------------------------
> v2:
> - changed cpu_* -> soc_* variable names
> - rebased on top of 'omap-for-v3.9/soc' branch of tmlind/linux-omap tree
> 
> 
> Ruslan Bilovol (3):
>   ARM: OMAP2+: Move common part of late init into common function
>   ARM: OMAP2+: SoC name and revision unification
>   ARM: OMAP2+: Export SoC information to userspace
> 
>  arch/arm/mach-omap2/common.h |    8 ++++
>  arch/arm/mach-omap2/id.c     |   95 ++++++++++++++++++++++++++++++++++++++----
>  arch/arm/mach-omap2/io.c     |   34 +++++++--------
>  arch/arm/plat-omap/Kconfig   |    1 +
>  4 files changed, 112 insertions(+), 26 deletions(-)
> 
> -- 
> 1.7.9.5
> 

  parent reply	other threads:[~2013-04-08 23:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-14 11:55 [PATCH v4 0/3] ARM: OMAP2+: Export SoC information to userspace using SoC infrastructure Ruslan Bilovol
2013-02-14 11:55 ` Ruslan Bilovol
2013-02-14 11:55 ` [PATCH v4 1/3] ARM: OMAP2+: Move common part of late init into common function Ruslan Bilovol
2013-02-14 11:55   ` Ruslan Bilovol
2013-02-14 11:55 ` [PATCH v4 2/3] ARM: OMAP2+: SoC name and revision unification Ruslan Bilovol
2013-02-14 11:55   ` Ruslan Bilovol
2013-02-14 11:55 ` [PATCH v4 3/3] ARM: OMAP2+: Export SoC information to userspace Ruslan Bilovol
2013-02-14 11:55   ` Ruslan Bilovol
2013-04-08 23:27 ` Tony Lindgren [this message]
2013-04-08 23:27   ` [PATCH v4 0/3] ARM: OMAP2+: Export SoC information to userspace using SoC infrastructure Tony Lindgren
2013-04-08 23:27   ` Tony Lindgren

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=20130408232718.GE10155@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=ruslan.bilovol@ti.com \
    /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.