public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Petr Tesarik <petrtesarik@huaweicloud.com>
Cc: anton ivanov <anton.ivanov@cambridgegreys.com>,
	 Johannes Berg <johannes@sipsolutions.net>,
	 linux-um <linux-um@lists.infradead.org>,
	 linux-kernel <linux-kernel@vger.kernel.org>,
	 Roberto Sassu <roberto.sassu@huaweicloud.com>,
	 petr <petr@tesarici.cz>
Subject: Re: [PATCH RESEND 1/1] um: oops on accessing a non-present page in the vmalloc area
Date: Wed, 20 Mar 2024 15:09:37 +0100 (CET)	[thread overview]
Message-ID: <156343757.79841.1710943777684.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <6a62f534-463f-45c4-a5ea-2c1021cf45d4@huaweicloud.com>

----- Ursprüngliche Mail -----
> Von: "Petr Tesarik" <petrtesarik@huaweicloud.com>
>> Yes. I'm just way behind my maintainer schedule. :-/
> 
> Understood. Thank you for your reply.
> 
> By the way, are you looking for more people to help with the amount of work?

Yes, help is always welcome!
Johannes and Anton do already a great job but more maintenance power is always good.
You could help with reviewing patches, testing stuff, etc. :-)
It's not that UML itself is a lot of work, it's just that $dayjob is not UML related at all...

Thanks,
//richard

  reply	other threads:[~2024-03-20 14:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-23 14:04 [PATCH RESEND 1/1] um: oops on accessing a non-present page in the vmalloc area Petr Tesarik
2024-03-12 15:07 ` Petr Tesarik
2024-03-18 13:09   ` Petr Tesarik
2024-03-19 22:18     ` Richard Weinberger
2024-03-20 13:58       ` Petr Tesarik
2024-03-20 14:09         ` Richard Weinberger [this message]
2024-03-20 15:14           ` Anton Ivanov
2024-03-21  4:44 ` David Gow
2024-03-21 17:30   ` Petr Tesarik

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=156343757.79841.1710943777684.JavaMail.zimbra@nod.at \
    --to=richard@nod.at \
    --cc=anton.ivanov@cambridgegreys.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-um@lists.infradead.org \
    --cc=petr@tesarici.cz \
    --cc=petrtesarik@huaweicloud.com \
    --cc=roberto.sassu@huaweicloud.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