linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Fionnuala Gunter <fin@linux.vnet.ibm.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] drivers/crypto/nx: saves chaining value from co-processor
Date: Fri, 02 Aug 2013 17:16:56 -0500	[thread overview]
Message-ID: <1375481816.32477.22.camel@what-is-leg> (raw)
In-Reply-To: <1375480754.15999.42.camel@pasglop>

On Sat, 2013-08-03 at 07:59 +1000, Benjamin Herrenschmidt wrote:
> On Fri, 2013-08-02 at 16:55 -0500, Fionnuala Gunter wrote:
> > Sorry, I thought linuxppc-dev was the right tree since the patch is
> > for
> > a ppc driver and you've carried previous nx driver submissions
> > upstream. 
> > 
> > I want to submit to the proper place, so what is your preference?
> 
> Well, that's the right place if you want me to merge it, which seems to
> be what Marcelo is also expecting...

Please merge this patch, it fixes a hot bug.

> However I do wonder why is that expectation there in the first place and
> why aren't those handled by the crypto maintainer...

In the future I can submit patches to the crypto maintainer.

-Fin

  reply	other threads:[~2013-08-02 22:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-02 20:58 [PATCH] drivers/crypto/nx: saves chaining value from co-processor Fionnuala Gunter
2013-08-02 21:09 ` Benjamin Herrenschmidt
2013-08-02 21:55   ` Fionnuala Gunter
2013-08-02 21:59     ` Benjamin Herrenschmidt
2013-08-02 22:16       ` Fionnuala Gunter [this message]
2013-08-05  2:21         ` Michael Ellerman

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=1375481816.32477.22.camel@what-is-leg \
    --to=fin@linux.vnet.ibm.com \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@lists.ozlabs.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).