From: Jonathan Corbet <corbet@lwn.net>
To: "Stephan Müller" <smueller@chronox.de>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
linux-crypto@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v2 0/8] Conversion crypto API documentation to Sphinx
Date: Tue, 13 Dec 2016 16:40:01 -0700 [thread overview]
Message-ID: <20161213164001.63fd5645@lwn.net> (raw)
In-Reply-To: <3555336.Wm4L5bpP9y@positron.chronox.de>
On Tue, 13 Dec 2016 23:06:14 +0100
Stephan Müller <smueller@chronox.de> wrote:
> I am sorry, then I may have misunderstood you.
>
> I would think that Herbert agreed that you push the entire patch set through
> your tree, including the documentation changes to the crypto header files.
>
> I just did a patch on the parts that touch the crypto header files. All apply
> cleanly except patch 07/08 which has a 5 line hunk due to other changes, Is
> that hunk ok for you, it would be great if you could take it. If you do not
> like that hunk, we could push it through the cryptodev tree once rc-1 is out.
Clearly there was a bit of misunderstanding going around :)
I've applied the patch set to docs-next. Oddly I had no trouble with #7,
but #2 was badly mailer-mangled and took some work.
Anyway, it should make its way into linux-next; if there's no fireworks,
I'll endeavor to send it Linusward in time to avoid interfering with his
kitchen duties.
Sorry for the confusion,
jon
next prev parent reply other threads:[~2016-12-13 23:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 2:53 [PATCH v2 0/8] Conversion crypto API documentation to Sphinx Stephan Mueller
2016-10-21 2:54 ` [PATCH v2 1/8] crypto: doc - convert " Stephan Mueller
2016-10-21 2:57 ` [PATCH v2 2/8] crypto: doc - remove crypto API DocBook Stephan Mueller
2016-10-21 2:57 ` [PATCH v2 3/8] crypto: doc - fix source comments for Sphinx Stephan Mueller
2016-10-21 2:57 ` [PATCH v2 4/8] crypto: doc - fix separation of cipher / req API Stephan Mueller
2016-10-21 2:58 ` [PATCH v2 5/8] crypto: doc - add KPP documentation Stephan Mueller
2016-10-21 2:58 ` [PATCH v2 6/8] crypto: doc - remove crypto_alloc_ablkcipher Stephan Mueller
2016-10-21 2:59 ` [PATCH v2 7/8] crypto: doc - clarify AEAD memory structure Stephan Mueller
2016-10-21 3:00 ` [PATCH v2 8/8] crypto: doc - optimize compilation Stephan Mueller
2016-10-23 16:32 ` [PATCH v2 0/8] Conversion crypto API documentation to Sphinx Jonathan Corbet
2016-10-23 16:46 ` Stephan Mueller
2016-10-25 2:35 ` Herbert Xu
2016-12-13 21:25 ` Stephan Müller
2016-12-13 21:50 ` Jonathan Corbet
2016-12-13 22:06 ` Stephan Müller
2016-12-13 23:40 ` Jonathan Corbet [this message]
2016-12-14 7:01 ` Stephan Müller
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=20161213164001.63fd5645@lwn.net \
--to=corbet@lwn.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-doc@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).