All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Jonathan Corbet <corbet@lwn.net>, Borislav Petkov <bp@alien8.de>
Cc: x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Documentation/submitting-patches: Document RESEND tag on patches
Date: Tue, 1 Jun 2021 15:31:05 -0700	[thread overview]
Message-ID: <452a0c53-8dae-870b-fd7b-807ade28701c@infradead.org> (raw)
In-Reply-To: <87zgw98blq.fsf@meer.lwn.net>

On 6/1/21 3:27 PM, Jonathan Corbet wrote:
> Borislav Petkov <bp@alien8.de> writes:
> 
>> Wow, time flies. :-\
>>
>> A month and a half later, Jon, how about it?
> 
> Oops...somehow I missed the fact that there was something there for me
> to look at and respond to, sorry.
> 
> I've just read it through...  if it were me, I would find a way to
> reduce its bulk in the hope that people would actually read it; much of
> what's there is in coding-style.rst (or should be).  But it's not me,
> and if you want to keep it I won't whine (much).  Except about reverse
> fir tree, perhaps, but nobody listens to me on that...:)  I'd say
> package it up as a maintainer-guide entry and go for it.

Yes, as a maintainer-profile/guide/whatever, please,
for X86/tip.

Same for several other feedback comments on patches that
are destined for the tip tree.

thanks.
-- 
~Randy


  reply	other threads:[~2021-06-01 22:31 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-17 18:37 [PATCH] Documentation/submitting-patches: Document the SoB chain Borislav Petkov
2020-12-21 16:54 ` Jonathan Corbet
2020-12-22 13:05   ` [PATCH] Documentation/submitting-patches: Add blurb about backtraces in commit messages Borislav Petkov
2020-12-22 18:59     ` Sean Christopherson
2020-12-22 19:25       ` Borislav Petkov
2020-12-28 17:59         ` Sean Christopherson
2020-12-28 18:15           ` Borislav Petkov
2020-12-28 19:02             ` Sean Christopherson
2021-01-04 23:19     ` Jonathan Corbet
2021-01-05 10:48       ` Borislav Petkov
2021-02-02 15:43         ` Borislav Petkov
2021-02-04 21:20           ` Jonathan Corbet
2021-02-15 14:19 ` [PATCH] Documentation/submitting-patches: Extend commit message layout description Borislav Petkov
2021-02-25 11:40   ` Robert Richter
2021-03-01 22:10   ` Jonathan Corbet
2021-04-13 11:38 ` [PATCH] Documentation/submitting-patches: Document RESEND tag on patches Borislav Petkov
2021-04-13 21:02   ` Jonathan Corbet
2021-04-15  6:05     ` Borislav Petkov
2021-05-31 14:35       ` Borislav Petkov
2021-06-01 22:27         ` Jonathan Corbet
2021-06-01 22:31           ` Randy Dunlap [this message]
2021-06-01 22:37           ` Borislav Petkov

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=452a0c53-8dae-870b-fd7b-807ade28701c@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=bp@alien8.de \
    --cc=corbet@lwn.net \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.