linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: linux-doc@vger.kernel.org, Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH] docs/driver-api/miscellaneous: Remove kernel-doc of serial_core.c
Date: Mon, 21 Nov 2022 16:29:38 -0700	[thread overview]
Message-ID: <877czn9999.fsf@meer.lwn.net> (raw)
In-Reply-To: <46789578-5785-eed3-24e7-14712ab78b99@gmail.com>

Akira Yokosawa <akiyks@gmail.com> writes:

> On Mon, 21 Nov 2022 14:01:16 -0700, Jonathan Corbet wrote:
>> So the purpose of this backmerge would be just to get rid of a few
>> warnings in docs-next for the next few weeks?  Given the jaundiced eye
>> with which Linus looks at backmerges, I'm inclined to just wait and let
>> it all settle out during the merge window.  Is there any work that would
>> be impeded by not doing that merge now?
> I thought the backmerge might reduce your annoyance when test-building
> for the next merge window with Sphinx >=3.1.
> You call those dozes of warnings *a few*.
> Of course, I can wait. :-)

Hey, I raised two kids, I'm good at dealing with annoyance...:)

Thanks,

jon

      reply	other threads:[~2022-11-21 23:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-02 11:48 [PATCH] docs/driver-api/miscellaneous: Remove kernel-doc of serial_core.c Akira Yokosawa
2022-11-03  6:35 ` Jiri Slaby
2022-11-09 14:45 ` Akira Yokosawa
2022-11-21 13:46   ` Akira Yokosawa
2022-11-21 20:59     ` Jonathan Corbet
2022-11-21 21:01     ` Jonathan Corbet
2022-11-21 23:10       ` Akira Yokosawa
2022-11-21 23:29         ` Jonathan Corbet [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=877czn9999.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=akiyks@gmail.com \
    --cc=linux-doc@vger.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).