kernel-janitors.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
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:02:00 +0000	[thread overview]
Message-ID: <20201211190200.GF25974@zn.tnic> (raw)
In-Reply-To: <CAKXUXMzZ7ejn1JrznDP6d7dk8tSsTznBO+423NAwf_nYsix=_w@mail.gmail.com>

On Fri, Dec 11, 2020 at 07:55:50PM +0100, Lukas Bulwahn wrote:
> 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.

Well, after I review it, I probably should know what the priority is,
right?

> If that comment disturbs you, please ignore it.

I was just wondering why you're writing something which is not really
needed. Notes under "---" are usually used to clarify aspects of the
patch handling, versioning, etc.

Thx.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

      reply	other threads:[~2020-12-11 19:02 UTC|newest]

Thread overview: 4+ 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
2020-12-11 19:02     ` Borislav Petkov [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=20201211190200.GF25974@zn.tnic \
    --to=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas.bulwahn@gmail.com \
    --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).