From: Johannes Berg <johannes@sipsolutions.net>
To: Pengpeng Hou <pengpeng@iscas.ac.cn>,
Richard Weinberger <richard@nod.at>,
Anton Ivanov <anton.ivanov@cambridgegreys.com>
Cc: linux-um@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] um: vector: reject interface specifications with too many arguments
Date: Fri, 17 Apr 2026 10:07:20 +0200 [thread overview]
Message-ID: <453f5e190ee7bc03c5e9c6326982559e40bed0ab.camel@sipsolutions.net> (raw)
In-Reply-To: <20260417073704.1817-1-pengpeng@iscas.ac.cn>
On Fri, 2026-04-17 at 15:37 +0800, Pengpeng Hou wrote:
>
> Fixes: 49da7e64f33e ("High Performance UML Vector Network Driver")
>
> Signed-off-by: Pengpeng Hou <pengpeng@iscas.ac.cn>
There should be no blank line here.
johannes
prev parent reply other threads:[~2026-04-17 8:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-17 7:37 [PATCH] um: vector: reject interface specifications with too many arguments Pengpeng Hou
2026-04-17 8:07 ` Johannes Berg [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=453f5e190ee7bc03c5e9c6326982559e40bed0ab.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=anton.ivanov@cambridgegreys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=pengpeng@iscas.ac.cn \
--cc=richard@nod.at \
/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