All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Chancellor <natechancellor@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, Ben Hutchings <ben@decadent.org.uk>,
	Jonathan Corbet <corbet@lwn.net>,
	Valdis Kletnieks <valdis.kletnieks@vt.edu>,
	Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Subject: kernel-doc patches for 4.18
Date: Fri, 24 Aug 2018 10:40:00 -0700	[thread overview]
Message-ID: <20180824174000.GA25131@flashbox> (raw)

Hi Greg,

Arch Linux recently enabled building the kernel documentation in their
PKGBUILD, which turned my normally peaceful build into a spamfest of
unescaped braces warnings from Perl.

These are fixed upstream with the following two patches:

701b3a3c0ac4 ("PATCH scripts/kernel-doc")
673bb2dfc364 ("scripts/kernel-doc: Escape all literal braces in regexes")

Could they please be applied to 4.18? They should be clean cherry-picks.

Thanks!
Nathan

             reply	other threads:[~2018-08-24 21:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-24 17:40 Nathan Chancellor [this message]
2018-08-24 17:51 ` kernel-doc patches for 4.18 Jonathan Corbet
2018-08-24 19:14   ` 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=20180824174000.GA25131@flashbox \
    --to=natechancellor@gmail.com \
    --cc=ben@decadent.org.uk \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=mchehab+samsung@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=valdis.kletnieks@vt.edu \
    /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.