Hi Kale,
On Fri, 2018-01-12 at 13:31 +0200, Kalle Valo wrote:
> From: Luca Coelho
> >
> > Hi,
> >
> > Here's the fourth and probably last batch of patches intended for
> > 4.16. Nothing major, just continued development, some cleanups and
> > small fixes here and
On Fri, Jan 12, 2018 at 4:15 PM, Tony Luck wrote:
>
> Here there isn't any reason for speculation. The core has the
> value of 'x' in a register and the upper bound encoded into the
> "cmp" instruction. Both are right there, no waiting, no speculation.
So this is an
Hi Dave,
this is a pull request to net-next tree for 4.16, more info in the
signed tag below. I'm not expecting any problems but please let me know
if you have any.
Kalle
The following changes since commit f66faae2f80a45feafc04ce63ef744ac4b6e8c05:
Merge branch 'ipv6-ipv4-nexthop-align'
Brian Norris writes:
> On Thu, Jan 11, 2018 at 06:25:09PM -0800, Brian Norris wrote:
>> Anyway, I'll do my own testing and then submit my patch properly.
>
> OK, so I definitely confirmed: if your patch does anything, it
> introduces a new deadlock possibility. Just
On 1/12/2018 9:18 PM, Kyle Evans wrote:
Thank you Arend. I updated to master again, v4.15-rc7+, and applied your
patch. All log snips are grabbed with dmesg|grep -E 'mmc0|brcm', as the
sdio device is on mmc0.
Could you follow the reply convention of not top-posting.
Without patch [1], for