From: Conor Dooley <conor@kernel.org>
To: Ivan Bornyakov <i.bornyakov@metrotek.ru>
Cc: linux-kernel@vger.kernel.org, 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: Re: [PATCH v2 0/2] replace Ivan Bornyakov maintainership
Date: Fri, 28 Apr 2023 17:55:52 +0100 [thread overview]
Message-ID: <20230428-marine-halogen-57d4b3c2ca0f@spud> (raw)
In-Reply-To: <20230428140150.2592-1-i.bornyakov@metrotek.ru>
[-- Attachment #1: Type: text/plain, Size: 483 bytes --]
On Fri, Apr 28, 2023 at 05:01:48PM +0300, Ivan Bornyakov wrote:
> As I'm leaving Metrotek, hand over my maintainership duties to Vladimir.
As I said yesterday, good luck!
> ChangeLog:
> v1:
> https://lore.kernel.org/lkml/20230426073519.9167-1-i.bornyakov@metrotek.ru/
> v2:
> * instead of replacing my Metrotek email to a shared Metrotek System
> Team mailbox, assign Vladimir to my former maintainership.
Acked-by: Conor Dooley <conor.dooley@microchip.com>
Thanks,
Conor.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-04-28 16:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 14:01 [PATCH v2 0/2] replace Ivan Bornyakov maintainership Ivan Bornyakov
2023-04-28 14:01 ` [PATCH v2 1/2] MAINTAINERS: update Microchip MPF FPGA reviewers Ivan Bornyakov
2023-04-28 14:01 ` [PATCH v2 2/2] dt-bindings: fpga: replace Ivan Bornyakov maintainership Ivan Bornyakov
2023-04-28 22:04 ` Rob Herring
2023-04-29 8:29 ` Ivan Bornyakov
2023-04-29 10:04 ` Conor Dooley
2023-05-04 11:32 ` Xu Yilun
2023-04-28 16:55 ` Conor Dooley [this message]
2023-04-28 17:19 ` [PATCH v2 0/2] " Ivan Bornyakov
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=20230428-marine-halogen-57d4b3c2ca0f@spud \
--to=conor@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=hao.wu@intel.com \
--cc=i.bornyakov@metrotek.ru \
--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 NNTP newsgroup(s).