On Mon, Nov 17, 2014 at 07:43:08AM -0800, Tadeusz Struk wrote:
> On 10/24/2014 07:45 AM, Herbert Xu wrote:
> > On Wed, Oct 15, 2014 at 07:25:45AM -0400, Prarit Bhargava wrote:
> >>
> >>
> >> On 10/15/2014 06:35 AM, Nikolay Aleksandrov wrote:
> >>> On 14/10/14 03:24, Tadeusz Struk wrote:
> >>>> Hi,
> >>>> These two patches fix invalid (zero length) dma mapping and
> >>>> enforce numa configuration for maximum performance.
> >>>>
> >>>> Change log:
> >>>> v2 - Removed numa node calculation based bus number and use predefined
> >>>> functions instead.
> >>>>
> >>>> Signed-off-by: Tadeusz Struk <tadeusz.st...@intel.com>
> >>>> ---
> >>>>
> >>>> Tadeusz Struk (2):
> >>>>        crypto: qat - Prevent dma mapping zero length assoc data
> >>>>        crypto: qat - Enforce valid numa configuration
> >>>>
> >>>>
> >>>>   drivers/crypto/qat/qat_common/adf_accel_devices.h |    3 +-
> >>>>   drivers/crypto/qat/qat_common/adf_transport.c     |   12 +++++---
> >>>>   drivers/crypto/qat/qat_common/qat_algs.c          |    7 +++--
> >>>>   drivers/crypto/qat/qat_common/qat_crypto.c        |    8 +++--
> >>>>   drivers/crypto/qat/qat_dh895xcc/adf_admin.c       |    2 +
> >>>>   drivers/crypto/qat/qat_dh895xcc/adf_drv.c         |   32 
> >>>> ++++++++-------------
> >>>>   drivers/crypto/qat/qat_dh895xcc/adf_isr.c         |    2 +
> >>>>   7 files changed, 32 insertions(+), 34 deletions(-)
> >>>>
> >>>
> >>> I just gave a quick run of these patches and they seem to fix the NUMA 
> >>> issue and
> >>> the 0 length warnings.
> >>>
> >>> Tested-by: Nikolay Aleksandrov <niko...@redhat.com>
> >>
> >> Thanks Nik :)
> >>
> >> Reviewed-by: Prarit Bhargava <pra...@redhat.com>
> > 
> > Patch applied to crypto and I will push this to stable.
> 
> Hi Greg,
> Any idea why this didn't make it to 3.17.3?

Because it showed up in Linus's tree _after_ 3.17.3-rc1 was released?
How can I go back in time?

confused,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to