On Fri, 20 Sept 2024 at 00:56, Ido Schimmel wrote:
>
> Hi,
>
> Thanks for the patch and sorry for the late reply (was OOO).
>
> On Mon, Sep 16, 2024 at 07:49:05PM +1000, Jamie Bainbridge wrote:
> > Running this test on a small system produces different failures every
>
runs in a row with 100% pass OK.
Fixes: b6d00da08610 ("selftests: forwarding: Add bridge MDB test")
Signed-off-by: Jamie Bainbridge
---
v2: Avoid false check failures as seen by Jakub Kicinski.
---
.../selftests/net/forwarding/bridge_mdb.sh| 28 +++
1 file changed, 28
On Sat, 14 Sept 2024 at 00:56, Jakub Kicinski wrote:
>
> On Fri, 13 Sep 2024 19:40:04 +1000 Jamie Bainbridge wrote:
> > Running this test on a small system produces different failures every
> > test checking deletions, and some flushes. From different test runs:
>
> This
ing in 100% pass OK.
Create a variable just for this test to allow short sleep, the default
WAIT_TIME of 5 seconds makes the test far longer than necessary.
Fixes: b6d00da08610 ("selftests: forwarding: Add bridge MDB test")
Signed-off-by: Jamie Bainbridge
---
.../selftests/net/forw
: 13715acf8ab5 ("selftest: Add test for bind() conflicts.")
Fixes: 2c042e8e54ef ("tcp: Add selftest for bind() and TIME_WAIT.")
Signed-off-by: Jamie Bainbridge
---
tools/testing/selftests/net/Makefile | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/tools/t
Jamie Heilman wrote:
> Greg Kroah-Hartman wrote:
> > On Sat, Mar 20, 2021 at 09:31:55PM +0000, Jamie Heilman wrote:
> > > [ugh, resent with the lkml headers unbroken, sorry about the dupe]
> > >
> > > Greg Kroah-Hartman wrote:
> > > > J. Bruce
Greg Kroah-Hartman wrote:
> On Sat, Mar 20, 2021 at 09:31:55PM +0000, Jamie Heilman wrote:
> > [ugh, resent with the lkml headers unbroken, sorry about the dupe]
> >
> > Greg Kroah-Hartman wrote:
> > > J. Bruce Fields (2):
> > > Revert "n
50.254789] ---[ end trace 171bde4774bc9795 ]---
Can't readily reproduce it though, so likely a race condition or
something that requires more state buildup than I have after a few
minutes of uptime. Kernel config at
http://audible.transient.net/~jamie/k/nfsd.config-5.10.25 in case you
think
Linus Torvalds wrote:
> On Sun, Mar 14, 2021 at 7:32 PM Rong Chen wrote:
> >
> > It can be reproduced with '-a' option in dash:
>
> Oh, ok. That kind of explains it.
>
> 'dash' is trash. Please somebody make a bug report.
>
> > $ a="!"
> > $ [ "$a" = ".size" ]
> > $ [ "$a" = ".si
Jamie Heilman wrote:
> Jamie Heilman wrote:
> > Karol Herbst wrote:
> > > fyi, there is a patch which solves a maybe related issue on your GPU,
> > > mind giving it a try before we dig further?
> > > https://gitlab.freedesktop.org/drm/nouveau/-/issues/14#n
Takashi Iwai wrote:
> On Sat, 23 Jan 2021 12:08:02 +0100,
> Jamie Heilman wrote:
> >
> > > If the problem is still seen with the very latest Linus tree and the
> > > previous patch, please enable the dyndbg, e.g. pass dydbg=+p option to
> > >
Takashi Iwai wrote:
> On Fri, 22 Jan 2021 11:03:48 +0100,
> Jamie Heilman wrote:
> >
> > Takashi Iwai wrote:
> > > You seem hitting a firmware bug, and it doesn't look like the only
> > > case. Interestingly, the backport of 5.11 USB-audio stuff on 5.3
&g
Jamie Heilman wrote:
> Karol Herbst wrote:
> > fyi, there is a patch which solves a maybe related issue on your GPU,
> > mind giving it a try before we dig further?
> > https://gitlab.freedesktop.org/drm/nouveau/-/issues/14#note_767791
>
> So, I tried that. Turns
he same set of
problems; hopefully that version is free from issues, but we'll
see...
> On Thu, Jan 21, 2021 at 3:33 AM Jamie Heilman
> wrote:
> >
> > Karol Herbst wrote:
> > > On Wed, Jan 6, 2021 at 4:25 AM Jamie Heilman
> > > wrote:
> > > >
ck workaround, perform it only for the necessary devices;
> currently MOTU devices are known to need the valid altset checks, so
> filter out other devices.
>
> Fixes: 93db51d06b32 ("ALSA: usb-audio: Check valid altsetting at parsing
> rates for UAC2/3")
> Reported-by: Jam
nging off a hub in my
monitor, not the most elegant of setups, I know---but none of this
changes even if I plug it directly into my workstation's USB ports, I
tried that).
I'm happy to try any patches, or provide more details, just ask.
--
Jamie Heilman http://audib
Karol Herbst wrote:
> On Wed, Jan 6, 2021 at 4:25 AM Jamie Heilman
> wrote:
> >
> > Jamie Heilman wrote:
> > > Jamie Heilman wrote:
> > > > Karol Herbst wrote:
> > > > > do you think you'd be able to do a kernel bisect in order
Jamie Heilman wrote:
> Jamie Heilman wrote:
> > Karol Herbst wrote:
> > > do you think you'd be able to do a kernel bisect in order to pinpoint
> > > the actual commit causing it? Thanks
> >
> > No. I can't reproduce it reliably. I if I could, b
Jamie Heilman wrote:
> Karol Herbst wrote:
> > do you think you'd be able to do a kernel bisect in order to pinpoint
> > the actual commit causing it? Thanks
>
> No. I can't reproduce it reliably. I if I could, bisection wouldn't
> be a problem but as I
e problem
to occur there's essentially no chance. I know it regressed roughly
in 5.8-rc1 only because that's what I was running when the first event
occured.
> On Sun, Dec 27, 2020 at 8:16 PM Jamie Heilman
> wrote:
> >
> > Something between v5.8 and v5.9 has resulted in periodic
x/linux-picochip-3.0/0001-picoxcell-support-for-Picochip-picoXcell-SoC.patch
>
> Signed-off-by: Arnd Bergmann
Acked-by: Jamie Iles
Thanks Arnd!
Jamie
s-kernel/linux/linux-picochip-3.0/0001-picoxcell-support-for-Picochip-picoXcell-SoC.patch
>
> Signed-off-by: Arnd Bergmann
Rob has a series to remove Picoxcell as there's no active development on
this anymore and Intel have stopped producing the chips.
Thanks,
Jamie
r messages a little less so.
If there's more debugging I can do when this happens, I'd love to know
what it is.
kernel config: http://audible.transient.net/~jamie/k/nouveau.config-5.10.0
dmesg at boot: http://audible.transient.net/~jamie/k/nouveau.dmesg
--
Jamie Heilman http://audible.transient.net/~jamie/
Acked-by: Jamie Iles
for the series. Intel EOLd this product now, good idea to remove it.
Thanks,
Jamie
On Thu, Dec 10, 2020 at 02:03:11PM -0600, Rob Herring wrote:
> PicoXcell has had nothing but treewide cleanups for at least the last 8
> years and no signs of activity. The most
by the end of the series.
>
> This series is a little rough around the monitors, would a fake
> struct resctrl_schema for the monitors simplify things, or be a source
> of bugs?
>
> This series is based on v5.10-rc1, and can be retrieved from:
> git://git.kernel.org/pub/scm/linux/kernel/git/morse/linux.git
> mpam/resctrl_merge_cdp/v1
>
> Parts were previously posted as an RFC here:
> https://lore.kernel.org/lkml/20200214182947.39194-1-james.mo...@arm.com/
Reviewed-by: Jamie Iles
Jamie
gt; + * and the root HPA will not have a shadow page associated with it.
> + */
> + if (!sp)
> + return false;
> +
> return sp->tdp_mmu_page && sp->root_count;
> }
>
> --
> 2.29.2.222.g5d2a92d10f8-goog
>
--
Jamie Heilman http://audible.transient.net/~jamie/
s->conf_type = resctrl_to_arch_res(r)->conf_type;
>
> + ret = snprintf(s->name, sizeof(s->name), r->name);
> + if (ret >= sizeof(s->name)) {
> + kfree(s);
> + return -EINVAL;
> + }
> +
How about:
+ ret = strscpy(s->name, r->name, sizeof(s->name));
+ if (ret < 0)) {
+ kfree(s);
+ return -EINVAL;
+ }
So that there isn't a non-constant format specifier that'll trip
Coverity+friends up later?
Thanks,
Jamie
you need anything else.
--
Jamie Heilman http://audible.transient.net/~jamie/
#
# Automatically generated file; DO NOT EDIT.
# Linux/x86 5.10.0-rc2 Kernel Configuration
#
CONFIG_CC_VERSION_TEXT="gcc (Debian 10.2.0-16) 10.2.0"
CONFIG_CC_IS_GCC=y
CONFIG_GCC_VERSION=1
aml: gpio@2:
> 'reg-io-width' does not match any of the regexes:
> '^gpio-(port|controller)@[0-9a-f]+$', 'pinctrl-[0-9]+'
>
> Signed-off-by: Krzysztof Kozlowski
Acked-by: Jamie Iles
Thanks!
ich updates engine->stat_irq_thresh,
> therefore initialize it before creating the file in probe function.
>
> Found by Linux Driver Verification project (linuxtesting.org).
>
> Signed-off-by: Madhuparna Bhowmik
Acked-by: Jamie Iles
Thanks!
vicetree/bindings/power/power-controller.txt
https://elixir.bootlin.com/linux/latest/source/drivers/mfd/max77620.c#L566
...maybe that can be added to the devices getting in the way?
Cheers,
[0]
https://elixir.bootlin.com/linux/latest/source/drivers/watchdog/bcm2835_wdt.c#L152
(chosen at random)
Andrew
--
Jamie Lentin
rification project (linuxtesting.org).
>
> Signed-off-by: Alexey Khoroshilov
Reviewed-by: Jamie Iles
On Mon, Nov 06, 2017 at 12:56:09PM +0100, Dmitry Vyukov wrote:
> On Mon, Nov 6, 2017 at 12:25 PM, Jamie Iles wrote:
> > Hi Dmitry,
> >
> > On Mon, Nov 06, 2017 at 12:02:19PM +0100, Dmitry Vyukov wrote:
> >> On Thu, Nov 2, 2017 at 6:01 PM, Oleg Nesterov wrote:
> &
: 7fd80a914133
[ 45.042451] RDX: 003d RSI: 7fff313d0860 RDI: 0004
[ 45.043307] RBP: 7fff313d0c50 R08: 7fff313d0860 R09: 8258efee6555c1f9
[ 45.044107] R10: R11: 0246 R12: 7fff313d0860
[ 45.045011] R13: R14: 7fff313d0c70 R15: 0001
[ 45.046217] Kernel Offset: disabled
[ 45.046615] Rebooting in 86400 seconds..
Running the same reproducer as an unprivileged user does not have any
effect - the system continues to run fine without any warning or panic.
Thanks,
Jamie
Cc: Jesper Nilsson
> Cc: Lars Persson
> Cc: Niklas Cassel
> Cc: "David S. Miller"
> Cc: Jamie Iles
> Cc: linux-arm-ker...@axis.com
> Cc: linux-cry...@vger.kernel.org
> Cc: linux-arm-ker...@lists.infradead.org
> Signed-off-by: Kees Cook
> ---
Acked-by: Jamie Iles
Thanks,
Jamie
Hi Linus,
On Tue, Sep 12, 2017 at 11:47:52AM +0200, Linus Walleij wrote:
> Jamie, do you consider yourself maintainer? If not
> would someone else using this driver please step up?
I don't think I'm best suited to the job - I don't actually have access
to the docs for this
fine, but then once debugging has finished, the
init process is left killable which is unlikely what the user expects,
resulting in either an accidentally killed init or an init that stops
reaping zombies.
Cc: Andrew Morton
Cc: Oleg Nesterov
Signed-off-by: Jamie Iles
---
kernel/signal.c | 6
Hi Oleg,
On Thu, Apr 27, 2017 at 01:16:51PM +0100, Jamie Iles wrote:
> On Wed, Apr 26, 2017 at 05:18:58PM +0200, Oleg Nesterov wrote:
> > Hi Jamie,
> >
> > On 04/25, Jamie Iles wrote:
> > >
> > > Hi Oleg,
> > >
> > > I'm back
Hi Oleg,
On Fri, May 05, 2017 at 06:26:07PM +0200, Oleg Nesterov wrote:
> Hi Jamie,
>
> I am sorry for being slow... yes, probably we should start with this
> simple change, and perhaps we do not really need anything else. But
> let me think about this till Monday, perhaps we
is "clear
> SIGNAL_UNKILLABLE" logic in force_sig_info() altogether.
No problem, I sent the patch to keep it on my own radar :)
Jamie
fine, but then once debugging has finished, the
init process is left killable which is unlikely what the user expects,
resulting in either an accidentally killed init or an init that stops
reaping zombies.
Cc: Andrew Morton
Cc: Oleg Nesterov
Signed-off-by: Jamie Iles
---
kernel/signal.c | 6
On Wed, Apr 26, 2017 at 05:18:58PM +0200, Oleg Nesterov wrote:
> Hi Jamie,
>
> On 04/25, Jamie Iles wrote:
> >
> > Hi Oleg,
> >
> > I'm back looking at SIGNAL_UNKILLABLE and debugging child reapers again,
> > and the current issue is when running cod
gt;signal->flags &= ~SIGNAL_UNKILLABLE;
ret = specific_send_sig_info(sig, info, t);
spin_unlock_irqrestore(&t->sighand->siglock, flags);
make any sense? It does address the issue that I'm seeing, but are
there any downsides to doing so?
Thanks,
Jamie
egister addresses.
>
> Signed-off-by: Hoan Tran
Reviewed-by: Jamie Iles
Hi Hoan,
On Tue, Feb 14, 2017 at 05:22:09PM -0800, Hoan Tran wrote:
> Hi Linus, Jamie and all,
>
> Do you have any comments on this patch?
I think that the CONFIG_ACPI ifdef can be removed to clean it up -
acpi_match_device() returns NULL for !CONFIG_ACPI.
Other than that, looks g
; > This patch modifies DW GPIO driver to accommodate the difference
> > in a few register addresses.
> >
> > Signed-off-by: Hoan Tran
>
> On next iteration please include Jamie Iles, Weike Chen and Sebastian
> Andrzej Siewior.
> They all provided substantial
crypto: picoxcell - Remove spacc_is_compatible() wrapper function
>
> drivers/crypto/Kconfig| 2 +-
> drivers/crypto/picoxcell_crypto.c | 28 +++-----
> 2 files changed, 4 insertions(+), 26 deletions(-)
Acked-by: Jamie Iles
Thanks,
Jamie
pond to future SIGSTOP signals rather than ignoring
them.
Make sure that when setting SIGNAL_STOP_CONTINUED/SIGNAL_STOP_STOPPED
that we don't clear SIGNAL_UNKILLABLE.
Cc: Alexander Viro
Cc: Ingo Molnar
Cc: Peter Zijlstra
Cc: Andrew Morton
Cc: Oleg Nesterov
Signed-off-by: Jamie Iles
--
Hi Oleg,
On Tue, Nov 29, 2016 at 03:06:00PM +0100, Oleg Nesterov wrote:
> Jamie,
>
> I am really sorry for the huge delay.
No problem!
> On 11/16, Jamie Iles wrote:
> >
> > Since 00cd5c37af (ptrace: permit ptracing of /sbin/init) we can now
> > trace init
Hi Oleg,
On Thu, Nov 17, 2016 at 08:04:20PM +0100, Oleg Nesterov wrote:
> On 11/16, Jamie Iles wrote:
> >
> > This can result in init becoming stoppable/killable after tracing. For
> > example, running:
> >
> > while true; do kill -STOP 1; done &
>
pond to future SIGSTOP signals rather than ignoring
them.
Instead of direct assignment to struct signal_struct::flags, provide
accessors that protect SIGNAL_UNKILLABLE.
Cc: Alexander Viro
Cc: Ingo Molnar
Cc: Peter Zijlstra
Cc: Andrew Morton
Cc: Oleg Nesterov
Signed-off-by: Jamie Iles
---
The module parameters FdirMode, FdirPballoc, AtrSampleRate, or Node are
not available in the in-kernel driver, only in Intel's out-of-tree
SourceForge driver. Remove these from the kernel documentation.
Remove reference to Intel affinity script. Move max_vfs to tidy up.
Signed-off-by:
Lift configuration command from udlfb. This appears to be essential for
at least a Rextron VCUD-60, without which no URB communication occurs.
Signed-off-by: Jamie Lentin
---
udl_encoder_commit() is too late to do this set up in it seems. This
setup doesn't need to be performed again af
on Linux 4.7.0
Signed-off-by: Jamie Lentin
---
This ended up in udl_connector_init() since the name suggests it has
something to do with configuring which output to use, although a quick
search through other displaylink drivers didn't shed any light on what
the bytes in set_def_chn actually
we already have some Orion5x converted to DT, and that use
PCI: board-rd88f5182.c is an example. So we could very well take Jamie
patches as-is, and move later to a DT-representation for PCI/PCIe.
Ah, I thought all the DT users were moved to mach-mvebu. I agree
this new patch isn't introducing
On Sun, 17 Jul 2016, Rob Herring wrote:
On Sat, Jul 16, 2016 at 03:29:04PM +0100, Jamie Lentin wrote:
This is a router based on the mv88f5181 chipset.
http://www.netgear.com/support/product/WNR854T.aspx
http://wiki.openwrt.org/toh/netgear/wnr854t
Signed-off-by: Jamie Lentin
On Sat, 16 Jul 2016, Arnd Bergmann wrote:
On Saturday, July 16, 2016 3:29:04 PM CEST Jamie Lentin wrote:
+
+#define WNR854T_PCI_SLOT0_OFFS 7
+#define WNR854T_PCI_SLOT0_IRQ_PIN 4
+
+static void __init wnr854t_pci_preinit(void)
+{
+ int pin;
+
+ /*
+* Configure PCI GPIO
The default bootloader leaves the LEDs orange, and the 88E1121R driver
applies it's own inappropriate configuration. Configure as per manual,
i.e. orange = 100 / green = 1000 / blink = activity
Signed-off-by: Jamie Lentin
---
arch/arm/boot/dts/orion5x-netgear-wnr854t.dts
As far as I'm aware the mv88f5181-b1 and mv88f5181l are the same at the
pinctrl level, so re-use the definitions for both.
Signed-off-by: Jamie Lentin
---
.../bindings/pinctrl/marvell,orion-pinctrl.txt | 4 ++--
drivers/pinctrl/mvebu/pinctrl-orion.c
This is a router based on the mv88f5181 chipset.
http://www.netgear.com/support/product/WNR854T.aspx
http://wiki.openwrt.org/toh/netgear/wnr854t
Signed-off-by: Jamie Lentin
---
.../bindings/arm/marvell/marvell,orion5x.txt | 1 +
arch/arm/boot/dts/Makefile | 1
marvell,reg-init is generally used to apply a custom LED configuration
on boot. However this is then blatted in m88e1121_config_aneg when the
interface is brought up. Re-apply any custom configuration afterwards,
to keep custom LED configuration.
Signed-off-by: Jamie Lentin
---
drivers/net/phy
Copy the format for kirkwood/dove to orion5x
Signed-off-by: Jamie Lentin
---
.../bindings/arm/marvell/marvell,orion5x.txt | 23 ++
1 file changed, 23 insertions(+)
create mode 100644
Documentation/devicetree/bindings/arm/marvell/marvell,orion5x.txt
diff --git a
Signed-off-by: Jamie Lentin
---
.../bindings/arm/marvell/marvell,orion5x.txt | 1 +
arch/arm/boot/dts/orion5x-mv88f5181.dtsi | 35 ++
2 files changed, 36 insertions(+)
create mode 100644 arch/arm/boot/dts/orion5x-mv88f5181.dtsi
diff --git a/Documentation
orion-wdt refuses to start without these properties defined, so lift
definitions out of kirkwood/dove.dtsi
Signed-off-by: Jamie Lentin
---
arch/arm/boot/dts/orion5x.dtsi | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/orion5x.dtsi b/arch/arm/boot/dts
If PHY is registered via. a DSA switch, the MDIO bus the phy is on does
not exist in devicetree, but there may be a reference to the PHY node
on the physical MDIO bus to use.
Signed-off-by: Jamie Lentin
---
drivers/net/phy/marvell.c | 22 --
1 file changed, 16 insertions
ollowing patch:
https://github.com/lentinj/linux/commit/d6b7b4695b7dcbf36d0663aea9cb4ecd65a1ada8
...but this is probably a matter for another thread.
Cheers,
[0] http://thread.gmane.org/gmane.linux.network/120616/focus=121320
[1]
https://github.com/lentinj/linux/commit/a4bceebb08ecdc25a4d49e23f2abad2148
Signed-off-by: Jamie Lentin
---
arch/arm/mach-orion5x/Makefile| 1 -
arch/arm/mach-orion5x/wnr854t-setup.c | 185 --
2 files changed, 186 deletions(-)
delete mode 100644 arch/arm/mach-orion5x/wnr854t-setup.c
diff --git a/arch/arm/mach-orion5x/Makefile
Referring to values in the u-boot port, add support for the mv88f5181
Signed-off-by: Jamie Lentin
---
.../devicetree/bindings/clock/mvebu-core-clock.txt | 1 +
drivers/clk/mvebu/orion.c | 70 ++
2 files changed, 71 insertions(+)
diff --git a
Tadeusz Struk wrote:
> On 05/03/2016 07:26 PM, Jamie Heilman wrote:
> >>> Alrighty, presumably relevant bits:
> >>> > >
> >>> > > X.509: Cert Issuer: Build time autogenerated kernel key
> >>> > > X.509: Cert Subject: Bu
David Howells wrote:
> (cc'ing Tadeusz as he did the pkcs1 padding function)
>
> Jamie Heilman wrote:
>
> > > > Problem loading in-kernel X.509 certificate (-2)
> > >
> > > ENOENT? Hmmm... The only place that is generated is in the crypto la
Tadeusz Struk wrote:
> Could you please check if this one fixes the problem for you:
> https://patchwork.kernel.org/patch/8766361/
That patch is already present by 4.6-rc5 and the problem still exists,
so no, it doesn't.
--
Jamie Heilman http://audible.transient.net/~jamie/
Herbert Xu wrote:
> On Sat, Apr 30, 2016 at 08:32:48AM +0000, Jamie Heilman wrote:
> > I usually build my kernels to require module signatures and use
> > automatic signing. As of v4.6-rc1 I'm getting this on boot:
> >
> > Problem loading in-kernel X.509 certifica
32081403f1709a312c302a06035504030c234275696c642074696d65206175746f67656e657261746564206b65726e656c206b6579"
X.509: Request for key
'ex:008a32081403f1709a312c302a06035504030c234275696c642074696d65206175746f67656e657261746564206b65726e656c206b6579'
err -11
full dmesg at http://audible.transient.net/~jamie/k/modsign.dmesg-debugging
--
Jamie Heilman http://audible.transient.net/~jamie/
o the crypto layer)
For some reason after this commit my system keyring always ends up
empty. I use the deb-pkg make target. My kernel config can
be found at
http://audible.transient.net/~jamie/k/modsign.config-4.6.0-rc5-guest
Let me know if you need anything else.
--
Jamie He
orentin
Acked-by: Jamie Iles
thanks for doing this!
Jamie
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Signed-off-by: Jamie Lentin
---
drivers/hid/hid-lenovo.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/hid/hid-lenovo.c b/drivers/hid/hid-lenovo.c
index 65df414..265bfe2 100644
--- a/drivers/hid/hid-lenovo.c
+++ b/drivers/hid/hid-lenovo.c
@@ -178,9 +178,12
tab as well as scrolling, for example.
This means you can no longer long-middle-click, but I don't think this
is likely to upset users as much as the current behaviour.
Tested against 4.1.2 with both Bluetooth and USB compact keyboards.
Cheers,
Jamie Lentin (3):
HID: lenovo: Use constant
Don't relay a middle button press to userspace until release, and then
only if there was no scroll events inbetween. This is closer to what
Xorg's wheel emulation does, and avoids spurious middle-click pastes.
Signed-off-by: Jamie Lentin
---
drivers/hid/hid-len
Signed-off-by: Jamie Lentin
---
drivers/hid/hid-lenovo.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/hid/hid-lenovo.c b/drivers/hid/hid-lenovo.c
index c4c3f09..65df414 100644
--- a/drivers/hid/hid-lenovo.c
+++ b/drivers/hid/hid-lenovo.c
@@ -117,10 +117,10
From: Jamie Garside
This patch fixes two bugs in the Microblaze syscall trap handler when an invalid
syscall ID is used.
First, the range check on line 351 only checks for syscall IDs greater than
__NR_syscalls. A negative syscall ID (either passed to `syscall()` or as
returned
by
code, but a glance over
the git logs shows this file has not been changed in the past two years,
hence this patch should be safe for the most recent kernel version.
Thanks,
Jamie
--
Jamie Garside
Department of Computer Science
University of York
United Kingdom
Disclaimer: http://www.york.ac.uk/
Chen, Tiejun wrote:
> On 2014/12/24 19:02, Jamie Heilman wrote:
> >Chen, Tiejun wrote:
> >>On 2014/12/23 15:26, Jamie Heilman wrote:
> >>>Chen, Tiejun wrote:
> >>>>On 2014/12/23 9:50, Chen, Tiejun wrote:
> >>>>>On 2014/12/22 17:2
Chen, Tiejun wrote:
> On 2014/12/23 15:26, Jamie Heilman wrote:
> >Chen, Tiejun wrote:
> >>On 2014/12/23 9:50, Chen, Tiejun wrote:
> >>>On 2014/12/22 17:23, Jamie Heilman wrote:
> >>>>KVM internal error. Suberror: 1
> >>>>emulation failu
Chen, Tiejun wrote:
> On 2014/12/23 9:50, Chen, Tiejun wrote:
> >On 2014/12/22 17:23, Jamie Heilman wrote:
> >>Chen, Tiejun wrote:
> >>>On 2014/12/21 20:46, Jamie Heilman wrote:
> >>>>With v3.19-rc1 when I run qemu-system-x86_64 -machine pc,accel=kv
Chen, Tiejun wrote:
> On 2014/12/21 20:46, Jamie Heilman wrote:
> >With v3.19-rc1 when I run qemu-system-x86_64 -machine pc,accel=kvm I
> >get:
> >
> >KVM: entry failed, hardware error 0x8021
>
> Looks some MSR writing issues such a failed entry.
>
>
in so far that I can
run kvm again without the aforementioned error, but I haven't tested
it thoroughly beyond that. Let me know if you need more information
or testing.
--
Jamie Heilman http://audible.transient.net/~jamie/
--
To unsubscribe from this list: send the line
vent comes after the wheel events.
Signed-off-by: Jamie Lentin
---
drivers/hid/hid-lenovo.c | 37 +
1 file changed, 37 insertions(+)
diff --git a/drivers/hid/hid-lenovo.c b/drivers/hid/hid-lenovo.c
index 0f35a76..c4c3f09 100644
--- a/drivers/hid/hid-lenovo.c
+
Jamie Lentin (2):
HID: lenovo: Add sensitivity control to compact keyboards
HID: lenovo: Use native middle-button mode for compact keyboards
drivers/hid/hid-lenovo.c | 79 +++-
1 file changed, 78 insertions(+), 1 deletion(-)
--
2.1.3
--
To
The trackpoint sensitivity can also be controlled, expose this via
sysfs.
Signed-off-by: Jamie Lentin
---
drivers/hid/hid-lenovo.c | 42 +-
1 file changed, 41 insertions(+), 1 deletion(-)
diff --git a/drivers/hid/hid-lenovo.c b/drivers/hid/hid-lenovo.c
There are 2 missing blank lines after variable declarations in
octeon/ethernet-rx.c. They have been added per the coding style.
Signed-off-by: Jamie Lawler
---
drivers/staging/octeon/ethernet-rx.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/staging/octeon/ethernet-rx.c
b
Hi,
There are 2 missing blank lines after declarations in
octeon/ethernet-rx.c. I have added them per the coding style.
Regards,
Jamie Lawler
Signed-off-by: Jamie Lawler
---
drivers/staging/octeon/ethernet-rx.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/staging/octeon
Thanks Aaro, I will do that now.
Jamie
On 3 December 2014 at 22:13, Aaro Koskinen wrote:
> Hi,
>
> On Wed, Dec 03, 2014 at 09:43:51PM +0000, Jamie Lawler wrote:
>> --- a/drivers/staging/octeon/ethernet-rx.c
>> +++ b/drivers/staging/octeon/ethernet-rx.c
>> @
Hi,
I've added blank lines after several declarations that were
previously missing them, reducing the number of warnings from
checkpatch.pl.
Regards,
Jamie Lawler
Signed-off-by: Jamie Lawler
---
drivers/staging/octeon/ethernet-rx.c | 4
drivers/staging/octeon/ethernet-tx.c
Hi,
I've attached a patch that fixes the lack of blank lines after 9 declarations
within drivers/thunderbolt/ctl.c. ctl.c now passes checkpatch.pl
Regards,
Jamie Lawler
Signed-off-by: Jamie Lawler
---
drivers/thunderbolt/ctl.c | 9 +
1 file changed, 9 insertions(+)
diff --
The bluetooth keyboard also generates 0x00fa when the middle button is
pressed. Move the made-up report out of the way so we don't trigger
KEY_FILE when middle button is pressed
Signed-off-by: Jamie Lentin
---
drivers/hid/hid-lenovo.c | 12 ++--
1 file changed, 6 insertions(
On the USB keyboard, the VENDOR hotkeys share the same device as the
mouse. Setting EV_REP also affects mouse buttons, so leave it off.
The bluetooth keyboard still has autorepeating mouse buttons, as it
only has one device and is set by the KEYBOARD pages.
Signed-off-by: Jamie Lentin
is is currently solvable.
The first 2 I will sort out once enough free time appears, if you would prefer
a single large patchset, feel free to ignore this and wait for a bigger
patchset.
Many thanks,
[0] https://lkml.org/lkml/2014/7/23/702
Jamie Lentin (2):
HID: lenovo: Move USB KEY_FILE to 0
gestion, and vice
versa; which is both counterintuitive and counterproductive.
On Wed, Oct 15, 2014 at 1:05 PM, Andrew Morton
wrote:
> On Wed, 15 Oct 2014 12:58:35 -0700 Jamie Liu wrote:
>
>> shrink_page_list() counts all pages with a mapping, including clean
>> pages, toward nr_
they count for nr_dirty.
Signed-off-by: Jamie Liu
---
mm/vmscan.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/mm/vmscan.c b/mm/vmscan.c
index dcb4707..ad9cd9f 100644
--- a/mm/vmscan.c
+++ b/mm/vmscan.c
@@ -875,7 +875,8 @@ static unsigned long shrink_page_list(struct list
6:3: warning: ‘relocs_size’ may be used uninitialized
> in this function [-Wmaybe-uninitialized]
>memset(relocs, 0, relocs_size);
>^
> scripts/sortextable.h:106:6: note: ‘relocs_size’ was declared here
> int relocs_size;
> ^
>
> gcc 4.9.1
>
> Cc: Andrew
1 - 100 of 498 matches
Mail list logo
