From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, X86 ML <x86@kernel.org>,
"H . Peter Anvin" <hpa@zytor.com>,
Al Viro <viro@zeniv.linux.org.uk>,
kernel-janitors@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: ia32_setup_rt_frame(): propagate __user annotations properly
Date: Fri, 11 Dec 2020 19:55:50 +0100 [thread overview]
Message-ID: <CAKXUXMzZ7ejn1JrznDP6d7dk8tSsTznBO+423NAwf_nYsix=_w@mail.gmail.com> (raw)
In-Reply-To: <20201211184715.GE25974@zn.tnic>
On Fri, Dec 11, 2020 at 7:47 PM Borislav Petkov <bp@alien8.de> wrote:
>
> On Mon, Dec 07, 2020 at 01:41:41PM +0100, Lukas Bulwahn wrote:
> > Thomas, Ingo, Boris, please pick this minor non-urgent clean-up patch.
>
> Why?
>
> Isn't it obvious that when you send a patch to us, the final goal is for
> it to be applied. Eventually.
>
Yes, agree. Other maintainers noted that I should point out that the
patch is only a minor clean-up and it is not urgent to be considered.
So, I add this remark to make clear that it is not top priority to
apply just that the maintainers know.
You will sure review it eventually, and hopefully accept it then.
If that comment disturbs you, please ignore it.
Lukas
next prev parent reply other threads:[~2020-12-11 20:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 12:41 [PATCH] x86: ia32_setup_rt_frame(): propagate __user annotations properly Lukas Bulwahn
2020-12-11 18:47 ` Borislav Petkov
2020-12-11 18:55 ` Lukas Bulwahn [this message]
2020-12-11 19:02 ` Borislav Petkov
2020-12-11 18:54 ` [tip: x86/cleanups] x86/ia32_signal: Propagate __user annotation properly tip-bot2 for Lukas Bulwahn
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='CAKXUXMzZ7ejn1JrznDP6d7dk8tSsTznBO+423NAwf_nYsix=_w@mail.gmail.com' \
--to=lukas.bulwahn@gmail.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
--cc=x86@kernel.org \
/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 NNTP newsgroup(s).