From: Oleksii Moisieiev <Oleksii_Moisieiev@epam.com>
To: Rob Herring <robh@kernel.org>
Cc: "robh+dt@kernel.org" <robh+dt@kernel.org>,
Sudeep Holla <sudeep.holla@arm.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Cristian Marussi <cristian.marussi@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] dt-bindings: Add vendor prefix for Xen hypervisor
Date: Thu, 10 Mar 2022 11:38:34 +0000 [thread overview]
Message-ID: <20220310113833.GA187897@EPUAKYIW015D> (raw)
In-Reply-To: <Yie5P/vcBz44QcPd@robh.at.kernel.org>
Hello,
On Tue, Mar 08, 2022 at 02:14:55PM -0600, Rob Herring wrote:
> On Mon, 07 Mar 2022 08:17:43 +0000, Oleksii Moisieiev wrote:
> > Xen is an open source stage-1 hypervisor.
> >
> > Signed-off-by: Oleksii Moisieiev <oleksii_moisieiev@epam.com>
> > ---
> > Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
> > 1 file changed, 2 insertions(+)
> >
>
> As 'xen' has been missing regardless of patch 2, I fixed up the commit
> message and applied, thanks!
So IIUC - this patch is already applied and I don't need to add it v3?
Best regards,
Oleksii.
next prev parent reply other threads:[~2022-03-10 11:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 8:17 [PATCH v2 0/2] dt-bindings: xen: Add xen,scmi-devid parameter for Oleksii Moisieiev
2022-03-07 8:17 ` [PATCH v2 1/2] dt-bindings: Add vendor prefix for Xen hypervisor Oleksii Moisieiev
2022-03-07 23:30 ` Stefano Stabellini
2022-03-08 20:14 ` Rob Herring
2022-03-10 11:38 ` Oleksii Moisieiev [this message]
2022-03-10 17:20 ` Stefano Stabellini
2022-03-07 8:17 ` [PATCH v2 2/2] dt-bindings: xen: Add xen,scmi-devid property description for SCMI Oleksii Moisieiev
2022-03-07 23:38 ` Stefano Stabellini
2022-03-08 20:13 ` Rob Herring
2022-03-16 16:46 ` Oleksii Moisieiev
2022-03-16 18:59 ` Sudeep Holla
2022-03-18 23:53 ` Stefano Stabellini
2022-03-22 11:12 ` Sudeep Holla
2022-03-22 19:21 ` Oleksii Moisieiev
2022-03-23 10:54 ` Sudeep Holla
2022-03-28 8:52 ` Oleksii Moisieiev
2022-04-12 22:42 ` Stefano Stabellini
2022-04-22 17:59 ` Sudeep Holla
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=20220310113833.GA187897@EPUAKYIW015D \
--to=oleksii_moisieiev@epam.com \
--cc=cristian.marussi@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=sstabellini@kernel.org \
--cc=sudeep.holla@arm.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