From: joro@8bytes.org (Joerg Roedel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] dt-binding: correct the larb port offset defines for mt2701
Date: Mon, 22 Aug 2016 12:47:51 +0200 [thread overview]
Message-ID: <20160822104751.GA17198@8bytes.org> (raw)
In-Reply-To: <1470902828-32496-1-git-send-email-honghui.zhang@mediatek.com>
On Thu, Aug 11, 2016 at 04:07:08PM +0800, honghui.zhang at mediatek.com wrote:
> From: Honghui Zhang <honghui.zhang@mediatek.com>
>
> larb2 have 23 ports, the LARB3_PORT_OFFSET should be LARB2_PORT_OFFSET
> plus larb2's port number, it should be 44 instead of 43.
>
> Signed-off-by: Honghui Zhang <honghui.zhang@mediatek.com>
> ---
> include/dt-bindings/memory/mt2701-larb-port.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied, thanks.
prev parent reply other threads:[~2016-08-22 10:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-11 8:07 [PATCH] dt-binding: correct the larb port offset defines for mt2701 honghui.zhang at mediatek.com
2016-08-22 10:47 ` Joerg Roedel [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=20160822104751.GA17198@8bytes.org \
--to=joro@8bytes.org \
--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).