linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 3/3] ARM: add support for bit sliced AES using NEON instructions
Date: Mon, 14 Oct 2013 16:28:26 +0100	[thread overview]
Message-ID: <20131014152826.GP25034@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20131014125019.GO25034@n2100.arm.linux.org.uk>

On Mon, Oct 14, 2013 at 01:50:19PM +0100, Russell King - ARM Linux wrote:
> On Mon, Oct 14, 2013 at 08:47:00PM +0800, Herbert Xu wrote:
> > On Mon, Oct 14, 2013 at 01:19:26PM +0100, Russell King - ARM Linux wrote:
> > > On Mon, Oct 14, 2013 at 08:10:21PM +0800, Herbert Xu wrote:
> > > > On Mon, Oct 14, 2013 at 01:08:37PM +0100, Russell King - ARM Linux wrote:
> > > > > On Mon, Oct 14, 2013 at 07:29:21PM +0800, Herbert Xu wrote:
> > > > > > On Sun, Oct 13, 2013 at 12:30:49PM +0100, Russell King - ARM Linux wrote:
> > > > > > > Herbert,
> > > > > > > 
> > > > > > > Could I have a git URL to pull the above commit please?
> > > > > > 
> > > > > > Russell, do you want me to revert this patch from cryptodev?
> > > > > > Otherwise I'm not quite sure what you want me to do here.
> > > > > 
> > > > > I'd like to pull a branch from you containing this commit to solve the
> > > > > build error I'm getting with my tree, so I can continue testing my tree.
> > > > > At the moment, this is an additional unnecessary cause of randconfig
> > > > > build failures.
> > > > 
> > > > I don't have a branch that contains just this patch so perhaps it
> > > > would be easiest if I just reverted it?
> > > 
> > > Well, I don't have it either.
> > 
> > Oh you were talking about the ablk_helper patch, and not some ARM
> > patch that sneaked into the crypto tree.
> > 
> > As it's a crypto driver that's being added then it should go
> > through the crypto tree.  If it depends on some ARM bits that's
> > only in linux-next then I could try to merge that, assuming the
> > underlying ARM tree is stable.
> 
> You're not listening to me.  I've had enough of trying to discuss this
> sensibly.  I'm reverting all of Ard's work, and my commit to fix up a
> missing .gitignore entry afterwards.  Congratuations.

Scrap that, I can't revert the merge resulting from the pull, because it
brought in everything between -rc1 and rc3, and git is trying to revert
everything in mainline between those two when I try and re-merge this
branch.

So I can't revert this.

  reply	other threads:[~2013-10-14 15:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-04 19:03 [PATCH v3 0/3] ARM: NEON based fast(er) AES in CBC/CTR/XTS modes Ard Biesheuvel
2013-10-04 19:03 ` [PATCH v3 1/3] ARM: pull in <asm/simd.h> from asm-generic Ard Biesheuvel
2013-10-04 19:03 ` [PATCH v3 2/3] ARM: move AES typedefs and function prototypes to separate header Ard Biesheuvel
     [not found] ` <1380913419-13296-4-git-send-email-ard.biesheuvel@linaro.org>
2013-10-13 10:03   ` [PATCH v3 3/3] ARM: add support for bit sliced AES using NEON instructions Russell King - ARM Linux
2013-10-13 10:21     ` Ard Biesheuvel
2013-10-13 11:14       ` Russell King - ARM Linux
2013-10-13 11:19         ` Ard Biesheuvel
2013-10-13 11:22           ` Russell King - ARM Linux
2013-10-13 11:28             ` Ard Biesheuvel
2013-10-13 11:30               ` Russell King - ARM Linux
2013-10-14 11:29                 ` Herbert Xu
2013-10-14 12:08                   ` Russell King - ARM Linux
2013-10-14 12:10                     ` Herbert Xu
2013-10-14 12:19                       ` Russell King - ARM Linux
2013-10-14 12:47                         ` Herbert Xu
2013-10-14 12:50                           ` Russell King - ARM Linux
2013-10-14 15:28                             ` Russell King - ARM Linux [this message]
2013-10-14 22:23                               ` Ard Biesheuvel

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=20131014152826.GP25034@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).