From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS, URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id CAE69C282DA for ; Fri, 1 Feb 2019 07:39:09 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 9B492204EC for ; Fri, 1 Feb 2019 07:39:09 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=linux-foundation.org header.i=@linux-foundation.org header.b="WHoUDOTj" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726330AbfBAHiT (ORCPT ); Fri, 1 Feb 2019 02:38:19 -0500 Received: from mail-lj1-f182.google.com ([209.85.208.182]:45655 "EHLO mail-lj1-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725831AbfBAHiT (ORCPT ); Fri, 1 Feb 2019 02:38:19 -0500 Received: by mail-lj1-f182.google.com with SMTP id s5-v6so4892663ljd.12 for ; Thu, 31 Jan 2019 23:38:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux-foundation.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=v9PwWNdYk99s1XiVFCbbI2TIH7NUhKU+WAIZzLBcrTY=; b=WHoUDOTjbKU//tqjtZ31mi3yl4meT6K9aA3LboDcQeezDQGNIdvTYH4eGqRcwnEVMD HOKtQTUlnk88vrfzzaJ0At3HoFMYDNoN8jdwcUe2eyvoPt5JPunAOyODkSppLPgxf7DD nKErCiFOxAYawx7qf0DlC7PpPtKVjsKhwpKbs= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=v9PwWNdYk99s1XiVFCbbI2TIH7NUhKU+WAIZzLBcrTY=; b=O4jGHtMtCYHYLRq2tlUhNm/oU6ojWCB6+mAfBBwFnRA3olsi8BWkm8vAENLkgMmvGD idDlAGqv4/tI4U4YEkJ4qrAodXaDIICYoluO+QdwjPg5t8It8skYxzpNNEBosQNLmd1K xI5nNE/jrizdNg/tnARKNObJ11IZ2sUITfaVKlTxhtYoYufXHbFgxm8EIuxwixskNtvS O459O8vaU1E6j+GbT5ZQTtBIxm8xA9xvynYHxKVbDPSiRxB/45K75GsT/C9oMtWH2lVd HJ1aXdZKjqrugz5EveI3GtumYE+KK9I7HhiAY64tNGrelZzFsUWGdkLFeJ9vjrfKakZ6 kfvA== X-Gm-Message-State: AJcUukcb5A4HK4mRd6PY8UsomGf8c1i7cmQb0Y85qAuE3rnp34Yw+VIm qpfDiglYgjAwyIg0OxuVMEnDprmdJpw= X-Google-Smtp-Source: ALg8bN7v9V38XySomiFDwURVrE6KIhYi9Lgg3XnsvDzbF7L6SQgQvseJnk7tAes4NKgal22QnOS7Hw== X-Received: by 2002:a2e:9849:: with SMTP id e9-v6mr30381771ljj.9.1549006696498; Thu, 31 Jan 2019 23:38:16 -0800 (PST) Received: from mail-lf1-f52.google.com (mail-lf1-f52.google.com. [209.85.167.52]) by smtp.gmail.com with ESMTPSA id v17-v6sm1133552ljg.32.2019.01.31.23.38.15 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 31 Jan 2019 23:38:15 -0800 (PST) Received: by mail-lf1-f52.google.com with SMTP id a8so4320639lfk.5 for ; Thu, 31 Jan 2019 23:38:15 -0800 (PST) X-Received: by 2002:a19:cbcc:: with SMTP id b195mr29545951lfg.117.1549006694740; Thu, 31 Jan 2019 23:38:14 -0800 (PST) MIME-Version: 1.0 References: <20171128230929.GA17783@gondor.apana.org.au> <20171222064931.GA27068@gondor.apana.org.au> <20180105073808.GA14405@gondor.apana.org.au> <20180212031702.GA26153@gondor.apana.org.au> <20180428080517.haxgpvqrwgotakyo@gondor.apana.org.au> <20180622145403.6ltjip7che227fuo@gondor.apana.org.au> <20180829033353.agnzxra3jk2r2mzg@gondor.apana.org.au> <20181116063146.e7a3mep3ghnfltxe@gondor.apana.org.au> <20181207061409.xflg423nknleuddw@gondor.apana.org.au> <20190118104006.ye5amhxkgd4xrbmc@gondor.apana.org.au> <20190201054204.ehl7u7aaqmkdh5b6@gondor.apana.org.au> In-Reply-To: <20190201054204.ehl7u7aaqmkdh5b6@gondor.apana.org.au> From: Linus Torvalds Date: Thu, 31 Jan 2019 23:37:58 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Crypto Fixes for 5.0 To: Herbert Xu , Konstantin Ryabitsev Cc: "David S. Miller" , Linux Kernel Mailing List , Linux Crypto Mailing List Content-Type: text/plain; charset="UTF-8" Sender: linux-crypto-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org On Thu, Jan 31, 2019 at 9:42 PM Herbert Xu wrote: > > This push fixes a bug in cavium/nitrox where the callback is invoked > prior to the DMA unmap. This is not so much a comment about the pull itself (which I did half an hour ago), as about the fact that it looks like the pr-tracker robot doesn't seem to trigger for your pull requests, even if they are cc'd to lkml. Maybe you don't care, but while I stopped doing the manual "ack" emails for pulls, I've continued to try to notice when some pull of mine doesn't get the attention of the pr-tracker. I've probably missed several cases of them... The reason seems to be that the pr-tracker bot only tracks pull requests from emails with one of - ^[GIT - ^[PULL - ^[PLEASE PULL in the subject line (case insensitive, afaik), and so your plain "Crypto Fixes for 5.0" doesn't trigger it. (My list of what triggers the pr-tracker bot may be old, I suspect Konstantin has ended up tweaking the bot more since the early descriptions he gave, so take the above more as a rough guide than any set-in-stone rules) Anyway, if you do care, maybe whatever script or workflow you use for pull requests could just add that "[GIT PULL]" to the subject line, and you'd get that automatic ack email when I've pulled and pushed out? Linus