From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Grant Likely <grant.likely@linaro.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Linux-sh list <linux-sh@vger.kernel.org>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Nobuhiro Iwamatsu <nobuhiro.iwamatsu.yj@renesas.com>,
Rob Landley <rob@landley.net>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Subject: Re: [PATCH v3] sh_eth: add device tree support
Date: Thu, 06 Feb 2014 11:52:07 +0000 [thread overview]
Message-ID: <52F37767.20607@cogentembedded.com> (raw)
In-Reply-To: <CAMuHMdUrAJOTvUPZXVVK3ZSWL1BhE=uiZq0Yxp8XQuRaAxYnKw@mail.gmail.com>
Hello.
On 06-02-2014 12:16, Geert Uytterhoeven wrote:
>> +- reg: offset and length of (1) the E-DMAC/feLic register block (required),
>> + (2) the TSU register block (optional).
> As there can be 2 regions, have you considered reg-names?
I've been asked already, and so considered them and found them unneeded.
> Gr{oetje,eeting}s,
> Geert
WBR, Sergei
WARNING: multiple messages have this Message-ID (diff)
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Grant Likely <grant.likely@linaro.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Linux-sh list <linux-sh@vger.kernel.org>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Nobuhiro Iwamatsu <nobuhiro.iwamatsu.yj@renesas.com>,
Rob Landley <rob@landley.net>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Subject: Re: [PATCH v3] sh_eth: add device tree support
Date: Thu, 06 Feb 2014 15:52:07 +0400 [thread overview]
Message-ID: <52F37767.20607@cogentembedded.com> (raw)
In-Reply-To: <CAMuHMdUrAJOTvUPZXVVK3ZSWL1BhE=uiZq0Yxp8XQuRaAxYnKw@mail.gmail.com>
Hello.
On 06-02-2014 12:16, Geert Uytterhoeven wrote:
>> +- reg: offset and length of (1) the E-DMAC/feLic register block (required),
>> + (2) the TSU register block (optional).
> As there can be 2 regions, have you considered reg-names?
I've been asked already, and so considered them and found them unneeded.
> Gr{oetje,eeting}s,
> Geert
WBR, Sergei
next prev parent reply other threads:[~2014-02-06 11:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 22:58 [PATCH v3] sh_eth: add device tree support Sergei Shtylyov
2014-02-05 23:58 ` Sergei Shtylyov
2014-02-06 8:16 ` Geert Uytterhoeven
2014-02-06 8:16 ` Geert Uytterhoeven
2014-02-06 11:52 ` Sergei Shtylyov [this message]
2014-02-06 11:52 ` Sergei Shtylyov
2014-02-07 1:29 ` Simon Horman
2014-02-07 1:29 ` Simon Horman
2014-02-07 13:05 ` Sergei Shtylyov
2014-02-07 13:05 ` Sergei Shtylyov
2014-02-11 16:08 ` Laurent Pinchart
2014-02-11 16:08 ` Laurent Pinchart
2014-02-15 0:03 ` Sergei Shtylyov
2014-02-15 1:03 ` Sergei Shtylyov
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=52F37767.20607@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=geert@linux-m68k.org \
--cc=grant.likely@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-doc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nobuhiro.iwamatsu.yj@renesas.com \
--cc=pawel.moll@arm.com \
--cc=rob@landley.net \
--cc=robh+dt@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.