Hi Anoob,
[auto build test ERROR on v4.9-rc8]
[also build test ERROR on next-20170519]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
On 20.05.2017 19:42, Paul E. McKenney wrote:
On Fri, May 19, 2017 at 10:03:59AM +0300, Konstantin Khlebnikov wrote:
This allows to get rid of unneeded invocations.
Function debug_lockdep_rcu_enabled() becomes really hot if several
debug options are enabled together with CONFIG_PROVE_RCU.
sysfs_get_dirent is usually invoked with a string literal, which
have the type char[]. While the toplevel Makefile
disables -Wpointer-sign, other Makefiles like
arch/x86/boot/compressed/Makefile
redefine KBUILD_CFLAGS. Fixes the warning:
In file included from
Hi all,
it seems like the Alpha Jense build (the only one using pci-noop.c)
and thus being a different build than all the later PCI capable
system has been broken since at least:
commit 6aca0503847f6329460b15b3ab2b0e30bb752793
Author: Christian Borntraeger
Date: Tue Feb 2 21:46:33 2016 -0800
Remove the space character between "PCI" and the colon.
This was printed before the patch:
PCI : PCI BIOS area is rw and x. Use pci=nobios if you want it NX.
Whereas other PCI printks are like that:
$ dmesg | grep 'PCI:'
[0.649178] PCI: MMCONFIG for domain [bus 00-7f] at [mem
Hi Borislav,
2017-05-21 5:33 GMT+09:00 Borislav Petkov :
> On Sun, May 21, 2017 at 04:38:35AM +0900, Masahiro Yamada wrote:
>> Strange, I could not reproduce this.
>
> Remove libncurses5-dev or whatever it is called on your system and do:
>
> $ make menuconfig
> HOSTCC scripts/kconfig/mconf.o
2017-05-13 1:25 GMT+08:00, James Morse :
> Hi gengdongjiu,
>
> On 10/05/17 09:44, gengdongjiu wrote:
>> On 2017/5/9 1:28, James Morse wrote:
> (hwpoison for KVM is a corner case as Qemu's memory effectively has two
> users,
> Qemu and KVM. This isn't the example of how user-space gets
On Sun, May 21, 2017 at 10:48:19AM +0300, Mika Westerberg wrote:
> On Sun, May 21, 2017 at 07:31:14AM +0200, Lukas Wunner wrote:
> > On Fri, May 19, 2017 at 01:28:36PM +0300, Mika Westerberg wrote:
> > > On Fri, May 19, 2017 at 12:07:10PM +0200, Lukas Wunner wrote:
> > > > If there can be many
> Markus, can you please stop CCing me on every of those patches?
Yes, of course.
>> Link:
>> http://events.linuxfoundation.org/sites/events/files/slides/LCJ16-Refactor_Strings-WSang_0.pdf
Did I interpret any information from your presentation slides in an
inappropriate way?
> And why do
On Sun, May 21, 2017 at 06:15:53PM +0900, Masahiro Yamada wrote:
> Could you change line 199
>
> $(addprefix $(obj)/,$(lxdialog)): $(obj)/dochecklxdialog
>
> to
>
> $(addprefix $(obj)/, mconf.o $(lxdialog)): $(obj)/dochecklxdialog
>
> and send v2, please?
Here it is:
---
From: Borislav
Hi,
On 20-05-17 21:26, Paul Gortmaker wrote:
On Sat, May 20, 2017 at 3:21 PM, Paul Gortmaker
wrote:
On Mon, May 15, 2017 at 2:20 PM, Hans de Goede wrote:
Hi,
This is actually v7, with the following changes:
Changes in v7:
-Add explanation why this is a bool and why it selects
> -Original Message-
> From: Levy, Amir (Jer)
> Sent: Sunday, May 21, 2017 11:07
> To: Mika Westerberg ; Lukas Wunner
>
> Cc: Greg Kroah-Hartman ; Andreas Noever
> ; Jamet, Michael ;
> Bernat, Yehezkel ; Andy Lutomirski
> ; mario.limoncie...@dell.com;
> jared.doming...@dell.com; Andy
Markus,
> > Markus, can you please stop CCing me on every of those patches?
>
> Yes, of course.
Thanks!
> >> Link:
> >> http://events.linuxfoundation.org/sites/events/files/slides/LCJ16-Refactor_Strings-WSang_0.pdf
>
> Did I interpret any information from your presentation slides in an
>
> Have you read my LWN article "Best practices for a big patch series"?
>
> https://lwn.net/Articles/585782/
Yes.
>> This can also happen as a side effect if such a source code search pattern
>> will point hundreds of places out for further software development
>> considerations.
>> How would
Linus,
please pull the latest irq-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
irq-urgent-for-linus
A set of small fixes for the irq subsystem:
- Cure a data ordering problem with chained interrupts
- Three small fixlets for the mbigen irq
Linus,
please pull the latest sched-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
sched-urgent-for-linus
A single scheduler fix:
Prevent idle task from ever being preempted. That makes sure that
synchronize_rcu_tasks() which is ignoring idle
> How do you think about to resolve them by additional means besides mail
> exchange?
That can work. E.g. meeting at conferences often solved mail
communication problems.
For now, I still wonder why you were unsure about grouping the changes
into one patch? Maybe there is something to be
From: Marek Belisko
The twl4030_charger driver expects an iio channel to detect the
presence of an AC charger by looking at VAC (madc channel 11).
This definition is missing in the device tree.
Signed-off-by: Marek Belisko
Signed-off-by: Sebastian Reichel
---
arch/arm/boot/dts/twl4030.dtsi |
Since we now support the standard 'input_current_limit' property by
commit 3fb319c2cdcd ("power: supply: twl4030-charger: add writable
INPUT_CURRENT_LIMIT property")
we can now remove the nonstandard 'max_current' sysfs attribute.
See Documentation/power/power_supply_class.txt line 125
Both
Changes V5:
* reworked max_current removal patch (comments by Sebastian Reichel)
* resubmit missing madc connection for AC power detection
* resubmit patch for irq allocation and -EPROBE_DEFER
* rebased on 4.12-rc1
Changes V4:
* resent commit (original one did contain material not upstream)
This fixes an issue if both this twl4030_charger driver and
phy-twl4030-usb are compiled as modules and loaded in random order.
It has been observed on GTA04 and OpenPandora devices that in worst
case the boot process hangs and in best case the AC detection fails
with a warning.
Therefore we add
Signed-off-by: H. Nikolaus Schaller
---
arch/arm/boot/dts/omap3-gta04.dtsi | 18 ++
1 file changed, 18 insertions(+)
diff --git a/arch/arm/boot/dts/omap3-gta04.dtsi
b/arch/arm/boot/dts/omap3-gta04.dtsi
index 430b438e0ee9..45f0c109960f 100644
---
Add driver for Wi2Wi W2CBW003 WiFi and Bluetooth module
where the Bluetooth interface is connected through uart.
Uses the new serdev API to glue with tty and turn on/off the
module if the tty port (/dev/ttyBTn) is opened.
Note that this is only for the Bluetooth side. The WLAN
(libertas) sdio
Since our proposed API was not acceptable and the new serdev API has arrived in
4.11 kernels,
we finally took the challenge to update the w2sg and w2cbw drivers to use the
serdev API.
The approach is to write a "man in the middle" driver which is on one side a
serdev client
which directly
On Sun, May 21, 2017 at 08:07:08AM +, Levy, Amir (Jer) wrote:
> On Sun, May 21 2017, 11:00 AM, Mika Westerberg wrote:
> > On Sun, May 21, 2017 at 10:40:41AM +0300, Mika Westerberg wrote:
> > > On Sun, May 21, 2017 at 07:35:21AM +0200, Lukas Wunner wrote:
> > > > On Sun, May 21, 2017 at
Add driver for Wi2Wi W2SG0004/84 GPS module connected through uart.
Use serdev API hooks to monitor and forward the UART traffic to /dev/BTn
and turn on/off the module. It also detects if the module is turned on (sends
data)
but should be off, e.g. if it was already turned on during boot or
>> How do you think about to resolve them by additional means besides mail
>> exchange?
>
> That can work.
I am curious to find out which other communication means could really help here.
> E.g. meeting at conferences often solved mail communication problems.
I find my resources too limited
On Sun, May 21, 2017 at 09:55:55AM +, Bernat, Yehezkel wrote:
>
>
> > -Original Message-
> > From: Levy, Amir (Jer)
> > Sent: Sunday, May 21, 2017 11:07
> > To: Mika Westerberg ; Lukas Wunner
> >
> > Cc: Greg Kroah-Hartman ; Andreas Noever
> > ; Jamet, Michael ;
> > Bernat, Yehezkel
On 17/05/17 16:28, Jan Kiszka wrote:
This is an upstream port of an IIO driver for the TI ADC108S102 and
ADC128S102. The former can be found on the Intel Galileo Gen2 and the
Siemens SIMATIC IOT2000. For those boards, ACPI-based enumeration is
included.
Due to the lack of regulators under ACPI,
> Am 21.05.2017 um 12:44 schrieb H. Nikolaus Schaller :
>
> Add driver for Wi2Wi W2SG0004/84 GPS module connected through uart.
>
> Use serdev API hooks to monitor and forward the UART traffic to /dev/BTn
s/BTn/GPSn/
> and turn on/off the module. It also detects if the module is turned on
On 20/05/17 19:36, Brian Masney wrote:
On Sat, May 20, 2017 at 06:55:02PM +0100, Jonathan Cameron wrote:
On 19/05/17 10:37, surenderpols...@gmail.com wrote:
From: Surender Polsani
Fixed the following checkpatch.pl warnings:
octal permissions are more preferable than symbolic permissions
From: Markus Elfring
Date: Sun, 21 May 2017 11:23:55 +0200
Omit an extra message for a memory allocation failure in this function.
This issue was detected by using the Coccinelle software.
Link:
http://events.linuxfoundation.org/sites/events/files/slides/LCJ16-Refactor_Strings-WSang_0.pdf
Commit-ID: 3780578761921f094179c6289072a74b2228c602
Gitweb: http://git.kernel.org/tip/3780578761921f094179c6289072a74b2228c602
Author: Rob Landley
AuthorDate: Sat, 20 May 2017 15:03:29 -0500
Committer: Thomas Gleixner
CommitDate: Sun, 21 May 2017 13:04:27 +0200
x86/boot: Use
A sealable memory allocator patch was proposed at
http://lkml.kernel.org/r/20170519103811.2183-1-igor.sto...@huawei.com ,
and is waiting for a follow-on patch showing how any of the kernel
can be changed to use this new subsystem. So, here it is for LSM hooks.
The LSM hooks ("struct
> -Original Message-
> From: Mika Westerberg [mailto:mika.westerb...@linux.intel.com]
> Sent: Sunday, May 21, 2017 13:47
> To: Bernat, Yehezkel
> Cc: Levy, Amir (Jer) ; Lukas Wunner
> ; Greg Kroah-Hartman ;
> Andreas Noever ; Jamet, Michael
> ; Andy Lutomirski ;
>
> Hi all,
>
> it seems like the Alpha Jense build (the only one using pci-noop.c)
> and thus being a different build than all the later PCI capable
> system has been broken since at least:
>
> commit 6aca0503847f6329460b15b3ab2b0e30bb752793
> Author: Christian Borntraeger
> Date: Tue Feb 2
On 2017-05-18 19:43, Andy Shevchenko wrote:
> On Thu, May 18, 2017 at 5:59 PM, Jan Kiszka wrote:
>> On the SIMATIC, IOT2040 only a single pin is exportable as GPIO, the
>> rest is required to operate the UART. To allow modeling this case,
>> expand the platform device data structure to specify a
On 2017-05-18 19:14, Andy Shevchenko wrote:
> On Thu, May 18, 2017 at 5:59 PM, Jan Kiszka wrote:
>> This fixes reloading of the GPIO driver for the same platform device
>> instance as created by the exar UART driver: First of all, the driver
>> sets drvdata to its own value during probing and
Hi Sudip,
why do we carry
if (pcidev->vendor != PCI_VENDOR_ID_EXAR)
return -ENODEV;
in gpio_exar_probe? This effectively prevents that
EXAR_DEVICE(COMMTECH, COMMTECH_4222PCIE, pbn_exar_XR17V35x),
EXAR_DEVICE(COMMTECH, COMMTECH_4224PCIE,
On Sun, May 21, 2017 at 11:18:01AM +, Bernat, Yehezkel wrote:
> Nothing that I'm aware of.
OK.
> Still, I like the idea of having a table-like construct somewhere in
> the code to centralize the handling of various controller-specific
> info (generation, DMA port, maybe more things in the
On 17/05/17 12:35, Eugen Hristev wrote:
On 17.05.2017 10:47, Peter Rosin wrote:
On 2017-05-16 20:03, Jonathan Cameron wrote:
As we are only left with one area of questions.
+static const struct at91_adc_trigger at91_adc_trigger_list[] = {
+{
+.name = "external-rising",
+
On 2017-05-21 12:47, Jonathan Cameron wrote:
> On 17/05/17 16:28, Jan Kiszka wrote:
>> This is an upstream port of an IIO driver for the TI ADC108S102 and
>> ADC128S102. The former can be found on the Intel Galileo Gen2 and the
>> Siemens SIMATIC IOT2000. For those boards, ACPI-based enumeration
On 16/05/17 07:52, Raveendra Padasalagi wrote:
The third argument of devm_request_threaded_irq() is the primary
handler. It is called in hardirq context and checks whether the
interrupt is relevant to the device. If the primary handler returns
IRQ_WAKE_THREAD, the secondary handler (a.k.a.
On Sun, May 21, 2017 at 01:19:39AM +, Wei Yongjun wrote:
> From: Wei Yongjun
>
> In case of error, the function platform_device_register_simple() returns
> ERR_PTR() and never returns NULL. The NULL test in the return value
> check should be replaced with IS_ERR().
>
> Fixes: 315f0242aa2b
On 21/05/17 12:59, Jan Kiszka wrote:
On 2017-05-21 12:47, Jonathan Cameron wrote:
On 17/05/17 16:28, Jan Kiszka wrote:
This is an upstream port of an IIO driver for the TI ADC108S102 and
ADC128S102. The former can be found on the Intel Galileo Gen2 and the
Siemens SIMATIC IOT2000. For those
On 21/05/17 13:17, Jonathan Cameron wrote:
On 21/05/17 12:59, Jan Kiszka wrote:
On 2017-05-21 12:47, Jonathan Cameron wrote:
On 17/05/17 16:28, Jan Kiszka wrote:
This is an upstream port of an IIO driver for the TI ADC108S102 and
ADC128S102. The former can be found on the Intel Galileo Gen2
On Fri, May 19, 2017 at 11:04 AM, Arnd Bergmann wrote:
> A rare randconfig build error shows up when we have CONFIG_CRYPTO=m
> in combination with a built-in CCREE driver:
>
> crypto/hmac.o: In function `hmac_update':
> hmac.c:(.text.hmac_update+0x28): undefined reference to `crypto_shash_update'
On Sun, May 21, 2017 at 9:00 AM, Christoph Hellwig wrote:
> On Thu, May 18, 2017 at 10:57:31AM +0200, Arnd Bergmann wrote:
>> How expensive would it be to add another field to timer_list and
>> just have both pointers?
>
> That would add 4/8 bytes to every structure containing a timer,
> so I'd
On 2017-05-21 14:18, Jonathan Cameron wrote:
> On 21/05/17 13:17, Jonathan Cameron wrote:
>> On 21/05/17 12:59, Jan Kiszka wrote:
>>> On 2017-05-21 12:47, Jonathan Cameron wrote:
On 17/05/17 16:28, Jan Kiszka wrote:
> This is an upstream port of an IIO driver for the TI ADC108S102 and
Hi everyone
This series adds support for the latest model in Linksys WRT AC series
of routers. The WRT3200ACM was released in October 2016 and the code
name is Rango.
As it comes with a flash chip twice as big the dts Imre Kaloz has
written for OpenWrt isn't based on armada-385-linksys.dtsi to
Add labels to nodes used by dependants. Also rename node gpio_keys to
gpio-keys to mach the style of the rest of the file as well as the
documented example.
Signed-off-by: Ralph Sennhauser
---
arch/arm/boot/dts/armada-385-linksys.dtsi | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
The Linksys WRT3200ACM (Rango) is the lates Armada-385 based router in
the Linksys WRT AC Series which got released in October 2016.
The file armada-385-linksys-rango.dts is loosly based off of a DTS
authored by Imre Kaloz.
As Rango is part of the armada-385-linksys family of boards use the
Buttons don't have a reg property; drop pseudo address and fixup names
of individual button nodes. Also drop #address-cells and #size-cells
properties.
Signed-off-by: Ralph Sennhauser
---
arch/arm/boot/dts/armada-385-linksys.dtsi | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff
Flatten dts of individual boards to match the new style used in
armada-385-linksys.dtsi and for the Rango addition.
* Caiman - Linksys WRT1200AC v1 & v2
* Cobra - Linksys WRT1900AC v2
* Shelby - Linksys WRT1900ACS v1 & v2
Signed-off-by: Ralph Sennhauser
---
Notes:
power and sata in _leds
Since the addition of the spi reference two styles are used. Use
references instead of recreating the same structure over and over again.
This helps to distinguish which are changes to the underlying nodes and
which are new additions and helps helps maintainability in general.
Verified the
Drop redundant declaration of #address-cells and #size-cells.
Signed-off-by: Ralph Sennhauser
---
arch/arm/boot/dts/armada-385-linksys-caiman.dts | 3 ---
arch/arm/boot/dts/armada-385-linksys-cobra.dts | 3 ---
arch/arm/boot/dts/armada-385-linksys-shelby.dts | 3 ---
3 files changed, 9
Which pools we assing doesn't matter. Use the order which doesen't leave
a chance for questions for first time readers.
Signed-off-by: Ralph Sennhauser
---
arch/arm/boot/dts/armada-385-linksys.dtsi | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git
Now that we use the reference for the USB3.0 port update the node name
and labels for the phy and vbus to match the label used by
armada-38x.dtsi.
Signed-off-by: Ralph Sennhauser
---
Notes:
Going by documentation regulator-name is only of informative nature so
changing it should be a non
The new ones work so there is little reason to keep the legacy bindings.
Use the rework as the oportunity to drop the legacy node.
Signed-off-by: Ralph Sennhauser
---
Notes:
There is little harm in keeping them but probably no value either, so
use the cleanup series to get rid of them.
Use IEEE 1541-2002 unit prefixes for sizes.
Signed-off-by: Ralph Sennhauser
---
arch/arm/boot/dts/armada-385-linksys.dtsi | 22 +++---
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a/arch/arm/boot/dts/armada-385-linksys.dtsi
The Linksys WRT3200ACM CPU is clocked at 1866MHz. Add 1866MHz to
the list of supported CPU frequencies.
Noticed by the following warning:
[0.00] Selected CPU frequency (16) unsupported
Signed-off-by: Ralph Sennhauser
---
drivers/clk/mvebu/armada-38x.c | 3 ++-
1 file changed, 2
A pin group per node is sufficient, further specialisation only serves
as documentation which can be a comment just as well. This simplifies
configuring pins for nodes in dependants.
Also use labels which end up right by the node they are intended for.
Signed-off-by: Ralph Sennhauser
---
Move the partition layout to individual boards. The Linksys WRT 3200 ACM
(Rango) comes with a 256MiB nand flash chip and different layout.
Signed-off-by: Ralph Sennhauser
---
Dismissed alternatives:
a) Partition layouts as fragments for use with overlay. While the only
alternative which
Hi Andi,
Thank you for looking at this. I mentioned earlier, I would not want to
impose a cap. However, if you think that for example dcache needs a cap,
there is already a mechanism for that via high_limit argument, so the
client can be changed to provide that cap. However, this particular
On Thu, May 18, 2017 at 03:22:42PM -0600, Tyler Baicar wrote:
> Check for pending errors when probing GHES entries. It is possible
> that a fatal error is already pending at this point, so we should
> handle it as soon as the driver is probed. This also avoids a
> potential issue if there was an
On Thu, May 18, 2017 at 4:38 PM, Mika Westerberg
wrote:
> At least Falcon Ridge when in host mode does not have any kind of DROM
> available and reading DROM offset returns 0 for these. Do not try to
> read DROM any further in that case.
>
> Signed-off-by: Mika Westerberg
> Reviewed-by: Yehezkel
On 21/05/17 13:44, Jan Kiszka wrote:
On 2017-05-21 14:18, Jonathan Cameron wrote:
On 21/05/17 13:17, Jonathan Cameron wrote:
On 21/05/17 12:59, Jan Kiszka wrote:
On 2017-05-21 12:47, Jonathan Cameron wrote:
On 17/05/17 16:28, Jan Kiszka wrote:
This is an upstream port of an IIO driver for
Hi valdis,
On 05/20/2017 10:18 PM, valdis.kletni...@vt.edu wrote:
Seeing problems with programs that use semaphores. The one
that I'm getting bit by is jackd. strace says:
getuid()= 967
semget(0x282929, 0, 000)= 229376
semop(229376, [{0, -1,
On 21/05/17 15:06, Jonathan Cameron wrote:
On 21/05/17 13:44, Jan Kiszka wrote:
On 2017-05-21 14:18, Jonathan Cameron wrote:
On 21/05/17 13:17, Jonathan Cameron wrote:
On 21/05/17 12:59, Jan Kiszka wrote:
On 2017-05-21 12:47, Jonathan Cameron wrote:
On 17/05/17 16:28, Jan Kiszka wrote:
On 18/05/17 07:51, Maxime Ripard wrote:
On Thu, May 18, 2017 at 08:36:07AM +0200, Quentin Schulz wrote:
For the sake of DT binding stability, this IIO driver is a child of an
MFD driver for Allwinner A10, A13 and A31 because there already exists a
DT binding for this IP. The MFD driver has a DT
On Fri, May 05, 2017 at 11:16:59AM -0700, Ricardo Neri wrote:
> In its current form, user_64bit_mode() can only be used when CONFIG_X86_64
> is selected. This implies that code built with CONFIG_X86_64=n cannot use
> it. If a piece of code needs to be built for both CONFIG_X86_64=y and
>
On Fri, May 05, 2017 at 11:17:00AM -0700, Ricardo Neri wrote:
> Up to this point, only fault.c used the definitions of the page fault error
> codes. Thus, it made sense to keep them within such file. Other portions of
> code might be interested in those definitions too. For instance, the User-
>
Hi Christoph
> -Original Message-
> From: linux-pci-ow...@vger.kernel.org [mailto:linux-pci-
> ow...@vger.kernel.org] On Behalf Of Christoph Hellwig
> Sent: 21 May 2017 09:33
> To: Gabriele Paoloni
> Cc: bhelg...@google.com; helg...@kernel.org; Linuxarm; linux-
> p...@vger.kernel.org;
This small patchset reorganizes magic.h and fixes filesystems
which defined locally super magic values.
Fabian Frederick (11):
uapi: reorganize magic.h
exofs: use magic.h
ceph: use magic.h
orangefs: use magic.h
ubifs: use magic.h
jfs: use magic.h
ocfs2: use magic.h
fuse: use
Filesystems generally use SUPER_MAGIC values from magic.h
instead of a local definition.
Signed-off-by: Fabian Frederick
---
fs/exofs/common.h | 6 +-
include/uapi/linux/magic.h | 1 +
2 files changed, 2 insertions(+), 5 deletions(-)
diff --git a/fs/exofs/common.h
-Sort magic.h in alphabetical order as there were no real logic
in this file.
-Replace all spaces with tabs
-Remove excessive comments for reiserfs
Signed-off-by: Fabian Frederick
---
include/uapi/linux/magic.h | 92 --
1 file changed, 40
Filesystems generally use SUPER_MAGIC values from magic.h
instead of a local definition.
Signed-off-by: Fabian Frederick
---
fs/ceph/super.h| 4 +---
include/uapi/linux/magic.h | 1 +
2 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/fs/ceph/super.h b/fs/ceph/super.h
Filesystems generally use SUPER_MAGIC values from magic.h
instead of a local definition.
Signed-off-by: Fabian Frederick
---
fs/orangefs/protocol.h | 3 +--
include/uapi/linux/magic.h | 1 +
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/fs/orangefs/protocol.h
Filesystems generally use SUPER_MAGIC values from magic.h
instead of a local definition.
Signed-off-by: Fabian Frederick
---
fs/jfs/jfs_incore.h| 6 +-
include/uapi/linux/magic.h | 1 +
2 files changed, 2 insertions(+), 5 deletions(-)
diff --git a/fs/jfs/jfs_incore.h
Filesystems generally use SUPER_MAGIC values from magic.h
instead of a local definition.
Signed-off-by: Fabian Frederick
---
fs/ubifs/ubifs.h | 4 +---
include/uapi/linux/magic.h | 1 +
2 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/fs/ubifs/ubifs.h b/fs/ubifs/ubifs.h
Filesystems generally use SUPER_MAGIC values from magic.h
instead of a local definition.
Signed-off-by: Fabian Frederick
---
fs/ocfs2/ocfs2_fs.h| 5 ++---
include/uapi/linux/magic.h | 1 +
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/fs/ocfs2/ocfs2_fs.h
hfs values were defined twice (in hfs and hfsplus)
This patch exports values globally and include magic.h
in hfs.h and hfsplus_raw.h where other magic are going to
be exported as well.
Signed-off-by: Fabian Frederick
---
fs/hfs/hfs.h | 4 ++--
fs/hfsplus/hfsplus_raw.h | 1 +
Filesystems generally use SUPER_MAGIC values from magic.h
instead of a local definition.
Signed-off-by: Fabian Frederick
---
fs/freevxfs/vxfs.h | 6 +-
include/uapi/linux/magic.h | 1 +
2 files changed, 2 insertions(+), 5 deletions(-)
diff --git a/fs/freevxfs/vxfs.h
Filesystems generally use SUPER_MAGIC values from magic.h
instead of a local definition.
Signed-off-by: Fabian Frederick
---
fs/fuse/control.c | 3 +--
fs/fuse/inode.c| 3 +--
include/uapi/linux/magic.h | 2 ++
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git
Filesystems generally use SUPER_MAGIC values from magic.h
instead of a local definition.
Signed-off-by: Fabian Frederick
---
fs/hfsplus/hfsplus_raw.h | 1 -
include/uapi/linux/magic.h | 1 +
2 files changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/hfsplus/hfsplus_raw.h
Hello
Since linux-next-20170517 at least I got the following DEADLOCK warning:
[4.311614]
[4.316919] WARNING: possible recursive locking detected
[4.37] 4.12.0-rc1-next-20170517+ #273 Not tainted
[4.327360]
Hi Rafael,
On 5/15/2017 6:59 AM, Rafael J. Wysocki wrote:
> On Mon, May 15, 2017 at 4:36 AM, Sinan Kaya wrote:
>> Hi Rafael,
>>
>> On 5/11/2017 10:52 AM, Rafael J. Wysocki wrote:
OK. I'll reach out to Harb and let's see where the proposal goes.
>>> It looks like this is about operation
On Sun, 21 May 2017, Corentin Labbe wrote:
> Since linux-next-20170517 at least I got the following DEADLOCK warning:
> [4.311614]
> [4.316919] WARNING: possible recursive locking detected
> [4.37] 4.12.0-rc1-next-20170517+ #273 Not
On Sun, May 21, 2017 at 08:58:25AM -0400, Pasha Tatashin wrote:
> Hi Andi,
>
> Thank you for looking at this. I mentioned earlier, I would not want to
> impose a cap. However, if you think that for example dcache needs a cap,
> there is already a mechanism for that via high_limit argument, so the
Fabian,
Am 21.05.2017 um 17:41 schrieb Fabian Frederick:
> Filesystems generally use SUPER_MAGIC values from magic.h
> instead of a local definition.
>
> Signed-off-by: Fabian Frederick
> ---
> fs/ubifs/ubifs.h | 4 +---
> include/uapi/linux/magic.h | 1 +
> 2 files changed, 2
On Tue, 16 May 2017, Arnd Bergmann wrote:
> On Tue, May 16, 2017 at 5:51 PM, Christoph Hellwig wrote:
> > Yes, that sounds useful to me as well. As you said it's an independent
> > but somewhat related change. I can add it to my series, but I'll
> > need a suggestions for a good and short name.
Fix for unsafe_put_user() (no callers currently in mainline,
but anyone starting to use it will step into that) + osf_wait4()
infoleak fix.
The following changes since commit 2ea659a9ef488125eb46da6eb571de5eae5c43f6:
Linux 4.12-rc1 (2017-05-13 13:19:49 -0700)
are available in the git
From: Corentin Labbe
Date: Fri, 19 May 2017 09:03:32 +0200
> This patch convert new_state from int to bool since it store only 1 or 0
>
> Signed-off-by: Corentin Labbe
You must also change it to use the values "true" and "false" as well.
Thanks.
From: Sivakumar Krishnasamy
Date: Fri, 19 May 2017 05:30:38 -0400
...
> Signed-off-by: Sivakumar Krishnasamy
Applied, thanks for the more detailed commit message.
On Thu, May 18, 2017 at 4:38 PM, Mika Westerberg
wrote:
> Intel Thunderbolt controllers support up to 16 MSI-X vectors. Using
Is that true for all generations? If so can we remove the legacy path?
> MSI-X is preferred over MSI or legacy interrupt and may bring additional
> performance because
On Thu, 18 May 2017, Christoph Hellwig wrote:
> On Thu, May 18, 2017 at 10:24:48AM +0200, Christoph Hellwig wrote:
> > > b) give the union a name (breaks any reference to timer_list->func in C
> > > code):
> > >
> > > + union {
> > > + void(*func)(struct
Hi Kees,
On 05/21/2017 07:20 AM, Kees Cook wrote:
On Sat, May 20, 2017 at 1:18 PM, wrote:
Seeing problems with programs that use semaphores. The one
that I'm getting bit by is jackd. strace says:
getuid()= 967
semget(0x282929, 0, 000)=
On Sun, 21 May 2017, Thomas Gleixner wrote:
> On Tue, 16 May 2017, Arnd Bergmann wrote:
> > On Tue, May 16, 2017 at 5:51 PM, Christoph Hellwig wrote:
> > > Yes, that sounds useful to me as well. As you said it's an independent
> > > but somewhat related change. I can add it to my series, but
On Sun, May 21, 2017 at 07:57:53PM +0200, Thomas Gleixner wrote:
> On Thu, 18 May 2017, Christoph Hellwig wrote:
> > On Thu, May 18, 2017 at 10:24:48AM +0200, Christoph Hellwig wrote:
> > > > b) give the union a name (breaks any reference to timer_list->func in C
> > > > code):
> > > >
> > > >
On Fri, 19 May 2017, Christoph Hellwig wrote:
> - /* Stabilize the cpumasks */
> - get_online_cpus();
How is that protected against physical CPU hotplug? Physical CPU hotplug
manipulates the present mask.
> - nodes = get_nodes_in_cpumask(cpu_online_mask, );
> + nodes =
301 - 400 of 542 matches
Mail list logo
