linux-ia64.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frank Scheiner <frank.scheiner@web.de>
To: "Tomáš Glozar" <tglozar@gmail.com>,
	linux-ia64@vger.kernel.org, linux-arch@vger.kernel.org
Cc: debian-ia64 <debian-ia64@lists.debian.org>, ia64@gentoo.org
Subject: Re: ia64 maintainership (resend)
Date: Sun, 24 Sep 2023 19:31:35 +0200	[thread overview]
Message-ID: <273eb7ed-9897-2350-946e-989f586580bc@web.de> (raw)
In-Reply-To: <CAHtyXDfvS4OYLjOqALy74vR4w9DOFjJ9z8UOFeDpyjv7_PHNXw@mail.gmail.com>

Dear Tomas,

On 24.09.23 19:20, Tomáš Glozar wrote:
> Hello linux-ia64,
> 
> I noticed following the news of the proposal to remove ia64 from the
> kernel that the architecture has no maintainer. I'd be happy to
> volunteer to maintain the architecture, should the decision of removal
> be reversed.
> 
> I'm not the ideal candidate, since I never contributed anything to the
> code, but I have an Itanium machine running Linux to test on, some
> spare time, and I've contributed a few patches as a part of my job of
> kernel developer at Red Hat.
> 
> I'm also a contributor to T2 SDE, a source-based community Linux
> distribution supporting various architectures including Alpha, HP
> PA-RISC, and Itanium. I have interest in the architecture, having done
> some experiments on it with code performance.
> 
> Tomas Glozar
> 
> PS: Original email got sent in multipart format by mistake, re-sending
> as plain text, sorry about that.

Great! I'd be happy to support you with my kernel testing.

Also CCing this to Debian's and Gentoo's ia64 lists.

Cheers,
Frank

  reply	other threads:[~2023-09-24 17:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-24 17:20 ia64 maintainership (resend) Tomáš Glozar
2023-09-24 17:31 ` Frank Scheiner [this message]
2023-10-30 18:54 ` Tomáš Glozar

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=273eb7ed-9897-2350-946e-989f586580bc@web.de \
    --to=frank.scheiner@web.de \
    --cc=debian-ia64@lists.debian.org \
    --cc=ia64@gentoo.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=tglozar@gmail.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).