Since retpoline capable compilers are widely available, make
CONFIG_RETPOLINE hard depend on it.
Change KBUILD to use CONFIG_RETPOLINE_SUPPORT to avoid conflict with
CONFIG_RETPOLINE which is used by kernel.
With all that stuff, the check of RETPOLINE is changed to
CONFIG_RETPOLINE.
This change
Since CONFIG_RETPOLINE hard depends on compiler support now, so
replacing indirect-jump check with the range check is safe in that case.
Signed-off-by: Zhenzhong Duan
Cc: Thomas Gleixner
Cc: Peter Zijlstra
Cc: Borislav Petkov
Cc: David Woodhouse
Cc: H. Peter Anvin
Cc: Ingo Molnar
Cc: Konrad
On Fri, Oct 26, 2018 at 10:46:36AM +0200, Michal Hocko wrote:
> On Wed 22-08-18 10:00:25, Michal Hocko wrote:
> > On Wed 22-08-18 01:37:48, Naoya Horiguchi wrote:
> > > On Wed, Aug 15, 2018 at 03:43:34PM -0700, Andrew Morton wrote:
> > > > On Tue, 17 Jul 2018 14:32:30 +0900 Naoya Horiguchi
> > > >
On Mon, Oct 29, 2018 at 11:29 PM Michal Hocko wrote:
>
> On Mon 29-10-18 12:59:11, Alexander Duyck wrote:
> > On Mon, 2018-10-29 at 19:18 +0100, Michal Hocko wrote:
[..]
> > The patches Andrew pushed addressed the immediate issue so that now
> > systems with nvdimm/DAX memory can at least initiali
Now that CONFIG_RETPOLINE hard depends on compiler support, there is no
reason for minimal stuff to still exist.
This change is based on suggestion in https://lkml.org/lkml/2018/9/18/1016
Signed-off-by: Zhenzhong Duan
Cc: Thomas Gleixner
Cc: Peter Zijlstra
Cc: Borislav Petkov
Cc: David Woodho
On Tue, 2018-10-30 at 07:06 +0100, Michal Hocko wrote:
> On Tue 30-10-18 09:29:10, Miles Chen wrote:
> > On Mon, 2018-10-29 at 09:17 +0100, Michal Hocko wrote:
> > > On Mon 29-10-18 09:07:08, Michal Hocko wrote:
> > > [...]
> > > > Besides that, the following doesn't make much sense to me. It simpl
According to Peter Zijlstra's suggestion in
https://lkml.org/lkml/2018/9/18/1016,
hard bind retpoline with compiler support and remove minimal stuff.
Tested with both CONFIG_RETPOLIN_SUPPORT enabled and disabled.
Zhenzhong Duan (3):
retpolines: Only enable retpoline when compiler support it
commit 3f5fe9fef5b2 ("sched/debug: Fix task state recording/printout")
tried to fix the problem introduced by a previous commit efb40f588b43
("sched/tracing: Fix trace_sched_switch task-state printing"). However
the prev_state output in sched_switch is still broken.
task_state_index() uses fls() w
Hi, Daniel:
On Mon, 2018-10-29 at 10:16 +0100, Daniel Vetter wrote:
> On Mon, Oct 29, 2018 at 11:11:16AM +0800, CK Hu wrote:
> > Hi,Daniel:
> >
> > On Fri, 2018-10-26 at 12:21 +0200, Daniel Vetter wrote:
> > > On Fri, Oct 26, 2018 at 03:22:03PM +0800, CK Hu wrote:
> > > > After adding dma_dev in
Dear Friend,
My name is Mr. Edward Yuan, a consultant/broker. I know you might be a bit
apprehensive because you do not know me. Nevertheless, I have a proposal on
behalf of a client, a lucrative business that might be of mutual benefit to you.
If interested in this proposition please kind
Laurence,
On Wed, 24 Oct 2018, Laurence Oberman wrote:
your subject line reads a bit strange:
Subject: [PATCH] V6 init/main.c Enable watchdog_thresh control from kernel line
To: lober...@redhat.com
Aside of that extra 'To:...', please move the V6 inside the square brackets
together with PATCH
On Fri, Oct 26, 2018 at 5:49 PM Martin Steigerwald wrote:
>
> This regression is gone with 4.19-rc8.
Thanks for the update!
> Martin Steigerwald - 11.09.18, 09:53:
> […]
> > Linus Torvalds - 02.09.18, 23:45:
> > > As usual, the rc2 release is pretty small. People are taking a
> >
> > With 4.19-
Any update on this ?
In V6, I have posted has only defect fixes (Other than HBA Hot-Plug
Surprise remove support).
We are reworking and incorporating the suggestions from Bjorn.
And after covering tests, we ll post Hot-Plug Surprise removal patches.
Thanks,
Suganath Prabu
On Tue, Oct 23, 2018 at
Hi Jae,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on wsa/i2c/for-next]
[also build test ERROR on v4.19 next-20181029]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
On Mon, Oct 29, 2018 at 10:11:36PM +0200, Sam Protsenko wrote:
> Hi Greg,
>
> On Mon, Oct 29, 2018 at 10:09 PM, Sam Protsenko
> wrote:
> > ctags indexing ("make tags" command) throws this warning:
> >
> > ctags: Warning: include/linux/notifier.h:125:
> > null expansion of name pattern "\1
On Tue 30-10-18 13:45:22, Tetsuo Handa wrote:
> Michal Hocko wrote:
> > @@ -3156,6 +3166,13 @@ void exit_mmap(struct mm_struct *mm)
> > vma = remove_vma(vma);
> > }
> > vm_unacct_memory(nr_accounted);
> > +
> > + /*
> > +* Now that the full address spac
On Mon, Oct 29, 2018 at 04:03:54PM -0700, Harry Cutts wrote:
> On Mon, 29 Oct 2018 at 15:01, Linus Torvalds
> wrote:
> > That would work, yes.
>
> OK, I'll write a patch for this. (It may be next week, though, as I
> have a deadline on a separate project this week.)
>
> > Except I think you *do*
On Mon 29-10-18 21:51:55, Roman Gushchin wrote:
> Mike Galbraith reported a regression caused by the commit 9b6f7e163cd0
> ("mm: rework memcg kernel stack accounting") on a system with
> "cgroup_disable=memory" boot option: the system panics with the
> following stack trace:
>
> [0.928542] BUG:
On Mon, Oct 29, 2018 at 9:56 PM Daniel Lezcano
wrote:
>
> When the function topology_parse_cpu_capacity() fails, we set the boolean
> cap_parsing_failed to true and we free the raw_capacity. This is correct as
> the function begins with a check against cap_parsing_failed thus protecting
> the func
On Tue 30-10-18 09:29:10, Miles Chen wrote:
> On Mon, 2018-10-29 at 09:17 +0100, Michal Hocko wrote:
> > On Mon 29-10-18 09:07:08, Michal Hocko wrote:
> > [...]
> > > Besides that, the following doesn't make much sense to me. It simply
> > > makes no sense to use vmalloc for sub page allocation reg
On 10/30/2018 12:13 AM, Stephen Boyd wrote:
Quoting Taniya Das (2018-10-28 03:34:55)
Hello Stephen,
On 2018-10-19 16:04, Taniya Das wrote:
Hello Stephen,
On 10/10/2018 2:04 AM, Stephen Boyd wrote:
Quoting Taniya Das (2018-10-09 06:57:47)
diff --git a/drivers/clk/qcom/dispcc-sdm845.c
b/dr
On Mon, Oct 29, 2018 at 9:54 PM Daniel Lezcano
wrote:
>
> The mutex protects a per_cpu variable access. The potential race can
> happen only when the cpufreq governor module is loaded and at the same
> time the cpu capacity is changed in the sysfs.
>
> There is no real interest of using a mutex to
Hi,
On 2018/10/30 14:04, Gao Xiang wrote:
> It is better to use wrapped smp_cond_load_relaxed
> instead of open-coded busy waiting for bit_spinlock.
>
> Signed-off-by: Gao Xiang
> ---
>
> change log v2:
> - fix the incorrect expression !(VAL >> (bitnum & (BITS_PER_LONG-1)))
> - the test resul
It is better to use wrapped smp_cond_load_relaxed
instead of open-coded busy waiting for bit_spinlock.
Signed-off-by: Gao Xiang
---
change log v2:
- fix the incorrect expression !(VAL >> (bitnum & (BITS_PER_LONG-1)))
- the test result is described in the following reply.
Thanks,
Gao Xiang
i
On Mon, Oct 29, 2018 at 9:56 PM Daniel Lezcano
wrote:
Would have been better if I was cc'd on all the patches since I was
looking at this
stuff actively this week :)
> The function 'register_cpufreq_notifier' registers the
> init_cpu_capacity_notifier() only if raw_capacity is not NULL.
>
> Henc
GPIOs 0 through 3 and 81 through 84 are configured to not be accessible
from the application CPUs. Mark them as reserved to allow the MSM8998
MTP to boot after the introduction of 3edfb7bd76bd ("gpiolib: Show
correct direction from the beginning").
Signed-off-by: Bjorn Andersson
---
arch/arm64/b
The stallwarn document incorrectly mentions 'fps=' instead of 'fqs='.
Correct that.
Signed-off-by: Joel Fernandes (Google)
---
Documentation/RCU/stallwarn.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/RCU/stallwarn.txt b/Documentation/RCU/stallwarn.txt
ind
Hi all,
Please do not add any v4.21/v5.1 code to your linux-next included trees
until after the merge window closes.
Changes since 20181029:
My fixes tree contains this:
"drivers: net: include linux/ip.h for iphdr"
The compiler-attributes tree gained a conflict against the kbuild
On 2018-10-29, Daniel Colascione wrote:
> Add a simple proc-based kill interface. To use /proc/pid/kill, just
> write the signal number in base-10 ASCII to the kill file of the
> process to be killed: for example, 'echo 9 > /proc/$$/kill'.
>
> Semantically, /proc/pid/kill works like kill(2), exce
Michal Hocko wrote:
> @@ -3156,6 +3166,13 @@ void exit_mmap(struct mm_struct *mm)
> vma = remove_vma(vma);
> }
> vm_unacct_memory(nr_accounted);
> +
> + /*
> +* Now that the full address space is torn down, make sure the
> +* OOM killer skips ov
Instead of specifying target/source pairs, let's list patterns that we
want to handle as single targets. This slightly changes the behavior;
the top Makefile previously checked the presence of a source file,
now Kbuild will descend into a subdirectory anyway to find out what to
do there.
Signed-of
There is one more user of $(cc-name) in the top Makefile. It is supposed
to detect Clang before invoking Kconfig, so it should still be there
in the $(shell ...) form. All the other users of $(cc-name) have been
replaced with $(CONFIG_CC_IS_CLANG). Hence, scripts/Kbuild.include does
not need to def
On Mon, Oct 29, 2018 at 06:37:53AM +, Peng15 Wang 王鹏 wrote:
>
>
> >From: Kees Cook
> >Sent: Monday, October 29, 2018 0:03
> >To: Peng15 Wang 王鹏
> >Cc: an...@enomsg.org; ccr...@android.com; tony.l...@intel.com;
> >linux-kernel@vger.kernel.org; Joel Fer
On Mon, Oct 29, 2018 at 07:27:35AM -0700, Paul E. McKenney wrote:
> On Mon, Oct 29, 2018 at 11:24:42AM +, Ran Rozenstein wrote:
> > Hi Paul and all,
> >
> > > -Original Message-
> > > From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel-
> > > ow...@vger.kernel.org] On Behalf
On Mon, Oct 29, 2018 at 3:11 PM Daniel Colascione wrote:
>
> Add a simple proc-based kill interface. To use /proc/pid/kill, just
> write the signal number in base-10 ASCII to the kill file of the
> process to be killed: for example, 'echo 9 > /proc/$$/kill'.
>
> Semantically, /proc/pid/kill works
On 2018-10-30, Masami Hiramatsu wrote:
> > Historically, kretprobe has always produced unusable stack traces
> > (kretprobe_trampoline is the only entry in most cases, because of the
> > funky stack pointer overwriting). This has caused quite a few annoyances
> > when using tracing to debug proble
Hi Duncan,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on soc-thermal/next]
[also build test ERROR on v4.19]
[cannot apply to next-20181029]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https
On Mon, 2018-10-29 at 21:49 +, Roman Gushchin wrote:
> On Mon, Oct 29, 2018 at 09:46:54PM +0100, Mike Galbraith wrote:
>
> > Ah, I have cgroup_disable=memory on the command line, which turns out
> > to be why your box doesn't explode, while mine does.
>
> Yeah, here it is. I'll send the fix i
On Mon, Oct 29, 2018 at 1:01 PM Daniel Colascione wrote:
>
> Thanks for taking a look.
>
> On Mon, Oct 29, 2018 at 7:45 PM, Joel Fernandes wrote:
> >
> > On Mon, Oct 29, 2018 at 10:53 AM Daniel Colascione
> > wrote:
> > >
> > > This patch adds a new file under /proc/pid, /proc/pid/exithand.
> >
On 10/29/2018 08:18 PM, Will Deacon wrote:
> On Mon, Oct 29, 2018 at 06:15:42PM +0530, Anshuman Khandual wrote:
>> On 10/29/2018 06:02 PM, John Garry wrote:
>>> On 29/10/2018 12:16, Will Deacon wrote:
On Mon, Oct 29, 2018 at 12:14:09PM +, John Garry wrote:
> On 29/10/2018 11:25, Wil
On Mon, Oct 29, 2018 at 12:29:22PM -0600, Alex Williamson wrote:
> On Mon, 29 Oct 2018 17:14:46 +0800
> Jason Wang wrote:
>
> > On 2018/10/29 上午10:42, Simon Guo wrote:
> > > Hi,
> > >
> > > I am using network device pass through mode with qemu x86(-device
> > > vfio-pci,host=:xx:yy.z)
> > >
Hello,
I'm trying to use a GPIO as an interrupt on an mt7620 (using OpenWRT
drivers) and I can't seem to figure out how to glue my two-celled
interrupt description (including the trigger) to the device tree code.
This is the gpio driver I'm using:
https://github.com/openwrt/openwrt/blob/master/t
On 10/29/2018 08:14 PM, John Garry wrote:
>
> I think we should either factor out the sanity check
>> into a core helper or make the core code robust to these funny
>> configurations.
>
> OK, so to me it would make sense to factor out a sanity check into a core
> he
> > > It's not obvious from this patch where this dependency comes
> > > from...why is SYSVIPC required? I'd like to not have to require
> > > IPC_NS either for devices.
> >
> > Yes, the patch is not highly dependent on SYSVIPC, but it will be
> > convenient if require it. I will update it to dr
On Mon, Oct 29, 2018 at 6:01 PM Rik van Riel wrote:
>
> On Mon, 2018-10-29 at 17:50 -0700, Shakeel Butt wrote:
> > On Mon, Oct 29, 2018 at 2:52 PM Roman Gushchin wrote:
> > >
> > > Mike Galbraith reported a regression caused by the commit
> > > 9b6f7e163cd0
> > > ("mm: rework memcg kernel stack a
> > > It's not obvious from this patch where this dependency comes
> > > from...why is SYSVIPC required? I'd like to not have to require
> > > IPC_NS either for devices.
> >
> > Yes, the patch is not highly dependent on SYSVIPC, but it will be
> > convenient if require it. I will update it to dr
Remove duplicated include.
Signed-off-by: YueHaibing
---
arch/nds32/kernel/pm.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/nds32/kernel/pm.c b/arch/nds32/kernel/pm.c
index 6989560..ffa8040 100644
--- a/arch/nds32/kernel/pm.c
+++ b/arch/nds32/kernel/pm.c
@@ -5,7 +5,6 @@
#include
#
On Mon, Oct 29, 2018 at 11:31:00PM +, Serge E. Hallyn wrote:
> On Mon, Oct 29, 2018 at 04:40:31PM -0600, Tycho Andersen wrote:
> > + if (req->data.nr != __NR_mount) {
> > + fprintf(stderr, "huh? trapped something besides mknod? %d\n",
> > req->data.nr);
>
> 'besides mount' ?
Yes,
Hi Laurence,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linux-sof-driver/master]
[also build test ERROR on v4.19 next-20181029]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day
On 10/29/2018 6:42 PM, David Miller wrote:
From: "Liang, Kan"
Date: Mon, 29 Oct 2018 18:32:40 -0400
- struct annotation_options *annotation_options
__maybe_unused)
+ struct annotation_options *annotation_options __maybe_unused,
+
From: Kan Liang
The main event processing thread may hang if the ring buffer event
processing timeouts.
Analysis from David Miller:
"It hangs the event thread, because the ui call waits for a keypress
but the display thread will eat them up and the event thread thus
hangs in select()."
The time
Hi Peter,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 4b42745211af552f170f38a1b97f4a112b5da6b2
commit: 7aa54be2976550f17c11a1c3e3630002dea39303 locking/qspinlock, x86:
Provide liveness guarantee
date: 13 days
On 2018/10/30 1:59, Will Deacon wrote:
> On Sat, Oct 20, 2018 at 03:36:54PM +0800, Zhen Lei wrote:
>> The standard GITS_TRANSLATER register in ITS is only 4 bytes, but
>> Hisilicon expands the next 4 bytes to carry some IMPDEF information. That
>> means, total 8 bytes data will be written to MSI
Hi Akshu,
On Mon, Oct 29, 2018 at 1:39 AM Agrawal, Akshu wrote:
>
> During simultaneous running of playback and capture, we
> got hit by incorrect value write on common register. This was due
> to race condition between 2 streams.
> Fixing this by locking the common register access.
Nice catch!
On Mon, 2018-10-29 at 09:17 +0100, Michal Hocko wrote:
> On Mon 29-10-18 09:07:08, Michal Hocko wrote:
> [...]
> > Besides that, the following doesn't make much sense to me. It simply
> > makes no sense to use vmalloc for sub page allocation regardless of
> > HIGHMEM.
>
> OK, it is still early mor
Hi Al,
Today's linux-next merge of the vfs tree got a conflict in:
fs/compat_ioctl.c
between commit:
77654350306a ("take compat TIOC[SG]SERIAL treatment into tty_compat_ioctl()")
from Linus' tree and commit:
69374d063be0 ("compat_ioctl: remove pointless HCI... ioctls")
from the vfs tre
Hi Rob,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 4b42745211af552f170f38a1b97f4a112b5da6b2
commit: 37c8a5fafa3bb7dcdd51774be353be6cb2912b86 kbuild: consolidate Devicetree
dtb build rules
date: 4 weeks ago
co
make[1]: Entering directory '/usr/src/linux-4.19'
CC [M] /tmp/rtl8812AU_8821AU_linux/os_dep/linux/os_intfs.o
/tmp/rtl8812AU_8821AU_linux/os_dep/linux/os_intfs.c:816:22: error:
initialization of ‘u16 (*)(struct net_device *, struct sk_buff *,
struct net_device *, u16 (*)(struct net_device *, st
Hi Aleksa,
On Sat, 27 Oct 2018 00:22:10 +1100
Aleksa Sarai wrote:
> Historically, kretprobe has always produced unusable stack traces
> (kretprobe_trampoline is the only entry in most cases, because of the
> funky stack pointer overwriting). This has caused quite a few annoyances
> when using tr
From: Yuantian Tang
The QorIQ Layerscape SoC has several thermal sensors but the current
driver only supports one.
Massage the code to be sensor oriented and allow the support for
multiple sensors.
Signed-off-by: Yuantian Tang
Reviewed-by: Daniel Lezcano
---
v3:
- add Reviewed-by
v2:
- up
On Mon, 2018-10-29 at 17:50 -0700, Shakeel Butt wrote:
> On Mon, Oct 29, 2018 at 2:52 PM Roman Gushchin wrote:
> >
> > Mike Galbraith reported a regression caused by the commit
> > 9b6f7e163cd0
> > ("mm: rework memcg kernel stack accounting") on a system with
> > "cgroup_disable=memory" boot opti
On Mon, Oct 29, 2018 at 11:04:45PM +, Daniel Colascione wrote:
> On Mon, Oct 29, 2018 at 7:25 PM, Davidlohr Bueso wrote:
> > This patch introduces a new /proc/stat2 file that is identical to the
> > regular 'stat' except that it zeroes all hard irq statistics. The new
> > file is a drop in rep
On Mon, Oct 29, 2018 at 2:52 PM Roman Gushchin wrote:
>
> Mike Galbraith reported a regression caused by the commit 9b6f7e163cd0
> ("mm: rework memcg kernel stack accounting") on a system with
> "cgroup_disable=memory" boot option: the system panics with the
> following stack trace:
>
> [0.92854
Hi Arnd,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 4b42745211af552f170f38a1b97f4a112b5da6b2
commit: 21924765862a0871908a35cb0e53e2e1c169b888 SUNRPC: use cmpxchg64() in
gss_seq_send64_fetch_and_inc()
date: 3
Hi Rakesh,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 4b42745211af552f170f38a1b97f4a112b5da6b2
commit: 6bae5ea9498926440ffc883f3dbceb0adc65e492 ASoC: hdac_hda: add asoc
extension for legacy HDA codec drivers
da
Thank you!
On Sun, Oct 28, 2018 at 1:38 PM Masahiro Yamada
wrote:
>
> On Tue, Oct 23, 2018 at 10:11 AM Leonardo Brás wrote:
> >
> > Creates DEF_FIELD_ADDR_VAR as a more generic version of the DEF_FIELD_ADD
> > macro, allowing usage of a variable name other than the struct element name.
> > Also,
Sorry, I will take care next time.
Thank you,
Leonardo Bras
On Sun, Oct 28, 2018 at 1:37 PM Masahiro Yamada
wrote:
>
> On Wed, Oct 24, 2018 at 1:04 PM Leonardo Bras wrote:
> >
> > Removes an unnecessary shadowed local variable (start).
> > It was used only once, with the same value it was star
+christ...@brauner.io
On Sun, Oct 28, 2018 at 7:29 PM chouryzhou(周威) wrote:
...
>
> > It's not obvious from this patch where this dependency comes
> > from...why is SYSVIPC required? I'd like to not have to require IPC_NS
> > either for devices.
>
> Yes, the patch is not highly dependent on SYSVI
Dear RT folks!
I'm pleased to announce the v4.19-rt1 patch set.
Changes since v4.18.16-rt9:
- rebase to v4.19
Known issues
- A warning triggered in "rcu_note_context_switch" originated from
SyS_timer_gettime(). The issue was always there, it is now
visible. Reported by Gry
On Mon, Oct 29, 2018 at 4:30 PM Bjorn Andersson
wrote:
>
> rpmsg updates for v4.20
Pulled (along with the remoteproc branch),
Linus
On Mon, Oct 29, 2018 at 11:40:47PM +, Daniel Colascione wrote:
> On Mon, Oct 29, 2018 at 11:34 PM, Alexey Dobriyan wrote:
> >> I'd much rather move to a model in which userspace *explicitly* tells
> >> the kernel which fields it wants, with the kernel replying with just
> >> those particular f
Make ARM and Unicore32 select ARCH_HAS_PHYS_INITRD meaning that they do
define phys_initrd_start/phys_initrd_size and make use of it.
Signed-off-by: Florian Fainelli
---
arch/Kconfig | 7 +++
arch/arm/Kconfig | 1 +
arch/unicore32/Kconfig | 1 +
3 files changed, 9 insertions(
ARM64 is the only architecture that re-defines
__early_init_dt_declare_initrd() in order for that function to populate
initrd_start/initrd_end with physical addresses instead of virtual
addresses. Instead of having an override, just get rid of that
implementation and select ARCH_HAS_PHYS_INITRD whi
Make phys_initrd_start and phys_initrd_size global variables that will
later be referenced by generic code under drivers/of/fdt.c.
Signed-off-by: Florian Fainelli
---
arch/arm/mm/init.c | 4 ++--
arch/unicore32/mm/init.c | 4 ++--
include/linux/initrd.h | 3 +++
3 files changed, 7 insert
With the one and only architecture (ARM64) no longer defining a custom
__early_init_dt_declare_initrd() function, just get rid of the check for
that function being already defined.
Signed-off-by: Florian Fainelli
---
drivers/of/fdt.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/o
If the architecture implements ARCH_HAS_PHYS_INITRD, make the FDT
scanning code populate the physical address of the start of the FDT and
its size.
Signed-off-by: Florian Fainelli
---
arch/arm/mm/init.c | 2 +-
drivers/of/fdt.c | 4
2 files changed, 5 insertions(+), 1 deletion(-)
diff --
This will conflict with a subsequent change making phys_initrd_start and
phys_initrd_size global variables. nds32 does not make use of those nor
provides a suitable declarations so just get rid of them.
Signed-off-by: Florian Fainelli
---
arch/nds32/mm/init.c | 2 --
1 file changed, 2 deletions(
--
I solicit your cooperation to transfer $7 million to your bank account
and you will be entitled to 40% of this fund, respond urgent if you
are interested for more details.
Hi all,
The numbers no longer make any sense since I either did not correctly
understand the feedback being given, or dramatically changed the
approach.
This version introduces an architecture symbol: ARCH_HAS_PHYS_INITRD
which indicates whether the architecture cares/supports parsing the
physica
Hi all,
On Tue, 30 Oct 2018 10:46:37 +1100 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the compiler-attributes tree got a conflict
> in:
>
> include/linux/compiler-gcc.h
>
> between commit:
>
> 94c7dfd01652 ("kernel hacking: support building kernel with -Og
> optimization lev
Hi Miguel,
Today's linux-next merge of the compiler-attributes tree got a conflict
in:
include/linux/compiler-gcc.h
between commit:
94c7dfd01652 ("kernel hacking: support building kernel with -Og optimization
level")
from the kbuild tree and commits:
5c67a52f3da0 ("Compiler Attributes:
On Mon, Oct 29, 2018 at 11:34 PM, Alexey Dobriyan wrote:
>> I'd much rather move to a model in which userspace *explicitly* tells
>> the kernel which fields it wants, with the kernel replying with just
>> those particular fields, maybe in their raw binary representations.
>> The ASCII-text bag-of-
> I'd much rather move to a model in which userspace *explicitly* tells
> the kernel which fields it wants, with the kernel replying with just
> those particular fields, maybe in their raw binary representations.
> The ASCII-text bag-of-everything files would remain available for
> ad-hoc and non-p
Am Dienstag, 30. Oktober 2018, 00:21:46 CET schrieb Colin King:
> From: Colin Ian King
>
> Currently a failure when calling ubifs_read_nnode results in a leak
> of desc and buf because of a direct return. Fix this by exiting via
> label 'out' that performs the necessary free'ing of the resources.
From: Colin Ian King
Replace a bunch of spaces with tab, cleans up indentation
Signed-off-by: Colin Ian King
---
kernel/events/core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/events/core.c b/kernel/events/core.c
index 8c490130c4fb..84530ab358c3 100644
--- a/ke
On Mon, Oct 29, 2018 at 04:40:31PM -0600, Tycho Andersen wrote:
> The idea here is just to give a demonstration of how one could safely use
> the SECCOMP_RET_USER_NOTIF feature to do mount policies. This particular
> policy is (as noted in the comment) not very interesting, but it serves to
> illus
The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3:
Linux 4.19-rc1 (2018-08-26 14:11:59 -0700)
are available in the Git repository at:
git://github.com/andersson/remoteproc tags/rpmsg-v4.20
for you to fetch changes up to 928002a5e9dab2ddc1a0fe3e00739e89be30dc6b:
The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3:
Linux 4.19-rc1 (2018-08-26 14:11:59 -0700)
are available in the Git repository at:
git://github.com/andersson/remoteproc tags/rproc-v4.20
for you to fetch changes up to f18b7e914fd2ed5e8b5733644cefcf62f7582679:
On Mon, Oct 29, 2018 at 4:58 PM Ard Biesheuvel
wrote:
>
> On 29 October 2018 at 16:59, Rob Herring wrote:
> > +Ard who last touched this.
> >
> > On Mon, Oct 29, 2018 at 2:23 PM Florian Fainelli
> > wrote:
> >>
> >> ARM64 is the only architecture that re-defines
> >> __early_init_dt_declare_ini
From: Colin Ian King
Currently a failure when calling ubifs_read_nnode results in a leak
of desc and buf because of a direct return. Fix this by exiting via
label 'out' that performs the necessary free'ing of the resources.
Fixes: a1dc58140f7e ("ubifs: authentication: Authenticate LPT")
Signed-
From: Alex Williams
Now the DMA engine is free to float elsewhere in the system map.
Signed-off-by: Alex Williams
---
Documentation/devicetree/bindings/net/nixge.txt | 14 +++---
1 file changed, 11 insertions(+), 3 deletions(-)
diff --git a/Documentation/devicetree/bindings/net/nixge.
On 28/10/18 1:39 am, Boris Brezillon wrote:
> Hi Brett,
>
> On Tue, 16 Oct 2018 00:57:41 +
> "Grandbois, Brett" wrote:
>
>> Add support to expose the SPI boot flash on AMD Family 16h CPUs as a
>> standard mtd device to give userspace BIOS updaters greater feature
>> support. The BIOS and Ker
On 2018-10-29 21:16:16 [+0100], Daniel Wagner wrote:
> From: Daniel Wagner
>
> v4.4.162-rt176-rc1 stable review patch.
> If anyone has any objections, please let me know.
I though that we are going to route this via Greg/stable for v4.4?
> --- a/arch/x86/Kconfig
> +++ b/arch/x86/Kconfig
> @@ -4
On Mon, Oct 29, 2018 at 7:25 PM, Davidlohr Bueso wrote:
> This patch introduces a new /proc/stat2 file that is identical to the
> regular 'stat' except that it zeroes all hard irq statistics. The new
> file is a drop in replacement to stat for users that need performance.
For a while now, I've be
On Mon, 29 Oct 2018 at 15:01, Linus Torvalds
wrote:
> That would work, yes.
OK, I'll write a patch for this. (It may be next week, though, as I
have a deadline on a separate project this week.)
> Except I think you *do* want the "reset on direction change" logic,
> because otherwise we still end
Hi Fenghua,
> -Original Message-
> From: linux-kernel-ow...@vger.kernel.org ow...@vger.kernel.org> On Behalf Of Fenghua Yu
> Sent: Thursday, October 25, 2018 6:07 PM
> To: Thomas Gleixner ; Ingo Molnar
> ; H Peter Anvin ; Tony Luck
> ; Peter Zijlstra ; Reinette
> Chatre ; Moger, Babu
> ;
On 10/26/18 4:44 PM, Jan H. Schönherr wrote:
On 19/10/2018 02.26, Subhra Mazumdar wrote:
Hi Jan,
Hi. Sorry for the delay.
On 9/7/18 2:39 PM, Jan H. Schönherr wrote:
The collective context switch from one coscheduled set of tasks to another
-- while fast -- is not atomic. If a use-case need
Hi Jae,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on wsa/i2c/for-next]
[also build test WARNING on v4.19 next-20181029]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci
On Thu, Oct 25, 2018 at 07:56:26AM +, visionsofal...@redchan.it wrote:
> The linux devs can rescind their license grant.
Greg KH responded on Thu, 25 Oct 2018 09:19:11 +0100:
>> No they can not, please do not keep spreading false information.
I was explicitly cc'ed on this thread by visionsofa
On Mon, 29 Oct 2018 21:15:01 +0800 kernel test robot
wrote:
> FYI, we noticed the following commit (built with gcc-7):
>
> commit: 68c37ccedcde10514898f4ba3b28c0de85c590d1 ("mm: nobootmem: remove
> bootmem allocation APIs")
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git mas
1 - 100 of 572 matches
Mail list logo
