From: Ard Biesheuvel <ard.biesheuvel@linaro.org> To: Brajeswar Ghosh <brajeswar.linux@gmail.com> Cc: Herbert Xu <herbert@gondor.apana.org.au>, "David S. Miller" <davem@davemloft.net>, Russell King <linux@armlinux.org.uk>, jrdr.linux@gmail.com, "open list:HARDWARE RANDOM NUMBER GENERATOR CORE" <linux-crypto@vger.kernel.org>, linux-arm-kernel <linux-arm-kernel@lists.infradead.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, sabyasachi.linux@gmail.com Subject: Re: [PATCH] arm/crypto/aes-ce-glue.c: Remove duplicate header Date: Tue, 6 Nov 2018 15:24:33 +0100 [thread overview] Message-ID: <CAKv+Gu-2-DkVCOzVb_dRqr=nfiaPuec5XQT9V7z3RxuBdd-k9g@mail.gmail.com> (raw) In-Reply-To: <20181106121614.GA1985@hp-pavilion-15-notebook-pc-brajeswar> On 6 November 2018 at 13:16, Brajeswar Ghosh <brajeswar.linux@gmail.com> wrote: > Remove asm/hwcap.h which is included more than once > > Signed-off-by: Brajeswar Ghosh <brajeswar.linux@gmail.com> Acked-by: Ard Biesheuvel <ard.biesheuvel@linaro.org> > --- > arch/arm/crypto/aes-ce-glue.c | 1 - > 1 file changed, 1 deletion(-) > > diff --git a/arch/arm/crypto/aes-ce-glue.c b/arch/arm/crypto/aes-ce-glue.c > index d0a9cec73707..5affb8482379 100644 > --- a/arch/arm/crypto/aes-ce-glue.c > +++ b/arch/arm/crypto/aes-ce-glue.c > @@ -10,7 +10,6 @@ > > #include <asm/hwcap.h> > #include <asm/neon.h> > -#include <asm/hwcap.h> > #include <crypto/aes.h> > #include <crypto/internal/simd.h> > #include <crypto/internal/skcipher.h> > -- > 2.17.1 >
WARNING: multiple messages have this Message-ID (diff)
From: ard.biesheuvel@linaro.org (Ard Biesheuvel) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH] arm/crypto/aes-ce-glue.c: Remove duplicate header Date: Tue, 6 Nov 2018 15:24:33 +0100 [thread overview] Message-ID: <CAKv+Gu-2-DkVCOzVb_dRqr=nfiaPuec5XQT9V7z3RxuBdd-k9g@mail.gmail.com> (raw) In-Reply-To: <20181106121614.GA1985@hp-pavilion-15-notebook-pc-brajeswar> On 6 November 2018 at 13:16, Brajeswar Ghosh <brajeswar.linux@gmail.com> wrote: > Remove asm/hwcap.h which is included more than once > > Signed-off-by: Brajeswar Ghosh <brajeswar.linux@gmail.com> Acked-by: Ard Biesheuvel <ard.biesheuvel@linaro.org> > --- > arch/arm/crypto/aes-ce-glue.c | 1 - > 1 file changed, 1 deletion(-) > > diff --git a/arch/arm/crypto/aes-ce-glue.c b/arch/arm/crypto/aes-ce-glue.c > index d0a9cec73707..5affb8482379 100644 > --- a/arch/arm/crypto/aes-ce-glue.c > +++ b/arch/arm/crypto/aes-ce-glue.c > @@ -10,7 +10,6 @@ > > #include <asm/hwcap.h> > #include <asm/neon.h> > -#include <asm/hwcap.h> > #include <crypto/aes.h> > #include <crypto/internal/simd.h> > #include <crypto/internal/skcipher.h> > -- > 2.17.1 >
next prev parent reply other threads:[~2018-11-06 23:50 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-11-06 12:16 [PATCH] arm/crypto/aes-ce-glue.c: Remove duplicate header Brajeswar Ghosh 2018-11-06 12:16 ` Brajeswar Ghosh 2018-11-06 14:24 ` Ard Biesheuvel [this message] 2018-11-06 14:24 ` Ard Biesheuvel 2018-11-06 14:24 ` Ard Biesheuvel 2018-11-16 6:18 ` Herbert Xu 2018-11-16 6:18 ` 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='CAKv+Gu-2-DkVCOzVb_dRqr=nfiaPuec5XQT9V7z3RxuBdd-k9g@mail.gmail.com' \ --to=ard.biesheuvel@linaro.org \ --cc=brajeswar.linux@gmail.com \ --cc=davem@davemloft.net \ --cc=herbert@gondor.apana.org.au \ --cc=jrdr.linux@gmail.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-crypto@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux@armlinux.org.uk \ --cc=sabyasachi.linux@gmail.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: linkBe 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.