On Wed, Apr 18, 2018 at 09:20:02AM +0200, Michal Hocko wrote:
> On Wed 18-04-18 11:29:12, Minchan Kim wrote:
> > If there are heavy memory pressure, page allocation with __GFP_NOWAIT
> > fails easily although it's order-0 request.
> > I got below warning 9 times for normal boot.
> >
> > [
Hi Arnd,
On Tue, Apr 17, 2018 at 9:53 PM, Arnd Bergmann wrote:
> On Tue, Apr 17, 2018 at 8:14 PM, Geert Uytterhoeven
> wrote:
>> The ARM TrustZone CryptoCell is found on ARM SoCs only. Hence make it
>> depend on ARM or ARM64, unless compile-testing.
>>
>> Drop the dependency on HAS_DMA, as DMA
Add LPtimer definitions, depending on features they provide:
- lptimer1 & 2 can act as PWM, trigger and encoder/counter
- lptimer3 can act as PWM and trigger
- lptimer4 & 5 can act as PWM
Signed-off-by: Fabrice Gasnier
---
arch/arm/boot/dts/stm32mp157c.dtsi | 108
On Tue, 17 Apr 2018 15:10:52 +0200
Peter Rosin wrote:
> Bump the minor version while at it.
>
> Signed-off-by: Peter Rosin
> ---
> drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_dc.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git
On 2018-04-18 09:29, Boris Brezillon wrote:
> On Tue, 17 Apr 2018 15:10:50 +0200
> Peter Rosin wrote:
>
>> This beats the heuristic that the connector is involved in what format
>> should be output for cases where this fails.
>>
>> E.g. if there is a bridge that changes format between the
Hi Gilad,
On Wed, Apr 18, 2018 at 6:32 AM, Gilad Ben-Yossef wrote:
> On Tue, Apr 17, 2018 at 9:14 PM, Geert Uytterhoeven
> wrote:
>> The ARM TrustZone CryptoCell is found on ARM SoCs only. Hence make it
>> depend on ARM or ARM64, unless compile-testing.
>
> Actually it is not. Despite what the
stm32mp157c has vrefbuf regulator that can provide analog reference
voltage from 1500mV to 2500mV.
Signed-off-by: Fabrice Gasnier
---
arch/arm/boot/dts/stm32mp157c.dtsi | 9 +
1 file changed, 9 insertions(+)
diff --git a/arch/arm/boot/dts/stm32mp157c.dtsi
On Tue, 17 Apr 2018 14:08:59 -0400
Tony Krowiak wrote:
> On 04/17/2018 11:21 AM, Cornelia Huck wrote:
> > On Tue, 17 Apr 2018 10:26:57 -0400
> > Tony Krowiak wrote:
> >
> >> On 04/17/2018 06:10 AM, Cornelia Huck wrote:
> >>> On Tue, 17 Apr 2018 09:49:58 +0200
> >>> "Harald Freudenberger"
On Tue 17-04-18 19:52:41, David Rientjes wrote:
> Since exit_mmap() is done without the protection of mm->mmap_sem, it is
> possible for the oom reaper to concurrently operate on an mm until
> MMF_OOM_SKIP is set.
>
> This allows munlock_vma_pages_all() to concurrently run while the oom
> reaper
Hi, Eduardo,
On 六, 2018-04-14 at 11:30 -0700, Eduardo Valentin wrote:
> Hello Linus,
>
> Please find thermal-soc changes for v4.17-rc1.
> Rui asked me to send the pull request directly to you
> as we are close to the end of the merge window.
> Essentially this pull removes the series that caused
When overriding the 'clean' target make throws up warnings:
Makefile:9: warning: overriding recipe for target 'clean'
../lib.mk:98: warning: ignoring old recipe for target 'clean'
In current code we change from TEST_PROGS to TEST_GEN_PROGS and that
does that we can remove the target 'clean' and
We were picking up the wrong header should use asm/ioctls.h form the kernel
and not the header from the system (sys/ioctl.h). In the current code we
added the correct include and we added the kernel headers path to the CFLAGS.
Fixes: ce290a19609d ("selftests: add devpts selftests")
Signed-off-by:
On Wed 18-04-18 16:41:17, Minchan Kim wrote:
> On Wed, Apr 18, 2018 at 09:20:02AM +0200, Michal Hocko wrote:
> > On Wed 18-04-18 11:29:12, Minchan Kim wrote:
[...]
> > > Let's not make user scared.
> >
> > This is not a proper explanation. So what exactly happens when this
> > allocation fails? I
On 18.04.2018 10:07, Uwe Kleine-König wrote:
> Hello,
Hello Uwe,
Thanks for your reply.
> On Wed, Apr 18, 2018 at 03:16:45AM +0300, Alexander Popov wrote:
>> Currently i2cdev_ioctl_rdwr() doesn't check i2c_msg len against zero
>> before calling memdup_user(). If this len is zero memdup_user()
>On 2018년 04월 13일 11:37, arvindY wrote:
>> On Friday 13 April 2018 07:59 AM, Chanwoo Choi wrote:
>>> On 2018년 04월 13일 11:15, arvindY wrote:
On Friday 13 April 2018 06:43 AM, Chanwoo Choi wrote:
> On 2018년 04월 13일 10:03, Chanwoo Choi wrote:
[]
>>> diff --git a/drivers/devfreq/devfreq.c
Hi Leo,
On Tuesday 17 Apr 2018 at 23:39:44 (+0800), Leo Yan wrote:
> > + for_each_freq_domain(fd) {
> > + unsigned long spare_cap, max_spare_cap = 0;
> > + int max_spare_cap_cpu = -1;
> > + unsigned long util;
> > +
> > + /* Find the CPU with the max
On 04/18/2018 10:35 AM, Roger Pau Monné wrote:
On Wed, Apr 18, 2018 at 09:38:39AM +0300, Oleksandr Andrushchenko wrote:
On 04/17/2018 11:57 PM, Dongwon Kim wrote:
On Tue, Apr 17, 2018 at 09:59:28AM +0200, Daniel Vetter wrote:
On Mon, Apr 16, 2018 at 12:29:05PM -0700, Dongwon Kim wrote:
3.2
On Tue 17-04-18 23:39:19, Cyrill Gorcunov wrote:
> On Tue, Apr 17, 2018 at 11:29:57AM -0700, Andrew Morton wrote:
> > On Sun, 15 Apr 2018 02:24:51 +0800 Yang Shi
> > wrote:
> >
> > > mmap_sem is on the hot path of kernel, and it very contended, but it is
> > > abused too. It is used to protect
On 2018-04-18 09:36, Boris Brezillon wrote:
> On Tue, 17 Apr 2018 15:10:51 +0200
> Peter Rosin wrote:
>
>> When the of-graph points to a tda998x-compatible HDMI encoder, register
>> as a component master and bind to the encoder/connector provided by
>> the tda998x driver.
>
> Can't we do the
2018-04-18 7:27 GMT+02:00 Sekhar Nori :
> On Tuesday 17 April 2018 11:00 PM, Bartosz Golaszewski wrote:
>> From: Bartosz Golaszewski
>>
>> We're currently switching the platform to using the common clock
>> framework. We need to explicitly prepare and unprepare the rproc
>> clock.
>>
>>
On Sun 15-04-18 02:24:51, Yang Shi wrote:
> mmap_sem is on the hot path of kernel, and it very contended, but it is
> abused too. It is used to protect arg_start|end and evn_start|end when
> reading /proc/$PID/cmdline and /proc/$PID/environ, but it doesn't make
> sense since those proc files just
Hi,
These pacthes begin categorizing memory management documentation. The
documents that describe userspace APIs and do not overload the reader with
implementation details can be moved to Documentation/admin-guide, so let's
do it :)
Mike Rapoport (7):
docs/vm: hugetlbpage: minor improvements
Signed-off-by: Mike Rapoport
---
Documentation/admin-guide/mm/hugetlbpage.rst| 3 ++-
Documentation/admin-guide/mm/idle_page_tracking.rst | 5 +++--
Documentation/admin-guide/mm/pagemap.rst| 18 +++---
3 files changed, 16 insertions(+), 10 deletions(-)
diff
Hi Finn,
On Thu, Apr 12, 2018 at 2:50 AM, Finn Thain wrote:
> The resource size is 0x2000 == end - start + 1.
> Therefore end == start + 0x2000 - 1.
>
> Cc: Laurent Vivier
> Cc: sta...@vger.kernel.org # v4.14+
> Tested-by: Stan Johnson
> Signed-off-by: Finn Thain
> Acked-by: Laurent Vivier
>
On Fri, Apr 13, 2018 at 10:42:55AM -0700, Sam Hansen wrote:
> This strips trailing whitespace in Documentation/i2c/dev-interface.
>
> Signed-off-by: Sam Hansen
Applied to for-current, thanks!
signature.asc
Description: PGP signature
* fixed mistypes
* added internal cross-references for sections
Signed-off-by: Mike Rapoport
---
Documentation/vm/hugetlbpage.rst | 17 ++---
1 file changed, 10 insertions(+), 7 deletions(-)
diff --git a/Documentation/vm/hugetlbpage.rst b/Documentation/vm/hugetlbpage.rst
index
On Fri, Apr 13, 2018 at 10:42:56AM -0700, Sam Hansen wrote:
> Currently, Documentation/i2c/dev-interface describes the use of
> i2c_smbus_* helper routines as static inlined functions provided by
> linux/i2c-dev.h. Work has been done to refactor the linux/i2c-dev.h file
> in the i2c-tools project
On 2018-04-18 09:44, Boris Brezillon wrote:
> On Tue, 17 Apr 2018 15:10:52 +0200
> Peter Rosin wrote:
>
>> Bump the minor version while at it.
>>
>> Signed-off-by: Peter Rosin
>> ---
>> drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_dc.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
Signed-off-by: Mike Rapoport
---
Documentation/admin-guide/index.rst| 1 +
Documentation/admin-guide/mm/index.rst | 19 +++
2 files changed, 20 insertions(+)
create mode 100644 Documentation/admin-guide/mm/index.rst
diff --git a/Documentation/admin-guide/index.rst
Several documents in Documentation/vm fit quite well into the "admin/user
guide" category. The documents that don't overload the reader with lots of
implementation details and provide coherent description of certain feature
can be moved to Documentation/admin-guide/mm.
Signed-off-by: Mike
On Fri, Apr 13, 2018 at 10:42:57AM -0700, Sam Hansen wrote:
> The example I2C code is rewritten to adopt the preferred kernel block
> commenting style.
>
> Signed-off-by: Sam Hansen
Applied to for-current, thanks!
signature.asc
Description: PGP signature
I wonder why I am starting to get CCed on Xen patches all of a sudden.
I happened to run into Jürgen at a conference only last weekend, but
I still don't know anything whatsoever about Xen or how it works.
If get_maintainer.pl has started to return my name on this stuff I
really want to know why
"pagemap from the Userspace Perspective" is not very descriptive for
unaware readers. Since the document describes how to examine a process page
tables, let's title it "Examining Process Page Tables"
Signed-off-by: Mike Rapoport
---
Documentation/vm/pagemap.rst | 6 +++---
1 file changed, 3
The hugetlbpage describes hugetlbfs from the user perspective and newer
hugetlbfs_reserv document targets kernel developers. Hence the section
about hugetlbfs kernel development naturally belongs there.
Signed-off-by: Mike Rapoport
---
Documentation/vm/hugetlbfs_reserv.rst | 8
On Tue, 2018-04-17 at 17:07 -0700, Linus Torvalds wrote:
> On Tue, Apr 17, 2018 at 4:35 PM, Martin Wilck
> wrote:
> > Sparse emits errors about ilog2() in array indices because of the
> > use of
> > __ilog2_32() and __ilog2_64(),
>
> If sparse warns about it, then presumably gcc with -Wvla warns
On Tuesday 17 Apr 2018 at 23:22:13 (+0800), Leo Yan wrote:
> On Fri, Apr 06, 2018 at 04:36:05PM +0100, Dietmar Eggemann wrote:
> > From: Quentin Perret
> >
> > In preparation for the definition of an energy-aware wakeup path, a
> > helper function is provided to estimate the consequence on
Den tis 17 apr. 2018 kl 18:35 skrev Guenter Roeck :
> Getting better; the log is much less noisy. Unfortunately, there are still
> locking problems, resulting in a hung task. I copied the log message to [1].
> This is with [2] applied on top of v4.17-rc1.
Now this version (this is a full patch
Signed-off-by: Mike Rapoport
---
Documentation/vm/pagemap.rst | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/Documentation/vm/pagemap.rst b/Documentation/vm/pagemap.rst
index d54b4bf..9644bc0 100644
--- a/Documentation/vm/pagemap.rst
+++
On Tue, 17 Apr 2018, Phil Edworthy wrote:
> The DesignWare GPIO IP can be configured for either 1 interrupt or 1
> per GPIO in port A, but the driver currently only supports 1 interrupt.
> See the DesignWare DW_apb_gpio Databook description of the
> 'GPIO_INTR_IO' parameter.
>
> This change
Hi!
Starting with 4.15.17 I got panic "timeout during microcode update"
which I bisected down to commit 8e1161f94614 ("x86/microcode: Synchronize
late microcode loading") - upstream commit
a5321aec6412b20b5ad15db2d6b916c05349dbff.
The panic happens during CPU microcode update.
The
On Tuesday 17 April 2018 10:59 PM, Santosh Shilimkar wrote:
> On 4/17/2018 5:36 AM, Bartosz Golaszewski wrote:
>> 2018-04-17 12:53 GMT+02:00 Sekhar Nori :
>>> Hi Bartosz,
>
> [...]
>
This series applies on top of v8 of David Lechner's CCF series.
>>>
>>> Are there any patches in the series
On Thu, Apr 12, 2018 at 6:08 PM, Miklos Szeredi wrote:
> This reverts commit a118084432d642eeccb961c7c8cc61525a941fcb.
>
> No user of d_real_inode() remains, so it can be removed.
>
FYI, there is a new user in v4.17-rc1 added by commit
f0a2aa5a2a40 tracing/uprobe: Add support for overlayfs
> +The above functions are made available by linking against the libi2c library,
> +which is provided by the i2c-tools project. See:
> +https://git.kernel.org/pub/scm/utils/i2c-tools/i2c-tools.git/.
In the beginning, we say that '#include ' is needed.
Shouldn't we mention i2c-tools there
> -Original Mail-
> Sender: Thomas Gleixner [mailto:t...@linutronix.de]
> Time : 2018/4/17 18:16
> Receiver: David Wang
> CC: mi...@redhat.com; h...@zytor.com; mi...@kernel.org;
> x...@kernel.org; linux-kernel@vger.kernel.org; brucechang@via-
> alliance.com; cooper...@zhaoxin.com;
On Wed, Apr 18, 2018 at 10:56:03AM +0300, Alexander Popov wrote:
> On 18.04.2018 10:07, Uwe Kleine-König wrote:
> > Hello,
>
> Hello Uwe,
>
> Thanks for your reply.
>
> > On Wed, Apr 18, 2018 at 03:16:45AM +0300, Alexander Popov wrote:
> >> Currently i2cdev_ioctl_rdwr() doesn't check i2c_msg
On Tue, Apr 17, 2018 at 07:17:55PM +0530, Souptick Joarder wrote:
> Use new return type vm_fault_t for fault handler. For
> now, this is just documenting that the function returns
> a VM_FAULT value rather than an errno. Once all instances
> are converted, vm_fault_t will become a distinct type.
>
When Rayd touchscreen resumed from S3, it issues too many errors like:
i2c_hid i2c-RAYD0001:00: i2c_hid_get_input: incomplete report (58/5442)
And all the report data are corrupted, touchscreen is unresponsive.
Fix this by re-sending report description command after resume.
Add device ID as a
On Wed, 18 Apr 2018 09:46:09 +0200
Peter Rosin wrote:
> On 2018-04-18 09:29, Boris Brezillon wrote:
> > On Tue, 17 Apr 2018 15:10:50 +0200
> > Peter Rosin wrote:
> >
> >> This beats the heuristic that the connector is involved in what format
> >> should be output for cases where this fails.
On Wed, 18 Apr 2018 09:31:53 +0200
Peter Rosin wrote:
> On 2018-04-18 09:16, Boris Brezillon wrote:
> > Hi Peter,
> >
> > On Tue, 17 Apr 2018 15:10:48 +0200
> > Peter Rosin wrote:
> >
> >> With bus-type/bus-width properties in the endpoint nodes, the video-
> >> interface of the connection
On Wed, Apr 18, 2018 at 10:12:54AM +0200, Martin Wilck wrote:
> On Tue, 2018-04-17 at 17:07 -0700, Linus Torvalds wrote:
> > On Tue, Apr 17, 2018 at 4:35 PM, Martin Wilck
> > wrote:
> > > Sparse emits errors about ilog2() in array indices because of the
> > > use of
> > > __ilog2_32() and
On 17/04/2018 20:11, Tony Krowiak wrote:
On 04/17/2018 12:55 PM, Pierre Morel wrote:
On 17/04/2018 18:22, Tony Krowiak wrote:
On 04/17/2018 12:13 PM, Pierre Morel wrote:
On 17/04/2018 17:02, Tony Krowiak wrote:
On 04/16/2018 06:51 AM, Pierre Morel wrote:
On 15/04/2018 23:22, Tony Krowiak
Hi, Sohil
On Wed, 2018-04-18 at 07:27 +, Mehta, Sohil wrote:
> On Wed, 2018-04-18 at 05:58 +, Yang, Shunyong wrote:
> >
> > Hi, Gary and Sohil,
> >
> > On Tue, 2018-04-17 at 13:38 -0400, Hook, Gary wrote:
> > >
> > > On 4/13/2018 8:08 PM, Mehta, Sohil wrote:
> > > >
> > > >
> > > >
On 17/04/2018 02:12 μμ, Jan Kara wrote:
> On Tue 17-04-18 01:31:24, Pavlos Parissis wrote:
>> On 16/04/2018 04:40 μμ, Jan Kara wrote:
>
>
>
>>> How easily can you hit this?
>>
>> Very easily, I only need to wait 1-2 days for a crash to occur.
>
> I wouldn't call that very easily but opinions
On Tue, Apr 17, 2018 at 5:07 PM, Masahiro Yamada
wrote:
> 2018-04-15 17:08 GMT+09:00 Ulf Magnusson :
>> On Fri, Apr 13, 2018 at 7:06 AM, Masahiro Yamada
>> wrote:
>>> Add a document for the macro language introduced to Kconfig.
>>>
>>> The motivation of this work is to move the compiler option
On Tue 2018-04-17 13:45:59, Sasha Levin wrote:
> On Tue, Apr 17, 2018 at 02:24:54PM +0200, Petr Mladek wrote:
> >Back to the trend. Last week I got autosel mails even for
> >patches that were still being discussed, had issues, and
> >were far from upstream:
> >
> >
On Wed, Apr 18, 2018 at 12:41:27PM +0800, Peter Xu wrote:
> (PSI stands for: Page Selective Invalidations)
>
> Intel IOMMU has the caching mode to ease emulation of the device.
> When that bit is set, we need to send PSIs even for newly mapped
> pages. However current driver is not fully obey
On Mon, Apr 09, 2018 at 09:02:33AM +0200, Hans de Goede wrote:
> HI,
>
> On 09-04-18 03:32, Kunihiko Hayashi wrote:
> > This reverts commit f0f56716fc3e5d547fd7811eb218a30ed0695605.
> >
> > According to Thierry's view,
> > https://www.spinics.net/lists/linux-ide/msg55357.html
> > some
Christophe,
On Wed, Apr 18, 2018 at 8:34 AM, Christophe LEROY
wrote:
>
>
> Le 17/04/2018 à 19:10, Mathieu Malaterre a écrit :
>>
>> On Tue, Apr 17, 2018 at 6:49 PM, Christophe LEROY
>> wrote:
>>>
>>>
>>>
>>> Le 17/04/2018 à 18:45, Mathieu Malaterre a écrit :
On Tue, Apr 17, 2018
AFS server records get removed from the net->fs_servers tree when they're
deleted, but not from the net->fs_addresses{4,6} lists, which can lead to
an oops in afs_find_server() when a server record has been removed, for
instance during rmmod.
Fix this by deleting the record from the by-address
Hi James,
On 18/04/18 00:09, James Hogan wrote:
On Wed, Apr 11, 2018 at 08:50:18AM +0100, Matt Redfearn wrote:
diff --git a/arch/mips/boot/compressed/Makefile
b/arch/mips/boot/compressed/Makefile
index adce180f3ee4..e03f522c33ac 100644
--- a/arch/mips/boot/compressed/Makefile
+++
Hi Sven,
On 4/18/2018 1:08 PM, Sven Eckelmann wrote:
> Hi,
>
> On Mittwoch, 18. April 2018 12:45:20 CEST Sricharan R wrote:
>> Right, will add the above change to soc.dtsi in V6. Does that sound ok for
>> you ?
>
> I have submitted a patch for this now [1] because I need this for OpenWrt
>
v2:
- cc correct people and iommu list
(PSI stands for: Page Selective Invalidations)
Intel IOMMU has the caching mode to ease emulation of the device.
When that bit is set, we need to send PSIs even for newly mapped
pages. However current driver is not fully obey the rule. E.g.,
iommu_map()
It is helpful to debug and triage PSI notification missings.
Signed-off-by: Peter Xu
---
drivers/iommu/dmar.c| 3 +++
drivers/iommu/intel-iommu.c | 3 +++
2 files changed, 6 insertions(+)
diff --git a/drivers/iommu/dmar.c b/drivers/iommu/dmar.c
index 9a7ffd13c7f0..62ae26c3f7b7 100644
Generalize this new helper to notify one newly created mapping on one
single IOMMU. We can further leverage this helper in the next patch.
Signed-off-by: Peter Xu
---
drivers/iommu/intel-iommu.c | 26 ++
1 file changed, 14 insertions(+), 12 deletions(-)
diff --git
When caching mode is enabled for IOMMU, we should send explicit IOTLB
PSIs even for newly created mappings. However these events are missing
for all intel_iommu_map() callers, e.g., iommu_map(). One direct user
is the vfio-pci driver.
To make sure we'll send the PSIs always when necessary, this
On Tue, Apr 17, 2018 at 11:31 PM, Amir Goldstein wrote:
> On Thu, Apr 12, 2018 at 6:08 PM, Miklos Szeredi wrote:
>> Since set of arguments are so similar, handle in a common helper.
>>
>> Signed-off-by: Miklos Szeredi
>> ---
>> fs/overlayfs/file.c | 79
>>
Signed-off-by: Geert Uytterhoeven
---
arch/m68k/configs/amiga_defconfig| 14 +-
arch/m68k/configs/apollo_defconfig | 14 +-
arch/m68k/configs/atari_defconfig| 14 +-
arch/m68k/configs/bvme6000_defconfig | 14 +-
On Wed, 18 Apr 2018 10:02:12 +0200
Peter Rosin wrote:
> On 2018-04-18 09:36, Boris Brezillon wrote:
> > On Tue, 17 Apr 2018 15:10:51 +0200
> > Peter Rosin wrote:
> >
> >> When the of-graph points to a tda998x-compatible HDMI encoder, register
> >> as a component master and bind to the
Correct all SATA ahci and phy controller register
addresses and interrupt lines to proper values.
Fixes: 344a2e514182 ("arm64: dts: Add SATA DT nodes for Stingray SoC")
Signed-off-by: Srinath Mannam
Reviewed-by: Ray Jui
Reviewed-by: Scott Branden
Reviewed-by: Andrew Gospodarek
---
On Tue, Apr 17, 2018 at 07:25:15PM +0800, Chen-Yu Tsai wrote:
> On Tue, Apr 17, 2018 at 7:17 PM, Maxime Ripard
> wrote:
> > On Tue, Apr 17, 2018 at 11:12:41AM +0800, Chen-Yu Tsai wrote:
> >> On Tue, Apr 17, 2018 at 5:50 AM, Mylène Josserand
> >> wrote:
> >> > Move the assembly code for cluster
> Il giorno 17 apr 2018, alle ore 23:42, Kees Cook ha
> scritto:
>
> Some elevators may not correctly check rq->rq_flags & RQF_ELVPRIV, and
> may attempt to read rq->elv fields. When requests got reused, this
> caused BFQ to think it already had a bfqq (rq->elv.priv[1]) allocated.
Hi Kees,
> -Original Mail-
> Sender: Thomas Gleixner [mailto:t...@linutronix.de]
> Time: 2018/4/17 18:19
> Receiver: David Wang
> CC: mi...@redhat.com; h...@zytor.com; mi...@kernel.org;
> gre...@linuxfoundation.org; x...@kernel.org; linux-
> ker...@vger.kernel.org; brucech...@via-alliance.com;
>
On Tue, 2018-04-17 at 19:30 +0200, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski
>
> Switch to using the reset framework instead of handcoded reset routines
> we used so far.
>
> Signed-off-by: Bartosz Golaszewski
[...]
> @@ -268,6 +282,15 @@ static int da8xx_rproc_probe(struct
2018-04-18 7:44 GMT+02:00 Sekhar Nori :
> On Tuesday 17 April 2018 11:00 PM, Bartosz Golaszewski wrote:
>> From: Bartosz Golaszewski
>>
>> Switch to using the reset framework instead of handcoded reset routines
>> we used so far.
>>
>> Signed-off-by: Bartosz Golaszewski
>
> Looks good!
>
>
On Wed, Apr 18, 2018 at 10:05:55AM +0200, Michal Hocko wrote:
>
> Yes, looks good to me. As mentioned in other emails prctl_set_mm_map
> really deserves a comment explaining why we are doing the down_read
>
> What about something like the following?
> "
> arg_lock protects concurent updates but
On Wed, Apr 18, 2018 at 11:24:22AM +0800, Wanpeng Li wrote:
> 2018-04-18 4:24 GMT+08:00 Eduardo Habkost :
> > On Tue, Apr 17, 2018 at 06:40:58PM +0800, Wanpeng Li wrote:
> >> Cc Eduardo,
> >> 2018-02-26 20:41 GMT+08:00 Paolo Bonzini :
> >> > On 26/02/2018 13:22, Borislav Petkov wrote:
> >> >> On
On Wed 18-04-18 12:02:17, Cyrill Gorcunov wrote:
> On Wed, Apr 18, 2018 at 10:05:55AM +0200, Michal Hocko wrote:
> >
> > Yes, looks good to me. As mentioned in other emails prctl_set_mm_map
> > really deserves a comment explaining why we are doing the down_read
> >
> > What about something like
On Mon, 16 Apr 2018 21:07:47 -0700
Joel Fernandes wrote:
> With TRACE_IRQFLAGS, we call trace_ API too many times. We don't need
> to if local_irq_restore or local_irq_save didn't actually do anything.
>
> This gives around a 4% improvement in performance when doing the
> following command:
Hi Bjorn,
Thank you very much for you time and solution.
On Tue, Apr 17, 2018 at 10:41 PM, Bjorn Helgaas wrote:
> On Tue, Apr 17, 2018 at 02:33:52PM +0530, Srinath Mannam wrote:
>> Hi Bjorn,
>>
>> Thank you for more insight you have given about the problem.
>>
>> For us the issue comes before
On Tue, Apr 17, 2018 at 08:13:06PM +0530, Souptick Joarder wrote:
> Use new return type vm_fault_t for fault handler. For
> now, this is just documenting that the function returns
> a VM_FAULT value rather than an errno. Once all instances
> are converted, vm_fault_t will become a distinct type.
>
> Il giorno 18 apr 2018, alle ore 00:57, Jens Axboe ha
> scritto:
>
> On 4/17/18 3:48 PM, Jens Axboe wrote:
>> On 4/17/18 3:47 PM, Kees Cook wrote:
>>> On Tue, Apr 17, 2018 at 2:39 PM, Jens Axboe wrote:
On 4/17/18 3:25 PM, Kees Cook wrote:
> On Tue, Apr 17, 2018 at 1:46 PM, Kees
Hello!
On 4/17/2018 4:35 PM, Jacopo Mondi wrote:
With commit ce88313069c36eef80f21fd7 ("arch/sh: make the DMA mapping
operations observe dev->dma_pfn_offset") the generic DMA allocation
function on which the SH 'dma_alloc_coherent()' function relies on,
access the 'dma_pfn_offset' field of
PPv2 TX/RX descriptors uses 40bits DMA addresses, but 41 bits masks were
used (GENMASK_ULL(40, 0)).
This commit fixes that by using the correct mask.
Fixes: e7c5359f2eed ("net: mvpp2: introduce PPv2.2 HW descriptors and adapt
accessors")
Signed-off-by: Maxime Chevallier
---
Hi Andrzej, Tomasz
2018-04-16 15:12 GMT+02:00 Tomasz Figa :
> Hi Andrzej,
>
> On Mon, Apr 16, 2018 at 6:57 PM Andrzej Hajda wrote:
>
>> On 05.04.2018 11:49, Enric Balletbo i Serra wrote:
>> > From: Tomasz Figa
>> >
>> > It looks like the driver subsystem detaches devices from power domains
>> >
On Wed, Apr 18, 2018 at 09:13:39AM +0100, Quentin Perret wrote:
> On Tuesday 17 Apr 2018 at 23:22:13 (+0800), Leo Yan wrote:
> > On Fri, Apr 06, 2018 at 04:36:05PM +0100, Dietmar Eggemann wrote:
> > > From: Quentin Perret
> > >
> > > In preparation for the definition of an energy-aware wakeup
On Fri, Apr 06, 2018 at 04:36:05PM +0100, Dietmar Eggemann wrote:
[...]
> +/*
> + * Estimates the system level energy assuming that p wakes-up on dst_cpu.
> + *
> + * compute_energy() is safe to call only if an energy model is available for
> + * the platform, which is when
On 17.04.2018 16:32, Peter Rosin wrote:
Use the new probe style for i2c drivers.
Signed-off-by: Peter Rosin
Thanks Peter,
Don't know why i2c needs a new probe style to save one function parameter...
But this patch looks otherwise good to me.
Acked-by: Michael Hennerich
---
Consistenly use << to define MS_* constants.
Signed-off-by: Christian Brauner
Cc: Alexander Viro
---
include/uapi/linux/fs.h | 33 +
1 file changed, 17 insertions(+), 16 deletions(-)
diff --git a/include/uapi/linux/fs.h b/include/uapi/linux/fs.h
index
This lets userspace query whether a mountpoint was made MS_SLAVE.
Signed-off-by: Christian Brauner
Cc: Alexander Viro
---
fs/statfs.c| 10 +-
include/linux/statfs.h | 1 +
2 files changed, 10 insertions(+), 1 deletion(-)
diff --git a/fs/statfs.c b/fs/statfs.c
index
This lets userspace query whether a mountpoint was made MS_SHARED.
Signed-off-by: Christian Brauner
Cc: Alexander Viro
---
fs/statfs.c| 2 ++
include/linux/statfs.h | 1 +
2 files changed, 3 insertions(+)
diff --git a/fs/statfs.c b/fs/statfs.c
index 61b3063d3921..2fc6f9c3793c
This lets userspace query whether a mountpoint was made MS_PRIVATE.
Signed-off-by: Christian Brauner
Cc: Alexander Viro
---
fs/statfs.c| 2 ++
include/linux/statfs.h | 1 +
2 files changed, 3 insertions(+)
diff --git a/fs/statfs.c b/fs/statfs.c
index 2fc6f9c3793c..26cda2586d7e
Hey,
This is a resend of this to CC more people and because it seems to have
gotten lost in the prior merge window. I should've sent it afterwards
right away.
This series:
- unifies the definition of constants in statfs.h and fs.h
Please note the comments by Greg and others on this part:
This lets userspace query whether a mountpoint was made MS_UNBINDABLE.
Signed-off-by: Christian Brauner
Cc: Alexander Viro
---
fs/statfs.c| 2 ++
include/linux/statfs.h | 1 +
2 files changed, 3 insertions(+)
diff --git a/fs/statfs.c b/fs/statfs.c
index 5b2a24f0f263..61b3063d3921
Consistenly use << to define ST_* constants. This also aligns them with
their MS_* counterparts in fs.h
Signed-off-by: Christian Brauner
Cc: Alexander Viro
---
include/linux/statfs.h | 26 +-
1 file changed, 13 insertions(+), 13 deletions(-)
diff --git
Allo Mylène,
On Mon, Apr 16, 2018 at 11:50 PM, Mylène Josserand
wrote:
> The CNTVOFF register from arch timer is uninitialized.
> It should be done by the bootloader but it is currently not the case,
> even for boot CPU because this SoC is booting in secure mode.
> It leads to an random offset
On Tue, 17 Apr 2018 10:30:46 +0300
Eugen Hristev wrote:
> On 15.04.2018 22:29, Jonathan Cameron wrote:
> > On Tue, 10 Apr 2018 11:57:49 +0300
> > Eugen Hristev wrote:
> >
> >> Add new channel type for relative position on a pad.
> >>
> >> These type of analog sensor offers the position of a
Since msleep is based on jiffies, this 3 ms sleep becomes actually 20 ms.
Worst of all, since this sleep is used in a loop when writing, a single page
write (256 to 1024 bytes) causes 17 ms extra time.
When writing large files (for example u-boot is usually 512 KB) this delay
adds up to minutes.
On Fri, 13 Apr 2018 10:44:32 -0400
Steven Rostedt wrote:
> On Fri, 13 Apr 2018 09:24:34 -0500
> Tom Zanussi wrote:
>
> > Yeah, I agree - I'd rather get it right than get it in now. I thought
> > this made sense, and was based on input from Masami, which I may have
> > misinterpreted, but I'll
The JIT compiler emits ia32 bit instructions. Currently, It supports
eBPF only. Classic BPF is supported because of the conversion by BPF core.
Almost all instructions from eBPF ISA supported except the following:
BPF_ALU64 | BPF_DIV | BPF_K
BPF_ALU64 | BPF_DIV | BPF_X
BPF_ALU64 | BPF_MOD | BPF_K
On Tue, 17 Apr 2018 12:19:06 -0700
Dmitry Torokhov wrote:
> Hi Eugen,
>
> On Tue, Apr 17, 2018 at 10:39:24AM +0300, Eugen Hristev wrote:
> >
> >
> > On 17.04.2018 02:58, Dmitry Torokhov wrote:
> > > On Sun, Apr 15, 2018 at 08:33:21PM +0100, Jonathan Cameron wrote:
> > > > On Tue, 10 Apr
901 - 1000 of 1686 matches
Mail list logo
