From: Jonathan Corbet <corbet@lwn.net>
To: Peter Rosin <peda@axentia.se>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v2 0/2] mux: add overview and add to driver-api docs
Date: Thu, 21 Dec 2017 14:35:19 -0700 [thread overview]
Message-ID: <20171221143519.29ca0b97@lwn.net> (raw)
In-Reply-To: <20171212084633.532-1-peda@axentia.se>
On Tue, 12 Dec 2017 09:46:31 +0100
Peter Rosin <peda@axentia.se> wrote:
> Changes since v1:
> - added a short introductory paragraph to mux.rst
> - added an entry in MAINTAINERS.
>
> I forgot to mention that this applies on top of linux-next, I suspect
> there will be a trivial conflict with an SPDX conversion in mux/core.c
> on Linus upstream.
Sorry, I've had this just sitting here for a bit. Did you want me to take
both patches through the docs tree?
Thanks,
jon
next prev parent reply other threads:[~2017-12-21 21:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 8:46 [PATCH v2 0/2] mux: add overview and add to driver-api docs Peter Rosin
2017-12-12 8:46 ` [PATCH v2 1/2] mux: core: add a brief overview of the subsystem Peter Rosin
2017-12-12 8:46 ` [PATCH v2 2/2] docs: add mux docs to the driver-api docs Peter Rosin
2017-12-21 21:35 ` Jonathan Corbet [this message]
2017-12-21 22:11 ` [PATCH v2 0/2] mux: add overview and add to " Peter Rosin
2018-03-03 0:04 ` Peter Rosin
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=20171221143519.29ca0b97@lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
/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