Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1168567 > unrolled thread

Re: [PATCH v7 04/14] crypto: add a new driver for Marvell's CESA

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: [PATCH v7 04/14] crypto: add a new driver for Marvell's CESA Herbert Xu <herbert@gondor.apana.org.au> - 2015-06-19 08:50 +0200
    Re: [PATCH v7 04/14] crypto: add a new driver for Marvell's CESA Thomas Petazzoni <thomas.petazzoni@free-electrons.com> - 2015-06-19 10:30 +0200
      Re: [PATCH v7 04/14] crypto: add a new driver for Marvell's CESA Gregory CLEMENT <gregory.clement@free-electrons.com> - 2015-06-19 10:50 +0200
        Re: [PATCH v7 04/14] crypto: add a new driver for Marvell's CESA Herbert Xu <herbert@gondor.apana.org.au> - 2015-06-19 16:10 +0200

#1168567 — Re: [PATCH v7 04/14] crypto: add a new driver for Marvell's CESA

On Thu, Jun 18, 2015 at 03:46:20PM +0200, Boris Brezillon wrote:
>
> +	dram = mv_mbus_dram_info_nooverlap();

This doesn't compile because it hasn't made it into mainline yet.
I'm afraid this patch-set will have to wait until that happens.

Cheers,
-- 
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [next] | [standalone]

#1168605

Hello Herbert,

On Fri, 19 Jun 2015 14:42:56 +0800, Herbert Xu wrote:
> On Thu, Jun 18, 2015 at 03:46:20PM +0200, Boris Brezillon wrote:
> >
> > +	dram = mv_mbus_dram_info_nooverlap();
> 
> This doesn't compile because it hasn't made it into mainline yet.
> I'm afraid this patch-set will have to wait until that happens.

We have two options here:

 1/ We can ask the mach-mvebu maintainers to provide a branch with just
    the commit implementing mv_mbus_dram_info_nooverlap(), and you
    merge that branch into your tree as a dependency.

 2/ We temporarily revert back to using mv_mbus_dram_info(). For the
    vast majority of platforms, this is OK. It's only if you have 4 GB
    of RAM or more that it causes problem. And then we switch to
    mv_mbus_dram_info_nooverlap() as part of the -rc cycle.

(2) is probably easier. Herbert, what do you think?

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1168633

Hi Thomas, Herbert,

On 19/06/2015 10:24, Thomas Petazzoni wrote:
> Hello Herbert,
> 
> On Fri, 19 Jun 2015 14:42:56 +0800, Herbert Xu wrote:
>> On Thu, Jun 18, 2015 at 03:46:20PM +0200, Boris Brezillon wrote:
>>>
>>> +	dram = mv_mbus_dram_info_nooverlap();
>>
>> This doesn't compile because it hasn't made it into mainline yet.
>> I'm afraid this patch-set will have to wait until that happens.
> 
> We have two options here:
> 
>  1/ We can ask the mach-mvebu maintainers to provide a branch with just
>     the commit implementing mv_mbus_dram_info_nooverlap(), and you
>     merge that branch into your tree as a dependency.

For this option you can use the branch mvebu/drivers located at
 git://git.infradead.org/linux-mvebu.git.

In this branch there is the commit "bus: mvebu-mbus: add mv_mbus_dram_info_nooverlap()"
but not only this one because it depends also on fixes which have been
merged in this same branch.

This branch is immutable and have already been merged in arm-soc.

Thanks,

Gregory

> 
>  2/ We temporarily revert back to using mv_mbus_dram_info(). For the
>     vast majority of platforms, this is OK. It's only if you have 4 GB
>     of RAM or more that it causes problem. And then we switch to
>     mv_mbus_dram_info_nooverlap() as part of the -rc cycle.
> 
> (2) is probably easier. Herbert, what do you think?
> 
> Thomas
> 


-- 
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1168800

On Fri, Jun 19, 2015 at 10:40:15AM +0200, Gregory CLEMENT wrote:
> 
> For this option you can use the branch mvebu/drivers located at
>  git://git.infradead.org/linux-mvebu.git.
> 
> In this branch there is the commit "bus: mvebu-mbus: add mv_mbus_dram_info_nooverlap()"
> but not only this one because it depends also on fixes which have been
> merged in this same branch.

It looks like the parent of this changeset is already in the mainline
so it's literally just a single patch.  I'll try to pull it into
cryptodev.

Thanks,
-- 
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web