From: Jonathan Corbet <corbet@lwn.net>
To: Darren Hart <dvhart@infradead.org>
Cc: Lukas Wunner <lukas@wunner.de>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
dri-devel@lists.freedesktop.org,
platform-driver-x86@vger.kernel.org,
Seth Forshee <seth.forshee@canonical.com>,
Andreas Heider <andreas@meetr.de>,
Matthew Garrett <mjg59@srcf.ucam.org>,
Bernhard Froemel <froemel@vmars.tuwien.ac.at>,
Bruno Premont <bonbons@linux-vserver.org>,
Bruno Bierbaumer <bruno@bierbaumer.net>,
William Brown <william@blackhats.net.au>,
Pierre Moreau <pierre.morrow@free.fr>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH 1/1] apple-gmux: Add initial documentation
Date: Fri, 8 Jan 2016 09:49:22 -0700 [thread overview]
Message-ID: <20160108094922.7df36afa@lwn.net> (raw)
In-Reply-To: <20160104202140.GE26072@malice.jf.intel.com>
On Mon, 4 Jan 2016 12:21:40 -0800
Darren Hart <dvhart@infradead.org> wrote:
> Any concerns with this series? If not, I'll take it in via the pdx86 tree.
>
Well, it's built around the asciidoc patch, which isn't in the mainline
at this point. Should things go a different direction, that could force
some changes here; meanwhile, it won't build 100% as intended on most
systems. It's intelligible anyway, though, and it's good to have the
information there, so I won't resist too hard.
I've not had a real chance to look seriously at the asciidoc stuff yet;
too much time dealing with sick people, foreign health systems, and such.
Very soon, I hope.
jon
next prev parent reply other threads:[~2016-01-08 16:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 16:52 [PATCH 0/1] apple-gmux: Add initial documentation Lukas Wunner
2016-01-04 16:52 ` [PATCH 1/1] " Lukas Wunner
2016-01-04 20:21 ` Darren Hart
2016-01-08 16:49 ` Jonathan Corbet [this message]
2016-01-08 20:42 ` Daniel Vetter
2016-01-05 8:19 ` Bruno Prémont
2016-01-05 8:19 ` Bruno Prémont
2016-01-04 20:31 ` [PATCH 0/1] " Darren Hart
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=20160108094922.7df36afa@lwn.net \
--to=corbet@lwn.net \
--cc=andreas@meetr.de \
--cc=bonbons@linux-vserver.org \
--cc=bruno@bierbaumer.net \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=dvhart@infradead.org \
--cc=froemel@vmars.tuwien.ac.at \
--cc=linux-doc@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mjg59@srcf.ucam.org \
--cc=pierre.morrow@free.fr \
--cc=platform-driver-x86@vger.kernel.org \
--cc=seth.forshee@canonical.com \
--cc=william@blackhats.net.au \
/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.