All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo@kernel.org>
To: Schrempf Frieder <frieder.schrempf@kontron.de>
Cc: Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <fabio.estevam@nxp.com>,
	NXP Linux Team <linux-imx@nxp.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	"boris.brezillon@bootlin.com" <boris.brezillon@bootlin.com>,
	"broonie@kernel.org" <broonie@kernel.org>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>
Subject: Re: [PATCH 0/5] Prepare devicetrees for the new FSL QSPI driver
Date: Sun, 16 Dec 2018 15:51:23 +0800	[thread overview]
Message-ID: <20181216075121.GH13243@dragon> (raw)
In-Reply-To: <937b0f34e3eb485aaae45cd649cdeb4f@kontron.de>

On Sat, Dec 15, 2018 at 10:04:55AM +0000, Schrempf Frieder wrote:
> I can confirm, that the series does only remove or add properties to the
> devicetree, that are currently not used by the driver. Therefore it won't break
> anything.

Okay, applied the series.

Shawn

WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo@kernel.org>
To: Schrempf Frieder <frieder.schrempf@kontron.de>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
	"boris.brezillon@bootlin.com" <boris.brezillon@bootlin.com>,
	"broonie@kernel.org" <broonie@kernel.org>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	NXP Linux Team <linux-imx@nxp.com>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <fabio.estevam@nxp.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 0/5] Prepare devicetrees for the new FSL QSPI driver
Date: Sun, 16 Dec 2018 15:51:23 +0800	[thread overview]
Message-ID: <20181216075121.GH13243@dragon> (raw)
In-Reply-To: <937b0f34e3eb485aaae45cd649cdeb4f@kontron.de>

On Sat, Dec 15, 2018 at 10:04:55AM +0000, Schrempf Frieder wrote:
> I can confirm, that the series does only remove or add properties to the
> devicetree, that are currently not used by the driver. Therefore it won't break
> anything.

Okay, applied the series.

Shawn

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2018-12-16  7:51 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-10 16:28 [PATCH 0/5] Prepare devicetrees for the new FSL QSPI driver Schrempf Frieder
2018-12-10 16:28 ` Schrempf Frieder
2018-12-10 16:28 ` [PATCH 1/5] arm64: dts: Remove unused properties from FSL QSPI driver nodes Schrempf Frieder
2018-12-10 16:28   ` Schrempf Frieder
2018-12-10 16:28 ` [PATCH 2/5] ARM: " Schrempf Frieder
2018-12-10 16:28   ` Schrempf Frieder
2018-12-10 16:28 ` [PATCH 4/5] arm64: dts: Add spi-[tx/rx]-bus-width for the FSL QSPI controller Schrempf Frieder
2018-12-10 16:28   ` Schrempf Frieder
2018-12-10 16:28 ` [PATCH 3/5] ARM: dts: imx6sx-sdb: Fix the reg properties for the FSL QSPI nodes Schrempf Frieder
2018-12-10 16:28   ` Schrempf Frieder
2018-12-10 16:28 ` [PATCH 5/5] ARM: dts: Add spi-[tx/rx]-bus-width for the FSL QSPI controller Schrempf Frieder
2018-12-10 16:28   ` Schrempf Frieder
2018-12-10 16:31 ` [PATCH 0/5] Prepare devicetrees for the new FSL QSPI driver Schrempf Frieder
2018-12-10 16:31   ` Schrempf Frieder
2018-12-13  9:45   ` Schrempf Frieder
2018-12-13  9:45     ` Schrempf Frieder
2018-12-14  0:42     ` Shawn Guo
2018-12-14  0:42       ` Shawn Guo
2018-12-15 10:04       ` AW: " Schrempf Frieder
2018-12-15 10:04         ` Schrempf Frieder
2018-12-16  7:51         ` Shawn Guo [this message]
2018-12-16  7:51           ` Shawn Guo

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=20181216075121.GH13243@dragon \
    --to=shawnguo@kernel.org \
    --cc=boris.brezillon@bootlin.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=fabio.estevam@nxp.com \
    --cc=frieder.schrempf@kontron.de \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=s.hauer@pengutronix.de \
    /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.