From: stefan.wahren@i2se.com (Stefan Wahren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/7] drivers: Introduce new eFuse subsystem stub
Date: Wed, 25 Feb 2015 13:29:24 +0100 [thread overview]
Message-ID: <54EDC024.2040804@i2se.com> (raw)
In-Reply-To: <1424864719-3390-4-git-send-email-ezequiel.garcia@imgtec.com>
Hi,
[adding devicetree list]
Am 25.02.2015 um 12:45 schrieb Ezequiel Garcia:
> This commit introduces a new eFuse subsystem stub to hold all the eFuse-like
> device drivers. This will be used to host the currently supported Tegra
> eFuse driver, and will allow to add support for other platforms as well.
as i mentioned in the old discussion it would be nice to keep drivers
and devicetree binding documentation consistent.
So how about renaming?
Documentation/devicetree/bindings/fuse/ ->
Documentation/devicetree/bindings/efuse/
Best regards
Stefan
WARNING: multiple messages have this Message-ID (diff)
From: Stefan Wahren <stefan.wahren-eS4NqCHxEME@public.gmane.org>
To: Ezequiel Garcia
<ezequiel.garcia-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org>,
Thierry Reding
<thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>,
Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>,
Maxime Ripard
<maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>,
Andrew Bresticker
<abrestic-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>,
James Hartley
<james.hartley-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org>
Cc: Thierry Reding <treding-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH 3/7] drivers: Introduce new eFuse subsystem stub
Date: Wed, 25 Feb 2015 13:29:24 +0100 [thread overview]
Message-ID: <54EDC024.2040804@i2se.com> (raw)
In-Reply-To: <1424864719-3390-4-git-send-email-ezequiel.garcia-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org>
Hi,
[adding devicetree list]
Am 25.02.2015 um 12:45 schrieb Ezequiel Garcia:
> This commit introduces a new eFuse subsystem stub to hold all the eFuse-like
> device drivers. This will be used to host the currently supported Tegra
> eFuse driver, and will allow to add support for other platforms as well.
as i mentioned in the old discussion it would be nice to keep drivers
and devicetree binding documentation consistent.
So how about renaming?
Documentation/devicetree/bindings/fuse/ ->
Documentation/devicetree/bindings/efuse/
Best regards
Stefan
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Stefan Wahren <stefan.wahren@i2se.com>
To: Ezequiel Garcia <ezequiel.garcia@imgtec.com>,
Thierry Reding <thierry.reding@gmail.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Arnd Bergmann <arnd@arndb.de>,
Maxime Ripard <maxime.ripard@free-electrons.com>,
Andrew Bresticker <abrestic@chromium.org>,
James Hartley <james.hartley@imgtec.com>
Cc: Thierry Reding <treding@nvidia.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH 3/7] drivers: Introduce new eFuse subsystem stub
Date: Wed, 25 Feb 2015 13:29:24 +0100 [thread overview]
Message-ID: <54EDC024.2040804@i2se.com> (raw)
In-Reply-To: <1424864719-3390-4-git-send-email-ezequiel.garcia@imgtec.com>
Hi,
[adding devicetree list]
Am 25.02.2015 um 12:45 schrieb Ezequiel Garcia:
> This commit introduces a new eFuse subsystem stub to hold all the eFuse-like
> device drivers. This will be used to host the currently supported Tegra
> eFuse driver, and will allow to add support for other platforms as well.
as i mentioned in the old discussion it would be nice to keep drivers
and devicetree binding documentation consistent.
So how about renaming?
Documentation/devicetree/bindings/fuse/ ->
Documentation/devicetree/bindings/efuse/
Best regards
Stefan
next prev parent reply other threads:[~2015-02-25 12:29 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 11:45 [PATCH 0/7] New eFuse subsystem Ezequiel Garcia
2015-02-25 11:45 ` Ezequiel Garcia
2015-02-25 11:45 ` [PATCH 1/7] soc: tegra: Add missing include linux/types.h Ezequiel Garcia
2015-02-25 11:45 ` Ezequiel Garcia
2015-02-25 11:45 ` [PATCH 2/7] soc: tegra: Move the fuse header to a separate directory Ezequiel Garcia
2015-02-25 11:45 ` Ezequiel Garcia
2015-02-25 11:45 ` [PATCH 3/7] drivers: Introduce new eFuse subsystem stub Ezequiel Garcia
2015-02-25 11:45 ` Ezequiel Garcia
2015-02-25 12:29 ` Stefan Wahren [this message]
2015-02-25 12:29 ` Stefan Wahren
2015-02-25 12:29 ` Stefan Wahren
2015-02-28 15:45 ` Paul Bolle
2015-02-28 15:45 ` Paul Bolle
2015-02-25 11:45 ` [PATCH 4/7] efuse: Move Tegra efuse driver Ezequiel Garcia
2015-02-25 11:45 ` Ezequiel Garcia
2015-02-28 15:51 ` Paul Bolle
2015-02-28 15:51 ` Paul Bolle
2015-02-25 12:02 ` [PATCH 0/7] New eFuse subsystem Maxime Ripard
2015-02-25 12:02 ` Maxime Ripard
2015-02-25 12:30 ` Ezequiel Garcia
2015-02-25 12:30 ` Ezequiel Garcia
2015-02-25 13:12 ` James Hartley
2015-02-25 13:12 ` James Hartley
2015-02-25 15:15 ` Maxime Ripard
2015-02-25 15:15 ` Maxime Ripard
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=54EDC024.2040804@i2se.com \
--to=stefan.wahren@i2se.com \
--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 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.