From: Jonathan Corbet <corbet@lwn.net>
To: Danilo Cesar Lemes de Paula <danilo.cesar@collabora.co.uk>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Stephan Mueller <smueller@chronox.de>,
Michal Marek <mmarek@suse.cz>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
Graham Whaley <graham.whaley@linux.intel.com>
Subject: Re: [PATCH] scripts/kernel-doc: Improve Markdown results
Date: Wed, 2 Sep 2015 16:15:20 +0200 [thread overview]
Message-ID: <20150902161520.45a14371@xps> (raw)
In-Reply-To: <55E5E70D.4050201@collabora.co.uk>
On Tue, 1 Sep 2015 14:57:33 -0300
Danilo Cesar Lemes de Paula <danilo.cesar@collabora.co.uk> wrote:
> Did you find time to check this patch? As you mentioned that you applied
> the Markdown support for the linux-next tree, this patch might be needed
> (maybe "wanted" is a better word).
Not quite what I said...I said I'd apply it right after the merge window
so it can sit in linux-next through the full cycle. It's a bit early to
be pushing 4.4 stuff into linux-next now...
Beyond that, I wasn't sure where things stand with fixes... Can you send
me a new patch set with this fix (and any others that might
exist) integrated in?
Thanks,
jon
next prev parent reply other threads:[~2015-09-02 14:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-21 19:39 [PATCH] scripts/kernel-doc: Improve Markdown results Danilo Cesar Lemes de Paula
2015-08-21 19:39 ` Danilo Cesar Lemes de Paula
2015-08-24 14:34 ` Graham Whaley
2015-08-24 14:34 ` Graham Whaley
2015-09-01 17:57 ` Danilo Cesar Lemes de Paula
2015-09-01 17:57 ` Danilo Cesar Lemes de Paula
2015-09-02 14:15 ` Jonathan Corbet [this message]
2015-09-04 17:53 ` Danilo Cesar Lemes de Paula
2015-09-04 20:39 ` Jonathan Corbet
2015-09-07 20:06 ` Danilo Cesar Lemes de Paula
2015-09-07 20:06 ` Danilo Cesar Lemes de Paula
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=20150902161520.45a14371@xps \
--to=corbet@lwn.net \
--cc=daniel.vetter@ffwll.ch \
--cc=danilo.cesar@collabora.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=graham.whaley@linux.intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=intel-gfx@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=rdunlap@infradead.org \
--cc=smueller@chronox.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 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.