The purpose of this series is to fix the integration of the ethernet phy
property "eee-broken-modes" [0]
The v3 of this series has been merged, missing a fix (error reported by
kbuild robot) available in the v4 [1]
More importantly, Florian opposed adding a DT property mapping a device
register t
Tested-by: Niklas Cassel
On 12/18/2016 09:38 PM, Pavel Machek wrote:
> Fix up memory barriers in stmmac driver. They are meant to protect
> against DMA engine, so smp_ variants are certainly wrong, and dma_
> variants are preferable.
>
> Signed-off-by: Pavel Machek
>
> diff --git a/drivers/
Hi all,
this series of patches is based on the git://github.com/spi-nor/linux.git
tree. It has been extracted from the SFDP series and is resent as
a standalone series.
This series fixes compatibility issue between Linux and many bootloaders
when using SPI flash with size greater than 128Mib.
In
The patches regarding eee-broken-modes was merged before all people
involved could find an agreement on the best way to move forward.
While we agreed on having a DT property to mark particular modes as broken,
the value used for eee-broken-modes mapped the phy register in very direct
way. Because
In genphy_config_eee_advert, the return value of phy_read_mmd_indirect is
checked to know if the register could be accessed but the result is
assigned to a 'u32'.
Changing to 'int' to correctly get errors from phy_read_mmd_indirect.
Fixes: d853d145ea3e ("net: phy: add an option to disable EEE adve
This patch provides an alternative mean to support memory above 16MiB
(128Mib) by replacing 3byte address op codes by their associated 4byte
address versions.
Using the dedicated 4byte address op codes doesn't change the internal
state of the SPI NOR memory as opposed to using other means such as
This patch renames the SPINOR_OP_* macros of the 4-byte address
instruction set so the new names all share a common pattern: the 4-byte
address name is built from the 3-byte address name appending the "_4B"
suffix.
The patch also introduces new op codes to support other SPI protocols such
as SPI 1
The patches regarding eee-broken-modes was merged before all people
involved could find an agreement on the best way to move forward.
While we agreed on having a DT property to mark particular modes as broken,
the value used for eee-broken-modes mapped the phy register in very direct
way. Because
To make the code clearer, use rb_entry() instead of container_of() to
deal with rbtree.
Signed-off-by: Geliang Tang
---
kernel/trace/trace_stat.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/trace/trace_stat.c b/kernel/trace/trace_stat.c
index 413ff10..0765150 1
To make the code clearer, use rb_entry() instead of container_of() to
deal with rbtree.
Signed-off-by: Geliang Tang
---
kernel/power/swap.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/power/swap.c b/kernel/power/swap.c
index 32e0c23..f80fd33 100644
--- a/kernel/pow
[+cc linux-pci, Linas]
On Mon, Dec 19, 2016 at 03:23:56PM +0800, Cao jin wrote:
> In AER recovery, pci_error_handlers.link_reset() is never called,
> drop it now.
I think it's true that .link_reset() is never called. If that's the
case, why not remove it completely, i.e., remove it from struct
p
On 19/12/2016 14:05, Denis Plotnikov wrote:
>>
> This new patch-set does avoid unnecessary interrupt re-injections -
> checked.
>
> The test (MS Windows, sending messages between multiple windows using
> windows-specific interface),
> which showed performance growth with "[PATCH v2] KVM: x86: av
On Fri, Dec 16, 2016 at 02:30:35PM -0800, David Matlack wrote:
> Modules that use static_key_deferred need a way to synchronize with
> any delayed work that is still pending when the module is unloaded.
> Introduce static_key_deferred_flush() which flushes any pending
> jump label updates.
Makes s
Am 16.12.2016 um 18:07 schrieb Radim Krčmář:
2016-12-16 17:53+0100, Paolo Bonzini:
On 16/12/2016 17:41, David Hildenbrand wrote:
Just to verify:
The GET_APIC_DEST_FIELD(mda) == APIC_BROADCAST is still correct in
kvm_apic_broadcast() ?
No, it seems wrong.
Definitely, sending v4 of this pat
To make the code clearer, use rb_entry() instead of container_of() to
deal with rbtree.
Signed-off-by: Geliang Tang
---
fs/overlayfs/readdir.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/overlayfs/readdir.c b/fs/overlayfs/readdir.c
index f241b4e..401bdc4 100644
--- a/f
Commit 008a2ebcd677 ("ARM: dts: omap3: Remove skeleton.dtsi usage")
removed the skeleton.dtsi usage since we want to get rid of it.
But this can cause issues when booting a kernel with a boot-loader
that doesn't create a chosen node if this isn't present in the DTB
since the decompressor relies on
To make the code clearer, use rb_entry() instead of container_of() to
deal with rbtree.
Signed-off-by: Geliang Tang
---
drivers/gpu/drm/i915/i915_debugfs.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/i915/i915_debugfs.c
b/drivers/gpu/drm/i915/i915_d
To make the code clearer, use rb_entry() instead of container_of() to
deal with rbtree.
Signed-off-by: Geliang Tang
---
fs/btrfs/ctree.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/fs/btrfs/ctree.c b/fs/btrfs/ctree.c
index a426dc8..146b2dc 100644
--- a/fs/btrfs/ct
Hi Arnaldo,
Ping
Are you OK with the fix?
Thanks,
Kan
>
> From: Kan Liang
>
> Fixes a perf diff regression issue which was introduced by commit
> 5baecbcd9c9a ("perf symbols: we can now read separate debug-info files
> based on a build ID")
>
> The binary name could be same when perf diff d
Commit 55871eb6e2cc ("ARM: dts: dra7: Remove skeleton.dtsi usage")
removed the skeleton.dtsi usage since we want to get rid of it.
But this can cause issues when booting a kernel with a boot-loader
that doesn't create a chosen node if this isn't present in the DTB
since the decompressor relies on
Commit 06bfb9c19957 ("ARM: dts: dm816x: Remove skeleton.dtsi usage")
removed the skeleton.dtsi usage since we want to get rid of it.
But this can cause issues when booting a kernel with a boot-loader
that doesn't create a chosen node if this isn't present in the DTB
since the decompressor relies o
Commit 76155b378c59 ("ARM: dts: dm814x: Remove skeleton.dtsi usage")
removed the skeleton.dtsi usage since we want to get rid of it.
But this can cause issues when booting a kernel with a boot-loader
that doesn't create a chosen node if this isn't present in the DTB
since the decompressor relies o
The purpose of USB Type-C connector class is to provide
unified interface for the user space to get the status and
basic information about USB Type-C connectors on a system,
control over data role swapping, and when the port supports
USB Power Delivery, also control over power role swapping
and Alt
Commit 75813028bbd7 ("ARM: dts: am4372: Remove skeleton.dtsi usage")
removed the skeleton.dtsi usage since we want to get rid of it.
But this can cause issues when booting a kernel with a boot-loader
that doesn't create a chosen node if this isn't present in the DTB
since the decompressor relies o
Commit f8bf01611c99 ("ARM: dts: am33xx: Remove skeleton.dtsi usage")
removed the skeleton.dtsi usage since we want to get rid of it.
But this can cause issues when booting a kernel with a boot-loader
that doesn't create a chosen node if this isn't present in the DTB
since the decompressor relies o
To make the code clearer, use rb_entry() instead of container_of() to
deal with rbtree.
Signed-off-by: Geliang Tang
---
drivers/iommu/iova.c | 23 +++
1 file changed, 11 insertions(+), 12 deletions(-)
diff --git a/drivers/iommu/iova.c b/drivers/iommu/iova.c
index 080beca..b7
Commit d1f3156fc8c7 ("ARM: dts: omap2: Remove skeleton.dtsi usage")
removed the skeleton.dtsi usage since we want to get rid of it.
But this can cause issues when booting a kernel with a boot-loader
that doesn't create a chosen node if this isn't present in the DTB
since the decompressor relies on
Commit 76a8548ea987 ("ARM: dts: omap5: Remove skeleton.dtsi usage")
removed the skeleton.dtsi usage since we want to get rid of it.
But this can cause issues when booting a kernel with a boot-loader
that doesn't create a chosen node if this isn't present in the DTB
since the decompressor relies on
Commit da6269e7e3dd ("ARM: dts: omap4: Remove skeleton.dtsi usage")
removed the skeleton.dtsi usage since we want to get rid of it.
But this can cause issues when booting a kernel with a boot-loader
that doesn't create a chosen node if this isn't present in the DTB
since the decompressor relies on
Hello Tony,
As discussed in [0], there's a regression when booting a kernel with a DTB
that doesn't have a pre-existing chosen node. This is usually not an issue
for most boards since u-boot creates an empty chosen node if isn't present
in the DTB.
But it can be an issue for others bootloaders as
Revision 2 of LCDC suffers from an issue where a SYNC_LOST error
caused by limited memory bandwidth may leave the picture shifted a
couple pixels to the right.
This issue has not been observed on revision 1, while the recovery
mechanism introduces a different issue, where the END_OF_FRAME
interrup
On Mon, Dec 19, 2016 at 02:57:00PM +0100, Geert Uytterhoeven wrote:
> Hi Konrad,
>
> On Mon, Dec 19, 2016 at 2:38 PM, Konrad Rzeszutek Wilk
> wrote:
> > On Fri, Dec 16, 2016 at 02:28:42PM +0100, Geert Uytterhoeven wrote:
> >> On architectures like arm64, swiotlb is tied intimately to the core
> >
On Sat, 17 Dec 2016, Konstantin Khlebnikov wrote:
> I've found some minor problems, this patch fixes:
>
> * save cmd_ld_ko_o into .module.cmd, if_changed_rule doesn't do that
> * fix bashisms for debian where /bin/sh is a symlink to /bin/dash
> * rename rule_link_module to rule_ld_ko_o, otherwise
On 19/12/2016 15:06, Icenowy Zheng wrote:
>
>
> 19.12.2016, 16:54, "Chen-Yu Tsai" :
>> On Mon, Dec 19, 2016 at 4:46 PM, Maxime Ripard
>> wrote:
>>> On Fri, Dec 16, 2016 at 02:27:54AM +0800, Icenowy Zheng wrote:
An operating point table is needed for the cpu frequency adjusting to
wo
On Sat, Nov 05, 2016 at 12:04:45AM -0400, Chris Metcalf wrote:
> A bunch of people got together this week at the Linux Plumbers
> Conference to discuss nohz_full, task isolation, and related stuff.
> (Thanks to Thomas for getting everyone gathered at one place and time!)
Which reminds me...
One s
To make the code clearer, use rb_entry() instead of container_of() to
deal with rbtree.
Signed-off-by: Geliang Tang
---
drivers/base/regmap/regcache-rbtree.c | 7 +++
drivers/base/regmap/regmap.c | 4 ++--
2 files changed, 5 insertions(+), 6 deletions(-)
diff --git a/drivers/base/r
On 19/12/2016 14:56, Pan Xinhui wrote:
> hi, Andrea
> thanks for your reply. :)
>
> 在 2016/12/19 19:42, Andrea Arcangeli 写道:
>> Hello,
>>
>> On Wed, Nov 02, 2016 at 05:08:35AM -0400, Pan Xinhui wrote:
>>> Support the vcpu_is_preempted() functionality under KVM. This will
>>> enhance lock per
# Some open questions about this patch below.
#
One of the rules regarding capabilities is:
A process that resides in the parent of the user namespace and
whose effective user ID matches the owner of the namespace has
all capabilities in the namespace.
Therefore, in order to write cod
On Fri 16-12-16 17:15:56, Kirill A. Shutemov wrote:
> Logic on whether we can reap pages from the VMA should match what we
> have in madvise_dontneed(). In particular, we should skip, VM_PFNMAP
> VMAs, but we don't now.
>
> Let's just call madvise_dontneed() from __oom_reap_task_mm(), so we
> won'
Linux 4.9 added two ioctl() operations that can be used to discover:
* the parental relationships for hierarchical namespaces (user and PID)
[NS_GET_PARENT]
* the user namespaces that owns a specified non-user-namespace
[NS_GET_USERNS]
For no good reason that I can glean, NS_GET_USERNS was ma
Eric,
The code proposed in this patch series is pretty small. Is there any
chance we could make the 4.10 merge window, if the changes seem
acceptable to you?
I would like to write code that can answer the question: "what
capabilities does process X have in namespace Y"? (where Y is defined by
a f
Added comments before memory barrier
Signed-off-by: Devendra Sharma
---
drivers/staging/comedi/drivers/dyna_pci10xx.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/staging/comedi/drivers/dyna_pci10xx.c
b/drivers/staging/comedi/drivers/dyna_pci10xx.c
index c9eb26f..c3b5236 10064
On Fri 16-12-16 17:15:55, Kirill A. Shutemov wrote:
> There's no users of zap_page_range() who wants non-NULL 'details'.
> Let's drop it.
>
> Signed-off-by: Kirill A. Shutemov
kbuild robot has noticed that you should remove doc part as well
* @details: details of shared cache invalidation
then
To make the code clearer, use rb_entry() instead of container_of() to
deal with rbtree.
Signed-off-by: Geliang Tang
---
arch/x86/mm/pat_rbtree.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/arch/x86/mm/pat_rbtree.c b/arch/x86/mm/pat_rbtree.c
index 159b52c..d76
On Mon, Dec 19, 2016 at 10:08 PM, Icenowy Zheng wrote:
>
>
> 19.12.2016, 18:09, "Maxime Ripard" :
>> On Fri, Dec 16, 2016 at 10:40:00PM +0800, Icenowy Zheng wrote:
>>> >> > > &r_pio {
>>> >> > > wifi_pwrseq_pin_q8: wifi_pwrseq_pin@0 {
>>> >> > > - pins = "PL6", "PL7", "PL11";
>>> >> > >
On Fri 16-12-16 17:15:54, Kirill A. Shutemov wrote:
> detail == NULL would give the same functionality as
> .check_swap_entries==true.
Yes, now that check_swap_entries is the only used flag from there we can
safely rely on detail == NULL check.
> Signed-off-by: Kirill A. Shutemov
Acked-by: Mich
Since do_IRQ is now invoked on a separate IRQ stack, we select
HAVE_IRQ_EXIT_ON_IRQ_STACK so that softirq's may be invoked directly
from irq_exit(), rather than requiring do_softirq_own_stack.
Signed-off-by: Matt Redfearn
---
Changes in v3: None
Changes in v2: None
arch/mips/Kconfig | 1 +
1 f
2016-12-16 14:30-0800, David Matlack:
> KVM's lapic emulation uses static_key_deferred (apic_{hw,sw}_disabled).
> These are implemented with delayed_work structs which can still be
> pending when the KVM module is unloaded. We've seen this cause kernel
> panics when the kvm_intel module is quickly
Hi,
On 19/12/2016 15:06, Icenowy Zheng wrote:
>
> After proper testing of A23 ccu, the operating points can also apply to A23.
> (According to A23 devices' fex)
>
I disagree. I've looked into using the same operating points for A23 and
A33 for CPUfreq and I came to the conclusion that not all A
Within unwind stack, check if the stack pointer being unwound is within
the CPU's irq_stack and if so use that page rather than the task's stack
page.
Signed-off-by: Matt Redfearn
---
Changes in v3: None
Changes in v2: None
arch/mips/kernel/process.c | 15 ++-
1 file changed, 14 in
The SAVE_SOME macro is used to save the execution context on all
exceptions.
If an exception occurs while executing user code, the stack is switched
to the kernel's stack for the current task, and register $28 is switched
to point to the current_thread_info, which is at the bottom of the stack
regi
On Fri 16-12-16 17:15:53, Kirill A. Shutemov wrote:
> The only user of ignore_dirty is oom-reaper. But it doesn't really use
> it.
>
> ignore_dirty only has effect on file pages mapped with dirty pte.
> But oom-repear skips shared VMAs, so there's no way we can dirty file
> pte in them.
Hmm, I am
When enterring interrupt context via handle_int or except_vec_vi, switch
to the irq_stack of the current CPU if it is not already in use.
The current stack pointer is masked with the thread size and compared to
the base or the irq stack. If it does not match then the stack pointer
is set to the to
This series adds a separate stack for each CPU wihin the system to use
when handling IRQs. Previously IRQs were handled on the kernel stack of
the current task. If that task was deep down a call stack at the point
of the interrupt, and handling the interrupt required a deep IRQ stack,
then there w
Allocate a per-cpu irq stack for use within interrupt handlers.
Also add a utility function on_irq_stack to determine if a given stack
pointer is within the irq stack for that cpu.
Signed-off-by: Matt Redfearn
---
Changes in v3: None
Changes in v2: None
arch/mips/include/asm/irq.h| 12 ++
2016-12-19 14:09 GMT+01:00 Jyri Sarha :
> One comment bellow.
>
> On 12/13/16 17:07, Bartosz Golaszewski wrote:
>> Revision 2 of LCDC suffers from an issue where a SYNC_LOST error
>> caused by limited memory bandwidth may leave the picture shifted a
>> couple pixels to the right.
>>
>> This issue h
Hi,
Some of my AMD servers often reported "L3 ECC error and L2 cache error".
I thought I could generated the errors if I set the machines on the heavy load.
So I ran stress-ng tool with various options but system did not generate any
error.
I wanted to check the stress-ng tool really generate
On 19/12/16 13:29, Chris Wilson wrote:
> On Mon, Dec 19, 2016 at 12:39:16PM +0100, Juergen Gross wrote:
>> With recent 4.10 kernel the graphics isn't coming up under Xen. First
>> failure message is:
>>
>> [ 46.656649] i915 :00:02.0: swiotlb buffer is full (sz: 1630208 bytes)
>
> Do we get a
From: George Spelvin
> Sent: 17 December 2016 15:21
...
> uint32_t
> hsiphash24(char const *in, size_t len, uint32_t const key[2])
> {
> uint32_t c = key[0];
> uint32_t d = key[1];
> uint32_t a = 0x6c796765 ^ 0x736f6d65;
> uint32_t b = d ^ 0x74656462 ^ 0x646f7261;
I've
On 12/18/2016 03:44 AM, Ingo Molnar wrote:
> * Boris Ostrovsky wrote:
>
>> On 12/08/2016 11:33 PM, Ingo Molnar wrote:
>>> * Boris Ostrovsky wrote:
>>>
The new Xen PVH entry point requires page tables to be setup by the
kernel since it is entered with paging disabled.
Pull the
Signed-off-by: Geert Uytterhoeven
---
Compile-tested only.
The extra assignment of 0 to err could be avoided:
do {
if (!(card->quirks & MMC_QUIRK_INAND_CMD38) ||
!(err = mmc_switch(card, EXT_CSD_CMD_SET_NORMAL,
IN
With gcc-4.1.2:
mmc/core/block.c: In function ‘mmc_blk_issue_discard_rq’:
mmc/core/block.c:1150: warning: ‘arg’ may be used uninitialized in this
function
mmc/core/block.c:1150: warning: ‘nr’ may be used uninitialized in this
function
mmc/core/block.c:1150: warning: ‘from’ may be
On Mon 19-12-16 11:27:59, Petr Mladek wrote:
> On Mon 2016-12-19 09:12:10, Michal Hocko wrote:
> > On Mon 19-12-16 16:32:28, Sergey Senozhatsky wrote:
> > [...]
> > > as far as I can tell, now for_each_populated_zone() iterations are
> > > split by non-CONT printk() from show_zone_node(), which pre
On Mon, Dec 19, 2016 at 02:50:25PM +0100, Martin Steigerwald wrote:
> Am Montag, 19. Dezember 2016, 14:19:11 CET schrieb Peter Zijlstra:
> > On Mon, Dec 19, 2016 at 01:06:00PM +0100, Martin Steigerwald wrote:
> > > Hello Ingo, Peter, Nicolas, Andrew, Balbir, Shailabh, Jay, Gerlof and
> > > Marc,
>
On Mon 19-12-16 20:39:24, Tetsuo Handa wrote:
> On 2016/12/16 23:15, Kirill A. Shutemov wrote:
> > Logic on whether we can reap pages from the VMA should match what we
> > have in madvise_dontneed(). In particular, we should skip, VM_PFNMAP
> > VMAs, but we don't now.
> >
> > Let's just call madvi
Hi Konrad,
On Mon, Dec 19, 2016 at 2:38 PM, Konrad Rzeszutek Wilk
wrote:
> On Fri, Dec 16, 2016 at 02:28:42PM +0100, Geert Uytterhoeven wrote:
>> On architectures like arm64, swiotlb is tied intimately to the core
>> architecture DMA support. In addition, ZONE_DMA cannot be disabled.
>>
>> To aid
hi, Andrea
thanks for your reply. :)
在 2016/12/19 19:42, Andrea Arcangeli 写道:
Hello,
On Wed, Nov 02, 2016 at 05:08:35AM -0400, Pan Xinhui wrote:
Support the vcpu_is_preempted() functionality under KVM. This will
enhance lock performance on overcommitted hosts (more runnable vcpus
than
On Sun, Dec 18, 2016 at 10:20:53PM -0600, Jiandi An wrote:
> crb_check_resource() in TPM CRB driver calls
> acpi_dev_resource_memory() which only handles 32-bit resources.
> Adding a call to acpi_dev_resource_address_space() in TPM CRB
> driver which handles 64-bit resources.
>
> Signed-off-by: Ji
Am Montag, 19. Dezember 2016, 14:19:11 CET schrieb Peter Zijlstra:
> On Mon, Dec 19, 2016 at 01:06:00PM +0100, Martin Steigerwald wrote:
> > Hello Ingo, Peter, Nicolas, Andrew, Balbir, Shailabh, Jay, Gerlof and
> > Marc,
> >
> > starting from a Debian bug report of mine, Gerlof Langeveld, develop
Hi,
On 12/19/2016 08:19 AM, Marion & Christophe JAILLET wrote:
> Hi,
>
> while playing with coccinelle, a missing 'of_node_put()' triggered in
> 'atlas7_pinmux_probe()', in file 'drivers/pinctrl/sirf/pinctrl-atlas7.c'.
>
> /* The sd3 and sd9 shared all pins, and the function select by
>
This is used by Dell Edge IoT Gateways.
Signed-off-by: Shrirang Bagul
---
sound/soc/intel/Kconfig | 13 +
sound/soc/intel/atom/sst/sst_acpi.c | 2 +
sound/soc/intel/boards/Makefile | 2 +
sound/soc/intel/boards/bytcr_rt5660.c | 573 ++
4
These patches add basic audio support on new Dell Edge IoT Gateways.
RT5660 codec is connected to SSP2 port on Intel Atom Baytrail E3815 SoC.
The machine driver is based on bytcr_rt5640. These devices have line-in and
line-out jacks with line-out mute enable gpio described in ACPI tables.
Shrirang
On Dell IoT Gateways, RT5660 codec is available with ACPI ID 10EC3277.
Also, GPIO's are only available by index, so we register mappings to allow
machine drivers to access them by name.
Signed-off-by: Shrirang Bagul
---
sound/soc/codecs/rt5660.c | 26 ++
1 file changed, 2
On Sat 17-12-16 22:06:47, Nils Holland wrote:
[...]
> Unfortunately, the reclaim trace messages stopped a while after the first
> OOM messages show up - most likely my "cat" had been killed at that
> point or became unresponsive. :-/
The later is more probable because I do not see the OOM killer t
Hi,
On Thursday, December 15, 2016 12:12:52 PM Andrew Morton wrote:
> On Thu, 8 Dec 2016 10:34:12 +0200 Tomi Valkeinen
> wrote:
>
> > Remove Tomi Valkeinen from fbdev maintainer and mark fbdev as orphan.
> >
> > ...
> >
> > I just don't have time to even pretend I maintain fbdev, so mark it a
On Wed, Nov 23, 2016 at 11:18:53PM +0800, Geliang Tang wrote:
> Drop duplicate header module.h from tpm_tis_spi.c.
>
> Signed-off-by: Geliang Tang
Reviewed-by: Jarkko Sakkinen
Applied.
/Jarkko
`
> ---
> drivers/char/tpm/tpm_tis_spi.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git
When building the XFS driver with clang, the compiler reports a
-Wformat-security warning in xlog_recover_validate_buf_type() because
xfs_warn() is being called with a non-literal string. Even though
variable warnmsg is always initialized as a constant string without any
'%' character, silent the w
On Thu, Dec 15, 2016 at 06:10:17PM +0100, Corentin Labbe wrote:
> tpm/st33zp24/st33zp24.c does not use any miscdevice so this patch remove
> this unnecessary inclusion.
>
> Signed-off-by: Corentin Labbe
Reviewed-by: Jarkko Sakkinen
Applied.
/Jarkko
> ---
> drivers/char/tpm/st33zp24/st33zp24
Hi,
On 12/16/2016 01:07 PM, Krzysztof Kozlowski wrote:
On Thu, Dec 15, 2016 at 04:52:58PM -0800, Doug Anderson wrote:
[ I added Arjun to Cc:, maybe he can help in explaining this issue
(unfortunately Inderpal's email is no longer working). ]
Please also note that on Exynos5422/5800 SoCs the
On 19.12.2016 12:47, Paolo Bonzini wrote:
This is the result of cleaning up the places that set REQ_EVENT unnecessarily.
The savings on self-IPI kvm-unit-tests are:
self_ipi_sti_nop~300 clock cycles
self_ipi_sti_hlt~300 clock cycles
self_ipi_tpr
On Fri, Dec 16, 2016 at 02:28:42PM +0100, Geert Uytterhoeven wrote:
> On architectures like arm64, swiotlb is tied intimately to the core
> architecture DMA support. In addition, ZONE_DMA cannot be disabled.
>
> To aid debugging and catch devices not supporting DMA to memory outside
> the 32-bit a
On Fri, 16 Dec 2016, Greg KH wrote:
> > You seem to be targeting a situation where the kernel memory can be
> > easily changed, but filesystem content cannot (if it could - the
> > attacker would simply replace /sbin/hotplug).
>
> Correct, like an embedded system with a read-only system partition
On Fri, Dec 16, 2016 at 02:28:39PM +0100, Geert Uytterhoeven wrote:
> Hi Konrad,
Heya!
>
> This patch series adds a kernel command line option to aid debugging
> when developing support for DMA to memory outside the 32-bit address
> space. If specified, trying to map memory that cannot be
On Mon, Dec 19, 2016 at 11:02:07AM +0100, Geert Uytterhoeven wrote:
> On Thu, Dec 15, 2016 at 6:53 PM, Mark Brown wrote:
> > On Mon, Sep 12, 2016 at 10:50:42PM +0200, Geert Uytterhoeven wrote:
> >> TBD:
> >> - s/spi_master/spi_controller/ where appropriate,
> >> - Provide wrappers (e.g. "#defi
__printf attributes help detecting issues in printf format strings at
compile time.
Even though imr_selftest.c is only compiled with
CONFIG_DEBUG_IMR_SELFTEST, gcc complains about a missing format
attribute when compiling allmodconfig with -Wmissing-format-attribute.
Silent this warning by adding
On Mon 19-12-16 11:05:49, Petr Mladek wrote:
> On Mon 2016-12-19 08:00:47, Vlastimil Babka wrote:
> > On 12/16/2016 01:32 PM, Michal Hocko wrote:
> > > From: Michal Hocko
> > >
> > > show_node currently only prints Node id while it is always followed by
> > > printing zone->name. As the node info
On Mon, Dec 19, 2016 at 01:06:00PM +0100, Martin Steigerwald wrote:
> Hello Ingo, Peter, Nicolas, Andrew, Balbir, Shailabh, Jay, Gerlof and Marc,
>
> starting from a Debian bug report of mine, Gerlof Langeveld, developer of
> system and process monitor atop¹, found two issues with process accoun
From: "Naveen N. Rao"
Introduce __PPC_SH64() as a 64-bit variant to encode shift field in some
of the shift and rotate instructions operating on double-words. Convert
some of the BPF instruction macros to use the same.
Signed-off-by: Naveen N. Rao
---
arch/powerpc/include/asm/ppc-opcode.h | 1
Hello Linus,
On Mon 19-12-16 10:34:42, Jan Kara wrote:
> could you please pull from
>
> git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.git for_linus
>
> to get changes to locking of some quota operations from dedicated quota mutex
> to s_umount semaphore, a fsnotify fix and a simp
From: "Naveen N. Rao"
To permit the use of relative branch instruction in powerpc, the target
address has to be relatively nearby, since the address is specified in an
immediate field (24 bit filed) in the instruction opcode itself. Here
nearby refers to 32MB on either side of the current inst
Detour buffer contains instructions to create an in memory pt_regs.
After the execution of the pre-handler, a call is made for instruction
emulation.
The NIP is determined in advanced through dummy instruction emulation and a
branch
instruction is created to the NIP at the end of the trampoline.
Kprobe placed on the kretprobe_trampoline during boot time can be
optimized, since the instruction at probe point is a 'nop'.
Signed-off-by: Anju T Sudhakar
Acked-by: Masami Hiramatsu
---
arch/powerpc/kernel/kprobes.c | 8
arch/powerpc/kernel/optprobes.c | 7 +++
2 files change
This is the V3 patchset of the kprobes jump optimization
(a.k.a OPTPROBES)for powerpc. Kprobe being an inevitable tool
for kernel developers, enhancing the performance of kprobe has
got much importance.
Currently kprobes inserts a trap instruction to probe a running kernel.
Jump optimization allow
On Mon, Dec 19, 2016 at 01:02:37PM +, James Hogan
wrote:
> Hi Matt,
>
> On Mon, Dec 19, 2016 at 12:04:54PM +, Matt Redfearn wrote:
> > On 19/12/16 02:07, Serge Semin wrote:
> > > It's useful to have some printed map of the kernel virtual memory,
> > > at least for debugging purpose.
> >
On Sun 18-12-16 13:32:29, Vegard Nossum wrote:
> Clarify documentation relating to mm_users and mm_count, and switch to
> kernel-doc syntax.
Looks good to me.
> Signed-off-by: Vegard Nossum
Acked-by: Michal Hocko
> ---
> include/linux/mm_types.h | 23 +--
> 1 file change
Hello,
On Sat, Dec 17, 2016 at 10:06:51PM +0100, Mickaël Salaün wrote:
> If I understand correctly, this patch is intended to add a delegation
> feature to cgroup v1, which does not really make sense for the v2
It's more about upstreaming a workaround for android somewhat like
including binder in
Hi,
On Friday, December 16, 2016 05:02:03 PM Kees Cook wrote:
> Prepare to mark sensitive kernel structures for randomization by making
> sure they're using designated initializers. These were identified during
> allyesconfig builds of x86, arm, and arm64, with most initializer fixes
> extracted
On Thu 2016-12-08 12:08:37, Josh Poimboeuf wrote:
> For the consistency model we'll need to know the sizes of the old and
> new functions to determine if they're on the stacks of any tasks.
>
> Signed-off-by: Josh Poimboeuf
Reviewed-by: Petr Mladek
Best Regards,
Petr
One comment bellow.
On 12/13/16 17:07, Bartosz Golaszewski wrote:
> Revision 2 of LCDC suffers from an issue where a SYNC_LOST error
> caused by limited memory bandwidth may leave the picture shifted a
> couple pixels to the right.
>
> This issue has not been observed on revision 1, while the rec
Hi Matt,
On Mon, Dec 19, 2016 at 12:04:54PM +, Matt Redfearn wrote:
> On 19/12/16 02:07, Serge Semin wrote:
> > It's useful to have some printed map of the kernel virtual memory,
> > at least for debugging purpose.
> >
> > Signed-off-by: Serge Semin
> > ---
> > @@ -106,6 +107,49 @@ static vo
401 - 500 of 671 matches
Mail list logo
