From: Greg KH <gregkh@linuxfoundation.org>
To: Tadeusz Struk <tadeusz.struk@intel.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
Prarit Bhargava <prarit@redhat.com>,
Nikolay Aleksandrov <nikolay@redhat.com>,
bruce.w.allan@intel.com, qat-linux@intel.com,
naleksan@redhat.com, linux-crypto@vger.kernel.org,
davem@davemloft.net
Subject: Re: [PATCH v2 0/2] crypto: qat - Fix for invalid dma mapping and numa
Date: Mon, 17 Nov 2014 10:33:51 -0800 [thread overview]
Message-ID: <20141117183351.GA12343@kroah.com> (raw)
In-Reply-To: <546A2E62.3020401@intel.com>
On Mon, Nov 17, 2014 at 09:20:34AM -0800, Tadeusz Struk wrote:
> On 11/17/2014 08:59 AM, Greg KH wrote:
> > Because it showed up in Linus's tree _after_ 3.17.3-rc1 was released?
> > How can I go back in time?
>
> I thought it was already possible, no? :)
> So will it be in 3.17.4?
Possibly, if I get around to it, relax please...
greg "burried in patches" k-h
next prev parent reply other threads:[~2014-11-17 18:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 1:24 [PATCH v2 0/2] crypto: qat - Fix for invalid dma mapping and numa Tadeusz Struk
2014-10-14 1:24 ` [PATCH v2 1/2] crypto: qat - Prevent dma mapping zero length assoc data Tadeusz Struk
2014-10-14 1:24 ` [PATCH v2 2/2] crypto: qat - Enforce valid numa configuration Tadeusz Struk
2014-10-14 10:53 ` Prarit Bhargava
2014-10-14 14:50 ` Tadeusz Struk
2014-10-14 15:41 ` Prarit Bhargava
2014-10-14 17:18 ` Tadeusz Struk
2014-10-14 17:27 ` Prarit Bhargava
2014-10-14 17:32 ` Prarit Bhargava
2014-10-15 10:35 ` [PATCH v2 0/2] crypto: qat - Fix for invalid dma mapping and numa Nikolay Aleksandrov
2014-10-15 11:25 ` Prarit Bhargava
2014-10-15 16:24 ` Tadeusz Struk
2014-10-24 14:45 ` Herbert Xu
2014-11-17 15:43 ` Tadeusz Struk
2014-11-17 16:59 ` Greg KH
2014-11-17 17:20 ` Tadeusz Struk
2014-11-17 18:33 ` Greg KH [this message]
2014-12-05 18:34 ` Tadeusz Struk
2014-12-06 6:45 ` 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=20141117183351.GA12343@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bruce.w.allan@intel.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=naleksan@redhat.com \
--cc=nikolay@redhat.com \
--cc=prarit@redhat.com \
--cc=qat-linux@intel.com \
--cc=tadeusz.struk@intel.com \
/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).