linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Keiji Hayashibara <hayashibara.keiji@socionext.com>
To: broonie@kernel.org, robh+dt@kernel.org, mark.rutland@arm.com,
	yamada.masahiro@socionext.com, linux-spi@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Cc: stable@vger.kernel.org, masami.hiramatsu@linaro.org,
	jaswinder.singh@linaro.org, linux-kernel@vger.kernel.org,
	hayashibara.keiji@socionext.com
Subject: [PATCH v2 0/2] spi: fix incorrect property items
Date: Fri, 26 Oct 2018 14:58:43 +0900	[thread overview]
Message-ID: <1540533525-1816-1-git-send-email-hayashibara.keiji@socionext.com> (raw)

This series fixes incorrect property because it was different
from the actual.

The commit 71b8dfc691a3 ("spi: uniphier: re-add addressing properties")
is the updated patch, therefore, it must be applied after
the commit 7662d1dc17d4 ("spi: uniphier: fix incorrect property items").

Changes since v1:
- Add commit 71b8dfc691a3 ("spi: uniphier: re-add addressing properties")
  The addressing properties of #address-cells and #size-cells
  are back again.

Keiji Hayashibara (2):
  spi: uniphier: fix incorrect property items
  spi: uniphier: re-add addressing properties

 Documentation/devicetree/bindings/spi/spi-uniphier.txt | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

-- 
2.7.4


             reply	other threads:[~2018-10-26  5:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-26  5:58 Keiji Hayashibara [this message]
2018-10-26  5:58 ` [PATCH v2 1/2] spi: uniphier: fix incorrect property items Keiji Hayashibara
2018-10-26  5:58 ` [PATCH v2 2/2] spi: uniphier: re-add addressing properties Keiji Hayashibara
2018-10-30 21:46   ` Rob Herring
2018-11-05 12:01   ` Applied "spi: uniphier: re-add addressing properties" to the spi tree Mark Brown

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=1540533525-1816-1-git-send-email-hayashibara.keiji@socionext.com \
    --to=hayashibara.keiji@socionext.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jaswinder.singh@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=masami.hiramatsu@linaro.org \
    --cc=robh+dt@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=yamada.masahiro@socionext.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 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).