All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Randy Dunlap <rdunlap@infradead.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Linux Media Mailing List <linux-media@vger.kernel.org>,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	linux-usb@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH 1/2] docs: usb: remove some broken references
Date: Wed, 29 Jan 2020 10:18:49 +0100	[thread overview]
Message-ID: <20200129091849.GA3802307@kroah.com> (raw)
In-Reply-To: <20200129064535.GA3771222@kroah.com>

On Wed, Jan 29, 2020 at 07:45:35AM +0100, Greg Kroah-Hartman wrote:
> On Wed, Jan 29, 2020 at 07:41:46AM +0100, Mauro Carvalho Chehab wrote:
> > Em Tue, 28 Jan 2020 15:47:18 -0800
> > Randy Dunlap <rdunlap@infradead.org> escreveu:
> > 
> > > On 1/28/20 12:42 PM, Jonathan Corbet wrote:
> > > > On Tue, 28 Jan 2020 07:41:00 +0100
> > > > Mauro Carvalho Chehab <mchehab+huawei@kernel.org> wrote:
> > > >   
> > > >> It seems that some files were removed from USB documentation.
> > > >>
> > > >> Update the links accordingly.
> > > >>
> > > >> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>  
> > > > 
> > > > Applied, thanks.
> > > > 
> > > > jon  
> > > 
> > > This warning has been around for quite awhile now:
> > > 
> > > lnx-55/Documentation/usb/text_files.rst:22: WARNING: Include file u'lnx/lnx-55/Documentation/usb/wusb-cbaf' not found or reading it failed
> > > 
> > > Looks like it has been moved to drivers/staging/wusbcore/Documentation/wusb-cbaf.
> > 
> > From the log of the patch that moved it:
> > 
> >   commit 71ed79b0e4be0db254640c3beb9a1a0316eb5f61
> >   Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> >   Date:   Tue Aug 6 12:15:09 2019 +0200
> > 
> >     USB: Move wusbcore and UWB to staging as it is obsolete
> >     
> >     The UWB and wusbcore code is long obsolete, so let us just move the code
> >     out of the real part of the kernel and into the drivers/staging/
> >     location with plans to remove it entirely in a few releases.
> >     
> >     Link: https://lore.kernel.org/r/20190806101509.GA11280@kroah.com
> >     Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > 
> > The plan seems to remove it in the future.
> > 
> > In any case, it makes sense to remove the broken link from the 
> > documentation.
> 
> Yes, please just remove it, that code is about to go away in the
> 5.6-rc1.

Oops, not yet, in 5.7-rc1.

      reply	other threads:[~2020-01-29  9:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-28  6:41 [PATCH 1/2] docs: usb: remove some broken references Mauro Carvalho Chehab
2020-01-28  6:41 ` [PATCH 2/2] docs: filesystems: add overlayfs to index.rst Mauro Carvalho Chehab
2020-01-28 20:42   ` Jonathan Corbet
2020-01-28 20:42 ` [PATCH 1/2] docs: usb: remove some broken references Jonathan Corbet
2020-01-28 23:47   ` Randy Dunlap
2020-01-29  6:41     ` Mauro Carvalho Chehab
2020-01-29  6:45       ` Greg Kroah-Hartman
2020-01-29  9:18         ` 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=20200129091849.GA3802307@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=mchehab@infradead.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 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.