From: Greg KH <gregkh@linuxfoundation.org>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Jonathan Corbet <corbet@lwn.net>,
Masanari Iida <standby24x7@gmail.com>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
Markus Heiser <markus.heiser@darmarit.de>,
linux-usb@vger.kernel.org
Subject: Re: [PATCH v2] Documentation: typec.rst: Use literal-block element with ascii art
Date: Wed, 25 Apr 2018 16:00:03 +0200 [thread overview]
Message-ID: <20180425140003.GA23493@kroah.com> (raw)
In-Reply-To: <87604fcsa2.fsf@intel.com>
On Wed, Apr 25, 2018 at 04:47:01PM +0300, Jani Nikula wrote:
> On Fri, 06 Apr 2018, Heikki Krogerus <heikki.krogerus@linux.intel.com> wrote:
> > Using reStructuredText literal-block element with ascii-art.
> > That prevents the ascii art from being processed as
> > reStructuredText.
> >
> > Reported-by: Masanari Iida <standby24x7@gmail.com>
> > Fixes: bdecb33af34f ("usb: typec: API for controlling USB Type-C Multiplexers")
> > Signed-off-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
>
> Jon, this fixes a documentation build failure in v4.17-rc1. It's not
> just a warning, it's a complete fail. Our docs builder at 01.org is
> failing, apparently the same at kernel.org. Please pick it up soon.
This is in my tree, will go to Linus in a day or so.
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Jonathan Corbet <corbet@lwn.net>,
Masanari Iida <standby24x7@gmail.com>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
Markus Heiser <markus.heiser@darmarit.de>,
linux-usb@vger.kernel.org
Subject: [v2] Documentation: typec.rst: Use literal-block element with ascii art
Date: Wed, 25 Apr 2018 16:00:03 +0200 [thread overview]
Message-ID: <20180425140003.GA23493@kroah.com> (raw)
On Wed, Apr 25, 2018 at 04:47:01PM +0300, Jani Nikula wrote:
> On Fri, 06 Apr 2018, Heikki Krogerus <heikki.krogerus@linux.intel.com> wrote:
> > Using reStructuredText literal-block element with ascii-art.
> > That prevents the ascii art from being processed as
> > reStructuredText.
> >
> > Reported-by: Masanari Iida <standby24x7@gmail.com>
> > Fixes: bdecb33af34f ("usb: typec: API for controlling USB Type-C Multiplexers")
> > Signed-off-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
>
> Jon, this fixes a documentation build failure in v4.17-rc1. It's not
> just a warning, it's a complete fail. Our docs builder at 01.org is
> failing, apparently the same at kernel.org. Please pick it up soon.
This is in my tree, will go to Linus in a day or so.
thanks,
greg k-h
---
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Jonathan Corbet <corbet@lwn.net>,
Masanari Iida <standby24x7@gmail.com>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
Markus Heiser <markus.heiser@darmarit.de>,
linux-usb@vger.kernel.org
Subject: Re: [PATCH v2] Documentation: typec.rst: Use literal-block element with ascii art
Date: Wed, 25 Apr 2018 16:00:03 +0200 [thread overview]
Message-ID: <20180425140003.GA23493@kroah.com> (raw)
In-Reply-To: <87604fcsa2.fsf@intel.com>
On Wed, Apr 25, 2018 at 04:47:01PM +0300, Jani Nikula wrote:
> On Fri, 06 Apr 2018, Heikki Krogerus <heikki.krogerus@linux.intel.com> wrote:
> > Using reStructuredText literal-block element with ascii-art.
> > That prevents the ascii art from being processed as
> > reStructuredText.
> >
> > Reported-by: Masanari Iida <standby24x7@gmail.com>
> > Fixes: bdecb33af34f ("usb: typec: API for controlling USB Type-C Multiplexers")
> > Signed-off-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
>
> Jon, this fixes a documentation build failure in v4.17-rc1. It's not
> just a warning, it's a complete fail. Our docs builder at 01.org is
> failing, apparently the same at kernel.org. Please pick it up soon.
This is in my tree, will go to Linus in a day or so.
thanks,
greg k-h
next prev parent reply other threads:[~2018-04-25 14:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 12:41 [PATCH v2] Documentation: typec.rst: Use literal-block element with ascii art Heikki Krogerus
2018-04-06 12:41 ` Heikki Krogerus
2018-04-06 12:41 ` [v2] " Heikki Krogerus
2018-04-06 14:10 ` [PATCH v2] " Jani Nikula
2018-04-06 14:10 ` Jani Nikula
2018-04-06 14:10 ` [v2] " Jani Nikula
2018-04-25 13:47 ` [PATCH v2] " Jani Nikula
2018-04-25 13:47 ` Jani Nikula
2018-04-25 13:47 ` [v2] " Jani Nikula
2018-04-25 13:55 ` [PATCH v2] " Jonathan Corbet
2018-04-25 13:55 ` Jonathan Corbet
2018-04-25 13:55 ` [v2] " Jonathan Corbet
2018-04-25 14:00 ` Greg KH [this message]
2018-04-25 14:00 ` [PATCH v2] " Greg KH
2018-04-25 14:00 ` [v2] " Greg Kroah-Hartman
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=20180425140003.GA23493@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=corbet@lwn.net \
--cc=heikki.krogerus@linux.intel.com \
--cc=jani.nikula@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=markus.heiser@darmarit.de \
--cc=standby24x7@gmail.com \
/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.