Ugh I completely missed CONFIG_IP_MULTIPLE_TABLES too, I sent the new
patch. This time I believe I cover all the cases. PTAL.
Thanks,
Brian
On Fri, Jul 31, 2020 at 5:50 PM Randy Dunlap wrote:
>
> On 7/31/20 5:35 PM, Stephen Rothwell wrote:
> > Hi Randy,
> >
> > On Fri, 31 Jul 2020 08:53:09
On 7/31/20 5:35 PM, Stephen Rothwell wrote:
> Hi Randy,
>
> On Fri, 31 Jul 2020 08:53:09 -0700 Randy Dunlap wrote:
>>
>> on i386:
>>
>> ld: net/core/fib_rules.o: in function `fib_rules_lookup':
>> fib_rules.c:(.text+0x16b8): undefined reference to `fib4_rule_match'
>> ld:
Hi Randy,
On Fri, 31 Jul 2020 08:53:09 -0700 Randy Dunlap wrote:
>
> on i386:
>
> ld: net/core/fib_rules.o: in function `fib_rules_lookup':
> fib_rules.c:(.text+0x16b8): undefined reference to `fib4_rule_match'
> ld: fib_rules.c:(.text+0x16bf): undefined reference to `fib4_rule_match'
> ld:
On 7/31/20 4:19 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20200730:
>
on i386:
ld: net/core/fib_rules.o: in function `fib_rules_lookup':
fib_rules.c:(.text+0x16b8): undefined reference to `fib4_rule_match'
ld: fib_rules.c:(.text+0x16bf): undefined reference to `fib4_rule_match'
Hi all,
Changes since 20200730:
My fixes tree contains:
dbf24e30ce2e ("device_cgroup: Fix RCU list debugging warning")
Linus' tree lost its build failure but gained another for which I applied
a patch.
The block/zonefs trees gained a conflict against Linus' tree.
I reverted 4 commits from
On Fri, Aug 02, 2019 at 09:44:43AM +0300, Ard Biesheuvel wrote:
>
> OK. I will adopt this mechanism [0] after all and resubmit, once I get
> confirmation from either Voldis or Heiko that this makes the issue go
> away (given that my local GCC does not reproduce the issue)
>
> [0]
>
On Fri, Aug 02, 2019 at 02:48:44PM +1000, Stephen Rothwell wrote:
> Hi Herbert,
>
> On Fri, 2 Aug 2019 13:14:14 +1000 Herbert Xu
> wrote:
> >
> > For now I'm going to back out those two specific patches as the
> > rest seem to be valid by themselves.
>
> I have applied the top commit from your
On Fri, 2 Aug 2019 at 09:46, Heiko Carstens wrote:
>
> On Thu, Aug 01, 2019 at 08:28:56PM +0300, Ard Biesheuvel wrote:
> > On Thu, 1 Aug 2019 at 15:28, Heiko Carstens
> > wrote:
> > > Still not... with linux-next as of today I get this (s390 defconfig):
> > >
> > > ERROR:
On Fri, 2 Aug 2019 at 03:20, Stephen Rothwell wrote:
>
> Hi Herbert,
>
> On Thu, 1 Aug 2019 20:28:56 +0300 Ard Biesheuvel
> wrote:
> >
> > On Thu, 1 Aug 2019 at 15:28, Heiko Carstens
> > wrote:
> > >
> > > On Wed, Jul 31, 2019 at 01:44:54PM +0200, Heiko Carstens wrote:
> > > > On Wed, Jul 31,
On Thu, Aug 01, 2019 at 08:28:56PM +0300, Ard Biesheuvel wrote:
> On Thu, 1 Aug 2019 at 15:28, Heiko Carstens wrote:
> > Still not... with linux-next as of today I get this (s390 defconfig):
> >
> > ERROR: "crypto_aegis128_decrypt_chunk_simd" [crypto/aegis128.ko] undefined!
> > ERROR:
On Fri, 2 Aug 2019 at 06:14, Herbert Xu wrote:
>
> Hi Stephen:
>
> On Fri, Aug 02, 2019 at 10:20:19AM +1000, Stephen Rothwell wrote:
> >
> > It might be time to revert all this series and try again. The
> > implementation seems to have not been well thought through from a kernel
> > building
Hi Herbert,
On Fri, 2 Aug 2019 13:14:14 +1000 Herbert Xu
wrote:
>
> For now I'm going to back out those two specific patches as the
> rest seem to be valid by themselves.
I have applied the top commit from your tree to linux-next today just
to help with building and testing over the weekend (I
Hi Stephen:
On Fri, Aug 02, 2019 at 10:20:19AM +1000, Stephen Rothwell wrote:
>
> It might be time to revert all this series and try again. The
> implementation seems to have not been well thought through from a kernel
> building point of view. For a start the two commits
>
> 7cdc0ddbf74a
Hi Herbert,
On Thu, 1 Aug 2019 20:28:56 +0300 Ard Biesheuvel
wrote:
>
> On Thu, 1 Aug 2019 at 15:28, Heiko Carstens wrote:
> >
> > On Wed, Jul 31, 2019 at 01:44:54PM +0200, Heiko Carstens wrote:
> > > On Wed, Jul 31, 2019 at 09:32:16PM +1000, Herbert Xu wrote:
> > > > On Wed, Jul 31, 2019
On Thu, 1 Aug 2019 at 15:28, Heiko Carstens wrote:
>
> On Wed, Jul 31, 2019 at 01:44:54PM +0200, Heiko Carstens wrote:
> > On Wed, Jul 31, 2019 at 09:32:16PM +1000, Herbert Xu wrote:
> > > On Wed, Jul 31, 2019 at 01:15:20PM +0200, Heiko Carstens wrote:
> > > >
> > > > However that doesn't fix the
On Wed, Jul 31, 2019 at 01:44:54PM +0200, Heiko Carstens wrote:
> On Wed, Jul 31, 2019 at 09:32:16PM +1000, Herbert Xu wrote:
> > On Wed, Jul 31, 2019 at 01:15:20PM +0200, Heiko Carstens wrote:
> > >
> > > However that doesn't fix the simd.h header file breakage with the
> > > second patch :)
> >
On Wed, Jul 31, 2019 at 09:32:16PM +1000, Herbert Xu wrote:
> On Wed, Jul 31, 2019 at 01:15:20PM +0200, Heiko Carstens wrote:
> >
> > However that doesn't fix the simd.h header file breakage with the
> > second patch :)
>
> That fix should be there now too.
Yes, works now. Thank you!
On Wed, Jul 31, 2019 at 01:15:20PM +0200, Heiko Carstens wrote:
>
> However that doesn't fix the simd.h header file breakage with the
> second patch :)
That fix should be there now too.
Thanks,
--
Email: Herbert Xu
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key:
On Wed, Jul 31, 2019 at 09:08:17PM +1000, Herbert Xu wrote:
> On Wed, Jul 31, 2019 at 10:58:20AM +0200, Heiko Carstens wrote:
> > On Wed, Jul 31, 2019 at 04:39:15PM +1000, Stephen Rothwell wrote:
> > > Hi all,
> > >
> > > Changes since 20190730:
> >
> > Hello Ard,
> >
> > two of your patches in
On Wed, Jul 31, 2019 at 10:58:20AM +0200, Heiko Carstens wrote:
> On Wed, Jul 31, 2019 at 04:39:15PM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20190730:
>
> Hello Ard,
>
> two of your patches in the crypto tree cause build breakage on s390:
>
> The patch ("crypto: aes -
On Wed, Jul 31, 2019 at 04:39:15PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20190730:
Hello Ard,
two of your patches in the crypto tree cause build breakage on s390:
The patch ("crypto: aes - create AES library based on the fixed time AES code")
causes this:
Hi all,
Changes since 20190730:
New tree: fpga-fixes
My fixes tree contains:
15b9fc624ba4 ("drivers/macintosh/smu.c: Mark expected switch fall-through")
The fsverity tree gained a conflict against the f2fs tree.
The pm tree gained a build failure for which I applied a patch.
The
On Tue, Jul 31, 2018 at 06:22:52PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20180730:
>
> The block tree gained a build failure so I used the version from
> next-20180730.
>
> The kvms390 tree gained a conflict against the kvm-arm tree.
>
> The staging tree still had its
On Tue, Jul 31, 2018 at 06:22:52PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20180730:
>
> The block tree gained a build failure so I used the version from
> next-20180730.
>
> The kvms390 tree gained a conflict against the kvm-arm tree.
>
> The staging tree still had its
Hi all,
Changes since 20180730:
The block tree gained a build failure so I used the version from
next-20180730.
The kvms390 tree gained a conflict against the kvm-arm tree.
The staging tree still had its build failure due to an interaction with
the vfs tree for which I disabled
Hi all,
Changes since 20180730:
The block tree gained a build failure so I used the version from
next-20180730.
The kvms390 tree gained a conflict against the kvm-arm tree.
The staging tree still had its build failure due to an interaction with
the vfs tree for which I disabled
Hi all,
Changes since 20170728:
The rdma tree gained a build failure so I used the version from
next-20170728.
The drm tree gained a conflict against Linus' tree.
The rcu tree gained a conflict against the tip tree.
Non-merge commits (relative to Linus' tree): 3288
3279 files changed, 115355
Hi all,
Changes since 20170728:
The rdma tree gained a build failure so I used the version from
next-20170728.
The drm tree gained a conflict against Linus' tree.
The rcu tree gained a conflict against the tip tree.
Non-merge commits (relative to Linus' tree): 3288
3279 files changed, 115355
On 07/30/15 22:47, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20150730:
>
on i386:
when CONFIG_EXTCON=m:
drivers/built-in.o: In function `phy_8x16_remove':
phy-qcom-8x16-usb.c:(.text+0x24170a): undefined reference to
`extcon_unregister_interest'
drivers/built-in.o: In function
On 07/30/15 22:47, Stephen Rothwell wrote:
Hi all,
Changes since 20150730:
on i386:
when CONFIG_EXTCON=m:
drivers/built-in.o: In function `phy_8x16_remove':
phy-qcom-8x16-usb.c:(.text+0x24170a): undefined reference to
`extcon_unregister_interest'
drivers/built-in.o: In function
Hi all,
Changes since 20150730:
The at91 tree gained a conflict against the arm-soc tree.
The net-next tree gained a conflict against the net tree.
Non-merge commits (relative to Linus' tree): 4897
4980 files changed, 244177 insertions(+), 113249 deletions(-)
Hi all,
Changes since 20150730:
The at91 tree gained a conflict against the arm-soc tree.
The net-next tree gained a conflict against the net tree.
Non-merge commits (relative to Linus' tree): 4897
4980 files changed, 244177 insertions(+), 113249 deletions(-)
Hi all,
Changes since 20140730:
Removed trees: mfd-fixes, mfd
Added tree: mips-fixes
Renamed tree: mfd-lj to mfd
The net tree lost its build failure.
The modules tree still had its build failure so I used the version from
next-20140725.
The mmc-uh tree still had its build failure so I used
Hi all,
Changes since 20140730:
Removed trees: mfd-fixes, mfd
Added tree: mips-fixes
Renamed tree: mfd-lj to mfd
The net tree lost its build failure.
The modules tree still had its build failure so I used the version from
next-20140725.
The mmc-uh tree still had its build failure so I used
Hi all,
Changes since 20130730:
Added tree: xen-tip
Removed trees: xen, xen-two (replaced by the above tree)
The ext4 tree still has its build failure so I used the version from
next-20130726.
The next-next tree lost its build failure.
The usb-gadget tree still had its build failure so I
Hi all,
Changes since 20130730:
Added tree: xen-tip
Removed trees: xen, xen-two (replaced by the above tree)
The ext4 tree still has its build failure so I used the version from
next-20130726.
The next-next tree lost its build failure.
The usb-gadget tree still had its build failure so I
36 matches
Mail list logo
