On Thu, May 26, 2016 at 11:29:45PM +0100, Catalin Marinas wrote:
> On Thu, May 26, 2016 at 11:48:19PM +0300, Yury Norov wrote:
> > On Wed, May 25, 2016 at 02:28:21PM -0700, David Miller wrote:
> > > From: Arnd Bergmann
> > > Date: Wed, 25 May 2016 23:01:06 +0200
> > >
> > > > On Wednesday, May 25
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/f2fs.h | 3 +++
fs/f2fs/inode.c | 5 +
fs/f2fs/super.c | 1 +
3 files changed, 9 insertions(+)
diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h
index 5daba19..c4697b7 100644
--- a/fs/f2fs/f2fs.h
+++ b/fs/f2fs/f2fs.h
@@ -45,6 +45,7 @@ enum {
FAULT_O
If there is no cold page, we don't need to do a loop to flush dirty
data pages.
On /dev/pmem0,
1. dd if=/dev/zero of=/mnt/test/testfile bs=1M count=2048 conv=fsync
Before : 1.1 GB/s
After : 1.2 GB/s
2. dd if=/dev/zero of=/mnt/test/testfile bs=1M count=2048
Before : 2.2 GB/s
After : 2.3 GB/
For data pages, let's try to flush as much as possible in background.
On /dev/pmem0,
1. dd if=/dev/zero of=/mnt/test/testfile bs=1M count=2048 conv=fsync
Before : 800 MB/s
After : 1.1 GB/s
2. dd if=/dev/zero of=/mnt/test/testfile bs=1M count=2048
Before : 1.3 GB/s
After : 2.2 GB/s
Signed-
If we get ENOMEM or EIO in f2fs_find_entry, we should stop right away.
Otherwise, for example, we can get duplicate directory entry by ->chash and
->clevel.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/dir.c| 23 ---
fs/f2fs/inline.c | 4 +++-
fs/f2fs/namei.c | 5 +
3 fi
On Thu, May 26, 2016 at 10:19:13AM -0700, Linus Torvalds wrote:
> On Wed, May 25, 2016 at 11:13 PM, Dave Chinner wrote:
> >
> > Just yell if this is not OK and I'll drop those branches for this
> > merge and resend the pull request
>
> i'm ok with the late branches, it's not like xfs has been
hrtimer_init_on_stack() needs a matching call to
destroy_hrtimer_on_stack(), so both need to be exported.
Signed-off-by: Guenter Roeck
---
kernel/time/hrtimer.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/kernel/time/hrtimer.c b/kernel/time/hrtimer.c
index 8c7392c4fdbd..e99df0ff1d42 1006
If CONFIG_DEBUG_OBJECTS_TIMERS=y, hrtimer_init_on_stack() requires
a matching call to destroy_hrtimer_on_stack() to clean up timer
debug objects.
Signed-off-by: Guenter Roeck
---
net/core/pktgen.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/net/core/pktgen.c b/net
On 05/26/2016 04:59 PM, Andrey Utkin wrote:
Could anybody please give a hint - which kernel-defined i2c objects, and how
many of them, I need to define and use to substitute these driver-defined
functions i2c_read(), i2c_write() ?
https://github.com/bluecherrydvr/linux/blob/release/tw5864/1.16/dr
On Tue, Apr 19, 2016 at 10:02:52AM +0800, Wan Zongshun wrote:
>
> You have to take carefully to arrange the calling sequence for
> iommuv1, iommuv2, kfd module, and drm like the following sequence :
> v1 ->v2->kfd, drm.
>
> iommuv1 -- rootfs_initcall(fn)
> IOMMUV2 -- device_initcall(fn)
> kfd mod
[ Alison, can you try this patch ]
This uses netpoll_poll_lock()/unlock() to synchronize netpoll and napi
poll operations. Without this method, the synchronization is done by
looping on NAPI_STATE_SCHED 'bitset'. This method works fine on a non-rt
kernel because a softirq can not be preempted, and
Fixed coding style issues.
Signed-off-by: Steven Laabs
---
drivers/staging/comedi/drivers/ni_atmio.c | 180 +++---
1 file changed, 91 insertions(+), 89 deletions(-)
diff --git a/drivers/staging/comedi/drivers/ni_atmio.c
b/drivers/staging/comedi/drivers/ni_atmio.c
index
Am Mittwoch, 25. Mai 2016, 16:51:56 schrieb Xing Zheng:
> Like rk3288, the pclk supplying the watchdog is controlled via the
> SGRF register area. Additionally the SGRF isn't even writable in
> every boot mode.
>
> But still the clock control is available and in the future someone
> might want to
On 5/25/2016 5:37 PM, Minchan Kim wrote:
On Tue, May 24, 2016 at 11:58:11AM +0900, Minchan Kim wrote:
On Mon, May 23, 2016 at 10:16:08AM -0700, Yang Shi wrote:
Per the discussion with Joonsoo Kim [1], we need check the return value of
lookup_page_ext() for all call sites since it might return N
This is helpful for debugging. Without this all I was getting from "iw"
command on failed creating of P2P interface was:
> command failed: Too many open files in system (-23)
Signed-off-by: Rafał Miłecki
---
V2: s/in/if/ in commit message
V3: Add one more error message as suggested by Arend
V4: A
On Thu, May 26, 2016 at 02:04:50PM -0700, Kees Cook wrote:
> One problem with seccomp was that ptrace could be used to change a
> syscall after seccomp filtering had completed. This was a well documented
> limitation, and it was recommended to block ptrace when defining a filter
> to avoid this pro
The mm-of-the-moment snapshot 2016-05-26-15-51 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You wi
On Thu, May 26, 2016 at 3:46 PM, Hillf Danton wrote:
>> > See if this fixes your reproducer.
>> >
>> > diff --git a/fs/xattr.c b/fs/xattr.c
>> > index b11945e..49b8eab 100644
>> > --- a/fs/xattr.c
>> > +++ b/fs/xattr.c
>> > @@ -667,6 +667,9 @@ xattr_resolve_name(const struct xattr_handler
>> > **
On 05/17/2016 10:30 AM, Al Stone wrote:
> On 05/16/2016 05:44 PM, Alexey Klimov wrote:
>> On Mon, May 2, 2016 at 09:19 PM, Al Stone wrote:
>>> On 04/25/2016 03:21 PM, Al Stone wrote:
The ACPI 6.1 specification was recently released at the end of January
2016, but the arm64 kernel document
On Thu, May 26, 2016 at 11:11:51AM +0100, Robin Murphy wrote:
>On 25/05/16 22:43, Wei Yang wrote:
>>On Wed, May 25, 2016 at 11:17:49AM +0100, Robin Murphy wrote:
>>>On 25/05/16 00:06, Wei Yang wrote:
Hi, Joerg
Not sure whether you think this calculation is correct.
If I missed
On Thu, May 26, 2016 at 11:48:19PM +0300, Yury Norov wrote:
> On Wed, May 25, 2016 at 02:28:21PM -0700, David Miller wrote:
> > From: Arnd Bergmann
> > Date: Wed, 25 May 2016 23:01:06 +0200
> >
> > > On Wednesday, May 25, 2016 1:50:39 PM CEST David Miller wrote:
> > >> From: Arnd Bergmann
> > >>
The block sector size should be in unit of 512 bytes, not in bytes.
Signed-off-by: Long Li
---
drivers/scsi/sd.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/scsi/sd.c b/drivers/scsi/sd.c
index 428c03e..4bce17e 100644
--- a/drivers/scsi/sd.c
+++ b/drivers/sc
The latest mainline kernel (commit 3f59de0) shows a regression. The symptom is
that as soon as the kernel is started, the display is blanked, and it is never
turned on again. This problem was bisected to commit
f21a21983ef13a031250c4c3f6018e29a549d0f1
("drm/i915: Splitting intel_dp_detect"). The
On 22/05/2016 13:36, Pali Rohár wrote:
> ACPI DSDT tables have defined other WMI codes, but does not contain any
> description when those codes are emitted. Some other codes can be found in
> logs on internet. In this patch are all which I saw, but lot of them are
> not tested properly (e.g. for du
Hi,
>> sg_set_buf expects that the buf parameter passed in should be from
>> lowmem and a valid pageframe. This is not true for pages from
>> dma_alloc_coherent which can be carveouts, hence the check fails.
>
>OK, given you mean dma_pool_alloc here, the check fails for the
>pageframe because of t
On 05/26/2016 12:55 PM, Boris Ostrovsky wrote:
> On 05/26/2016 12:26 PM, Jan Beulich wrote:
> Boris Ostrovsky 05/25/16 9:17 PM >>>
>>> On 05/05/2016 12:58 AM, Lv Zheng wrote:
+static u8
+acpi_hw_get_access_bit_width(struct acpi_generic_address *reg, u8
max_bit_width)
+{
>>
Follow up Sergey's review
>From 2deede28c91910a9d3493feae30bed507e72f213 Mon Sep 17 00:00:00 2001
From: Minchan Kim
Date: Thu, 5 May 2016 00:01:03 +0900
Subject: [PATCH v6r2] zsmalloc: page migration support
This patch introduces run-time migration feature for zspage.
For migration, VM uses pag
Am Donnerstag, 26. Mai 2016, 21:49:08 schrieb Xing Zheng:
> It maybe due to a copy-paste error the error handing should be
> cclk not clk.
>
> Reported-by: Lin Huang
> Signed-off-by: Xing Zheng
applied to my clk-fixes branch after adapting the commit message a bit.
Thanks for catching that
He
On Thu, 26 May 2016, Linus Torvalds wrote:
> On Thu, May 26, 2016 at 11:31 AM, Linus Torvalds
> wrote:
> >
> > Pulled and then immediately unpulled again.
>
> .. and having thought it over, I ended up re-pulling again, so now
> it's going through my build test.
>
> Consider this discussion a str
On 05/25/2016 06:04 PM, Rich Felker wrote:
> On Wed, May 25, 2016 at 11:22:15AM +0100, Mark Rutland wrote:
>> * What state should the CPU be in when it branches to the provided
>> address?
>> - Must the MMU be off?
>
> Current models are nommu.
As far as I know, we're the first nommu SMP im
> From: Dey, Megha
> Sent: Thursday, May 19, 2016 5:43 PM
> To: herb...@gondor.apana.org.au
> Cc: tim.c.c...@linux.intel.com; da...@davemloft.net; linux-
> cry...@vger.kernel.org; linux-kernel@vger.kernel.org; Dey, Megha
> ; Yu, Fenghua ; Megha
> Dey
> Subject: [PATCH 2/7] crypto : async implement
On 05/26/2016 03:17 PM, Stephen Warren wrote:
On 05/26/2016 09:40 AM, Thierry Reding wrote:
From: Thierry Reding
All of these Tegra SoC generations have a ChipIdea UDC IP block that can
be used for device mode communication with a host. Implement rudimentary
support that doesn't allow switchin
mpi_read_from_buffer() reads a MPI from a buffer into a newly allocated
MPI instance. It expects the buffer's leading two bytes to contain the
number of bits, followed by the actual payload.
On failure, it returns NULL and updates the in/out argument ret_nread
somewhat inconsistently:
- If the giv
Currently, if digsig_verify_rsa() detects that the modulo's length is zero,
i.e. mlen == 0, it returns -ENOMEM which doesn't really fit here.
Make digsig_verify_rsa() return -EINVAL upon mlen == 0.
Signed-off-by: Nicolai Stange
---
lib/digsig.c | 8 +---
1 file changed, 5 insertions(+), 3 d
mpi_read_from_buffer() and mpi_read_raw_data() do basically the same thing
except that the former extracts the number of payload bits from the first
two bytes of the input buffer.
Besides that, the data copying logic is exactly the same.
Replace the open coded buffer to MPI instance conversion by
The first two bytes of the input buffer encode its expected length and
mpi_read_from_buffer() prints a console message if the given buffer is too
short.
However, there are some oddities with how this message is printed:
- It is printed at the default loglevel. This is different from the
one used
Currently, if the input buffer is shorter than the expected length as
indicated by its first two bytes, an MPI instance of this expected length
will be allocated and filled with as much data as is available. The rest
will remain uninitialized.
Instead of leaving this condition undetected, an error
mpi_read_from_buffer() and mpi_read_raw_data() do almost the same and share a
fair amount of common code.
This patchset attempts to rewrite mpi_read_from_buffer() in order to implement
it in terms of mpi_read_raw_data().
The patches 1 and 3, i.e.
"lib/mpi: mpi_read_from_buffer(): return error c
On Thu, May 26, 2016 at 1:10 PM, Al Viro wrote:
>
> How about the things like followups to earlier merges?
Small and obvious follow-ups are fine. What I really hated about this
ceph pull request was that it was multiple thousand lines of changes,
with no previous work or warning, and effectively
On 05/26/2016 09:40 AM, Thierry Reding wrote:
From: Thierry Reding
All of these Tegra SoC generations have a ChipIdea UDC IP block that can
be used for device mode communication with a host. Implement rudimentary
support that doesn't allow switching between host and device modes.
Are you sure
On 5/16/2016 1:18 PM, Pantelis Antoniou wrote:
> This patchset implements two new target methods.
>
> A target index method which allows selecting different
> targets according to an argument using an extended API and
> a target root method that fences the target only
> to a specific given root.
>
On Thu, May 26, 2016 at 11:31 AM, Linus Torvalds
wrote:
>
> Pulled and then immediately unpulled again.
.. and having thought it over, I ended up re-pulling again, so now
it's going through my build test.
Consider this discussion a strong encouragement to *not* do this in
the future - sending me
On 5/26/2016 10:19 AM, Peter Zijlstra wrote:
--- a/arch/tile/lib/spinlock_32.c
+++ b/arch/tile/lib/spinlock_32.c
@@ -72,10 +72,14 @@ void arch_spin_unlock_wait(arch_spinlock
if (next == curr)
return;
+ smp_rmb();
+
/* Wait until the current locker has released
On Thu, May 26, 2016 at 09:49:42PM +0800, Zhangjian (Bamvor) wrote:
> Hi, yury
>
> The coredump is usable in our platform. It miss the following definition:
> +#define compat_elf_greg_telf_greg_t
> +#define compat_elf_gregset_t elf_gregset_t
>
> And it leads to the wrong register save in core
It doesn't make sense to allow the duty cycle to be larger than the
period. I can see this behavior by, e.g.:
# echo 1 > /sys/class/pwm/pwmchip0/export
# cat /sys/class/pwm/pwmchip0/pwm1/period
100
# echo 101 > /sys/class/pwm/pwmchip0/pwm1/duty_cycle
[... driver may or may not reject the
One problem with seccomp was that ptrace could be used to change a
syscall after seccomp filtering had completed. This was a well documented
limitation, and it was recommended to block ptrace when defining a filter
to avoid this problem. This can be quite a limitation for containers or
other places
Hola
Am Dr. Eric, legítimo y confiable prestamista préstamo de Skye de Servicios
Financieros. Ofrecemos préstamos en una forma clara y comprensible y
condiciones en la tasa de interés del 3%. De $ 5,000.00 a $ 450,000,000.00USD y
Euros Solo. Nos ofrecen préstamos de negocios, préstamos personal
On 05/26/2016 08:47 PM, Mark Brown wrote:
> On Thu, May 26, 2016 at 12:58:22PM +0200, Christer Weinigel wrote:
>
>> One of the main drivers behind devicetree was that Linus got fed
>> up with the churn for all platform device changes in arch/arm.
>> I faintly recall him writing that he would be r
On Thu, May 26, 2016 at 2:51 AM, Florian Westphal wrote:
> John Stultz wrote:
>> In updating a 32bit arm device from 4.6 to Linus' current HEAD, I
>> noticed I was having some trouble with networking, and realized that
>> /proc/net/ip_tables_names was suddenly empty.
>>
>> Digging through the reg
On Thu, May 26, 2016 at 3:30 AM, Felipe Balbi
wrote:
>
> Hi,
>
> Leo Li writes:
On certain platforms (e.g. ARM64) the dma_ops needs to be explicitly set
to be able to do DMA allocations, so use the of_dma_configure() helper
to populate the dma properties and assign an appropriate d
Hi Linus,
this is the non-critical part of kbuild:
- Coccinelle fixes, one semantic patch less in this round [Vaishali
Thakkar, Wolfram Sang, Kees Cook]
- rpm-pkg support for (open)SUSE's update-bootloader [Jiří Kosian]
- rpm-pkg restored support for $RPMOPTS [Srinivas Pandruvada]
- deb-pkg fixe
Hi Lorenzo,
On Thu, May 26, 2016 at 5:34 AM, Lorenzo Pieralisi
wrote:
> Hi Duc,
>
> On Wed, May 25, 2016 at 04:13:35PM -0700, Duc Dang wrote:
>> On Thu, Feb 25, 2016 at 9:38 AM, Lorenzo Pieralisi
>> wrote:
>> > On Wed, Feb 24, 2016 at 02:28:10PM -0800, Duc Dang wrote:
>> >> On Wed, Feb 24, 2016
On 26.5.2016 21:21, Tejun Heo wrote:
> Hello,
>
> On Thu, May 26, 2016 at 11:19:06AM +0200, Vlastimil Babka wrote:
>>> if (is_atomic) {
>>> margin = 3;
>>>
>>> if (chunk->map_alloc <
>>> - chunk->map_used + PCPU_ATOMIC_MAP_MARGIN_LOW &&
>>> -
On Wed, May 25, 2016 at 02:28:21PM -0700, David Miller wrote:
> From: Arnd Bergmann
> Date: Wed, 25 May 2016 23:01:06 +0200
>
> > On Wednesday, May 25, 2016 1:50:39 PM CEST David Miller wrote:
> >> From: Arnd Bergmann
> >> Date: Wed, 25 May 2016 22:47:33 +0200
> >>
> >> > If we use the normal c
On Thu, May 26, 2016 at 10:39:31PM +0200, Radim Krčmář wrote:
> 2016-05-26 10:32+0300, km...@yandex-team.ru:
> > From: Dmitry Bilunov
> >
> > Intel CPUs having Turbo Boost feature implement an MSR to provide a
> > control interface via rdmsr/wrmsr instructions. One could detect the
> > presence o
Hi Linus,
Please pull these kconfig fixes for v4.7-rc1:
- Fix for behavior of tristate choice items and fix for documentation
of existing kconfig behavior [Dirk Gouders]
- More helpful "unexpected data" kconfig warning [Paul Bolle]
Thanks,
Michal
The following changes since commit f55532a0c0b8
On Thu, 26 May 2016 12:26:27 +0200
Paolo Bonzini wrote:
>
>
> On 25/05/2016 04:47, Wanpeng Li wrote:
> > From: Wanpeng Li
> >
> > If an emulated lapic timer will fire soon(in the scope of 10us the
> > base of dynamic halt-polling, lower-end of message passing workload
> > latency TCP_RR's pol
2016-05-26 10:32+0300, km...@yandex-team.ru:
> From: Dmitry Bilunov
>
> Intel CPUs having Turbo Boost feature implement an MSR to provide a
> control interface via rdmsr/wrmsr instructions. One could detect the
> presence of this feature by issuing one of these instructions and
> handling the #GP
On 5/26/2016 12:48 AM, Bjorn Andersson wrote:
> On Tue 24 May 12:54 PDT 2016, Neil Leeder wrote:
>
>>
>>
>> On 5/24/2016 07:23 AM, Mark Rutland wrote:
>>> On Mon, May 23, 2016 at 02:22:59PM -0400, Neil Leeder wrote:
On 5/23/2016 01:25 PM, Mark Rutland wrote:
> On Fri, May 20, 2016
chosen
because they provide a bit more entropy early on boot and better
performance when specific arch instructions are not available.
Signed-off-by: Thomas Garnier
Reviewed-by: Kees Cook
---
Based on next-20160526
---
include/linux/slab_def.h | 2 +-
mm/slab.c| 80
Context Switches 189140 (2282.15)
Sleeps 99008.6 (768.091)
After:
Average Optimal load -j 12 Run (std deviation):
Elapsed Time 102.47 (0.562732)
User Time 1045.3 (1.34263)
System Time 88.311 (0.342554)
Percent CPU 1105.8 (6.49444)
Context Switches 189081 (2355.78)
Sleeps 99231.5 (800.358)
Signed-
This is PATCH v1 for the SLUB Freelist randomization. The patch is now based
on the Linux master branch (as the based SLAB patch was merged).
Changes since RFC v2:
- Redone slab_test testing to decide best entropy approach on new page
creation.
- Moved to use get_random_int as best approach t
Hi Linus,
please pull these kbuild changes for v4.7-rc1:
- New option CONFIG_TRIM_UNUSED_KSYMS which does a two-pass build and
unexports symbols which are not used in the current config [Nicolas
Pitre]
- Several kbuild rule cleanups [Masahiro Yamada]
- Warning option adjustments for gcov etc [
On Fri, May 27, 2016 at 01:07:33AM +0530, Bhaktipriya Shridhar wrote:
> alloc_workqueue replaces deprecated create_workqueue().
>
> create_workqueue has been replaced with alloc_workqueue with max_active
> as 0 since there is no need for throttling the number of active work items.
>
> WQ_MEM_RECL
Hello,
On 18 May 2016 at 03:24, Brian Norris wrote:
> On Mon, May 16, 2016 at 09:47:20PM +0200, Michal Suchanek wrote:
>> Hello,
>>
>> On 6 May 2016 at 02:31, Brian Norris wrote:
>> > Hi,
>> >
>> > I'm picking up Michal's patch set, since he dropped it on the floor, and
>> > it's
>> > useful fo
On Thu, May 26, 2016 at 12:54:27PM -0700, Linus Torvalds wrote:
> Having entirely new pull requests show up that haven't even been on my
> radar because they weren't in linux-next is annoying.
How about the things like followups to earlier merges? I've got in
#for-linus
update D/f/directory-
Recursive locking for ww_mutexes was originally conceived as an
exception. However, it is heavily used by the DRM atomic modesetting
code. Currently, the recursive deadlock is checked after we have queued
up for a busy-spin and as we never release the lock, we spin until
kicked, whereupon the deadl
On Thu, May 26, 2016 at 12:02 PM, Sage Weil wrote:
>
> The branch was assembled in its current form yesterday and is included in
> today's -next:
So that's what I *don't* want, and it's not the point of "next".
The next branch is about the *next* merge window. If it was about the
current one, it
From: Catalin Marinas
Date: Thu, 26 May 2016 15:20:58 +0100
> We can solve (a) by adding more __SC_WRAP annotations in the generic
> unistd.h.
...
I really think it's much more robust to clear the tops of the registers
by default. Then you won't be auditing constantly and adding more and
more
Hello,
A follow-up patch. Will queue in cgroup/for-4.7-fixes.
Thanks.
-- 8< --
If percpu_ref initialization fails during css_create(), the free path
can end up trying to free css->id of zero. As ID 0 is unused, it
doesn't cause a critical breakage but it does trigger a warning
message.
From: Naveen Kaje
I2C QUP driver relies on SMBus emulation support from the framework.
To handle SMBus block reads, the driver should check I2C_M_RECV_LEN
flag and should read the first byte received as the message length.
The driver configures the QUP hardware to read one byte. Once the
message
From: Naveen Kaje
Add support to get the device parameters from ACPI. Assume
that the clocks are managed by firmware.
Signed-off-by: Naveen Kaje
Signed-off-by: Austin Christ
---
drivers/i2c/busses/i2c-qup.c | 60
1 file changed, 44 insertions(+), 1
alloc_workqueue replaces deprecated create_workqueue().
create_workqueue has been replaced with alloc_workqueue with max_active
as 0 since there is no need for throttling the number of active work items.
WQ_MEM_RECLAIM has not been set to because kfd_process_wq will not be used in
memory reclaim
On Tue, Apr 12, 2016 at 12:42:11AM +0300, Cyrill Gorcunov wrote:
...
> I think so. At least this gives some kind of consistensy while we're
> fetching data. Something close to peeking data from pipes/sockets.
>
> > In that case, I think just write trylocking the termios rwsem should
> > prevent an
Some SPI controllers can transfer only small piece of data at a time.
Since SPI core gained a function to get the maximum transfer length use
it.
Signed-off-by: Michal Suchanek
---
Tested on sunxi spi with DMA enabled and disabled. Makes a visible speed
difference and display works in either ca
Hello,
I was updating my config by make oldconfig for a while and noticed that my USB
OTG controller is not working. Apparently it grew dependency on NOP_USB_XCEIV
over time.
Looking through defconfigs some have it included and some which seem in need of
it don't.
Since the dependency is not obv
From: Feng Tang
Date: Thu, 26 May 2016 16:41:55 +0800
> Maybe the driver maintainer from Atheros could take a look, as they
> can reach all the real HWs :)
Don't hold your breath.
On 05/18/2016 09:52 PM, Huang Shijie wrote:
On Wed, Apr 27, 2016 at 02:53:02PM -0400, David Long wrote:
From: Sandeepa Prabhu
Kprobes needs simulation of instructions that cannot be stepped
from a different memory location, e.g.: those instructions
that uses PC-relative addressing. In simulati
On 05/17/2016 11:29 PM, Masami Hiramatsu wrote:
On Tue, 17 May 2016 16:58:09 +0800
Huang Shijie wrote:
On Wed, Apr 27, 2016 at 02:53:00PM -0400, David Long wrote:
+
+/*
+ * Interrupts need to be disabled before single-step mode is set, and not
+ * reenabled until after single-step mode ends.
Hello,
On Thu, May 26, 2016 at 11:19:06AM +0200, Vlastimil Babka wrote:
> > if (is_atomic) {
> > margin = 3;
> >
> > if (chunk->map_alloc <
> > - chunk->map_used + PCPU_ATOMIC_MAP_MARGIN_LOW &&
> > - pcpu_async_enabled)
> > -
Hello,
Nice catch. I added more details to the changelog, tagged it for
-stable and applied it to cgroup/for-4.7-fixes.
Thanks!
-- 8< --
>From b00c52dae6d9ee8d0f2407118ef6544ae5524781 Mon Sep 17 00:00:00 2001
From: Wenwei Tao
Date: Fri, 13 May 2016 22:59:20 +0800
When create css faile
The upstream commit 1771c6e1a567ea0ba20a4ffe68a1419fd8ef
("x86/kasan: instrument user memory access API") added KASAN instrument to
x86 user memory access API, so added such instrument to ARM64 too.
Tested by test_kasan module.
Signed-off-by: Yang Shi
---
arch/arm64/include/asm/uaccess.h |
On Thu, 26 May 2016, Linus Torvalds wrote:
> On Thu, May 26, 2016 at 11:18 AM, Sage Weil wrote:
> >
> > Please pull the following Ceph updates from
>
> Why was that branch rebased yesterday?
>
> What has been in next, if anything?
>
> And if something has been in next, why was _that_ not sent t
> RK3399 has a PCIe controller which can be used as Root Complex.
> This driver supports a PCIe controller as Root Complex mode.
1 general feedback I have is that there are a lot of magic constants.
I'd appreciate if they could be converted into macros for easy readability.
>
> Signed-off-by: Sh
On Tue, May 24, 2016 at 02:52:19PM -0600, Ross Zwisler wrote:
> Hi Linus, please pull from
>
> git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm
> tags/dax-locking-for-4.7
>
> ... to receive filesystem DAX locking changes for v4.7.
>
> These current version of these changes have bee
Currently, the trace_printk code chooses which static buffer to use based
on what type of atomic context (NMI, IRQ, etc) it's in. Simplify the
code and make it more robust: simply count the nesting depth and choose
a buffer based on the current nesting depth.
The new code will only drop an event
On Thu, May 26, 2016 at 11:00:55AM +0200, Linus Walleij wrote:
> On Thu, May 12, 2016 at 8:42 PM, Uwe Kleine-König
> wrote:
>
> > [added Linus Walleij to Cc, there is a question for you/him below]
> (...)
> >> +void mdio_device_reset(struct mdio_device *mdiodev, int value)
> >> +{
> >> + if (
On Mon, May 16, 2016 at 07:41:28PM +0300, Pantelis Antoniou wrote:
> The changeset helpers are easier to use, use them instead of
> using the static property.
>
> Signed-off-by: Pantelis Antoniou
If you think this is worthwhile, then it's fine with me :)
Acked-by: Wolfram Sang
> +
On Thu, May 26, 2016 at 11:43 AM, Josh Poimboeuf wrote:
>
> That's fine with me, it is indeed a rare case. We can always add the
> per-instruction macro later if needed. Here's a patch.
Ingo, I can take this directly, unless you have other things pending
that you want to send anyway and would
On Fri, May 20, 2016 at 02:06:31PM +0200, Ludovic Desroches wrote:
> When the DMA configuration fails, there is a log reporting that we can't
> use DMA and indicating the error number. When booting the kernel, it is
> annoying to see this error number. Moreover, people can think something
> is goin
On Thu, May 26, 2016 at 12:58:22PM +0200, Christer Weinigel wrote:
> One of the main drivers behind devicetree was that Linus got fed up
> with the churn for all platform device changes in arch/arm. I faintly
> recall him writing that he would be rather unhappy if that just got
> replaced with ch
On Mon, May 23, 2016 at 11:44:39AM -0700, Moritz Fischer wrote:
> This commit fixes a simple typo s/mvmem/nvmem in the
> example.
>
> Signed-off-by: Moritz Fischer
Applied to for-next, thanks!
signature.asc
Description: PGP signature
On Wed, May 25, 2016 at 6:09 PM, Joonsoo Kim wrote:
> On Tue, May 24, 2016 at 02:15:22PM -0700, Thomas Garnier wrote:
>> This commit reorganizes the previous SLAB freelist randomization to
>> prepare for the SLUB implementation. It moves functions that will be
>> shared to slab_common. It also mov
On Fri, May 27, 2016 at 12:15:17AM +0530, Bhaktipriya Shridhar wrote:
> alloc_workqueue replaces deprecated create_workqueue().
>
> kfd_process_wq is used for delay destruction. A work item embedded in
> kfd_process gets queued to kfd_process_wq and when it executes it
> destroys and frees the con
Linus,
The following changes since commit 9842df62004f366b9fed2423e24df10542ee0dc5:
KVM: MTRR: remove MSR 0x2f8 (2016-05-18 18:04:32 +0200)
are available in the git repository at:
git://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus
for you to fetch changes up to fabc712866435660f7
> sg_set_buf expects that the buf parameter passed in should be from
> lowmem and a valid pageframe. This is not true for pages from
> dma_alloc_coherent which can be carveouts, hence the check fails.
OK, given you mean dma_pool_alloc here, the check fails for the
pageframe because of the pool? I
On 05/25/2016 02:09 AM, Pan Xinhui wrote:
In pv_wait_head_or_lock, if there is a spurious_wakeup, and it fails to
get the lock as there is lock stealing, then after a short spin, we need
hash the lock again and enter pv_wait to yield.
Currently after a spurious_wakeup, as l->locked is not _Q_SLO
alloc_workqueue replaces deprecated create_workqueue().
kfd_process_wq is used for delay destruction. A work item embedded in
kfd_process gets queued to kfd_process_wq and when it executes it
destroys and frees the containing kfd_process and thus itself.
This requires a dedicated workqueue becaus
On Wed, May 25, 2016 at 04:51:21PM -0700, Linus Torvalds wrote:
> On Wed, May 25, 2016 at 10:56 AM, Josh Poimboeuf wrote:
> >
> > I used to have a STACKTOOL_IGNORE_INSN macro that would tell the tool to
> > skip warnings for specific instructions in inline asm:
> >
> > Here's an example of it how
Philipp Zabel writes:
> Am Mittwoch, den 25.05.2016, 19:42 -0700 schrieb Kevin Hilman:
>> Neil Armstrong writes:
>>
>> > This patch adds the platform driver for the Amlogic Meson SoC Reset
>> > Controller.
>> >
>> > The Meson8b and GXBB SoCs are supported.
>> >
>> > Signed-off-by: Neil Armstron
101 - 200 of 458 matches
Mail list logo
