On 5/15/20 9:32 AM, Trond Myklebust wrote:
> Hi Randy,
>
> On Fri, 2020-05-15 at 08:28 -0700, Randy Dunlap wrote:
>> On 5/15/20 5:42 AM, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Changes since 20200514:
>>>
>>> -
>>> ---
>>
On Fri, 2020-05-15 at 16:32 +, Trond Myklebust wrote:
> Hi Randy,
>
> On Fri, 2020-05-15 at 08:28 -0700, Randy Dunlap wrote:
> > On 5/15/20 5:42 AM, Stephen Rothwell wrote:
> > > Hi all,
> > >
> > > Changes since 20200514:
> > >
> > > -
Hi Randy,
On Fri, 2020-05-15 at 08:28 -0700, Randy Dunlap wrote:
> On 5/15/20 5:42 AM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20200514:
> >
> > -
> > ---
>
> on i386:
>
> CC fs/nfs/fsinfo.o
> ../f
Hi all,
Changes since 20200514:
My fixes tree contains:
daacad4c457a ("device_cgroup: Fix RCU list debugging warning")
8c7062890c9c ("ipv6: Fix suspicious RCU usage warning in ip6mr")
5743dc1ff4f7 ("ipmr: Add lockdep expression to ipmr_for_each_table macro")
564b182eb1b8 ("ipmr: Fix RCU
Hi all,
Please do not add any v5.3 material to your linux-next included
trees/branches until after v5.2-rc1 has been released.
Changes since 20190514:
The thermal-soc tree lost its build failure but gained conflicts against
Linus' tree.
The akpm-current tree gained a conflict against the pidfd
Hi all,
News: I will not be doing any linux-next releases between Friday 18 May
and Friday 25 May inclusive.
Changes since 20180514:
New trees: drivers-x86-fixes
mmc-fixes
rtc-fixes
The kbuild tree gained a build failure for which I applied a patch.
The audit tree gained a conf
Hi all,
Changes since 20170512:
Non-merge commits (relative to Linus' tree): 508
569 files changed, 13787 insertions(+), 5574 deletions(-)
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/k
Hi all,
Changes since 20150514:
The rcu tree gained a conflict against the net-next tree.
The target-updates tree still had its build failure so I used the version
from next-20150511.
The akpm-current tree lost its build failure.
Non-merge commits (relative to Linus' tree): 4200
3935 files ch
Hi all,
Changes since 20140514:
My fixes tree contains:
powerpc/ppc64: Allow allmodconfig to build (finally !)
The gpio tree still had its build failure for which I reverted 2 commits.
The clk tree gained a conflict against the renesas tree.
The akpm-current tree lost its build failure
On Mon, May 20, 2013 at 12:09:45PM -0700, Tim Chen wrote:
> On Mon, 2013-05-20 at 19:47 +0800, Herbert Xu wrote:
>
> >
> > Nope this is still broken. We need to move the actual crct10dif
> > code into crypto/. I'll fix up the patch in the tree.
> >
> > Also I'm going to get rid of crc_t10dif_u
On Mon, 2013-05-20 at 19:47 +0800, Herbert Xu wrote:
>
> Nope this is still broken. We need to move the actual crct10dif
> code into crypto/. I'll fix up the patch in the tree.
>
> Also I'm going to get rid of crc_t10dif_update_lib function. If you
> still want to maintain the ordering you sh
On Mon, May 20, 2013 at 07:47:07PM +0800, Herbert Xu wrote:
> On Thu, May 16, 2013 at 11:03:32AM -0700, Tim Chen wrote:
> >
> > Need to also add select CRYPTO for CRC_T10DIF. Updated fix below:
> >
> >
> > Signed-off-by: Tim Chen
> > ---
> > diff --git a/crypto/Kconfig b/crypto/Kconfig
> > inde
On Thu, May 16, 2013 at 11:03:32AM -0700, Tim Chen wrote:
>
> Need to also add select CRYPTO for CRC_T10DIF. Updated fix below:
>
>
> Signed-off-by: Tim Chen
> ---
> diff --git a/crypto/Kconfig b/crypto/Kconfig
> index d1ca631..015df24 100644
> --- a/crypto/Kconfig
> +++ b/crypto/Kconfig
> @@ -
2013/5/17 Tim Chen :
> On Thu, 2013-05-16 at 09:59 -0700, Tim Chen wrote:
>> On Thu, 2013-05-16 at 09:22 +0200, Geert Uytterhoeven wrote:
>> > On Thu, May 16, 2013 at 5:57 AM, Xiong Zhou
>> > wrote:
>> > > --- a/crypto/Kconfig
>> > > +++ b/crypto/Kconfig
>> > > @@ -378,6 +378,7 @@ config CRYPTO_C
2013/5/16 Geert Uytterhoeven :
> On Thu, May 16, 2013 at 5:57 AM, Xiong Zhou wrote:
>> --- a/crypto/Kconfig
>> +++ b/crypto/Kconfig
>> @@ -378,6 +378,7 @@ config CRYPTO_CRC32_PCLMUL
>>
>> config CRYPTO_CRCT10DIF
>> tristate "CRCT10DIF algorithm"
>> + depends on CRC_T10DIF
>
> This i
On Thu, 2013-05-16 at 09:59 -0700, Tim Chen wrote:
> On Thu, 2013-05-16 at 09:22 +0200, Geert Uytterhoeven wrote:
> > On Thu, May 16, 2013 at 5:57 AM, Xiong Zhou wrote:
> > > --- a/crypto/Kconfig
> > > +++ b/crypto/Kconfig
> > > @@ -378,6 +378,7 @@ config CRYPTO_CRC32_PCLMUL
> > >
> > > config CR
On Thu, 2013-05-16 at 09:22 +0200, Geert Uytterhoeven wrote:
> On Thu, May 16, 2013 at 5:57 AM, Xiong Zhou wrote:
> > --- a/crypto/Kconfig
> > +++ b/crypto/Kconfig
> > @@ -378,6 +378,7 @@ config CRYPTO_CRC32_PCLMUL
> >
> > config CRYPTO_CRCT10DIF
> > tristate "CRCT10DIF algorithm"
> > +
On Thu, 2013-05-16 at 09:22 +0200, Geert Uytterhoeven wrote:
> On Thu, May 16, 2013 at 5:57 AM, Xiong Zhou wrote:
> > --- a/crypto/Kconfig
> > +++ b/crypto/Kconfig
> > @@ -378,6 +378,7 @@ config CRYPTO_CRC32_PCLMUL
> >
> > config CRYPTO_CRCT10DIF
> > tristate "CRCT10DIF algorithm"
> > +
On Thu, May 16, 2013 at 5:57 AM, Xiong Zhou wrote:
> --- a/crypto/Kconfig
> +++ b/crypto/Kconfig
> @@ -378,6 +378,7 @@ config CRYPTO_CRC32_PCLMUL
>
> config CRYPTO_CRCT10DIF
> tristate "CRCT10DIF algorithm"
> + depends on CRC_T10DIF
This is a library symbol, so "select CRC_T10DIF"?
On Wed, 15 May 2013, Randy Dunlap wrote:
> On 05/14/13 20:26, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20130514:
> >
>
> on x86_64:
>
> crypto/built-in.o: In function `chksum_digest':
> crct10dif.c:(.text+0x2789f): undefined reference to `crc_t10dif_generic'
> crypto/built-i
On 05/14/13 20:26, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20130514:
>
on x86_64:
drivers/built-in.o: In function `brcms_led_unregister':
(.text+0x136f0e): undefined reference to `led_classdev_unregister'
drivers/built-in.o: In function `brcms_led_register':
(.text+0x1370b5): undefi
Hi all,
Changes since 20130514:
I have started doing some builds with gcc 4.8.0 and while I can't easily
tell if I am getting more or less warnings, the ones I do get are now
much more verbose. This is a hint to people to clean some of them up,
please!
-
22 matches
Mail list logo
