On 09/13/2017 07:27 PM, Linus Torvalds wrote:
> On Wed, Sep 13, 2017 at 7:12 PM, Tim Chen wrote:
>>
>> BTW, will you be merging these 2 patches in 4.14?
>
> Yes, and thanks for reminding me.
>
> In fact, would you mind sending me the latest versions, rather than me
> digging them out of the disa
2017-09-14 03:54-0700, Wanpeng Li:
> From: Wanpeng Li
>
> qemu-system-x86-8600 [004] d..1 7205.687530: kvm_entry: vcpu 2
> qemu-system-x86-8600 [004] 7205.687532: kvm_exit: reason EXCEPTION_NMI
> rip 0xa921297d info eb2c0e44e018 8b0e
> qemu-system-x86-8600 [004] 7
On 09/14/17 06:26, Michael Kerrisk (man-pages) wrote:
> Hello Joe,
>
> On 5 September 2017 at 16:44, Joe Lawrence wrote:
>> While backporting Michael's "pipe: fix limit handling" [1] patchset to a
>> distro-kernel, Mikulas noticed that current upstream pipe limit handling
>> contains a few proble
On 09/14/2017 05:24 PM, Geert Uytterhoeven wrote:
Hi Ludovic,
On Thu, Sep 14, 2017 at 5:13 PM, Ludovic BARRE wrote:
On 09/14/2017 03:38 PM, Geert Uytterhoeven wrote:
On Thu, Sep 14, 2017 at 1:06 PM, Arnd Bergmann wrote:
If we send zero-length data to stm32_qspi_tx_poll() on older
compiler
On Wed 13 Sep 09:04 PDT 2017, srinivas.kandaga...@linaro.org wrote:
> From: Srinivas Kandagatla
>
> All Qualcomm PIL drivers require SMP2P module to get a functional PIL,
> Currently user has to explicitly select SMP2P module, after looking
> at failure logs.
>
> Fix this by selecting SMP2P as
On 09/13/2017 07:37 PM, Masahiro Yamada wrote:
This driver implements .alloc() hook, so .map() is not used.
Have you tested this?
I will have to test this on a real system next week before I can really
comment on it.
David.
Signed-off-by: Masahiro Yamada
---
drivers/gpio/gpio-thund
On 14/09/2017 at 16:28, Claudiu Beznea wrote:
> Hi,
>
> This series contains fixes for SAMA5D27 SoM1 EK board. It would be
> good if we will have this in 4.14 version.
>
> Thank you,
> Claudiu
>
> Ludovic Desroches (2):
> ARM: dts: at91: sama5d27_som1_ek: update pinmux/pinconf for LEDs and
>
Add MADV_WIPEONFORK and MADV_KEEPONFORK documentation to
madvise.2. The new functionality was recently merged by
Linus, and should be in the 4.14 kernel.
While documenting what EINVAL means for MADV_WIPEONFORK,
I realized that MADV_FREE has the same thing going on,
so I documented EINVAL for both
From: Colin King
Date: Thu, 14 Sep 2017 17:01:25 +0100
> From: Colin Ian King
>
> tnapi is being initialized and then immediately updated and
> hence the initialiation is redundant. Clean up the warning
> by moving the declaration and initialization to the inside
> of the for-loop.
>
> Cleans
On Thu, Sep 14, 2017 at 9:50 AM, Tim Chen wrote:
>
> Kan tested this before so it should be still good.
> I checked that it applied cleanly on latest master.
Thanks, applied.
I really hope we end up fixing the migration thing too, but at least
4.14 will have the mitigation for the long wait queu
On Thu, Sep 14 2017 at 10:57:28 am BST, Eric Auger
wrote:
> At the moment, the in-kernel emulated ITS is not properly reset.
> On guest restart/reset some registers keep their old values and
> internal structures like device, ITE, collection lists are not emptied.
>
> This may lead to various bug
Great change, just some suggestions ...
On Thu, Sep 14, 2017 at 10:00 AM, Rik van Riel wrote:
> Add MADV_WIPEONFORK and MADV_KEEPONFORK documentation to
> madvise.2. The new functionality was recently merged by
> Linus, and should be in the 4.14 kernel.
>
> While documenting what EINVAL means fo
Add "-U" option to show unreclaimable slabs only.
"-U" and "-S" together can tell us what unreclaimable slabs use the most
memory to help debug huge unreclaimable slabs issue.
Signed-off-by: Yang Shi
---
tools/vm/slabinfo.c | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff
Kernel may panic when oom happens without killable process sometimes it
is
caused by huge unreclaimable slabs used by kernel.
Altough kdump could help debug such problem, however, kdump is not
available on all architectures and it might be malfunction sometime.
And, since kernel already panic it i
Although slabinfo in tools can print out the flag of slabs to show which
one is reclaimable, it sounds nice to have reclaimable flag shows in
/proc/slabinfo too since /proc should be still the first place to check
those slab info.
Add a new column called "reclaim" in /proc/slabinfo, "1" means
recl
Recently we ran into a oom issue, kernel panic due to no killable process.
The dmesg shows huge unreclaimable slabs used almost 100% memory, but kdump
doesn't capture vmcore due to some reason.
So, it may sound better to capture unreclaimable slab info in oom message when
kernel panic to aid trou
On Thu, Sep 14, 2017 at 7:48 AM, Josh Poimboeuf wrote:
>
> As it turns out, the real problem with this option is that it imposes a
> penalty for CONFIG_FRAME_POINTER=n: even with frame pointers disabled,
> it forces the frame pointer to be saved for each function which uses the
> inline asm "call"
On 14/09/2017 at 19:00:13 +0200, Nicolas Ferre wrote:
> On 14/09/2017 at 16:28, Claudiu Beznea wrote:
> > Hi,
> >
> > This series contains fixes for SAMA5D27 SoM1 EK board. It would be
> > good if we will have this in 4.14 version.
> >
> > Thank you,
> > Claudiu
> >
> > Ludovic Desroches (2):
>
On 09/11/2017 07:46 PM, kernel test robot wrote:
> FYI, we noticed the following commit:
>
> commit: 05aa90edc7910ec3d1ed791fa77371b3acb9bf08 ("x86/topology: Avoid
> wasting 128k for package id array")
> url:
> https://github.com/0day-ci/linux/commits/Andi-Kleen/perf-x86-intel-uncore-Cache-log
On Thu, Sep 14, 2017 at 10:16:08AM -0700, Linus Torvalds wrote:
> On Thu, Sep 14, 2017 at 7:48 AM, Josh Poimboeuf wrote:
> >
> > As it turns out, the real problem with this option is that it imposes a
> > penalty for CONFIG_FRAME_POINTER=n: even with frame pointers disabled,
> > it forces the fram
Acked-by: Christoph Lameter
The patch
ASoC: rockchip: i2s: fix unbalanced clk_disable
has been applied to the asoc tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to
Well /proc/slabinfo is a legacy interface. The infomation if a slab is
reclaimable is available via the slabinfo tool. We would break a format
that is relied upon by numerous tools.
On Wed, Sep 13, 2017 at 2:34 PM, Pavel Machek wrote:
>
> On Wed 2017-09-13 14:20:58, David Lin wrote:
> > On Wed, Sep 13, 2017 at 1:20 PM, Pavel Machek wrote:
> > >
> > > Hi!
> > >
> > > > These patch series add the LED_BRIGHTNESS_FAST flag support for
> > > > ledtrig-transient to use hrtimer so
I am not sure that this is generally useful at OOM times unless this is
not a rare occurrence.
Certainly information like that would create more support for making
objects movable.
Richard Guy Briggs writes:
> The trigger is a pseudo filesystem (proc, since PID tree already exists)
> write of a u64 representing the container ID to a file representing a
> process that will become the first process in a new container.
> This might place restrictions on mount namespaces requir
On Thu, Sep 14, 2017 at 12:26:27PM -0500, Josh Poimboeuf wrote:
> On Thu, Sep 14, 2017 at 10:16:08AM -0700, Linus Torvalds wrote:
> > On Thu, Sep 14, 2017 at 7:48 AM, Josh Poimboeuf wrote:
> > >
> > > As it turns out, the real problem with this option is that it imposes a
> > > penalty for CONFIG_
> Everytime a socket is down'd and up'd the logical_packages value increases by
> one, and eventually overflows.
>
> Andi -- I can add this to your patch if you're okay with it.
Sure looks good (minus all the pr_debugs). Thanks for debugging.
-Andi
On Wed, Sep 13, 2017 at 06:51:25PM -0500, Rob Landley wrote:
> From: Rob Landley
>
> Make initramfs honor CONFIG_DEVTMPFS_MOUNT, and move
> /dev/console open after devtmpfs mount.
>
> Add workaround for Debian bug that was copied by Ubuntu.
>
> Signed-off-by: Rob Landley
> ---
>
> v2 discussi
On 9/14/17 10:32 AM, Christopher Lameter wrote:
I am not sure that this is generally useful at OOM times unless this is
not a rare occurrence.
I would say it is not very rare. But, it is definitely troublesome to
narrow down without certain information about slab usage when it happens.
Tha
On Thu, 14 Sep 2017, Andrey Konovalov wrote:
> Looked at this a little more.
>
> dummy_timer() stucks in an infinite loop. It calls
> usb_hcd_giveback_urb(), which in turn calls usbtouch_irq(), which
> calls usb_submit_urb(), which calls dummy_urb_enqueue() and puts urb
> back into dummy urb queu
On Wed, 13 Sep 2017, Davidlohr Bueso wrote:
- /*
-* Pairs with implicit barrier in wait_event_freezable()
-* such that wakeups are not missed in the lockless
-* waitqueue_active() call.
-*/
smp_acquire__after_ctrl_dep();
sorry, forgot to delete thi
On 9/14/17 10:27 AM, Christopher Lameter wrote:
Well /proc/slabinfo is a legacy interface. The infomation if a slab is
reclaimable is available via the slabinfo tool. We would break a format
that is relied upon by numerous tools.
Thanks for pointing this out. It would be unacceptable if it wo
On Thu, Sep 14, 2017 at 7:49 PM, Alan Stern wrote:
> On Thu, 14 Sep 2017, Andrey Konovalov wrote:
>
>> Looked at this a little more.
>>
>> dummy_timer() stucks in an infinite loop. It calls
>> usb_hcd_giveback_urb(), which in turn calls usbtouch_irq(), which
>> calls usb_submit_urb(), which calls
From: Colin Ian King
The variable len is set to zero, never read and then later updated
to p - name, so clearly the zero'ing of len is redundant and
can be removed.
Detected by clang scan-build:
" warning: Value stored to 'len' is never read"
Signed-off-by: Colin Ian King
---
crypto/algboss.c
On 09/14/2017 08:30 AM, Zwindl wrote:
Dear developers:
I'm using Arch Linux with testing enabled, the current kernel version and
details are
`Linux zwindl 4.13.2-1-ARCH #1 SMP PREEMPT Thu Sep 14 02:57:34 UTC 2017 x86_64
GNU/Linux`.
The wireless card can't work properly from the kernel 4.13. Her
On 2017-09-14 12:33, Eric W. Biederman wrote:
> Richard Guy Briggs writes:
>
> > The trigger is a pseudo filesystem (proc, since PID tree already exists)
> > write of a u64 representing the container ID to a file representing a
> > process that will become the first process in a new container.
>
On Fri, Sep 15, 2017 at 12:41 AM, Andreas Dilger wrote:
> I don't think a reproducer is needed. It looks like the fsync callpath
> is happening from an IRQ context due to IO completion, and then re-entering
> the filesystem while a transaction is already started. It looks like the
> original IO
Hi,
On Thu, Sep 07, 2017 at 11:36:03AM -0600, Tycho Andersen wrote:
> From: Juerg Haefliger
>
> Enable support for eXclusive Page Frame Ownership (XPFO) for arm64 and
> provide a hook for updating a single kernel page table entry (which is
> required by the generic XPFO code).
>
> v6: use flush
Drop the global lru lock in isolate callback
before calling zap_page_range which calls
cond_resched, and re-acquire the global lru
lock before returning. Also change return
code to LRU_REMOVED_RETRY.
Use mmput_async when fail to acquire mmap sem
in an atomic context.
Fix "BUG: sleeping function c
On Thu, Sep 07, 2017 at 11:36:05AM -0600, Tycho Andersen wrote:
> From: Juerg Haefliger
>
> If the page is unmapped by XPFO, a data cache flush results in a fatal
> page fault, so let's temporarily map the region, flush the cache, and then
> unmap it.
>
> v6: actually flush in the face of xpfo,
On Thu, Sep 14, 2017 at 10:33 AM, Josh Poimboeuf wrote:
>>
>> a) uglifying the 15 or so relevant inline asm locations with ifdefs; or
>
> Actually I guess we could put the "sp" in a macro... I'll try it.
Exactly. Do something like
#ifdef CONFIG_FRAME_POINTER
# define EXTRA_ASM_CLOBBERS "
On Fri, 2017-09-08 at 15:35 +0200, Borislav Petkov wrote:
> On Fri, Aug 18, 2017 at 05:27:51PM -0700, Ricardo Neri wrote:
> >
> > The function get_reg_offset() returns the offset to the register
> > the
> > argument specifies as indicated in an enumeration of type offset.
> > Callers
> > of this f
On 9/14/2017 9:49 AM, Catalin Marinas wrote:
> On Thu, Aug 24, 2017 at 04:37:49PM -0400, Roy Pledge wrote:
>> From: Claudiu Manoil
>>
>> Not relevant and arch dependent. Overkill for PPC.
>>
>> Signed-off-by: Claudiu Manoil
>> Signed-off-by: Roy Pledge
>> ---
>> drivers/soc/fsl/qbman/dpaa_sys.
On Fri, 2017-09-08 at 15:57 +0200, Borislav Petkov wrote:
> On Fri, Aug 18, 2017 at 05:27:52PM -0700, Ricardo Neri wrote:
> >
> > String instructions are special because, in protected mode, the
> > linear
> > address is always obtained via the ES segment register in operands
> > that
> > use the (
On Thu, Sep 14 2017 at 3:54:02 pm BST, Stafford Horne wrote:
> On Wed, Sep 13, 2017 at 06:21:39PM +0100, Marc Zyngier wrote:
[...]
>> > +{
>> > + unsigned int dst_cpu;
>> > + unsigned int src_cpu = smp_processor_id();
>> > +
>> > + for_each_cpu(dst_cpu, mask) {
>> > + set_bit(ipi_ms
On Wed, Sep 13, 2017 at 01:07:34PM -0500, Rob Herring wrote:
> On Fri, Sep 08, 2017 at 09:11:48AM +0200, Corentin Labbe wrote:
> > This patch restore dt-bindings documentation about dwmac-sun8i
> > This reverts commit 8aa33ec2f481 ("dt-bindings: net: Revert sun8i dwmac
> > binding")
>
> Why?
>
On Thu, Sep 07, 2017 at 11:36:08AM -0600, Tycho Andersen wrote:
> We need someting like this for testing XPFO. Since it's architecture
> specific, putting it in the test code is slightly awkward, so let's make it
> an arch-specific symbol and export it for use in LKDTM.
>
> v6: * add a definition
On Thu, Sep 14, 2017 at 02:30:17AM +0100, Al Viro wrote:
> On Wed, Sep 13, 2017 at 06:10:48PM -0700, Jaegeuk Kim wrote:
>
> > Android triggers umount(2) by init process, which is definitely not a kernel
> > thread. But, we've seen some kernel panics which say umount(2) was
> > succeeded,
> > but
On Thu, Sep 14, 2017 at 5:54 AM, Leon Romanovsky wrote:
> On Thu, Sep 14, 2017 at 01:06:18PM +0200, Arnd Bergmann wrote:
>> calling mlx5_fpga_mem_{read,write}_i2c() with a zero length on
>> older compiler version such as gcc-4.6 results in a warning that
>> the return code is not initialized:
>>
>
Bhumika Goyal wrote:
> Make this const as it not modified anywhere. It is only used during a
> copy operation. Also, add const to the declaration in header.
>
> Signed-off-by: Bhumika Goyal
Acked-by: Clemens Ladisch
> ---
> sound/pci/oxygen/xonar_dg.h | 2 +-
> sound/pci/oxygen/xonar_dg_
On Wed, Sep 13, 2017 at 10:39:20PM -0700, Nicolin Chen wrote:
> The driver also supports 2_BYTES and 1_BYTE in sdma_prep_slave_sg().
> So this patch just adds them to the lists.
>
> Signed-off-by: Nicolin Chen
Please ignore this one as I just found the "directions" is also
wrong. Sending a v2..
On Mon, Sep 11, 2017 at 12:00:21PM +0200, Thiebaud Weksteen wrote:
> With TPM 2.0 specification, the event logs may only be accessible by
> calling an EFI Boot Service. Modify the EFI stub to copy the log area to
> a new Linux-specific EFI configuration table so it remains accessible
> once booted.
On Thu, Sep 14, 2017 at 11:28:30AM -0700, Linus Torvalds wrote:
> On Thu, Sep 14, 2017 at 10:33 AM, Josh Poimboeuf wrote:
> >>
> >> a) uglifying the 15 or so relevant inline asm locations with ifdefs; or
> >
> > Actually I guess we could put the "sp" in a macro... I'll try it.
>
> Exactly. Do s
The driver already supports DMA_DEV_TO_DEV in sdma_config(),
DMA_SLAVE_BUSWIDTH_2_BYTES and DMA_SLAVE_BUSWIDTH_1_BYTE in
sdma_prep_slave_sg(). So this patch adds them to the lists.
Signed-off-by: Nicolin Chen
---
drivers/dma/imx-sdma.c | 14 +++---
1 file changed, 11 insertions(+), 3 del
ACPI 6.2 adds a new table, which describes how processing units
are related to each other in tree like fashion. Caches are
also sprinkled throughout the tree and describe the properties
of the caches in relation to other caches and processing units.
Add the code to parse the cache hierarchy and re
ACPI 6.2 adds a new table, which describes how processing units
are related to each other in tree like fashion. Caches are
also sprinkled throughout the tree and describe the properties
of the caches in relation to other caches and processing units.
Add the code to parse the cache hierarchy and re
On Mon, Sep 11, 2017 at 12:00:22PM +0200, Thiebaud Weksteen wrote:
> If we are not able to retrieve the TPM event logs from the ACPI table,
> check the EFI configuration table (Linux-specific GUID).
>
> The format version of the log may be returned by the function. If not
> specified (by previous
On Thu, Sep 14, 2017 at 11:43 AM, Jarkko Sakkinen
wrote:
> On Mon, Sep 11, 2017 at 12:00:21PM +0200, Thiebaud Weksteen wrote:
>> With TPM 2.0 specification, the event logs may only be accessible by
>> calling an EFI Boot Service. Modify the EFI stub to copy the log area to
>> a new Linux-specific
On Mon, Sep 11, 2017 at 09:12:18AM -0700, Ryan Lee wrote:
> Signed-off-by: Ryan Lee
> ---
Please make an effort to write changelogs that clearly describe the
change you're making. This is doing way more than just implementing DSP
mode, it's also adding a fairly complicated set_tdm_slot() impleme
Hi Anthony,
On Thu, Sep 14, 2017 at 01:36:44PM +0900, Anthony Kim wrote:
> The HiDeep touchscreen device is a capacitive multi-touch controller
> mainly for multi-touch supported devices use. It use I2C interface for
> communication to IC and provide axis X, Y, Z locations for ten finger
> touch t
On Wed, Sep 13, 2017 at 01:20:04PM -0500, Rob Herring wrote:
> On Fri, Sep 08, 2017 at 09:43:25AM +0200, Corentin Labbe wrote:
> > On Fri, Sep 08, 2017 at 09:25:38AM +0200, Maxime Ripard wrote:
> > > On Fri, Sep 08, 2017 at 09:11:51AM +0200, Corentin Labbe wrote:
> > > > This patch add documentatio
From: Colin Ian King
pio is initialized and the data is never read, instead it is almost
immediately being updated to a new value. Fix this by removing the
initialization.
Detected by scan-build:
"warning: Value stored to 'pio' during its initialization is never read"
Fixes: 669a5db411d8 ("[lib
On Thu, Sep 14, 2017 at 5:51 PM, Levin, Alexander (Sasha Levin)
wrote:
> From: Marcin Nowakowski
>
> [ Upstream commit 73fbc1eba7ffa3bf0ad12486232a8a1edb4e4411 ]
>
> When a memory offset is specified through the commandline, add the
> memory in range PHYS_OFFSET:Y as reserved memory area.
> Other
From: Jérôme Glisse
Fix for 4.14, zone device page always have an elevated refcount
of one and thus page count sanity check in uncharge_page() is
inappropriate for them.
Signed-off-by: Jérôme Glisse
Reported-by: Evgeny Baskakov
Cc: Andrew Morton
Cc: Johannes Weiner
Cc: Michal Hocko
Cc: Vlad
On Thu, Sep 14, 2017 at 11:48:54AM -0700, Matthew Garrett wrote:
> On Thu, Sep 14, 2017 at 11:43 AM, Jarkko Sakkinen
> wrote:
> > On Mon, Sep 11, 2017 at 12:00:21PM +0200, Thiebaud Weksteen wrote:
> >> With TPM 2.0 specification, the event logs may only be accessible by
> >> calling an EFI Boot Se
v2: implement the improvements suggested by Colm, and add
Colm's text to the fork.2 man page
(Colm, I have added a signed-off-by in your name - is that ok?)
Add MADV_WIPEONFORK and MADV_KEEPONFORK documentation to
madvise.2. The new functionality was recently merged by
Linus, and should b
On 9/14/2017 10:00 AM, Catalin Marinas wrote:
> On Thu, Aug 24, 2017 at 04:37:51PM -0400, Roy Pledge wrote:
>> diff --git a/drivers/soc/fsl/qbman/bman.c b/drivers/soc/fsl/qbman/bman.c
>> index ff8998f..e31c843 100644
>> --- a/drivers/soc/fsl/qbman/bman.c
>> +++ b/drivers/soc/fsl/qbman/bman.c
>> @@
On Thu, Sep 14, 2017 at 12:05 PM, Rik van Riel wrote:
> v2: implement the improvements suggested by Colm, and add
> Colm's text to the fork.2 man page
> (Colm, I have added a signed-off-by in your name - is that ok?)
Yep, that's ok! Whole thing LGTM.
--
Colm
On Thu, Sep 14, 2017 at 08:59:05PM +0200, Mathieu Malaterre wrote:
>On Thu, Sep 14, 2017 at 5:51 PM, Levin, Alexander (Sasha Levin)
> wrote:
>> From: Marcin Nowakowski
>>
>> [ Upstream commit 73fbc1eba7ffa3bf0ad12486232a8a1edb4e4411 ]
>>
>> When a memory offset is specified through the commandline
On 09/14, Al Viro wrote:
> On Thu, Sep 14, 2017 at 02:30:17AM +0100, Al Viro wrote:
> > On Wed, Sep 13, 2017 at 06:10:48PM -0700, Jaegeuk Kim wrote:
> >
> > > Android triggers umount(2) by init process, which is definitely not a
> > > kernel
> > > thread. But, we've seen some kernel panics which
On Thu, Sep 14, 2017 at 9:11 PM, Levin, Alexander (Sasha Levin)
wrote:
> On Thu, Sep 14, 2017 at 08:59:05PM +0200, Mathieu Malaterre wrote:
>>On Thu, Sep 14, 2017 at 5:51 PM, Levin, Alexander (Sasha Levin)
>> wrote:
>>> From: Marcin Nowakowski
>>>
>>> [ Upstream commit 73fbc1eba7ffa3bf0ad12486232
On 09/14/2017 12:57 PM, Randy Dunlap wrote:
> On 09/14/17 06:26, Michael Kerrisk (man-pages) wrote:
>> Hello Joe,
>>
>> On 5 September 2017 at 16:44, Joe Lawrence wrote:
>>> While backporting Michael's "pipe: fix limit handling" [1] patchset to a
>>> distro-kernel, Mikulas noticed that current ups
> > Is the MDIO controller "allwinner,sun8i-h3-emac" or "snps,dwmac-mdio"?
> > If the latter, then I think the node is fine, but then the mux should be
> > a child node of it. IOW, the child of an MDIO controller should either
> > be a mux node or slave devices.
Hi Rob
Up until now, children o
On Thu, Sep 14 2017 at 1:15:14 pm BST, zijun_hu wrote:
> From: zijun_hu
>
> get_cpu_number() doesn't use existing helper to iterate over possible
> CPUs, so error happens in case of discontinuous @cpu_possible_mask
> such as 0b0001.
Do you have an example of such a situation? Your patch is
From: Petr Vandrovec
Binutils 2.29-9 in Debian return an error when elf_getdata is invoked
on empty section (.note.GNU-stack in all kernel files), causing
immediate failure of kernel build with:
elf_getdata: can't manipulate null section
As nothing is done with sections that have zero size, jus
On Wed, Sep 13, 2017 at 6:38 PM, wrote:
Hi Matthew,
>
> Hi Alan,
>
> Two minor nits below.
>
> Matthew Gerlach
>
> On Wed, 13 Sep 2017, Alan Tull wrote:
>
>> Add two functions for getting the FPGA bridge from the device
>> rather than device tree node. This is to enable writing code
>> that wi
Quoting Colin King (2017-09-14 17:21:54)
> From: Colin Ian King
>
> hw_check is being assigned and updated but is no longer being read,
> hence it is redundant and can be removed.
>
> Detected by clang scan-build:
> "warning: Value stored to 'hw_check' during its initialization
> is never read"
From: Yogesh Siraswar
On am438x EPOS boards there is only one ethernet port, remove extra
port definition.
This boot log warnings during PHY detection.
Signed-off-by: Yogesh Siraswar
Signed-off-by: Andrew F. Davis
---
arch/arm/boot/dts/am43x-epos-evm.dts | 6 +-
1 file changed, 1 inserti
Add event names so that common events can be
specified symbolically, for example:
l2cache_0/total-reads/,l2cache_0/cycles/
Event names are displayed in 'perf list'.
Signed-off-by: Neil Leeder
---
drivers/perf/qcom_l2_pmu.c | 54 ++
1 file changed, 54
Hi David and Pavel,
On 09/13/2017 10:20 PM, Pavel Machek wrote:
> Hi!
>
>> These patch series add the LED_BRIGHTNESS_FAST flag support for
>> ledtrig-transient to use hrtimer so that platforms with high-resolution timer
>> support can have better accuracy in the trigger duration timing. The need
On Thu, Sep 14, 2017 at 4:50 AM, Wu Hao wrote:
Hi Hao,
> On Thu, Sep 14, 2017 at 04:48:34AM +0800, Alan Tull wrote:
>> * Create fpga-region.h.
>> * Export fpga_region_program_fpga.
>> * Move struct fpga_region and other things to the header.
>>
>> This is a step in separating FPGA region common
On Thu, Sep 14, 2017 at 12:31 PM, Jacek Anaszewski
wrote:
> I would change one more thing in this patch, though. The hr_timer engine
> should be made optional and not used by default for fast LEDs.
> It could be made configurable by exposing additional sysfs file from
> ledtrig-transient.c, e.g. h
On Wed, Sep 13, 2017 at 4:49 PM, Oleg Nesterov wrote:
> IOW, why do we want to silently ignore the upper bits in $rax ?
By the way, they are ignored elsewhere, in audit[1] or seccomp[2], for example.
[1] include/linux/audit.h
[2] include/uapi/linux/seccomp.h, definition of struct seccomp_data
-
Hi!
> > > > NAK.
> > > >
> > > > LEDs do not need extra overhead, and vibrator control should not go
> > > > through LED subsystem.
> > > >
> > > > Input subsystem includes support for vibrations and force
> > > > feedback. Please use that instead.
> > >
> > > I thought we are already over this di
Hi Nicolin,
On Thu, Sep 14, 2017 at 3:46 PM, Nicolin Chen wrote:
> The driver already supports DMA_DEV_TO_DEV in sdma_config(),
> DMA_SLAVE_BUSWIDTH_2_BYTES and DMA_SLAVE_BUSWIDTH_1_BYTE in
> sdma_prep_slave_sg(). So this patch adds them to the lists.
>
> Signed-off-by: Nicolin Chen
Patch looks
Hi David,
Thanks for the patch.
On 09/13/2017 07:53 PM, David Lin wrote:
> This is for readability as well as to avoid checkpatch warnings when
> adding new bit flag information in the future.
>
> Signed-off-by: David Lin
> ---
> include/linux/leds.h | 18 +-
> 1 file changed,
Hi Linus, please consider pulling:
git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm
tags/map-shared-validate-for-4.14
...for 4.14 as a pre-requisite for the proposed mmap flags (MAP_SYNC
and MAP_DIRECT) being developed for 4.15 consideration. As I
highlighted in the last posting [1]
Adds a new domain property for iommu clients to opt-in to stalling
with asynchronous resume, and for the client to determine if the
iommu supports this.
Current motivation is that:
a) On 8x96/a530, if we don't enable CFCFG (or HUPCF) then non-
faulting translations which are happening concurre
On 07/27/2017 03:05 AM, yinbo@nxp.com wrote:
> From: Rajesh Bhagat
>
> Add USB EHCI support for ls1012aqds platform
>
> Signed-off-by: Rajat Srivastava
> Signed-off-by: Rajesh Bhagat
> Signed-off-by: yinbo.zhu
> ---
> arch/arm/include/asm/arch-fsl-layerscape/immap_lsch2.h | 1 +
> incl
On 09/14/2017 12:54 PM, York Sun wrote:
> On 07/27/2017 03:05 AM, yinbo@nxp.com wrote:
>> From: Rajesh Bhagat
>>
>> +#elif defined(CONFIG_LS102XA) || defined(CONFIG_ARCH_LS1012A)
>
> Please use CONFIG_ARCH_LS1021A, not CONFIG_LS102XA.
>
Never mind. This is merged. I will send a patch to
debugfs here is very very useful to read registers directly and
compare what use space tools see. Cool feature to get regs by port and
use standard tools to diff and print them. Even might be better to
allow drivers to decode register names and bits values. Once that is
done driver mainaince will b
On Wed, Sep 13, 2017 at 11:46 PM, Miklos Szeredi wrote:
>
> d_real() is currently is *the* overlayfs-op:
I know. And it's ugly as #%^! hell.
We don't want to make it uglier.
And honestly, if you think that "it's only for overlayfs, so I can do
anything I damn well want to this p[iece of shit"
On Thu, Sep 14, 2017 at 4:56 AM, Wu Hao wrote:
> On Thu, Sep 14, 2017 at 04:48:36AM +0800, Alan Tull wrote:
>> Another step in separating common code from device tree specific
>> code for FPGA regions.
>>
>> * add FPGA region register/unregister functions.
>> * add the register/unregister function
On 09/14/2017 09:38 PM, David Lin wrote:
> On Thu, Sep 14, 2017 at 12:31 PM, Jacek Anaszewski
> wrote:
>> I would change one more thing in this patch, though. The hr_timer engine
>> should be made optional and not used by default for fast LEDs.
>> It could be made configurable by exposing addition
On Thu, 14 Sep 2017, Michal Hocko wrote:
> > It is certainly possible to add oom priorities on top before it is merged,
> > but I don't see why it isn't part of the patchset.
>
> Because the semantic of the priority for non-leaf memcgs is not fully
> clear and I would rather have the core of the
Hi Arnaldo,
I found some more missing brackets with metrics. Now I fixed it all with a
script.
This replaces the earlier patch to only fix up ILP, and fixes other
metrics too.
Please pull the metrics updates. It's on top of current acme perf/core
The following changes since commit f94843e827787
On Thu, Sep 14, 2017 at 10:00 PM, Linus Torvalds
wrote:
> If you can't bother to try to make it act as a proper VFS thing, then
> I don't want to see patches from you to the VFS code.
I was saying that it's a bad idea to mix external and internal flags.
That was the reason the two were separated
On Thu, Sep 14, 2017 at 12:59 PM, Maxim Uvarov wrote:
> debugfs here is very very useful to read registers directly and
> compare what use space tools see. Cool feature to get regs by port and
> use standard tools to diff and print them. Even might be better to
> allow drivers to decode register n
On Thu, 14 Sep 2017 14:22:25 -0400 Sherry Yang wrote:
> Drop the global lru lock in isolate callback
> before calling zap_page_range which calls
> cond_resched, and re-acquire the global lru
> lock before returning. Also change return
> code to LRU_REMOVED_RETRY.
>
> Use mmput_async when fail to
401 - 500 of 688 matches
Mail list logo
