> How many times have I told you to include the reason for your patches
> in your proposed commit message?
Will it be useful to look again at the involved circumstances?
> Too often.
Did I answer any concerns partly?
> Many people do not know that a generic kmalloc does a dump_stack() on OOM.
On Fri, Oct 13, 2017 at 03:08:34PM +0900, yasunari.takigu...@sony.com wrote:
> From: Yasunari Takiguchi
>
> These functions monitor the driver and watch for task completion.
> This is part of the Sony CXD2880 DVB-T2/T tuner + demodulator driver.
>
> Signed-off-by: Yasunari Takiguchi
> Signed-of
No need to get into the submenu to disable all ANDROID-related config entries
Signed-off-by: Vincent Legoll
---
drivers/android/Kconfig | 6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/drivers/android/Kconfig b/drivers/android/Kconfig
index 7dce3795b887..e9434777acba 1006
/linux/commits/Giuseppe-Scrivano/ipc-mqueue-lazy-call-kern_mount_data-in-new-namespaces/20171203-201041
config: i386-randconfig-c0-12032036 (attached as .config)
compiler: gcc-7 (Debian 7.2.0-12) 7.2.1 20171025
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
Hi Joel,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: ae64f9bd1d3621b5e60d7363bc20afb46aede215
commit: d59158162e032917a428704160a2063a02405ec6 tracing: Add support for
preempt and irq enable/disable events
date:
On Thu, Nov 02, 2017 at 02:53:48PM +1100, Joel wrote:
> The ASPEED SoC must deassert a reset in order to use the PWM/tach
> peripheral.
>
> Signed-off-by: Joel Stanley
I have not heard from anyone objecting to this change, so I am going to
accept it. See below for a list of changes required to g
On Sun, Dec 03, 2017 at 06:24:02AM -0800, syzbot wrote:
> Hello,
>
> syzkaller hit the following crash on
> dbf9f9124937139e6fcd3f6c64154a699408b481
> git://git.cmpxchg.org/linux-mmots.git/master
> compiler: gcc (GCC) 7.1.1 20170620
> .config is attached
> Raw console output is attached.
>
> Unfo
NTB API has been updated to support multi-port devices like IDT
89HPESx series or Microsemi Switchtec. Message registers
functionality has also been added to new API. In order to keep
the new hardware and corresponding capabilities well tested, NTB
pingpong driver is accordingly altered.
Signed-of
If some of the variables like LOC/REM or LOCAL_*/REMOTE_* got
whitespaces, the script may fail with syntax error.
Signed-off-by: Serge Semin
Acked-by: Logan Gunthorpe
Fixes: a9c59ef77458 ("ntb_test: Add a selftest script for the NTB subsystem")
---
tools/testing/selftests/ntb/ntb_test.sh | 62 +
Simple (1 << pidx) operation causes undefined behaviour when
pidx >= 32. It must be casted to u64 to match the actual return
value of ntb_link_is_up() method, so to have all the possible
peer indexes covered and to get rid of undefined behaviour.
Additionally there are special macros in "linux/bito
ntb_perf driver has been also updated so to have the multi-port
interface support. User now must specify what peer port is going
to be used to perform the test.
Signed-off-by: Serge Semin
---
tools/testing/selftests/ntb/ntb_test.sh | 13 +++--
1 file changed, 7 insertions(+), 6 deletions
Link Up and Down methods are used to change NTB link settings on
local side only for multi-port devices. Link is considered up
only if both sides local and peer set it up. Intel/AMD hardware
acts a bit different by assigning the Primary and Secondary roles,
so Primary device only is able to change
DB interface of ntb_tool driver hasn't been changed much, but
db_valid_mask DebugFS file has still been added to new ntb_tool
driver. In this case it's much better to test all valid DB bits
instead of using the predefined mask, which may be incorrect in
general.
Signed-off-by: Serge Semin
---
to
There are devices (like IDT PCIe switches), which outbound MWs xlat address
is setup on peer side. In this case local side is supposed to allocate
a memory buffer and somehow deliver the xlat DMA address to peer so one
could set the outbound MW up. The MW test is altered so to support both
previous
Since Switchtec patch there has been a new topology added to
the NTB API. It's called NTB_TOPO_SWITCH and dedicated for
in general multi-port PCIe switch chips. Even though topo field
isn't used within the IDT driver much, lets set it for the sake
of unification.
Signed-off-by: Serge Semin
---
d
Scratchpad NTB API has been changed so has the ntb_tool driver.
Outbound Scratchpad DebugFS files have been moved to peer specific
directories. Each scratchpad is now available via separate file.
The test code has been accordingly altered.
Signed-off-by: Serge Semin
---
tools/testing/selftests/n
Messages NTB API is now available. ntb_tool driver has been altered
to perform messages send and receive operations. The test of messages
read/write to/from peer device has been added to the script.
Signed-off-by: Serge Semin
---
tools/testing/selftests/ntb/ntb_test.sh | 37 +
NTB API has been updated to support multi-port devices like IDT
89HPESx series or Microsemi Switchtec. Message registers
functionality has also been added to new API. In order to keep
the new hardware and corresponding capabilities well tested, NTB
performance driver is accordingly altered.
Signed
The dma_mask and dma_coherent_mask fields of the NTB struct device
weren't initialized in hardware drivers. In fact it should be done
instead of PCIe interface usage, since NTB clients are supposed to
use NTB API only and left unaware of real hardware implementation.
In addition to that ntb_device_
Multi-port interface is now available in ntb_tool driver. According
to the new NTB API, there might be more than two devices connected
over NTB. It means that each device can have multiple freely
enumerated ports. Each port got index assigned by the NTB hardware
driver. This test is performed to de
The multi-port NTB API was introduced in kernel 4.13 as well as the
first driver for the true multi-port devices of IDT PCIe-switches
series. But the test drivers still were left almost unchanged. Yes,
they didn't fail being used with new NTB API, but they only worked
with two-ports NTB devices. Th
NTB API has been updated to support multi-port devices like IDT
89HPESx series or Microsemi Switchtec. Message registers
functionality has also been added to new API. In order to keep
the new hardware and corresponding capabilities well tested, NTB
tool driver is accordingly altered.
Signed-off-by
There is a common methods signature form used over all the NTB API
like functions naming scheme, arguments names and order, etc.
Recently added NTB messaging API IO callbacks were named a bit
different so should be renamed to be in compliance with the rest
of the API. The changes are made in a way
Hi David,
> The bt_* printk macros include a \n already, so we don't need extra ones
> here.
>
> Signed-off-by: David Lechner
> ---
> drivers/bluetooth/hci_ll.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
patch has been applied to bluetooth-next tree.
Regards
Marcel
Hi David,
> When a TI Bluetooth chip is reset, it takes about 100ms for the RTS line of
> the chip to deassert. For my use case with a TI CC2560A chip, this delay
> was not long enough and caused the local UART to never transmit at all (TI
> AM1808 SoC UART2).
>
> We can wait for the CTS signal u
On Sun, Dec 03, 2017 at 04:37:01AM -0800, syzbot wrote:
> BUG: KASAN: use-after-free in skcipher_request_set_tfm
> include/crypto/skcipher.h:499 [inline]
> BUG: KASAN: use-after-free in crypto_aead_copy_sgl crypto/algif_aead.c:85
> [inline]
> BUG: KASAN: use-after-free in _aead_recvmsg crypto/algif
On 11/28/2017 11:29 AM, Sinan Kaya wrote:
> On 11/28/2017 10:30 AM, Ville Syrjälä wrote:
>>> + dev_priv->bridge_dev =
>>> + pci_get_domain_bus_and_slot(domain, 0, PCI_DEVFN(0, 0));
>> Maybe just pci_get_slot(pdev->bus, PCI_DEVFN(0, 0)) ?
>>
>> I guess if we want to be pedantic we could
This fixes the battery voltage monitoring gpio-hog settings.
When the gpio is low, it turns off the battery voltage to the ADC chip.
However, this needs to be on all of the time so that we can monitor
battery voltage.
Signed-off-by: David Lechner
---
arch/arm/boot/dts/da850-lego-ev3.dts | 2 +-
Hi Serge,
I love your patch! Yet something to improve:
[auto build test ERROR on v4.15-rc1]
[cannot apply to ntb/ntb-next next-20171201]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Serge-Sem
> > > We pretty much assume everything is DMA safe already, the majority of
> > > transfers go to/from kmalloc()ed scratch buffers so actually are DMA
> > > safe but for bulk transfers we use the caller buffer and there might be
> > > some problem users.
>
> > So, pretty much the situation I2C wa
On 12/03/2017 01:29 PM, David Lechner wrote:
This fixes the battery voltage monitoring gpio-hog settings.
When the gpio is low, it turns off the battery voltage to the ADC chip.
However, this needs to be on all of the time so that we can monitor
battery voltage.
Signed-off-by: David Lechner
-
2017-12-02 15:48 GMT+01:00 Sakari Ailus :
> Hi,
>
> On Fri, Dec 01, 2017 at 01:37:12PM -0500, Sven Van Asbroeck wrote:
>> From: Sakari Ailus
>>
>> The at24 driver creates dummy I2C devices to access offsets in the chip
>> that are outside the area supported using a single I2C address. It is not
>>
The capability check in nfnetlink_rcv() verifies that the caller
has CAP_NET_ADMIN in the namespace that "owns" the netlink socket.
However, nfnl_cthelper_list is shared by all net namespaces on the
system. An unprivileged user can create user and net namespaces
in which he holds CAP_NET_ADMIN to
+Cc linux-block
On Sun, Dec 03, 2017 at 06:25:01AM -0800, syzbot wrote:
> WARNING: CPU: 0 PID: 3081 at mm/slab_common.c:971 kmalloc_slab+0x5d/0x70
> mm/slab_common.c:971
> Kernel panic - not syncing: panic_on_warn set ...
>
[...]
> __do_kmalloc mm/slab.c:3706 [inline]
> __kmalloc+0x25/0x760 mm/
On Sun, Nov 19, 2017 at 02:36:01AM -0800, syzbot wrote:
> Hello,
>
> syzkaller hit the following crash on
> d9e0e63d9a6f88440eb201e1491fcf730272c706
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master
> compiler: gcc (GCC) 7.1.1 20170620
> .config is attached
> Raw console o
Hi Andrew,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.15-rc2 next-20171201]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/c
Hi Serge,
I love your patch! Yet something to improve:
[auto build test ERROR on v4.15-rc1]
[cannot apply to ntb/ntb-next next-20171201]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Serge-Sem
On Wed, Nov 15, 2017 at 12:29:19PM +0100, Steffen Klassert wrote:
> On Fri, Nov 10, 2017 at 02:14:06PM +1100, Herbert Xu wrote:
> > On Fri, Nov 10, 2017 at 01:30:38PM +1100, Herbert Xu wrote:
> > >
> > > I found the problem. This crap is coming from clone_policy. Now
> > > let me where this code
On Tue, Nov 14, 2017 at 04:46:01AM -0800, syzbot wrote:
> RBP: R08: R09:
> R10: R11: R12:
> R13: R14: R15:
> kasan: CONFIG_KASAN_INLINE enabled
>
Hi Lorenzo,
Le 29/11/2017 à 18:34, Lorenzo Pieralisi a écrit :
> On Thu, Nov 23, 2017 at 04:01:48PM +0100, Cyrille Pitchen wrote:
>> This patch adds support to the Cadence PCIe controller in host mode.
>
> Bjorn already commented on this, it would be good to add some
> of the cover letter details
Hello,
I have constructed another demonstration program.
#include
#include
#include
int main(void)
{
FILE *f = fopen("/dev/full", "a");
if (!f)
goto report_failure;
{
int const c = 'X';
if (fputc(c, f) != c)
goto repo
On 2017-12-03 12:12, Fabio Estevam wrote:
> Hi Peter,
>
> On Sun, Dec 3, 2017 at 4:59 AM, Peter Rosin wrote:
>
>> Right. However, the patch adding that should have been sent to me, the
>> maintainer of the driver. That is carefully recorded in MAINTAINERS. So,
>> forgive me for assuming that not
On Sun, Dec 3, 2017 at 6:53 PM, Peter Rosin wrote:
> That's funny, because I get the below on both 4.14 and 4.15-rc1. And I
> expect the same ever since the driver was added some 3 years ago.
>
> $ scripts/get_maintainer.pl your-patch-from[1].diff | grep Peter
> Peter Rosin (maintainer:NXP TFA98
Hi Ben,
Thanks for the patch. I have some comments in the code below.
Please take a look.
On 11/28/2017 10:54 PM, Ben Whitten wrote:
> This commit introduces a NETDEV trigger for named device
> activity. Available triggers are link, rx, and tx.
>
> Signed-off-by: Ben Whitten
> ---
> .../ABI/te
With gcc 4.1.2:
mm/memory.o: In function `wp_huge_pmd':
memory.c:(.text+0x9b4): undefined reference to `do_huge_pmd_wp_page'
Interestingly, wp_huge_pmd() is emitted in the assembler output, but
never called.
Apparently replacing the call to pmd_write() in __handle_mm_fault() by a
call to
From: Randy Dunlap
The pci/htirq.c file was removed so remove it from the documentation
file also.
Error: Cannot open file ../drivers/pci/htirq.c
WARNING: kernel-doc '../scripts/kernel-doc -rst -enable-lineno -export
../drivers/pci/htirq.c' failed with return code 2
Fixes: fd2fa6c18b72 ("x86/P
From: Randy Dunlap
Fix kernel-doc warnings after code restructuring.
../kernel/sched/core.c:5113: warning: No description found for parameter 't'
../kernel/sched/core.c:5113: warning: Excess function parameter 'interval'
description in 'sched_rr_get_interval'
Fixes: abca5fc535a3e ("sched_rr_ge
The following patch makes it easier to disable all SSB config
options without entering the submenu. It will also enable one
to see that en-disabled state from the outside menu.
This is only intended to change menuconfig UI, not change
the config dependencies.
No need to get into the submenu to disable all SSB-related config entries
Signed-off-by: Vincent Legoll
---
drivers/ssb/Kconfig | 9 -
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/drivers/ssb/Kconfig b/drivers/ssb/Kconfig
index d8e4219c2324..f48a2ee587a4 100644
--- a/dri
On Sun, 3 Dec 2017 15:17:32 +
Trond Myklebust wrote:
> > I would like to check corresponding build results then without extra
> > optimisation applied by the compiler.
> > But I got surprised by error messages for a command like the
> > following.
> >
> > elfring@Sonne:~/Projekte/Linux/next-
Hi all,
Commit
5f56b7f4854a ("Revert "Merge tag 'scpi-updates-4.15' of
git://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux into
next/drivers"")
is missing a Signed-off-by from its author or committer.
Reverts are commits as well and so need an explanation of why they
are done a
The buses should honor the firmware interface used to register the device,
but the I2C core reports a MODALIAS of the form i2c: even for I2C
devices registered via OF.
This means that user-space will never get an OF stype uevent MODALIAS even
when the drivers modules contain aliases exported from
We need to always wait for the last write to complete and we want the
regmap to be protected from concurrent access during that wait. That
makes using the regmap's default locking impossible and we're
protecting it with an external mutex.
Set an empty function as the callback for regmap's lock and
Convert the driver to the modern blk-mq framework.
As byproduct we get rid of our open coded restart logic and let
blk-mq handle it.
Signed-off-by: Richard Weinberger
---
arch/um/drivers/ubd_kern.c | 178 +++--
1 file changed, 93 insertions(+), 85 deletion
These duplicate includes have been found with scripts/checkincludes.pl but
they have been removed manually to avoid removing false positives.
Unit Testing:
- build successful
- LTP testsuite passes.
- checkpatch.pl passes
Signed-off-by: Pravin Shedge
---
arch/arm/crypto/aes-ce-glue.c
Christoph,
Am Mittwoch, 29. November 2017, 22:46:51 CET schrieb Christoph Hellwig:
> On Sun, Nov 26, 2017 at 02:10:53PM +0100, Richard Weinberger wrote:
> > MAX_SG is 64, used for blk_queue_max_segments(). This comes from
> > a0044bdf60c2 ("uml: batch I/O requests"). Is this still a good/sane
> >
> Why would you compile the kernel without optimization?
I would like to see how big an effect finally is in such a build configuration
after specific source code adjustments.
> There's many places in the kernel that WILL NOT BUILD without optimization.
I did not really know this detail so far.
This fixes the battery voltage monitoring gpio-hog settings.
When the gpio is low, it turns off the battery voltage to the ADC chip.
However, this needs to be on all of the time so that we can monitor
battery voltage.
Also, there was a typo that prevented pinmuxing from working correctly.
Signed
Am 03.12.2017 21:46, schrieb SF Markus Elfring:
> Hello,
>
> I have constructed another demonstration program.
>
>
> #include
> #include
> #include
>
> int main(void)
> {
> FILE *f = fopen("/dev/full", "a");
>
> if (!f)
> goto report_failure;
>
> {
>
This fixes the battery voltage monitoring gpio-hog settings.
When the gpio is low, it turns off the battery voltage to the ADC chip.
However, this needs to be on all of the time so that we can monitor
battery voltage.
Also, there was a typo that prevented pinmuxing from working correctly.
Signed
On Sun, 3 Dec 2017 13:15:39 -0800
Randy Dunlap wrote:
> The pci/htirq.c file was removed so remove it from the documentation
> file also.
>
> Error: Cannot open file ../drivers/pci/htirq.c
> WARNING: kernel-doc '../scripts/kernel-doc -rst -enable-lineno -export
> ../drivers/pci/htirq.c' failed
On Mon, Nov 27, 2017 at 10:25:16AM -0800, Vineet Gupta wrote:
> +CC linux-arch, Arnd
>
> On 11/23/2017 09:17 AM, Alexey Brodkin wrote:
> >Hi Sudip,
> >
> >On Tue, 2017-11-21 at 22:10 +, Sudip Mukherjee wrote:
> I understand the case/need for adding a weak/common abort() as a
> quick fix for
Hi Krzysztof,
Today's linux-next merge of the samsung-krzk tree got a conflict in:
arch/arm/configs/multi_v7_defconfig
between commit:
f15187dcdbcd ("ARM: config: sync multi-v7 config with keystone peripherals")
from the keystone tree and commit:
453c63073185 ("ARM: multi_v7_defconfig:
Add support for the ACPI batteries on newer thinkpad models
(>Sandy Bridge) that support the setting of start and stop
thresholds.
The actual interface to the driver is a extension for the
existing ACPI battery driver. This was done so that users
can write transparently to the interface of the ACP
Add support for the ACPI batteries on newer thinkpad models
(>Sandy Bridge) that support the setting of start and stop
thresholds.
The actual interface to the driver is a extension for the
existing ACPI battery driver. This was done so that users
can write transparently to the interface of the ACP
On 03/12/17 21:54, Richard Weinberger wrote:
> Christoph,
>
> Am Mittwoch, 29. November 2017, 22:46:51 CET schrieb Christoph Hellwig:
>> On Sun, Nov 26, 2017 at 02:10:53PM +0100, Richard Weinberger wrote:
>>> MAX_SG is 64, used for blk_queue_max_segments(). This comes from
>>> a0044bdf60c2 ("uml: b
Hello,
Many thanks for the driver.
The ./scripts/checkpatch.pl with --strict has many warnings, some of which might
be nice to have cleaned up.
There are some very minor comments below. Similar constructs are in other files
too.
After reading and understanding through all the code, I think the
Hi Al,
Today's linux-next merge of the vfs tree got a conflict in:
drivers/net/ethernet/via/via-rhine.c
between commit:
a7e4fbbfdf79 ("net: via: via-rhine: use %p to format void * address instead
of %x")
from Linus' tree and commit:
68fef306c2a5 ("via: trivial sparse annotations")
fro
On Mon, Dec 04, 2017 at 03:19:39AM +0530, Pravin Shedge wrote:
> These duplicate includes have been found with scripts/checkincludes.pl but
> they have been removed manually to avoid removing false positives.
>
> Unit Testing:
>
> - build successful
> - LTP testsuite passes.
> - checkpatch.pl pas
Hi Ravi,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on shawnguo/for-next]
[also build test ERROR on v4.15-rc2 next-20171201]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linu
Hi Al,
After merging the vfs tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
arch/powerpc/kvm/../../../virt/kvm/kvm_main.c: In function 'hva_to_pfn_slow':
arch/powerpc/kvm/../../../virt/kvm/kvm_main.c:1379:35: error: 'start'
undeclared (first use in this function)
np
On Mon, 2017-12-04 at 03:19 +0530, Pravin Shedge wrote:
> These duplicate includes have been found with scripts/checkincludes.pl but
> they have been removed manually to avoid removing false positives.
Can you list the duplicates that were not removed as well please?
As per MADT specification, it's perfectly valid firmware can pass
MADT table to OS with disabled GICC entries. ARM64-SMP code skips
those cpu cores to bring online. However the current GICv3 driver
probe bails out in this case on systems where redistributor regions
are not in the always-on power do
There is currently very little documentation in the kernel on maintainer
level tasks. In particular there are no documents on creating pull
requests to submit to Linus.
Quoting Greg Kroah-Hartman on LKML:
Anyway, this actually came up at the kernel summit / maintainer
meeting a few weeks
From: Randy Dunlap
Fix documentation build errors after intel_guc_loader.c was
renamed to intel_guc_fw.c.
Error: Cannot open file ../drivers/gpu/drm/i915/intel_guc_loader.c
WARNING: kernel-doc '../scripts/kernel-doc -rst -enable-lineno -function
GuC-specific firmware loader ../drivers/gpu/drm/i
Hi all,
There is a series of commits
54cff6479fd8 - c1802534e5a6
(not all in that range)
that are missing a Signed-off-by from their committer.
--
Cheers,
Stephen Rothwell
Hi all,
After merging the net-next tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
drivers/net/phy/broadcom.c:391:12: warning: 'bcm5482_read_status' defined but
not used [-Wunused-function]
static int bcm5482_read_status(struct phy_device *phydev)
^
dr
If there's enthusiasm for what I've proposed over Eddy and Brad's patch,
I'll clean up the kbuild issues and resend. It was more meant to trigger
discussion than sent as ready for submission.
Cheers,
Andrew
On Mon, 4 Dec 2017, at 06:55, kbuild test robot wrote:
> Hi Andrew,
>
> Thank you for th
On Fri, Dec 01, 2017 at 06:39:07PM +0530, kaiwan.billimo...@gmail.com wrote:
> Hi,
>
> Applies upon the previous one in this thread.
> Found and fixed some minor issues with light testing on a 32-bit x86.
> (I realize this isn't an ideal description, forgive me!).
>
> Have also emitted a 'noisy'
On Thu, Nov 16, 2017 at 08:22:37AM +0100, Ingo Molnar wrote:
>
> * Byungchul Park wrote:
>
> > On Sat, Nov 11, 2017 at 10:45:24PM +0900, Byungchul Park wrote:
> > > This is the big one including all of version 3.
> > >
> > > You can take only this.
> >
> > Hello Ingo,
> >
> > Could you consid
Am 03.12.2017 um 15:15 schrieb Andreas Färber:
> Hi,
>
> Am 21.06.2017 um 16:42 schrieb Neil Armstrong:
>> diff --git a/arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi
>> b/arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi
>> index 17d3efd..ea53cc2 100644
>> --- a/arch/arm64/boot/dts/amlogic/meson-gxbb.dts
On 12/03/2017 01:24 PM, Eric Biggers wrote:
> On Sun, Nov 19, 2017 at 02:36:01AM -0800, syzbot wrote:
>> Hello,
>>
>> syzkaller hit the following crash on
>> d9e0e63d9a6f88440eb201e1491fcf730272c706
>> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master
>> compiler: gcc (GCC) 7
Sending the switch state change twice within the same frame is invalid evdev
protocol and only works if the client handles keys immediately as well.
Processing events immediately is incorrect, it forces a fake order of events
that does not exist on the device.
Recent versions of libinput changed t
Hi all,
After merging the drm tree, today's linux-next build (x86_64 allmodconfig)
produced this warning:
drivers/gpu/drm/i915/gvt/cmd_parser.c: In function 'perform_bb_shadow':
drivers/gpu/drm/i915/gvt/cmd_parser.c:1647:8: warning: unused variable 'dst'
[-Wunused-variable]
void *dst = NULL;
On Sun, Dec 03, 2017 at 05:24:32PM -0700, Jens Axboe wrote:
> On 12/03/2017 01:24 PM, Eric Biggers wrote:
> > On Sun, Nov 19, 2017 at 02:36:01AM -0800, syzbot wrote:
> >> Hello,
> >>
> >> syzkaller hit the following crash on
> >> d9e0e63d9a6f88440eb201e1491fcf730272c706
> >> git://git.kernel.org/pu
On 12/03/2017 05:44 PM, Eric Biggers wrote:
> On Sun, Dec 03, 2017 at 05:24:32PM -0700, Jens Axboe wrote:
>> On 12/03/2017 01:24 PM, Eric Biggers wrote:
>>> On Sun, Nov 19, 2017 at 02:36:01AM -0800, syzbot wrote:
Hello,
syzkaller hit the following crash on
d9e0e63d9a6f88440eb201
Hi Vlastimil,
On 2017/12/1 23:18, Vlastimil Babka wrote:
> On 12/01/2017 10:55 AM, Yisheng Xie wrote:
>> As in manpage of migrate_pages, the errno should be set to EINVAL when
>> none of the node IDs specified by new_nodes are on-line and allowed by the
>> process's current cpuset context, or none
The series is aimed at making input events y2038 safe.
It extends the lifetime of the realtime timestamps in the
events to year 2106.
The series is also a necessary update as glibc is set to provide
64 bit time_t support for 32 bit binaries. glibc plan is detailed
at https://sourceware.org/glibc/wi
struct timeval which is part of struct input_event to
maintain the event times is not y2038 safe.
Real time timestamps are also not ideal for input_event
as this time can go backwards as noted in the patch
a80b83b7b8 by John Stultz.
Arnd Bergmann suggested deprecating real time and using
monotoni
struct timeval is not y2038 safe.
All usage of timeval in the kernel will be replaced by
y2038 safe structures.
The change is also necessary as glibc is introducing support
for 32 bit applications to use 64 bit time_t. Without this
change, many applications would incorrectly interpret values
in the
struct timeval is not y2038 safe.
All references to timeval in the kernel will be replaced
by y2038 safe structures.
Replace all references to timeval with y2038 safe
struct timespec64 here.
struct input_event will be changed in a different patch.
Signed-off-by: Deepa Dinamani
Reviewed-by: Arnd
struct timeval is not y2038 safe.
All references to timeval will be deleted from the
kernel to make it y2038 safe.
Replace its uses by y2038 safe struct timespec64.
The timestamps changed here only keep track of delta
times. These timestamps are also internal to kernel.
Hence, monotonic times are
On 4 December 2017 at 10:30, Stephen Rothwell wrote:
> Hi all,
>
> After merging the drm tree, today's linux-next build (x86_64 allmodconfig)
> produced this warning:
Oops, not sure how I missed it, force pushed drm-next with the merge fixed.
Dave.
On Fri, 1 Dec 2017, Paul E. McKenney wrote:
> Now that the associative-array library properly heads dependency chains,
> the various smp_read_barrier_depends() calls in security/keys/keyring.c
> are no longer needed. This commit therefore removes them.
>
> Signed-off-by: Paul E. McKenney
> Cc:
Hi Emil,
On Saturday, December 02, 2017 01:55 AM, Emil Velikov wrote:
On 30 November 2017 at 06:13, Lin Huang wrote:
Support Innolux P097PFG 9.7" 1536x2048 TFT LCD panel,
it refactor Innolux P079ZCA panel driver, let it support
multi panel, and add support P097PFG panel in this driver.
Coup
2017-12-01 20:19 GMT+08:00 Linus Walleij :
> On Mon, Nov 27, 2017 at 1:28 PM, Greentime Hu wrote:
>
>> From: Rick Chen
>>
>> Add a document to describe Andestech atcpit100 timer and
>> binding information.
>>
>> Signed-off-by: Rick Chen
>> Acked-by: Rob Herring
>> Signed-off-by: Greentime Hu
>
On Tue, Nov 07, 2017 at 07:23:27PM -0800, Richard Cochran wrote:
> The application does join that group on the external (slave)
> interface. I'll find out why the delay request mechanism isn't
> working...
Looking back, I now recall that the series lets the HW embed the time
stamps into the proto
On 12/1/2017 2:25 PM, BILL ENGVALD wrote:
> One of the flaws in *NIX software is that a simple command can lead to
> a nightmare, so I would like the kernel devs to write code that
> repairs Linux automatically. I would like it if Linux became
> completely stable regardless of memory failures, gene
> >>> + case MSR_IA32_RTIT_ADDR0_A ... MSR_IA32_RTIT_ADDR3_B: {
> >>> + u32 eax, ebx, ecx, edx;
> >>> +
> >>> + cpuid_count(0x14, 1, &eax, &ebx, &ecx, &edx);
> >>
> >> Please cache the cpuid_count result, or do the cpuid_count after testing
> >> vmx_pt_suppor
Hi Anderson,
Could you please check about below thread?
https://patchwork.kernel.org/patch/6357751/
Your patch is same as my old one.
On 11/30/17, Bjorn Andersson wrote:
> Occasionally the following error message can be seen in the logs of
> Qualcomm devices using UFS:
>
> EXT4-fs (sda9): Dela
101 - 200 of 332 matches
Mail list logo
