From: Michal Simek <michal.simek@xilinx.com>
To: Mark Brown <broonie@kernel.org>, Michal Simek <monstr@monstr.eu>
Cc: LKML <linux-kernel@vger.kernel.org>, git <git@xilinx.com>,
Rob Herring <robh+dt@kernel.org>,
DTML <devicetree@vger.kernel.org>,
linux-arm <linux-arm-kernel@lists.infradead.org>,
<linux-spi@vger.kernel.org>
Subject: Re: [PATCH v2] dt-bindings: spi: zynq: Convert Zynq QSPI binding to yaml
Date: Thu, 11 Feb 2021 13:54:51 +0100 [thread overview]
Message-ID: <2421214b-0f7b-93a1-c718-f0b96caceafb@xilinx.com> (raw)
In-Reply-To: <20210211123907.GA5217@sirena.org.uk>
On 2/11/21 1:39 PM, Mark Brown wrote:
> On Thu, Feb 11, 2021 at 10:37:30AM +0100, Michal Simek wrote:
>> st 10. 2. 2021 v 11:10 odesílatel Michal Simek <michal.simek@xilinx.com> napsal:
>
>>> +description:
>>> + The Xilinx Zynq QSPI controller is used to access multi-bit serial flash
>>> + memory devices.
>
>> Applied.
>
> Doesn't really matter here but I would really expect subsystem binding
> documents to go through the subsystem tree.
Sorry about it. I will keep that in my mind for future.
Thanks,
Michal
WARNING: multiple messages have this Message-ID (diff)
From: Michal Simek <michal.simek@xilinx.com>
To: Mark Brown <broonie@kernel.org>, Michal Simek <monstr@monstr.eu>
Cc: DTML <devicetree@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-spi@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
git <git@xilinx.com>,
linux-arm <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2] dt-bindings: spi: zynq: Convert Zynq QSPI binding to yaml
Date: Thu, 11 Feb 2021 13:54:51 +0100 [thread overview]
Message-ID: <2421214b-0f7b-93a1-c718-f0b96caceafb@xilinx.com> (raw)
In-Reply-To: <20210211123907.GA5217@sirena.org.uk>
On 2/11/21 1:39 PM, Mark Brown wrote:
> On Thu, Feb 11, 2021 at 10:37:30AM +0100, Michal Simek wrote:
>> st 10. 2. 2021 v 11:10 odesílatel Michal Simek <michal.simek@xilinx.com> napsal:
>
>>> +description:
>>> + The Xilinx Zynq QSPI controller is used to access multi-bit serial flash
>>> + memory devices.
>
>> Applied.
>
> Doesn't really matter here but I would really expect subsystem binding
> documents to go through the subsystem tree.
Sorry about it. I will keep that in my mind for future.
Thanks,
Michal
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-02-11 13:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 10:10 [PATCH v2] dt-bindings: spi: zynq: Convert Zynq QSPI binding to yaml Michal Simek
2021-02-10 10:10 ` Michal Simek
2021-02-10 22:45 ` Rob Herring
2021-02-10 22:45 ` Rob Herring
2021-02-11 9:37 ` Michal Simek
2021-02-11 9:37 ` Michal Simek
2021-02-11 12:39 ` Mark Brown
2021-02-11 12:39 ` Mark Brown
2021-02-11 12:54 ` Michal Simek [this message]
2021-02-11 12:54 ` Michal Simek
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=2421214b-0f7b-93a1-c718-f0b96caceafb@xilinx.com \
--to=michal.simek@xilinx.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=git@xilinx.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=monstr@monstr.eu \
--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.