From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: torvalds@linux-foundation.org, konrad.wilk@oracle.com,
linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com,
roger.pau@citrix.com, jgross@suse.com, sstabellini@kernel.org,
hch@infradead.org
Subject: [PATCH] Mainternership changes.
Date: Fri, 17 Sep 2021 12:16:50 -0400 [thread overview]
Message-ID: <20210917161652.2431563-1-konrad.wilk@oracle.com> (raw)
Heya folks,
I am finding that I don't have enough time to be a responsive maintainer
as such I am handing it off.
MAINTAINERS | 11 ++++++-----
1 file changed, 6 insertions(+), 5 deletions(-)
Konrad Rzeszutek Wilk (2):
MAINTAINERS: Update SWIOTLB maintainership
MAINTAINERS: Update Xen-[PCI,SWIOTLB,Block] maintainership
next reply other threads:[~2021-09-17 16:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-17 16:16 Konrad Rzeszutek Wilk [this message]
2021-09-17 16:16 ` [PATCH 1/2] MAINTAINERS: Update SWIOTLB maintainership Konrad Rzeszutek Wilk
2021-09-17 16:16 ` [PATCH 2/2] MAINTAINERS: Update Xen-[PCI,SWIOTLB,Block] maintainership Konrad Rzeszutek Wilk
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=20210917161652.2431563-1-konrad.wilk@oracle.com \
--to=konrad.wilk@oracle.com \
--cc=hch@infradead.org \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=xen-devel@lists.xensource.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 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.