SC-V Linux kernel documentation
> -Documentation/devicetree/bindings/riscv/cpus.txt
> +Documentation/devicetree/bindings/riscv/cpus.yaml
> [4] https://www.devicetree.org/specifications/
For the RISC-V related change:
Acked-by: Paul Walmsley # RISC-V
- Paul
Hi,
thanks for taking a shot at the eBPF JIT; this will be very useful.
On Tue, 15 Jan 2019, Björn Töpel wrote:
> * I've added "HAVE_EFFICIENT_UNALIGNED_ACCESS" to
> arch/riscv/Kconfig. Is this assumption correct?
From a hardware point of view, this is not the case on the Linux-capable
RISC-
d before tok_open(), but tok_interrupt() gets called anyway
when the card is ejected. So, set an already-existing flag which
causes tok_interrupt() to bail out early upon card ejection. Tested by
inserting and removing the PCMCIA card several times.
Patch against 2.6.21-rc6.
Signed-off-by: Paul
On Tue, 8 May 2007, Jeff Garzik wrote:
ACK but does not apply
Thanks. Some mailer trouble I guess - will resend via quilt.
- Paul
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/m
s called anyway when the card is
ejected. So, set an already-existing flag which causes tok_interrupt() to
bail out early upon card ejection. Tested by inserting and removing the
PCMCIA card several times.
Patch against 2.6.21-rc6.
Signed-off-by: Paul Walmsley <[EMAIL PROTECTED]>
---
d
From: Paul Walmsley <[EMAIL PROTECTED]>
Ejecting a PCMCIA IBM Token Ring card that has not had its dev->open()
called will reliably trigger an uninitialized spinlock oops when
spinlock debugging is enabled. The system then hangs, occasionally
softlockup oopsing. It s
