From: Richard Weinberger <richard@nod.at>
To: YueHaibing <yuehaibing@huawei.com>
Cc: Anton Ivanov <anton.ivanov@cambridgegreys.com>,
Jeff Dike <jdike@addtoit.com>,
kernel-janitors@vger.kernel.org, linux-um@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [-next] um: Remove duplicated include from vector_user.c
Date: Wed, 27 Feb 2019 09:37:15 +0100 [thread overview]
Message-ID: <5780390.ocBjdziHdJ@blindfold> (raw)
In-Reply-To: <3691363f-84b1-b5ab-8637-132fdc4cbd81@huawei.com>
Am Mittwoch, 27. Februar 2019, 06:46:35 CET schrieb YueHaibing:
>
> Friendly ping:
>
> Who can take this, please?
The winner takes it all. ;-)
Just kidding, Anton and I take care.
Thanks,
//richard
prev parent reply other threads:[~2019-02-27 8:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 3:12 [PATCH -next] um: Remove duplicated include from vector_user.c YueHaibing
2019-01-20 18:54 ` [-next] " Anton Ivanov
2019-02-27 5:46 ` YueHaibing
2019-02-27 8:37 ` Richard Weinberger [this message]
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=5780390.ocBjdziHdJ@blindfold \
--to=richard@nod.at \
--cc=anton.ivanov@cambridgegreys.com \
--cc=jdike@addtoit.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=yuehaibing@huawei.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