linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Christophe Leroy <christophe.leroy@csgroup.eu>,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-serial@vger.kernel.org,
	Randy Dunlap <rdunlap@infradead.org>,
	Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH 1/3] Documentation: devices.txt: Remove ttyIOC*
Date: Fri, 18 Aug 2023 23:22:15 +0200	[thread overview]
Message-ID: <2023081806-bobtail-donut-f0a3@gregkh> (raw)
In-Reply-To: <87il9cl00v.fsf@meer.lwn.net>

On Fri, Aug 18, 2023 at 11:42:56AM -0600, Jonathan Corbet wrote:
> Christophe Leroy <christophe.leroy@csgroup.eu> writes:
> 
> > IOC4 serial driver was removed, remove associated devices
> > from documentation.
> >
> > Fixes: a017ef17cfd8 ("tty/serial: remove the ioc4_serial driver")
> > Cc: Christoph Hellwig <hch@lst.de>
> > Signed-off-by: Christophe Leroy <christophe.leroy@csgroup.eu>
> > ---
> >  Documentation/admin-guide/devices.txt | 9 ---------
> >  1 file changed, 9 deletions(-)
> 
> This doesn't apply to docs-next, seemingly as the result of a change
> that went through Greg's tree, so these should follow the same path,
> methinks.

I'll be glad to take it, thanks.

greg k-h

      reply	other threads:[~2023-08-18 21:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-14  6:02 [PATCH 1/3] Documentation: devices.txt: Remove ttyIOC* Christophe Leroy
2023-08-14  6:02 ` [PATCH 2/3] Documentation: devices.txt: Remove ttySIOC* Christophe Leroy
2023-08-14  6:02 ` [PATCH 3/3] Documentation: devices.txt: Fix minors for ttyCPM* Christophe Leroy
2023-08-14 22:52   ` Randy Dunlap
2023-08-18 17:42 ` [PATCH 1/3] Documentation: devices.txt: Remove ttyIOC* Jonathan Corbet
2023-08-18 21:22   ` Greg Kroah-Hartman [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=2023081806-bobtail-donut-f0a3@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=christophe.leroy@csgroup.eu \
    --cc=corbet@lwn.net \
    --cc=hch@lst.de \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=rdunlap@infradead.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).