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=-10.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_CR_TRAILER, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=ham 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 18FCDC433B4 for ; Tue, 18 May 2021 21:36:16 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id EF6F261244 for ; Tue, 18 May 2021 21:36:15 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1352337AbhERVhd (ORCPT ); Tue, 18 May 2021 17:37:33 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39162 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S244028AbhERVhd (ORCPT ); Tue, 18 May 2021 17:37:33 -0400 Received: from mail-lj1-x233.google.com (mail-lj1-x233.google.com [IPv6:2a00:1450:4864:20::233]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8A4A3C061573 for ; Tue, 18 May 2021 14:36:14 -0700 (PDT) Received: by mail-lj1-x233.google.com with SMTP id o8so13237874ljp.0 for ; Tue, 18 May 2021 14:36:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=dn4EVgYJrZEh+NwmIsnwQyOdHzd0yPpGagCfbDkwtqA=; b=X0U/cWNHtr9rj18Ej6uRpSwMq9LAHrLwzRrt8j/1xbDDR3dC6q7f2BOTa7z06ry3vm zwoG7M3aOaXMrIxlPbLasgkIMRg/PI1A+Y+EqZmeTYuoeu8tvk9BJU7Pr/BM2NfzZBIz Myayrc2FepSptqNzp+HBnDzeek6r5xIk54DOvDeBARwJ4C9ixlkCXhDq3e+KjdrKr1Qx yLtrUgL/tSzUhh/pytENftLVRcYGI7BaMSq7zPh2WOw76vl83zo3FZ5dMQEpkehaGTeE txeRQlOs8FFEDhMX5xEQ4Z5SXxKQf77eCj24jNyG1DdYCMVU67lKpSbAO98GvYRUI8hs CmAw== 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=dn4EVgYJrZEh+NwmIsnwQyOdHzd0yPpGagCfbDkwtqA=; b=LzuVJhytSlIcib0Z+gczOkdvoo52BXnqMzzsWnh/hpXyaHFieSG1UkfrEORDaMNNCY iqHhJB1u161dHkZwGBqvFLZe9i5jJaT5BbWsgDu8ZlPsrnlSLupJrj2ppMa97cnXULpK XAvgRVZSmYLF4poxAjTK0WyTdIH8/xLVwHeXrtsu7L1QMBPOGRyba4nE5j5RmEjX/T+M MIy6UNWatBSAuQj5Gg8BweSJpZ/+aUkoCUkSmmV6EDeo4NoxegEis3XwKNqWbYrpKC65 kbhJCt2DcTwEwYJbc80YAzMTjC+w4X6fmkZlvxttNWIL5Oc4M16PzAitti/2u0VtpJuL PXqg== X-Gm-Message-State: AOAM530V++C/HC/sCPgoujQh5X6B31/yCYVeBKqVazKLpWBNed46lrvH 2EbJAR9O1hbAY7+EA+Qrr97sib4y/aCwPt6xVXPyDoHbQPM7LA== X-Google-Smtp-Source: ABdhPJxiiYCLgo6v1wkmf1ffz+9LT1EFC2e9HHWQhseZrXKs2+leqMj7P7SZn6RRYUWehbP2Y/PLl9VwzWnfzUL542U= X-Received: by 2002:a2e:90c7:: with SMTP id o7mr5685489ljg.368.1621373773064; Tue, 18 May 2021 14:36:13 -0700 (PDT) MIME-Version: 1.0 References: <20210505202618.2663889-1-clabbe@baylibre.com> <20210518011930.nywtcgualmsrx35v@gondor.apana.org.au> In-Reply-To: <20210518011930.nywtcgualmsrx35v@gondor.apana.org.au> From: Linus Walleij Date: Tue, 18 May 2021 23:36:01 +0200 Message-ID: Subject: Re: [PATCH 00/11] crypto: start to fix ixp4xx To: Herbert Xu Cc: Corentin Labbe , chohnstaedt@innominate.com, "David S. Miller" , Linux Crypto Mailing List , linux-kernel Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org On Tue, May 18, 2021 at 3:19 AM Herbert Xu wrote: > On Tue, May 18, 2021 at 01:53:56AM +0200, Linus Walleij wrote: > > On Wed, May 5, 2021 at 10:26 PM Corentin Labbe wrote: > > > > > Loading the ixp4xx crypto driver exhibits lots of error. > > > All algorithm fail selftests with different reasons. > > > This series start to fixes some of thoses problem. > > > > Excellent! Thanks for taking over this Corentin!! > > FWIW: > > Acked-by: Linus Walleij > > > > If I merge my 3 additional patches through ARM SoC > > will it work out or do I need to think about some clever > > merging strategy? > > Well if your patches don't touch the drivers/crypto then there > shouldn't be any conflicts. Sadly they do, it's these: https://lore.kernel.org/linux-crypto/20210510213634.600866-1-linus.walleij@linaro.org/ https://lore.kernel.org/linux-crypto/20210510213634.600866-2-linus.walleij@linaro.org/ https://lore.kernel.org/linux-crypto/20210510213634.600866-3-linus.walleij@linaro.org/ I guess we could turn it around: I see if I can apply these two on top of the crypto tree and resend then we hope there is no collision in the ARM SoC tree instead. I need to respin the series anyway so shall we try this? Yours, Linus Walleij