public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Jani Nikula <jani.nikula@intel.com>
Cc: Christian Kujau <lists@nerdbynature.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation/sphinx: do not warn about missing tools in 'make help'
Date: Wed, 3 Aug 2016 15:42:15 -0600	[thread overview]
Message-ID: <20160803154215.39d0cc5a@lwn.net> (raw)
In-Reply-To: <1470044225-20009-1-git-send-email-jani.nikula@intel.com>

On Mon,  1 Aug 2016 12:37:05 +0300
Jani Nikula <jani.nikula@intel.com> wrote:

> Simply move the dochelp rule outside of the HAVE_SPHINX check,
> overriding the .DEFAULT rule for HAVE_SPHINX=0.

I've applied this, will send it upward soonish.

Thanks,

jon

      reply	other threads:[~2016-08-03 22:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-28 22:05 Makefile.sphinx:17: The 'sphinx-build' command was not found Christian Kujau
2016-07-29 13:48 ` Jonathan Corbet
2016-08-01  9:34   ` Jani Nikula
2016-08-01  9:37     ` [PATCH] Documentation/sphinx: do not warn about missing tools in 'make help' Jani Nikula
2016-08-03 21:42       ` 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=20160803154215.39d0cc5a@lwn.net \
    --to=corbet@lwn.net \
    --cc=jani.nikula@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@nerdbynature.de \
    /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