From: Ivan Bornyakov <i.bornyakov@metrotek.ru>
To: linux-kernel@vger.kernel.org
Cc: Ivan Bornyakov <i.bornyakov@metrotek.ru>,
Moritz Fischer <mdf@kernel.org>, Wu Hao <hao.wu@intel.com>,
Xu Yilun <yilun.xu@intel.com>, Tom Rix <trix@redhat.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor.dooley@microchip.com>,
Vladimir Georgiev <v.georgiev@metrotek.ru>,
system@metrotek.ru, linux-fpga@vger.kernel.org,
devicetree@vger.kernel.org
Subject: [PATCH v3 0/2] replace Ivan Bornyakov maintainership
Date: Sat, 29 Apr 2023 13:48:36 +0300 [thread overview]
Message-ID: <20230429104838.5064-1-i.bornyakov@metrotek.ru> (raw)
As I'm leaving Metrotek, hand over my maintainership duties to Vladimir.
ChangeLog:
v1:
https://lore.kernel.org/lkml/20230426073519.9167-1-i.bornyakov@metrotek.ru/
v2:
https://lore.kernel.org/lkml/20230428140150.2592-1-i.bornyakov@metrotek.ru/
* instead of replacing my Metrotek email to a shared Metrotek System
Team mailbox, assign Vladimir to my former maintainership.
v3:
* replace Vladimir's "Signed-off-by" with "Acked-by"
* add Conor's "Acked-by" form v2
Ivan Bornyakov (2):
MAINTAINERS: update Microchip MPF FPGA reviewers
dt-bindings: fpga: replace Ivan Bornyakov maintainership
Documentation/devicetree/bindings/fpga/lattice,sysconfig.yaml | 2 +-
.../devicetree/bindings/fpga/microchip,mpf-spi-fpga-mgr.yaml | 2 +-
MAINTAINERS | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
--
2.40.0
next reply other threads:[~2023-04-29 10:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-29 10:48 Ivan Bornyakov [this message]
2023-04-29 10:48 ` [PATCH v3 1/2] MAINTAINERS: update Microchip MPF FPGA reviewers Ivan Bornyakov
2023-05-04 11:34 ` Xu Yilun
2023-05-04 10:25 ` Vladimir Georgiev
2023-05-06 9:57 ` Xu Yilun
2023-04-29 10:48 ` [PATCH v3 2/2] dt-bindings: fpga: replace Ivan Bornyakov maintainership Ivan Bornyakov
2023-05-04 13:32 ` Vladimir Georgiev
2023-05-05 20:20 ` Rob Herring
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=20230429104838.5064-1-i.bornyakov@metrotek.ru \
--to=i.bornyakov@metrotek.ru \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=hao.wu@intel.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=robh+dt@kernel.org \
--cc=system@metrotek.ru \
--cc=trix@redhat.com \
--cc=v.georgiev@metrotek.ru \
--cc=yilun.xu@intel.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 read-only IMAP folder(s) and NNTP newsgroup(s).