From: Herbert Xu <herbert@gondor.apana.org.au>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Pascal Van Leeuwen <pvanleeuwen@verimatrix.com>,
Linux Crypto List <linux-crypto@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the crypto tree
Date: Mon, 18 Nov 2019 21:04:53 +0800 [thread overview]
Message-ID: <20191118130453.zioloc2qg66i6zae@gondor.apana.org.au> (raw)
In-Reply-To: <20191118191223.1b7c11a9@canb.auug.org.au>
On Mon, Nov 18, 2019 at 07:12:23PM +1100, Stephen Rothwell wrote:
>
> Unless Herbert wants to rebase the crypto tree (and I think this is not
> a good reason to do that), you should just consider this a learning
> experience. :-)
Right. It just so happens that I screwed up one of the patches
applied prior to the one in question so I had to rebase the tree.
The problem should now be fixed.
Thanks,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2019-11-18 13:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 23:19 linux-next: Fixes tag needs some work in the crypto tree Stephen Rothwell
2019-11-18 7:58 ` Pascal Van Leeuwen
2019-11-18 8:12 ` Stephen Rothwell
2019-11-18 13:04 ` Herbert Xu [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-02 21:03 Stephen Rothwell
2023-07-23 22:37 Stephen Rothwell
2023-07-24 1:54 ` Weili Qian
2022-09-18 22:12 Stephen Rothwell
2022-09-19 9:38 ` Cabiddu, Giovanni
2022-09-20 8:28 ` Herbert Xu
2022-04-18 21:17 Stephen Rothwell
2022-04-19 10:41 ` Giovanni Cabiddu
2021-07-18 22:13 Stephen Rothwell
2021-07-19 5:43 ` Stephan Mueller
2021-07-19 5:46 ` Herbert Xu
2021-04-11 22:28 Stephen Rothwell
2019-12-11 20:37 Stephen Rothwell
2019-08-02 6:02 Stephen Rothwell
2019-04-22 21:30 Stephen Rothwell
2019-04-23 4:08 ` Herbert Xu
2019-04-15 21:23 Stephen Rothwell
2019-04-16 1:05 ` Herbert Xu
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=20191118130453.zioloc2qg66i6zae@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=pvanleeuwen@verimatrix.com \
--cc=sfr@canb.auug.org.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.