On 2021/3/12 2:18 上午, Randy Dunlap wrote:
On 3/10/21 9:14 PM, Stephen Rothwell wrote:
Hi all,
Warning: Some of the branches in linux-next are still based on v5.12-rc1,
so please be careful if you are trying to bisect a bug.
News: if your -next included tree is based on Linus' tree tag
On Thu, Mar 11, 2021 at 10:51:14AM -0800, Randy Dunlap wrote:
> On 3/10/21 9:14 PM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Warning: Some of the branches in linux-next are still based on v5.12-rc1,
> > so please be careful if you are trying to bisect a bug.
> >
> > News: if your -next
On 11/03/2021 18:37, Randy Dunlap wrote:
> On 3/10/21 9:14 PM, Stephen Rothwell wrote:
>> Hi all,
>>
>> Warning: Some of the branches in linux-next are still based on v5.12-rc1,
>> so please be careful if you are trying to bisect a bug.
>>
>> News: if your -next included tree is based on Linus'
On 3/10/21 9:14 PM, Stephen Rothwell wrote:
> Hi all,
>
> Warning: Some of the branches in linux-next are still based on v5.12-rc1,
> so please be careful if you are trying to bisect a bug.
>
> News: if your -next included tree is based on Linus' tree tag
> v5.12-rc1{,-dontuse} (or somewhere
On 3/10/21 9:14 PM, Stephen Rothwell wrote:
> Hi all,
>
> Warning: Some of the branches in linux-next are still based on v5.12-rc1,
> so please be careful if you are trying to bisect a bug.
>
> News: if your -next included tree is based on Linus' tree tag
> v5.12-rc1{,-dontuse} (or somewhere
On 3/10/21 9:14 PM, Stephen Rothwell wrote:
> Hi all,
>
> Warning: Some of the branches in linux-next are still based on v5.12-rc1,
> so please be careful if you are trying to bisect a bug.
>
> News: if your -next included tree is based on Linus' tree tag
> v5.12-rc1{,-dontuse} (or somewhere
Hi all,
Warning: Some of the branches in linux-next are still based on v5.12-rc1,
so please be careful if you are trying to bisect a bug.
News: if your -next included tree is based on Linus' tree tag
v5.12-rc1{,-dontuse} (or somewhere between v5.11 and that tag), please
consider rebasing it onto
Hi all,
Changes since 20160310:
New tree: rpmsg
The tip tree gained a conflict against the pm tree.
The aio tree still had a build failure so I used the version from
next-20160111.
Non-merge commits (relative to Linus' tree): 10657
8209 files changed, 406492 insertions(+), 196211
Hi all,
Changes since 20160310:
New tree: rpmsg
The tip tree gained a conflict against the pm tree.
The aio tree still had a build failure so I used the version from
next-20160111.
Non-merge commits (relative to Linus' tree): 10657
8209 files changed, 406492 insertions(+), 196211
A little bit later, but thank you guys for fix it.
The issue seems happens just in BE machines, and using _GLOBAL instead
.globl seems fix it so build the correct vmx-crypto.ko. On LE it does
not happens.
On Thu, Mar 12, 2015 at 02:53:27PM +1100, Herbert Xu wrote:
> On Wed, Mar 11, 2015 at
Hi,
On 03/11/2015 05:51 PM, Guenter Roeck wrote:
> On Wed, Mar 11, 2015 at 04:35:58PM +1100, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20150310:
>>
>> New tree: drm-exynos
>>
>> The sound-asoc tree still had its build failure so I used the version from
>> next-20150306.
>>
>> The
A little bit later, but thank you guys for fix it.
The issue seems happens just in BE machines, and using _GLOBAL instead
.globl seems fix it so build the correct vmx-crypto.ko. On LE it does
not happens.
On Thu, Mar 12, 2015 at 02:53:27PM +1100, Herbert Xu wrote:
On Wed, Mar 11, 2015 at
Hi,
On 03/11/2015 05:51 PM, Guenter Roeck wrote:
On Wed, Mar 11, 2015 at 04:35:58PM +1100, Stephen Rothwell wrote:
Hi all,
Changes since 20150310:
New tree: drm-exynos
The sound-asoc tree still had its build failure so I used the version from
next-20150306.
The regulator tree lost its
On Wed, Mar 11, 2015 at 08:51:32PM -0700, Guenter Roeck wrote:
>
> Yes, this helps.
>
> Feel free to add
>
> Tested-by: Guenter Roeck
Thanks for testing and the quick feedback.
--
Email: Herbert Xu
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key:
On 03/11/2015 08:28 PM, Herbert Xu wrote:
On Wed, Mar 11, 2015 at 07:43:22PM -0700, Guenter Roeck wrote:
It looks like the perl scripts do run - I see the .S files, and I do see .o
files created.
But I still get the error.
Looking into the object files, I see
$ nm vmx-crypto.o | grep
On Wed, Mar 11, 2015 at 07:43:22PM -0700, Guenter Roeck wrote:
>
> It looks like the perl scripts do run - I see the .S files, and I do see .o
> files created.
> But I still get the error.
>
> Looking into the object files, I see
>
> $ nm vmx-crypto.o | grep aes_p8_cbc_encrypt
>
On 03/11/2015 06:23 PM, Herbert Xu wrote:
On Wed, Mar 11, 2015 at 08:47:17AM -0700, Guenter Roeck wrote:
Building powerpc:allmodconfig:
ERROR: ".aes_p8_cbc_encrypt" [drivers/crypto/vmx/vmx-crypto.ko] undefined!
ERROR: ".aes_p8_set_encrypt_key" [drivers/crypto/vmx/vmx-crypto.ko] undefined!
On Wed, Mar 11, 2015 at 08:47:17AM -0700, Guenter Roeck wrote:
>
> Building powerpc:allmodconfig:
>
> ERROR: ".aes_p8_cbc_encrypt" [drivers/crypto/vmx/vmx-crypto.ko] undefined!
> ERROR: ".aes_p8_set_encrypt_key" [drivers/crypto/vmx/vmx-crypto.ko] undefined!
> ERROR: ".aes_p8_set_decrypt_key"
On Wed, Mar 11, 2015 at 08:55:48AM -0700, Guenter Roeck wrote:
> On Wed, Mar 11, 2015 at 04:35:58PM +1100, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20150310:
> >
> > New tree: drm-exynos
> >
> > The sound-asoc tree still had its build failure so I used the version from
> >
On 11/03/2015 17:21, Simon Guinot wrote:
> On Wed, Mar 11, 2015 at 08:55:48AM -0700, Guenter Roeck wrote:
>> On Wed, Mar 11, 2015 at 04:35:58PM +1100, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Changes since 20150310:
>>>
>>> New tree: drm-exynos
>>>
>>> The sound-asoc tree still had its build
On Wed, Mar 11, 2015 at 04:35:58PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20150310:
>
> New tree: drm-exynos
>
> The sound-asoc tree still had its build failure so I used the version from
> next-20150306.
>
> The regulator tree lost its build failure.
>
> The tip tree
On Wed, Mar 11, 2015 at 04:35:58PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20150310:
>
> New tree: drm-exynos
>
> The sound-asoc tree still had its build failure so I used the version from
> next-20150306.
>
> The regulator tree lost its build failure.
>
> The tip tree
On Wed, Mar 11, 2015 at 04:35:58PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20150310:
>
> New tree: drm-exynos
>
> The sound-asoc tree still had its build failure so I used the version from
> next-20150306.
>
> The regulator tree lost its build failure.
>
> The tip tree
On Wed, Mar 11, 2015 at 04:35:58PM +1100, Stephen Rothwell wrote:
Hi all,
Changes since 20150310:
New tree: drm-exynos
The sound-asoc tree still had its build failure so I used the version from
next-20150306.
The regulator tree lost its build failure.
The tip tree gained a
On Wed, Mar 11, 2015 at 04:35:58PM +1100, Stephen Rothwell wrote:
Hi all,
Changes since 20150310:
New tree: drm-exynos
The sound-asoc tree still had its build failure so I used the version from
next-20150306.
The regulator tree lost its build failure.
The tip tree gained a
On 11/03/2015 17:21, Simon Guinot wrote:
On Wed, Mar 11, 2015 at 08:55:48AM -0700, Guenter Roeck wrote:
On Wed, Mar 11, 2015 at 04:35:58PM +1100, Stephen Rothwell wrote:
Hi all,
Changes since 20150310:
New tree: drm-exynos
The sound-asoc tree still had its build failure so I used the
On Wed, Mar 11, 2015 at 04:35:58PM +1100, Stephen Rothwell wrote:
Hi all,
Changes since 20150310:
New tree: drm-exynos
The sound-asoc tree still had its build failure so I used the version from
next-20150306.
The regulator tree lost its build failure.
The tip tree gained a
On Wed, Mar 11, 2015 at 08:55:48AM -0700, Guenter Roeck wrote:
On Wed, Mar 11, 2015 at 04:35:58PM +1100, Stephen Rothwell wrote:
Hi all,
Changes since 20150310:
New tree: drm-exynos
The sound-asoc tree still had its build failure so I used the version from
next-20150306.
On Wed, Mar 11, 2015 at 07:43:22PM -0700, Guenter Roeck wrote:
It looks like the perl scripts do run - I see the .S files, and I do see .o
files created.
But I still get the error.
Looking into the object files, I see
$ nm vmx-crypto.o | grep aes_p8_cbc_encrypt
0680 t
On Wed, Mar 11, 2015 at 08:51:32PM -0700, Guenter Roeck wrote:
Yes, this helps.
Feel free to add
Tested-by: Guenter Roeck li...@roeck-us.net
Thanks for testing and the quick feedback.
--
Email: Herbert Xu herb...@gondor.apana.org.au
Home Page: http://gondor.apana.org.au/~herbert/
PGP
On 03/11/2015 08:28 PM, Herbert Xu wrote:
On Wed, Mar 11, 2015 at 07:43:22PM -0700, Guenter Roeck wrote:
It looks like the perl scripts do run - I see the .S files, and I do see .o
files created.
But I still get the error.
Looking into the object files, I see
$ nm vmx-crypto.o | grep
On 03/11/2015 06:23 PM, Herbert Xu wrote:
On Wed, Mar 11, 2015 at 08:47:17AM -0700, Guenter Roeck wrote:
Building powerpc:allmodconfig:
ERROR: .aes_p8_cbc_encrypt [drivers/crypto/vmx/vmx-crypto.ko] undefined!
ERROR: .aes_p8_set_encrypt_key [drivers/crypto/vmx/vmx-crypto.ko] undefined!
ERROR:
On Wed, Mar 11, 2015 at 08:47:17AM -0700, Guenter Roeck wrote:
Building powerpc:allmodconfig:
ERROR: .aes_p8_cbc_encrypt [drivers/crypto/vmx/vmx-crypto.ko] undefined!
ERROR: .aes_p8_set_encrypt_key [drivers/crypto/vmx/vmx-crypto.ko] undefined!
ERROR: .aes_p8_set_decrypt_key
Hi all,
Changes since 20150310:
New tree: drm-exynos
The sound-asoc tree still had its build failure so I used the version from
next-20150306.
The regulator tree lost its build failure.
The tip tree gained a conflict against the usb-gadget-fixes tree.
The staging tree lost its build failure.
Hi all,
Changes since 20150310:
New tree: drm-exynos
The sound-asoc tree still had its build failure so I used the version from
next-20150306.
The regulator tree lost its build failure.
The tip tree gained a conflict against the usb-gadget-fixes tree.
The staging tree lost its build failure.
35 matches
Mail list logo
