From: "Cooper Jr., Franklin"
Add additional details to the GPMC NAND documentation to clarify
what is needed to enable NAND DMA prefetch.
Signed-off-by: Franklin S Cooper Jr
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/memory-controllers/omap-gpmc.txt | 7 ++-
Documentation
Add license and copyrights (file introduced in 2014) to header with
Exynos5410 clock IDs. Additionally reformat it to improve readability.
Signed-off-by: Krzysztof Kozlowski
---
include/dt-bindings/clock/exynos5410.h | 54 --
1 file changed, 32 insertions(+), 22 d
Hi,
I am in the middle (or beginning) of adding DTS for Odroid XU. This
patchset is a preparation for that. I still did not figure out two
things:
1. clock IDs, should we follow Exynos5420 (or maybe reuse entirely?)
see patch 1.
2. sd0_rclk - see patch 5.
The Odroid XU board is based on Exyn
The i2c-arbitrator node in exynos5250-snow-common used absolute path to
reference other node (the i2c parent). Use phandle instead, because the
depth of the other node may be changed (like moving it under 'soc'
node).
Signed-off-by: Krzysztof Kozlowski
---
arch/arm/boot/dts/exynos5250-snow-commo
The exynos5.dtsi is used for common nodes shared between Exynos5250 and
Exynos542x. Since Exynos5410 is very similar to Exynos5420 it can
include the common file as well to remove duplication and make
everything more consistent.
Signed-off-by: Krzysztof Kozlowski
---
arch/arm/boot/dts/exynos5410
The 'sd0_rclk' was put in the middle of SD1 nodes. Remove the confusion.
Signed-off-by: Krzysztof Kozlowski
---
arch/arm/boot/dts/exynos5420-pinctrl.dtsi | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/arch/arm/boot/dts/exynos5420-pinctrl.dtsi
b/arch/arm/boot/dt
The conventions it to put SoC devices under 'soc' node. In fact other
our DTSes (like exynos3250.dtsi or exynos5410.dtsi) already follows it.
Adjust exynos5250 and exynos5420 DTSI to follow this convention. This is
also necessary for the upcoming change in exynos5410.dtsi to inherit
from common exy
The LED nodes can be shared between Odroid XU3, XU3-Lite and XU (not yet
added) thus removing duplication.
Signed-off-by: Krzysztof Kozlowski
---
arch/arm/boot/dts/exynos5422-odroidxu3-lite.dts | 35 +
arch/arm/boot/dts/exynos5422-odroidxu3.dts | 35 +
arch/a
Just like other Exynos5 family SoCs, this one has four UARTs. Configure
clocks for UART3 and enable it.
Signed-off-by: Krzysztof Kozlowski
---
arch/arm/boot/dts/exynos5410.dtsi | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/exynos5410.dtsi
b/arch/arm/boo
Configure the pinctrl for MMC0 (eMMC) and MMC2 (microSD card).
Signed-off-by: Krzysztof Kozlowski
---
I am not sure about sd0_rclk. Also I wonder whether this should go to
board DTS...
---
arch/arm/boot/dts/exynos5410-pinctrl.dtsi | 87 +++
1 file changed, 87 insert
Add 'sromc' label to SROM memory controller in common exynos5.dtsi so it
can be referenced by ihneriting DTSI.
Signed-off-by: Krzysztof Kozlowski
---
arch/arm/boot/dts/exynos5.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/exynos5.dtsi b/arch/arm/boot/
Fro consistency lowercase node labels are used.
Signed-off-by: Krzysztof Kozlowski
---
arch/arm/boot/dts/exynos5410.dtsi | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/arch/arm/boot/dts/exynos5410.dtsi
b/arch/arm/boot/dts/exynos5410.dtsi
index 7a56aec2c5ba..8de8c644
Exynos5420 and Exynos5250 share some nodes: the PWM and syscon
(sysreg_system_controller). Move them to parent DTSI to avoid
duplication.
Signed-off-by: Krzysztof Kozlowski
---
arch/arm/boot/dts/exynos5.dtsi| 12
arch/arm/boot/dts/exynos5250.dtsi | 19 +--
arch/a
On Tue, May 3, 2016 at 10:45 AM, Brian Gerst wrote:
> On Mon, May 2, 2016 at 10:56 AM, Denys Vlasenko wrote:
>> Use of a temporary R8 register here seems to be unnecessary.
>>
>> "push %r8" is a two-byte insn (it needs REX prefix to specify R8),
>> "push $0" is two-byte too. It seems just using t
2016-04-16 22:56 GMT+02:00 Wolfram Sang :
> On Mon, Apr 11, 2016 at 11:57:20AM -0700, Bartosz Golaszewski wrote:
>> The only field in struct at24_data that needs locking in the module
>> code is u8 *writebuf. Other data is already protected by i2c core.
>>
>> Rename the lock in at24_data to wrbuf_l
Add ID for PWM clock to Exynos5410. Use the same number as for
Exynos5420.
Signed-off-by: Krzysztof Kozlowski
---
A question: does it make sense to stick to same IDs?
---
include/dt-bindings/clock/exynos5410.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/dt-bindings/clock/exyn
On Mon, May 02, 2016 at 11:55:01AM +0100, Mark Brown wrote:
> On Mon, May 02, 2016 at 11:49:12AM +0200, Krzysztof Kozlowski wrote:
>
> > This VDD regulator supply actually is not a usb3503 USB HUB regulator
> > supply... but a supply to the LAN attached to this HUB. Regulator off/on
> > is needed
John,
This patch is against the devel/v0.98 branch. It turns off tracing in the
tracemark() so that we don't lose information about what was going on when we
hit the latency:
The current logic of using --tracemark and --notrace works for running
cyclictest with trace-cmd, but even if we are no
On Fri, Apr 29, 2016 at 02:58:25PM +0200, Geert Uytterhoeven wrote:
> Some Renesas SCIF UARTs have dedicated lines for RTS/CTS hardware flow
> control. Whether these lines exist depends on SoC and UART instance
> inside the SoC. Whether these lines can be used for hardware flow
> control depends
When driver unbinds while media_ioctl is in progress, cdev_put() fails with
when app exits after driver unbinds.
Add devnode struct device kobj as the cdev parent kobject. cdev_add() holds
a reference to it and releases the reference in cdev_del() ensuring that the
media_devnode is not deallocated
3.365019] [ cut here ]
[3.369639] WARNING: CPU: 0 PID: 1 at drivers/reset/core.c:187
__of_reset_control_get+0x16c/0x23c
[3.382151] Modules linked in:
[3.385214] CPU: 0 PID: 1 Comm: swapper/0 Not tainted
4.6.0-rc6-next-20160503 #140
[3.392769] Hardware name: NVIDIA
* J.D. Schroeder [160503 10:50]:
> On 05/03/2016 12:32 PM, Tero Kristo wrote:
> > Personally I would not recommend using this clock for any timing sensitive
> > applications. May I ask why you are interested in the exact clock rate of
> > this
> > clock anyway?
>
> I'm not interested in using th
On Tue, May 3, 2016 at 1:55 PM, Andy Lutomirski wrote:
> On Tue, May 3, 2016 at 10:45 AM, Brian Gerst wrote:
>> On Mon, May 2, 2016 at 10:56 AM, Denys Vlasenko wrote:
>>> Use of a temporary R8 register here seems to be unnecessary.
>>>
>>> "push %r8" is a two-byte insn (it needs REX prefix to sp
From: Heinz Mauelshagen
Introduced by upstream commit 70d9798b95562abac005d4ba71d28820f9a201eb
The raid0 personality does not create mddev->thread as oposed to
other personalities leading to its unconditional access in
mddev_suspend() causing an oops.
Patch checks for mddev->thread in order to
On 05/03, Sudeep Holla wrote:
> Functions dev_pm_opp_of_{cpumask_,}remove_table removes/frees all the
> static OPP entries associated with the device and/or all cpus(in case
> of cpumask) that are created from DT.
>
> However the OPP entries are populated reading from the firmware or some
> differ
On Tue, May 03, 2016 at 10:10:24AM -0700, Luis R. Rodriguez wrote:
> On Tue, May 3, 2016 at 10:07 AM, Luis R. Rodriguez wrote:
> > Thanks! Can you confirm if any Android or Brillo builds are already using
> > it?
>
> Also more importantly, any chance you can provide any technical
> reasons why i
On 05/03/2016 10:59 AM, Jens Axboe wrote:
On 05/03/2016 09:48 AM, Jan Kara wrote:
On Tue 03-05-16 17:40:32, Jan Kara wrote:
On Tue 03-05-16 11:34:10, Jan Kara wrote:
Yeah, once I'll hunt down that regression with old disk, I can have
a look
into how writeback throttling plays together with blk
On 04/29/2016 05:36 AM, Len Brown wrote:
> But above is all cosmetic. The real "bug" that users are running into is
> that they can't get into deep c-states when they are enabled.
> Linux (and Intel) need to do a much better job enabling diagnosis of
> that condition.
>
Okay, I geddit.
Acked-
On 03/05/16 20:49, J.D. Schroeder wrote:
On 05/03/2016 12:32 PM, Tero Kristo wrote:
Personally I would not recommend using this clock for any timing sensitive
applications. May I ask why you are interested in the exact clock rate of this
clock anyway?
I'm not interested in using this clock and
On 03/05/16 18:42, Kees Cook wrote:
On Tue, May 3, 2016 at 10:25 AM, Janis Danisevskis wrote:
On 26/04/16 21:14, Kees Cook wrote:
On Tue, Apr 26, 2016 at 10:20 AM, Janis Danisevskis
wrote:
The PR_DUMPABLE flag causes the pid related paths of the
proc file system to be owned by ROOT. Th
On Tue, May 03, 2016 at 07:38:27PM +0300, Pranay Kr. Srivastava wrote:
> Signed-off-by: Pranay Kr. Srivastava
You have to have a changelog text.
And try doing one-patch-per-checkpatch-warning-type.
That's all I will accept for drivers/staging/ files, but maybe the nbd.c
maintainer has different
On Tue, May 03, 2016 at 09:04:17PM +1000, Michael Neuling wrote:
> On Tue, 2016-05-03 at 08:32 +0200, Jiri Slaby wrote:
> > On 01/27/2016, 07:12 PM, Greg Kroah-Hartman wrote:
> > >
> > > 4.4-stable review patch. If anyone has any objections, please let me
> > > know.
> > >
> > >
On Tue, May 03, 2016 at 04:44:22PM +1000, Stephen Rothwell wrote:
> Hi Greg,
>
> Today's linux-next merge of the staging tree got a conflict in:
>
> drivers/staging/lustre/lustre/llite/rw26.c
>
> between commit:
>
> c8b8e32d700f ("direct-io: eliminate the offset argument to ->direct_IO")
>
On Tue, May 03, 2016 at 08:59:18AM -0600, Shuah Khan wrote:
> On 05/02/2016 06:09 PM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.5.3 release.
> > There are 200 patches in this series, all will be posted as a response
> > to this one. If anyone has any issu
3.382151] Modules linked in:
> [3.385214] CPU: 0 PID: 1 Comm: swapper/0 Not tainted
> 4.6.0-rc6-next-20160503 #140
> [3.392769] Hardware name: NVIDIA Tegra SoC (Flattened Device Tree)
> [3.399046] [] (unwind_backtrace) from []
> (show_stack+0x10/0x14)
> [3.406787]
On Tue, May 03, 2016 at 12:27:09AM -0700, Guenter Roeck wrote:
> On 05/02/2016 05:10 PM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.4.9 release.
> > There are 163 patches in this series, all will be posted as a response
> > to this one. If anyone has any i
This patch fixes a couple of bugs regarding to orphan inodes when handling
errors.
This tries to
- call alloc_nid_done with add_orphan_inode in handle_failed_inode
- let truncate blocks in f2fs_evict_inode
- not make a bad inode due to i_mode change
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/dir
This patch modifies to retry truncating node blocks in -ENOMEM case.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/inode.c | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/fs/f2fs/inode.c b/fs/f2fs/inode.c
index f4ac851..5cccd7a 100644
--- a/fs/f2fs/inode.c
+++ b/fs/f2fs/inode.
This adds macros to be used multiple proc entries.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/super.c | 25 ++---
1 file changed, 14 insertions(+), 11 deletions(-)
diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c
index 19a85cf..b006de6 100644
--- a/fs/f2fs/super.c
+++ b/fs/f2fs/su
This patch adds a new proc entry to show segment information in more detail.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/super.c | 32 +++-
1 file changed, 31 insertions(+), 1 deletion(-)
diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c
index b006de6..90d4b86 100644
--- a/f
When unmounting filesystem, we should release all the ino entries.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/checkpoint.c | 6 +++---
fs/f2fs/f2fs.h | 2 +-
fs/f2fs/super.c | 2 +-
3 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/fs/f2fs/checkpoint.c b/fs/f2fs/checkpoint.c
On Tue, May 03, 2016 at 12:39:51AM -0700, Guenter Roeck wrote:
> On 05/02/2016 05:09 PM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.5.3 release.
> > There are 200 patches in this series, all will be posted as a response
> > to this one. If anyone has any i
On Fri, Apr 29, 2016 at 02:53:45PM +0100, Jon Hunter wrote:
> Add binding documentation for the Tegra ACONNECT bus that is part of the
> Audio Processing Engine (APE) on Tegra210. The ACONNECT bus is used to
> access devices within the APE subsystem. The APE is located in a
> separate power domain
This patch injects kmalloc failure given a fault injection rate.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/f2fs.h | 29 +
fs/f2fs/super.c | 6 ++
2 files changed, 35 insertions(+)
diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h
index 0684d3e..60098df 100644
--- a/fs/
On Tue, May 03, 2016 at 01:31:31PM +0200, Peter Zijlstra wrote:
> Then flip on the last_idle tracking in select_idle_core():
>
> root@ivb-ep:~/bench/sysbench# for i in NO_OLD_IDLE NO_ORDER_IDLE IDLE_CORE
> NO_FORCE_CORE IDLE IDLE_SMT IDLE_LAST NO_IDLE_FIRST ; do echo $i >
> /debug/sched_features
This patch adds page allocation failures.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/f2fs.h | 9 +
fs/f2fs/super.c | 1 +
2 files changed, 10 insertions(+)
diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h
index 60098df..02c2c96 100644
--- a/fs/f2fs/f2fs.h
+++ b/fs/f2fs/f2fs.h
@@ -40,6 +40,7 @@
This patch adds f2fs_kmalloc.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/acl.c| 4 ++--
fs/f2fs/dir.c| 2 +-
fs/f2fs/f2fs.h | 5 +
fs/f2fs/gc.c | 2 +-
fs/f2fs/inline.c | 2 +-
5 files changed, 10 insertions(+), 5 deletions(-)
diff --git a/fs/f2fs/acl.c b/fs/f2fs/acl.c
index c8f25
This patch injects ENOSPC failures.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/checkpoint.c | 7 +++
fs/f2fs/dir.c| 4
fs/f2fs/f2fs.h | 10 ++
fs/f2fs/node.c | 4
fs/f2fs/super.c | 4
5 files changed, 29 insertions(+)
diff --git a/fs/f2fs/chec
This patch converts grab_cache_page to f2fs_grab_cache_page.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/checkpoint.c | 7 ---
fs/f2fs/inline.c | 4 ++--
fs/f2fs/node.c | 8
3 files changed, 10 insertions(+), 9 deletions(-)
diff --git a/fs/f2fs/checkpoint.c b/fs/f2fs/checkpoin
This patch adds a mount option to select fault ratio.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/Kconfig | 8
fs/f2fs/f2fs.h | 1 +
fs/f2fs/super.c | 16
3 files changed, 25 insertions(+)
diff --git a/fs/f2fs/Kconfig b/fs/f2fs/Kconfig
index 1f8982a..378c221 100644
--- a
On Tue, May 03, 2016 at 12:19:09AM -0700, Guenter Roeck wrote:
> On 05/02/2016 05:11 PM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 3.14.68 release.
> > There are 37 patches in this series, all will be posted as a response
> > to this one. If anyone has any
>
>And when the filesystem says no because the fs devs don't want to
>have to deal with broken apps because app devs learn that "this is a
>go fast knob" and data integrity be damned? It's "fsync is slow so I
>won't use it" all over again...
...
>
>And, please keep in mind: many application develop
Per the QEMU fw_cfg documentation, items targeted at guest-side
userspace should have names beginning with the string "opt/".
This patch limits the default sysfs fw_cfg listing to items
named "opt/*".
The "opt/" prefix on a fw_cfg item name may be interpreted as
being analogous to bit 2 in ACPI's
Any feedback on this? It is mandatory if we want to mount a ecryptfs
directory while the session keyring is used.
Thanks,
Gwendal.
On Thu, Mar 17, 2016 at 10:04 AM, Gwendal Grignou wrote:
> Resent to a larger audience.
>
> On Thu, Mar 10, 2016 at 2:20 PM, Gwendal Grignou wrote:
>> Currently, if
Fix checkpatch.pl warning about 'line over 80 characters'.
I just split line with function.
Signed-off-by: Patryk Mezydlo
---
drivers/staging/dgnc/dgnc_tty.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/staging/dgnc/dgnc_tty.c b/drivers/staging/dgnc/dgnc_tty.c
in
On Tue, May 03, 2016 at 01:47:04PM -0400, Josh Boyer wrote:
> The promise of pretty boot splashes from firmware via BGRT was at
> best only that; a promise. The kernel diligently checks to make
> sure the BGRT data firmware gives it is valid, and dutifully warns
> the user when it isn't. However,
On Tue, May 03, 2016 at 11:48:20AM +0200, Borislav Petkov wrote:
> On Mon, May 02, 2016 at 07:10:36PM -0500, Alex Thorlton wrote:
> > +#define uv_call_virt(f, args...) \
> > +({ \
> > + efi_status_t __s;
On Thu, Apr 28, 2016 at 08:09:35PM +0800, Lijun Ou wrote:
> The HiSilicon Network Substem is a long term evolution IP which is
> supposed to be used in HiSilicon ICT SoCs. HNS (HiSilicon Network
> Sybsystem) also has a hardware support of performing RDMA with
> RoCEE.
> The driver for HiSilicon RoC
i2c-dev had never moved away from the older register_chrdev interface to
implement its char device registration. The register_chrdev API has the
limitation of enabling only up to 256 i2c-dev busses to exist.
Large platforms with lots of i2c devices (i.e. pluggable transceivers)
with dedicated buss
On 05/01/2016 10:58 PM, Jonathan Cameron wrote:
> On 27/04/16 16:56, One Thousand Gnomes wrote:
>> On Tue, 26 Apr 2016 18:07:55 -0500
>> Michael Welling wrote:
>>
>>> On Tue, Apr 26, 2016 at 11:26:51PM +0100, One Thousand Gnomes wrote:
This now causes us to crash and burn on the ASUS T10
Never use sg++, always use sg = sg_next(sg). Scatterlist entries can
be combined if the memory is contiguous but sg++ won't know about
that. It sure would run on the slower side.
But regardless, sg++ should never be used, only sg_next is safe.
Signed-off-by: Muhammad Falak R Wani
---
crypto/algi
This fixes a simple typo in one of the comments.
Signed-off-by: Moritz Fischer
---
drivers/spi/spi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/spi/spi.c b/drivers/spi/spi.c
index 0239b45..af7c48d 100644
--- a/drivers/spi/spi.c
+++ b/drivers/spi/spi.c
@@ -933,7 +
On Tue, 03 May, at 01:47:04PM, Josh Boyer wrote:
> The promise of pretty boot splashes from firmware via BGRT was at
> best only that; a promise. The kernel diligently checks to make
> sure the BGRT data firmware gives it is valid, and dutifully warns
> the user when it isn't. However, it does so
On Tue, May 3, 2016 at 11:16 AM, Janis Danisevskis wrote:
>
>
> On 03/05/16 18:42, Kees Cook wrote:
>>
>> On Tue, May 3, 2016 at 10:25 AM, Janis Danisevskis
>> wrote:
>>>
>>>
>>>
>>> On 26/04/16 21:14, Kees Cook wrote:
On Tue, Apr 26, 2016 at 10:20 AM, Janis Danisevskis
wrote
On 05/03/2016 12:14 PM, Jens Axboe wrote:
On 05/03/2016 10:59 AM, Jens Axboe wrote:
On 05/03/2016 09:48 AM, Jan Kara wrote:
On Tue 03-05-16 17:40:32, Jan Kara wrote:
On Tue 03-05-16 11:34:10, Jan Kara wrote:
Yeah, once I'll hunt down that regression with old disk, I can have
a look
into how w
On Tue, May 3, 2016 at 11:51 AM, Boris Brezillon
wrote:
> Hi Rob,
>
> On Tue, 3 May 2016 11:40:19 -0500
> Rob Herring wrote:
>
>> On Thu, Apr 28, 2016 at 02:03:27PM +0200, Boris Brezillon wrote:
>> > The EBI (External Bus Interface) is used to access external peripherals
>> > (NOR, SRAM, NAND, an
Hi,
I am a newbie to VFIO framework and trying to use it for MSIX interrupt
handling in my userspace application. My userspace application is like intel's
dpdk.
My query is why vfio kernel code does not support msix masking/ unmasking i.e
VFIO_SET_ACTION_TRIGGER is not implemented in kernel vf
I don't see much difference. I will update the commits on next
iteration with the following:
Kernbench shows almost no difference (-+ less than 1%):
Before:
Average Optimal load -j 12 Run (std deviation):
Elapsed Time 102.63 (1.2695)
User Time 1034.89 (1.18115)
System Time 87.056 (0.456416)
Perc
On Tue, 3 May 2016, Thierry Reding wrote:
> From: Thierry Reding
>
> Starting with commit 0b52297f2288 ("reset: Add support for shared reset
> controls") there is a reference count for reset control assertions. The
> goal is to allow resets to be shared by multiple devices and an assert
> will t
robert.f...@collabora.com writes:
> From: Robert Foss
>
> As per the documentation in drm_crtc.h, atomic_commit should return
> -EBUSY if an asycnhronous update is requested and there is an earlier
> update pending.
>
> Note: docs cited here are drm_crtc.h, and the whole quote is:
>
> * - -E
On Sat, 2016-04-30 at 11:48 +0100, Russell King - ARM Linux wrote:
> On Fri, Apr 29, 2016 at 06:42:35PM -0400, Javier Martinez Canillas wrote:
> > Maybe a third opinion could make this conversation constructive again.
And maybe a forth.
> > I think Doug's point is that using a UUID or labels for
On Tuesday 03 May 2016 11:11:56 Rob Herring wrote:
> > +
> > +Child nodes:
> > +Every SLIMbus controller node can contain zero or more child nodes
> > +representing slave devices on the bus. Every SLIMbus slave device is
> > +uniquely determined by the enumeration address containing 4 fields:
> > +
From: Anna-Maria Gleixner
Date: Mon, 2 May 2016 11:02:51 +0200
> Since commit 3b9d6da67e11 ("cpu/hotplug: Fix rollback during error-out
> in __cpu_disable()") it is ensured that callbacks of CPU_ONLINE and
> CPU_DOWN_PREPARE are processed on the hotplugged CPU. Due to this SMP
> function calls a
Mark Brown writes:
> On Sat, Apr 30, 2016 at 11:15:33PM +0200, Robert Jarzmik wrote:
>> Split out from the ac97_codec.h the ac97 generic registers, which can be
>> used by a codec, typically a generic ac97 codec, and by the ac97 bus, to
>> scan an ac97 AC-Link.
>
> I don't entirely see the value
Mark reported that having asterisks on the end of directory names
confuses get_maintainer.pl when it encounters subdirectories, and that
my name does not appear when run on drivers/firmware/efi/libstub.
Reported-by: Mark Rutland
Cc: Ard Biesheuvel
Cc: Catalin Marinas
Cc:
Signed-off-by: Matt Fl
From: Josh Boyer
The promise of pretty boot splashes from firmware via BGRT was at
best only that; a promise. The kernel diligently checks to make
sure the BGRT data firmware gives it is valid, and dutifully warns
the user when it isn't. However, it does so via the pr_err log
level which seems
From: Wang YanQing
We can't just break out when meet start is equal to zero,
this will cause us to miss valid address ranges in later BARs.
On the other hand, it isn't enough to test start only
for below situation:
0(start) <= lfb_base < end
Due to the BUG this patch fix, I can't use video=e
Folks, here are a few small fixes. One from Josh to stop the ACPI BGRT
driver wrecking the splash screen even though the "quiet" kernel
parameter is passed, another to fix sysfb_efi on a ThinkPad E550, and
one to MAINTAINERS so that get_maintainer.pl finds the EFI entry for
all subdirectores of dri
Randomizes the virtual address space of kernel memory sections (physical
memory mapping, vmalloc & vmemmap) for x86_64. This security feature
mitigates exploits relying on predictable kernel addresses. These
addresses can be used to disclose the kernel modules base addresses or
corrupt specific str
This is PATCH v3 for KASLR memory implementation for x86_64.
Recent changes:
Add performance information on commit.
Add details on PUD alignment.
Add information on testing against the KASLR bypass exploit.
Rebase on next-20160502.
***Background:
The current implementation of KASL
Minor change that allows early boot physical mapping of PUD level virtual
addresses. The current implementation expect the virtual address to be
PUD aligned. For KASLR memory randomization, we need to be able to
randomize the offset used on the PUD table.
It has no impact on current usage.
Signed
Add a new option (CONFIG_RANDOMIZE_MEMORY_PHYSICAL_PADDING) to define
the padding used for the physical memory mapping section when KASLR
memory is enabled. It ensures there is enough virtual address space when
CONFIG_MEMORY_HOTPLUG is used. The default value is 10 terabytes. If
CONFIG_MEMORY_HOTPL
Move the KASLR entropy functions in x86/libray to be used in early
kernel boot for KASLR memory randomization.
Signed-off-by: Thomas Garnier
---
Based on next-20160502
---
arch/x86/boot/compressed/kaslr.c | 76 +++---
arch/x86/include/asm/kaslr.h | 6 +++
arc
Mark Brown writes:
> On Sat, Apr 30, 2016 at 11:15:34PM +0200, Robert Jarzmik wrote:
>> AC97 is a bus for sound usage. It enables for a AC97 AC-Link to link one
>> controller to 0 to 4 AC97 codecs.
>
>> The goal of this new implementation is to implement a device/driver
>> model for AC97, with an
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git for-linus
to fix a regression and update the MAINTAINERS entry for fuse.
Thanks,
Miklos
---
Ashish Samant (1):
fuse: Fix return value from fuse_get_user_pages()
Miklos Szeredi (1):
fuse:
If we're accessing rq_clock() (e.g. in sched_avg_update()) we should
update the rq clock before calling cpu_load_update(), otherwise any
time calculations will be stale.
All other paths currently call update_rq_clock().
Cc: Peter Zijlstra
Cc: Ingo Molnar
Cc: Mike Galbraith
Cc: Mel Gorman
Cc:
On Tue, 3 May 2016 12:59:53 -0500
Clark Williams wrote:
> John,
>
> This patch is against the devel/v0.98 branch. It turns off tracing in the
> tracemark() so that we don't lose information about what was going on when we
> hit the latency:
>
>
> The current logic of using --tracemark and --
On 05/03/16 11:46, Ulf Hansson wrote:
> On 29 April 2016 at 15:06, Peter Ujfalusi wrote:
>> With the new dma_request_chan() the client driver does not need to look for
>> the DMA resource and it does not need to pass filter_fn anymore.
>> By switching to the new API the driver can now support defe
Hi,
On Tue, 3 May 2016 23:56:38 +0530
Nitin Saxena wrote:
> Hi,
>
> I am a newbie to VFIO framework and trying to use it for MSIX interrupt
> handling in my userspace application. My userspace application is like
> intel's dpdk.
>
> My query is why vfio kernel code does not support msix maskin
On 05/02/2016 10:25 PM, Stephen Rothwell wrote:
Hi Jens,
Today's linux-next merge of the block tree got a conflict in:
drivers/nvme/host/pci.c
between commit:
9bf2b972afea ("NVMe: Fix reset/remove race")
from Linus' tree and commit:
bb8d261e0888 ("nvme: introduce a controller state
Hi Al,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git overlayfs-next
This fixes two issues with overlayfs.
Thanks,
Miklos
---
Miklos Szeredi (3):
vfs: rename: check backing inode being equal
vfs: export lookup_hash() to modules
ovl: ignore
On Mon, Apr 25, 2016 at 10:12 PM, Yangbo Lu wrote:
> Hi Scott and Leo,
>
>
>> -Original Message-
>> From: linux-mmc-ow...@vger.kernel.org [mailto:linux-mmc-
>> ow...@vger.kernel.org] On Behalf Of Scott Wood
>> Sent: Saturday, April 23, 2016 7:23 AM
>> To: Yangbo Lu; linux-...@vger.kernel.o
On Tuesday 03 May 2016 18:07:08 Thierry Reding wrote:
> Wouldn't that be more of a case for a select dependency? I'm thinking
> something like the below (untested, yet).
>
I usually prefer 'depends on' in a case like this, but it doesn't make
a huge difference. If we end up using 'select' here, w
On Tue, May 03, 2016 at 01:47:04PM -0400, Josh Boyer wrote:
> The promise of pretty boot splashes from firmware via BGRT was at
> best only that; a promise. The kernel diligently checks to make
> sure the BGRT data firmware gives it is valid, and dutifully warns
> the user when it isn't. However,
On Monday 02 May 2016 19:12:31 Olof Johansson wrote:
> On Mon, May 2, 2016 at 12:24 AM, Arnd Bergmann wrote:
> > On Sunday 01 May 2016 16:19:53 Olof Johansson wrote:
> >> On Sun, May 1, 2016 at 2:26 PM, Olof's autobuilder wrote:
> >> > Here are the build results from automated periodic testing.
>
Andreas Dilger wrote:
> > __u32 st_win_attrs;
>
> It seems some of these flags are duplicated with the st_information field,
> and some are duplicate with FS_IOC_GETFLAGS values, and returning the same
> information in multiple ways is confusing.
>
> If these flags are part of the CIFS pro
Andreas Dilger wrote:
> > (3) FS_xxx_FL flags are returned as for ioctl(FS_IOC_GETFLAGS), setting
> > STATX_IOC_FLAGS.
>
> I don't see where this is implemented in this patch, and it should be
> removed from the commit message to avoid confusion.
Oops - I forgot to remove it from the other
On Tue, 3 May 2016 22:18:54 +0200
Linus Lüssing wrote:
> diff --git a/net/bridge/br_multicast.c b/net/bridge/br_multicast.c
> index 03661d9..7105cdf 100644
> --- a/net/bridge/br_multicast.c
> +++ b/net/bridge/br_multicast.c
> @@ -1271,6 +1271,7 @@ static int br_ip4_multicast_query(struct net_bri
Add a unit test that provides coverage for the bug fixed in the commit
entitled "radix-tree: rewrite radix_tree_locate_item fix" from Hugh
Dickins. I've verified that this test fails before his patch due to
miscalculated 'index' values in __locate() in lib/radix-tree.c, and passes
with his fix.
S
On Tue, 3 May 2016 15:56:44 -0400
Luiz Capitulino wrote:
> On Tue, 3 May 2016 12:59:53 -0500
> Clark Williams wrote:
>
> > John,
> >
> > This patch is against the devel/v0.98 branch. It turns off tracing in the
> > tracemark() so that we don't lose information about what was going on when
>
601 - 700 of 953 matches
Mail list logo
