From: jason@lakedaemon.net (Jason Cooper)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: mvebu: Add a SOC bus device entry
Date: Thu, 24 Apr 2014 00:27:17 -0400 [thread overview]
Message-ID: <20140424042717.GR28159@titan.lakedaemon.net> (raw)
In-Reply-To: <1393955507-26436-1-git-send-email-andrew@lunn.ch>
On Tue, Mar 04, 2014 at 06:51:47PM +0100, Andrew Lunn wrote:
> Add the SoC Family, device ID and revision to /sys/bus/soc.
>
> Signed-off-by: Andrew Lunn <andrew@lunn.ch>
> ---
> arch/arm/mach-mvebu/Kconfig | 1 +
> arch/arm/mach-mvebu/mvebu-soc-id.c | 28 ++++++++++++++++++++++++++++
> 2 files changed, 29 insertions(+)
Applied to mvebu/soc
Please make sure to run make with -q to catch newly introduced warnings.
I added 'return 0;' to the end of the function, and explicitly 'return
0;' for !is_id_valid.
thx,
Jason.
prev parent reply other threads:[~2014-04-24 4:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 17:51 [PATCH] ARM: mvebu: Add a SOC bus device entry Andrew Lunn
2014-04-24 4:27 ` Jason Cooper [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=20140424042717.GR28159@titan.lakedaemon.net \
--to=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).