The AM654 SoC is a lead device of the K3 Multicore SoC architecture
platform, targeted for broad market and industrial control with aim to
meet the complex processing needs of modern embedded products.
Some highlights of this SoC are:
* Quad ARMv8 A53 cores split over two clusters
* GICv3
The EValuation Module(EVM) platform for AM654 consists of a
common Base board + one or more of daughter cards, which include:
a) "Personality Modules", which can be specific to a profile, such as
ICSSG enabled or Multi-media (including audio).
b) SERDES modules, which may be 2 lane PCIe or two
On 06/05/2018 08:36 AM, H. Peter Anvin wrote:
> On 06/04/18 20:57, Mika Penttilä wrote:
>>
>> This won't work on X86-32 because it actually uses the segment limit with
>> fs: access. So there
>> is a reason why the lsl based method is X86-64 only.
>>
>
>
>
> Why does that matter in any shape,
From: Lokesh Vutla
Allow 8250 omap serial driver to be used for K3 platforms.
Signed-off-by: Lokesh Vutla
Signed-off-by: Nishanth Menon
---
drivers/tty/serial/8250/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/tty/serial/8250/Kconfig
Add support for Texas Instrument's K3 Multicore SoC architecture
processors.
Signed-off-by: Nishanth Menon
---
arch/arm64/Kconfig.platforms | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm64/Kconfig.platforms b/arch/arm64/Kconfig.platforms
index d5aeac351fc3..52df25bf4f8c
On 05-06-18, 11:12, Sricharan R wrote:
> +config QCOM_Q6V5_WCSS
> + tristate "Qualcomm Hexagon based WCSS Peripheral Image Loader"
> + depends on OF && ARCH_QCOM
> + depends on QCOM_SMEM
> + depends on RPMSG_QCOM_SMD || (COMPILE_TEST && RPMSG_QCOM_SMD=n)
> + depends on
In a much bigger system SoCs, the number of Rx channels can be
many and mostly unused based on the system of choice, and not all
Rx channels need IRQs and allocating all memory at probe will be
inefficient. Some SoCs could have total threads in the 100s and usage
would be just 1 Rx thread.
Thus,
For newer generation of the hardware, the naming of the region is
decided at integration level and there could be additional regions
as well. Hence move the region naming to be described from compatible
descriptor.
Signed-off-by: Nishanth Menon
---
drivers/mailbox/ti-msgmgr.c | 10 --
1
Add support for Secure Proxy instances in AM6 family of SoCs.
Signed-off-by: Nishanth Menon
---
arch/arm64/boot/dts/ti/k3-am6.dtsi | 11 +++
1 file changed, 11 insertions(+)
diff --git a/arch/arm64/boot/dts/ti/k3-am6.dtsi
b/arch/arm64/boot/dts/ti/k3-am6.dtsi
index
Just CC’ed to some of maintainers.
$ perl scripts/get_maintainer.pl
fs/0001-ksys_mount-check-for-permissions-before-resource-all.patch
Alexander Viro (maintainer:FILESYSTEMS (VFS and
infrastructure))
linux-fsde...@vger.kernel.org (open list:FILESYSTEMS (VFS and infrastructure))
On Wed, 30 May 2018, Gwendal Grignou wrote:
> Use dev_kzmalloc, remove .release entry point.
>
> Signed-off-by: Gwendal Grignou
> ---
> Change sinc v1:
> - Readd __remove to avoid a warning when loaded as a module.
>
> drivers/mfd/cros_ec_dev.c | 10 ++
> 1 file changed, 2
On Mon, Jun 4, 2018 at 8:33 AM, Thomas Gleixner wrote:
> apic_ack_edge() is explicitely for handling interrupt affinity cleanup when
> interrupt remapping is not available or disable.
>
> Remapped interrupts and also some of the platform specific special
> interrupts, e.g. UV, invoke
+++ Josh Poimboeuf [04/06/18 18:02 -0500]:
On Mon, Jun 04, 2018 at 05:56:05PM -0500, Josh Poimboeuf wrote:
On Mon, Jun 04, 2018 at 09:54:12AM -0500, Josh Poimboeuf wrote:
> On Mon, Jun 04, 2018 at 04:05:11PM +0200, Jessica Yu wrote:
> > +++ Josh Poimboeuf [04/06/18 08:16 -0500]:
> > > On Mon,
From: Changbin Du
Hi all,
I know some kernel developers was searching for a method to dissable GCC
optimizations, probably they want to apply GCC '-O0' option. But since Linux
kernel replys on GCC optimization to remove some dead code, so '-O0' just
breaks the build. They do need this because
From: Changbin Du
This will apply GCC '-Og' optimization level which is supported
since GCC 4.8. This optimization level offers a reasonable level
of optimization while maintaining fast compilation and a good
debugging experience. It is similar to '-O1' while perferring
to keep debug ability
On 01.06.2018 18:25, Eric W. Biederman wrote:
> Michal Hocko writes:
>
>> On Fri 01-06-18 09:32:42, Eric W. Biederman wrote:
>>> Michal Hocko writes:
>> [...]
Group leader exiting early without tearing down the whole thread
group should be quite rare as well. No question that somebody
Like LibreTech-CC, the USB0 needs the 5V regulator to be enabled to power the
devices on the P212 Reference Design based boards.
Fixes: b9f07cb4f41f ("ARM64: dts: meson-gxl-s905x-p212: enable the USB
controller")
Signed-off-by: Neil Armstrong
---
Hi,
On 04.06.2018 22:16, Arnaldo Carvalho de Melo wrote:
> Em Mon, Jun 04, 2018 at 06:22:43PM +0300, Alexey Budankov escreveu:
>> On 04.06.2018 17:58, Arnaldo Carvalho de Melo wrote:
>>> Em Mon, Jun 04, 2018 at 05:51:03PM +0300, Alexey Budankov escreveu:
event names quoted there. If such
Though q_proxies and q_slices do describe the hardware configuration,
they are not necessary for operation given that the values are
always default. Hence drop the same.
Signed-off-by: Nishanth Menon
---
drivers/mailbox/ti-msgmgr.c | 6 --
1 file changed, 6 deletions(-)
diff --git
Hi Randy,
2018-06-04 11:59 GMT+09:00 Randy Dunlap :
> From: Randy Dunlap
>
> Each of 'make {menu,n,g,x}config' uses (needs) pkg-config to make sure
> that other required files are present and to determine build flags
> settings, but none of these check that pkg-config itself is present.
> Add a
On Tue, 05 Jun 2018, Stephen Rothwell wrote:
> Hi Lee,
>
> After merging the mfd tree, today's linux-next build (x86_64 allmodconfig)
> produced this warning:
>
> drivers/mfd/cros_ec_dev.c:265:13: warning: '__remove' defined but not used
> [-Wunused-function]
> static void __remove(struct
Tested-by: Song Liu
On Mon, Jun 4, 2018 at 8:33 AM, Thomas Gleixner wrote:
>
Tested-by: Song Liu
On Mon, Jun 4, 2018 at 8:33 AM, Thomas Gleixner wrote:
>
Tested-by: Song Liu
On Mon, Jun 4, 2018 at 8:33 AM, Thomas Gleixner wrote:
>
* Peter Zijlstra [2018-06-04 21:28:21]:
> > if (time_after(jiffies, pgdat->numabalancing_migrate_next_window)) {
> > - spin_lock(>numabalancing_migrate_lock);
> > - pgdat->numabalancing_migrate_nr_pages = 0;
> > - pgdat->numabalancing_migrate_next_window =
://github.com/0day-ci/linux/commits/Nadav-Amit/x86-macrofying-inline-asm-for-better-compilation/20180605-124313
config: i386-tinyconfig (attached as .config)
compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All error
Hi,
On 05-06-18 04:31, Darren Hart wrote:
On Mon, Jun 04, 2018 at 04:23:04PM +0200, Hans de Goede wrote:
Hi,
On 04-06-18 15:51, Daniel Drake wrote:
On Mon, Jun 4, 2018 at 7:22 AM, Hans de Goede wrote:
Is this really a case of the hardware itself processing the
keypress and then changing
On Mon, Jun 04, 2018 at 03:30:10PM +0530, Srikar Dronamraju wrote:
> numa_entry is a list_head defined in task_struct, but never used.
>
> No functional change
>
> Signed-off-by: Srikar Dronamraju
Acked-by: Mel Gorman
--
Mel Gorman
SUSE Labs
On Tue, Jun 05, 2018 at 08:16:50AM +, Stanislav Nijnikov wrote:
> Hi Sayali,
>
> I think that passing an array of values in a string is not proper way
> to work with a sysfs entry. There are binary attributes to do such
> things.
No, don't do that, sysfs is for "one value per file", and
Hi Andy,
On 2018/6/4 18:06, Andy Shevchenko wrote:
> On Mon, Jun 4, 2018 at 4:06 AM, Yisheng Xie wrote:
>> Hi Andy,
>>
>> On 2018/6/1 19:34, Andy Shevchenko wrote:
>>> On Thu, May 31, 2018 at 2:11 PM, Yisheng Xie wrote:
match_string() returns the index of an array for a matching string,
On Tue, Jun 05, 2018 at 04:54:17PM +0800, gengdongjiu wrote:
>
>
> On 2018/6/5 16:40, Greg KH wrote:
> > On Wed, Jun 06, 2018 at 12:35:00AM +0800, Dongjiu Geng wrote:
> >> Initialize the 'err' variate to remove the build warning,
> >> the warning is shown as below:
> >>
> >>
The AM654 SoC is a lead device of the K3 Multicore SoC architecture
platform, targeted for broad market and industrial control with aim to
meet the complex processing needs of modern embedded products.
Some highlights of this SoC are:
* Quad ARMv8 A53 cores split over two clusters
* GICv3
Hi,
The following series enables support for newest addition in TI's SoC
portfolio - AM654 SoC.
The series is an RFC based off next-20180604 and will post formally once
v4.18-rc1 is available.
The series (part 1 of 4) is available here:
AM654 uses a UART controller that is compatible (partially) with
existing 8250 UART, however, has a few differences with respect to DMA
support and control paths. Introduce a base definition that allows us
to build up the differences in follow on patches.
Cc: Sekhar Nori
Cc: Vignesh R
ti-msgmr driver can support K3 platforms as well.
Signed-off-by: Nishanth Menon
---
drivers/mailbox/Kconfig | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/mailbox/Kconfig b/drivers/mailbox/Kconfig
index 725dce5ba62d..f87a857d21a5 100644
---
Secure Proxy is another communication scheme in Texas Instrument's
devices intended to provide an unique communication path from various
processors in the System on Chip(SoC) to a central System Controller.
Secure proxy is, in effect, an evolution of current generation Message
Manager hardware
Secure Proxy is another communication scheme in Texas Instrument's
devices intended to provide an unique communication path from various
processors in the System on Chip(SoC) to a central System Controller.
Secure proxy is, in effect, an evolution of current generation Message
Manager hardware
Hi,
The following series enables support for Secure Proxy in newest addition in
TI's SoC
portfolio - AM654 SoC.
The series is an RFC based off next-20180604 and will post formally once
v4.18-rc1 is available.
The DT and ARCH part of the series is based on
Change mask used to extract the message count to be descriptor based.
This is to support changes for count location for various SoC
solutions.
Signed-off-by: Nishanth Menon
---
drivers/mailbox/ti-msgmgr.c | 25 ++---
1 file changed, 18 insertions(+), 7 deletions(-)
diff
Hi,
The following series enables TI System Control Interface(TISCI) support for
the newest addition in TI's SoC portfolio - AM654 SoC.
The series is an RFC based off next-20180604 and will post formally once
v4.18-rc1 is available.
The series (part 4 of 4) is available here:
Texas Instrument's System Control Interface (TISCI) permits the
ability for Operating Systems to running in virtual machines to be
able to independently communicate with the firmware without the need
going through an hypervisor.
The "host-id" in effect is the hardware representation of the
host
Texas Instrument's System Control Interface (TISCI) permits the
ability for Operating Systems to running in virtual machines to be
able to independently communicate with the firmware without the need
going through an hypervisor.
The "host-id" in effect is the hardware representation of the
host
Add TISCI compatible System controller for AM6 SoCs.
Signed-off-by: Nishanth Menon
---
arch/arm64/boot/dts/ti/k3-am6.dtsi | 32
1 file changed, 32 insertions(+)
diff --git a/arch/arm64/boot/dts/ti/k3-am6.dtsi
b/arch/arm64/boot/dts/ti/k3-am6.dtsi
index
On 4 June 2018 at 18:06, Patrick Bellasi wrote:
> The estimated utilization of a task is affected by the task being
> preempted, either by another FAIR task of by a task of an higher
> priority class (i.e. RT or DL). Indeed, when a preemption happens, the
> PELT utilization of the preempted task
On Mon, Jun 4, 2018 at 8:33 AM, Thomas Gleixner wrote:
> The case that interrupt affinity setting fails with -EBUSY can be handled
> in the kernel completely by using the already available generic pending
> infrastructure.
>
> If a irq_chip::set_affinity() fails with -EBUSY, handle it like the
>
On Mon 04-06-18 09:31:46, Eric W. Biederman wrote:
[...]
> My key point is that it is easy to trigger which makes the current
> mm_update_next_owner a fundamentally flawed design, and something that
> needs to be fixed.
Ohh, absolutely agreed! I was not trying to argue that part of course.
--
Dear friend
I am contacting you for a business deal of $17.5 Million US Dollars,
ready for transfer into your account
if we make this claim, we will share it 60%/40%.
100% risk free and it will be legally backed up with government
approved If you are interested reply for more details.
Best
Initialize the 'err' variate to remove the build warning,
the warning is shown as below:
drivers/usb/host/xhci-tegra.c: In function ‘tegra_xusb_mbox_thread’:
drivers/usb/host/xhci-tegra.c:552:6: warning: ‘err’ may be used uninitialized
in this function [-Wuninitialized]
Livepatch modules are special in that we preserve their entire symbol
tables in order to be able to apply relocations after module load. The
unwanted side effect of this is that undefined (SHN_UNDEF) symbols of
livepatch modules are accessible via the kallsyms api and this can
confuse symbol
On Mon, Jun 04, 2018 at 03:30:18PM +0530, Srikar Dronamraju wrote:
> There are checks in migrate_swap_stop that check if the task/cpu
> combination is as per migrate_swap_arg before migrating.
>
> However atleast one of the two tasks to be swapped by migrate_swap could
> have migrated to a
Hi Linus,
Here's the PR with MMC updates for v4.18. Details about the highlights are as
usual found in the signed tag.
Please pull this in!
Kind regards
Ulf Hansson
The following changes since commit 3de06d5a1f05c11c94cbb68af14dbfa7fb81d78b:
mmc: sdhci-iproc: add
On Tue, 5 Jun 2018 15:09:27 +0800
kernel test robot wrote:
> FYI, we noticed the following commit (built with gcc-7):
>
> commit: b4331a681822b420511b3258f1c3db35001fde48 ("vti6: Change minimum MTU
> to IPV4_MIN_MTU, vti6 can carry IPv4 too")
>
On 4 June 2018 at 12:27, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.14.48 release.
> There are 52 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
K3_ARCH uses TISCI for clocks as well. Enable the same
for the driver support.
Signed-off-by: Nishanth Menon
---
Hi,
This patch depends on
https://marc.info/?l=linux-arm-kernel=152817866312732=2
and is an RFC based off next-20180604 and will post formally once
v4.18-rc1 is available.
The
On Mon, Jun 04, 2018 at 04:18:07PM +0300, Matti Vaittinen wrote:
> +static struct regmap_irq_chip bd71837_irq_chip = {
> + .name = "bd71837-irq",
> + .irqs = bd71837_irqs,
> + .num_irqs = ARRAY_SIZE(bd71837_irqs),
> + .num_regs = 1,
> + .irq_reg_stride = 1,
> + .status_base
://github.com/0day-ci/linux/commits/Nadav-Amit/x86-macrofying-inline-asm-for-better-compilation/20180605-124313
config: x86_64-fedora-25 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All
From: Changbin Du
With '-Og' optimization level, GCC would not optimize a count for a loop
as a constant value. But BUILD_BUG_ON() only accept compile-time constant
values. Let's use __fix_to_virt() to avoid the error.
arch/arm/mm/mmu.o: In function `fix_to_virt':
From: Changbin Du
This patch add a new kernel hacking option NO_AUTO_INLINE. Selecting
this option will prevent the compiler from optimizing the kernel by
auto-inlining functions not marked with the inline keyword.
With this option, only functions explicitly marked with "inline" will
be
From: Changbin Du
The level4_kernel_pgt is only defined when X86_5LEVEL is enabled. So
surround level4_kernel_pgt with #ifdef CONFIG_X86_5LEVEL...#endif to
make code correct.
Signed-off-by: Changbin Du
Acked-by: Steven Rostedt (VMware)
---
arch/x86/include/asm/pgtable_64.h | 2 ++
On Mon, Jun 04, 2018 at 03:30:12PM +0530, Srikar Dronamraju wrote:
> Currently load_too_imbalance() cares about the slope of imbalance.
> It doesn't care of the direction of the imbalance.
>
> However this may not work if nodes that are being compared have
> dissimilar capacities. Few nodes might
utente webmail
Tieni presente che il 95% delle tue e-mail ricevute dopo l'ultima volta che hai
bisogno di aggiornare il tuo server di versione webmail nel nostro database
sono state ritardate. Per ricevere e inviare i tuoi messaggi su base regolare.
Il nostro team tecnico di webmail aggiornerà
Hi Linus,
please pull from the 'for-linus' branch of
git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git for-linus
to receive the following updates:
- A rework for the s390 arch random code, the TRNG instruction is rather
slow and should not be used on the interrupt path
Hi,
On 05-06-18 05:18, Chris Chiu wrote:
On Tue, Jun 5, 2018 at 10:31 AM, Darren Hart wrote:
On Mon, Jun 04, 2018 at 04:23:04PM +0200, Hans de Goede wrote:
Hi,
On 04-06-18 15:51, Daniel Drake wrote:
On Mon, Jun 4, 2018 at 7:22 AM, Hans de Goede wrote:
Is this really a case of the
On Tue, 29 May 2018 14:35:06 +0200
Cornelia Huck wrote:
Ping.
> The following changes since commit 3376d98021e915196f4894d835325a884e635a04:
>
> s390/archrandom: Rework arch random implementation. (2018-05-25 08:12:58
> +0200)
>
> are available in the Git repository at:
>
>
On Mon, Jun 04, 2018 at 06:20:44AM -0700, Guenter Roeck wrote:
> On 06/03/2018 11:58 PM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.16.14 release.
> > There are 47 patches in this series, all will be posted as a response
> > to this one. If anyone has any
On Tue, Jun 05, 2018 at 12:24:39AM -0700, Srikar Dronamraju wrote:
> * Peter Zijlstra [2018-06-04 21:28:21]:
>
> > > if (time_after(jiffies, pgdat->numabalancing_migrate_next_window)) {
> > > - spin_lock(>numabalancing_migrate_lock);
> > > -
On Mon, Jun 04, 2018 at 01:47:12PM -0600, Shuah Khan wrote:
> On 06/04/2018 12:58 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.16.14 release.
> > There are 47 patches in this series, all will be posted as a response
> > to this one. If anyone has any
On Mon 04-06-18 17:23:06, Roman Gushchin wrote:
[...]
> I'm happy to discuss any concrete issues/concerns, but I really see
> no reasons to drop it from the mm tree now and start the discussion
> from scratch.
I do not think this is ready for the current merge window. Sorry! I
would really prefer
When the kernel booted with maxcpus=x, 'x' is smaller
than actual cpu numbers, the TAs of offline cpus won't
be set to its->collection.
If LPI is bind to offline cpu, sync cmd will use zero TA,
it leads to ITS queue timeout. Fix this by choosing a
online cpu, if there is no online cpu in
On 4 June 2018 at 12:28, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.16.14 release.
> There are 47 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On Mon, 04 Jun 2018, Fabien Parent wrote:
> On Mon, Jun 4, 2018 at 1:59 AM, Lee Jones wrote:
> > On Tue, 29 May 2018, Fabien Parent wrote:
> >
> >> A new more command has been added to the ChromeOS embedded controller
> >> that allows to get the number of charger port count. Unlike
> >>
On Tue, Jun 05, 2018 at 10:17:49AM +0530, Viresh Kumar wrote:
> The cooling device properties, like "#cooling-cells" and
> "dynamic-power-coefficient", should either be present for all the CPUs
> of a cluster or none. If these are present only for a subset of CPUs of
> a cluster then things will
Fix object code reading and the "Object code reading" test for PTI entry
trampolines.
perf tools uses map__rip_2objdump() to calculate objdump virtual addresses.
map__rip_2objdump() needs to be amended to deal with PTI entry trampolines.
Also the "Object code reading" test will not create maps
Hi Quentin,
On 25 May 2018 at 15:12, Vincent Guittot wrote:
> This patchset initially tracked only the utilization of RT rq. During
> OSPM summit, it has been discussed the opportunity to extend it in order
> to get an estimate of the utilization of the CPU.
>
> - Patches 1-3 correspond to the
This adds a base device tree file for the RZN1-DB board, with only the
basic support allowing the system to boot to a prompt. Only one UART is
used, with only a single CPU running.
Signed-off-by: Michel Pollet
Reviewed-by: Geert Uytterhoeven
---
arch/arm/boot/dts/Makefile | 1
On Mon, Jun 04, 2018 at 03:30:16PM +0530, Srikar Dronamraju wrote:
> When comparing two nodes at a distance of hoplimit, we should consider
> nodes only upto hoplimit. Currently we also consider nodes at hoplimit
> distance too. Hence two nodes at a distance of "hoplimit" will have same
>
On Mon, Jun 04, 2018 at 03:30:15PM +0530, Srikar Dronamraju wrote:
> Fix the order in which the private and shared numa faults are getting
> printed.
>
> Shouldn't have any performance impact.
>
> Signed-off-by: Srikar Dronamraju
Acked-by: Mel Gorman
--
Mel Gorman
SUSE Labs
On Mon, Jun 04, 2018 at 03:30:17PM +0530, Srikar Dronamraju wrote:
> task_capacity field in struct numa_stats is redundant.
> Also move nr_running for better packing within the struct.
>
> No functional changes.
>
> Signed-off-by: Srikar Dronamraju
Acked-by: Mel Gorman
--
Mel Gorman
SUSE
On Mon 04-06-18 21:25:39, David Rientjes wrote:
> On Fri, 1 Jun 2018, Michal Hocko wrote:
>
> > > We've discussed the mm
> > > having a single blockable mmu notifier. Regardless of how we arrive at
> > > the point where the oom reaper can't free memory, which could be any of
> > > those three
On Tue, Jun 05, 2018 at 11:02:36AM +0530, Viresh Kumar wrote:
> On 03-06-18, 08:52, Janani Sankara Babu wrote:
> > This patch replaces comparison of var to NULL with !var
> >
> > Signed-off-by: Janani Sankara Babu
> > ---
> > drivers/staging/greybus/core.c | 2 +-
> > 1 file changed, 1
On 4 June 2018 at 12:27, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.106 release.
> There are 29 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On Mon, 4 Jun 2018, Josh Poimboeuf wrote:
> On Mon, Jun 04, 2018 at 04:16:35PM +0200, Miroslav Benes wrote:
> > An administrator may send a fake signal to all remaining blocking tasks
> > of a running transition by writing to
> > /sys/kernel/livepatch//signal attribute. Let's do it
> >
On Mon, Jun 04, 2018 at 06:18:36PM -0700, Matthew Wilcox wrote:
> On Tue, Jun 05, 2018 at 12:54:03AM +, Naoya Horiguchi wrote:
> > Reproduction precedure is like this:
> > - enable RAM based PMEM (with a kernel boot parameter like memmap=1G!4G)
> > - read /proc/kpageflags (or call
On Tue, Jun 05, 2018 at 11:02:36AM +0530, Viresh Kumar wrote:
> On 03-06-18, 08:52, Janani Sankara Babu wrote:
> > This patch replaces comparison of var to NULL with !var
> >
> > Signed-off-by: Janani Sankara Babu
> > ---
> > drivers/staging/greybus/core.c | 2 +-
> > 1 file changed, 1
On 05/23/2018 06:29 AM, Viresh Kumar wrote:
> On 22-05-18, 08:28, Sébastien Szymanski wrote:
>> Check the max speed supported from the fuses for i.MX6ULL and update the
>> operating points table accordingly.
>>
>> Signed-off-by: Sébastien Szymanski
>> ---
>>
>> Changes for v3:
>> - none
>
>
On Tue, Jun 05, 2018 at 12:17:50PM +0530, Naresh Kamboju wrote:
> On 4 June 2018 at 12:28, Greg Kroah-Hartman
> wrote:
> > This is the start of the stable review cycle for the 4.16.14 release.
> > There are 47 patches in this series, all will be posted as a response
> > to this one. If anyone
On Mon, Jun 04, 2018 at 04:11:03PM -0700, Kevin Hilman wrote:
> kernelci.org bot writes:
>
> > Full Boot Summary:
> > https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.14.y/kernel/v4.14.47-53-g721adf61fde2/
> > Full Build Summary:
> >
On 05.06.2018 08:27, Masahiro Yamada wrote:
> 2018-06-05 14:50 GMT+09:00 Stefan Agner :
>> On 05.06.2018 02:07, Masahiro Yamada wrote:
>>> Hi Stefan
>>>
>>> 2018-06-05 6:49 GMT+09:00 Stefan Agner :
Hi Masahiro,
On 28.05.2018 11:22, Masahiro Yamada wrote:
> This will be useful to
On Mon, Jun 04, 2018 at 09:27:02PM +0200, Thibaut Robert wrote:
> Le lundi 04 juin 2018 à 10:55:49 (+0530), Ajay Singh a écrit :
> >
> > Thank you for submitting the patches.
> >
> > The modification in this patch looks okay to me.
> > Please resend this by including changes as suggested by Dan.
On Sun, May 20, 2018 at 12:07:22AM +0200, Maciej S. Szmigiero wrote:
> Currently, the code scanning a CPU equivalence table read from a microcode
> container file assumes that it actually contains a terminating zero entry,
> but if does not then the code will continue the scan past its valid data.
2018-06-05 14:50 GMT+09:00 Stefan Agner :
> On 05.06.2018 02:07, Masahiro Yamada wrote:
>> Hi Stefan
>>
>> 2018-06-05 6:49 GMT+09:00 Stefan Agner :
>>> Hi Masahiro,
>>>
>>> On 28.05.2018 11:22, Masahiro Yamada wrote:
This will be useful to specify the required compiler version,
like
On 05/06/2018 07:53, Viresh Kumar wrote:
> On 05-06-18, 07:48, Daniel Lezcano wrote:
>> As soon as we reach complete(), no timer can be set because of the
>> condition before.
>
> Why not ? We aren't using any locks here and it is possible that
> run_duration_ms
> is set to 0 from
>On Mon, Jun 04, 2018 at 02:01:34PM -0700, Casey Schaufler wrote:
>> On 6/1/2018 10:45 AM, Casey Schaufler wrote:
>> > Fix memory leak in smack_inode_getsecctx
>> >
>> > The implementation of smack_inode_getsecctx() made
>> > incorrect assumptions about how Smack presents a security
>> >
FYI, we noticed the following commit (built with gcc-5):
commit: f52001961d6e5c397e40c4d440103288cdce9a79 ("x86/vdso: Move out the CPU
number store")
url:
https://github.com/0day-ci/linux/commits/Chang-S-Bae/x86-Enable-FSGSBASE-instructions/20180602-125452
in testcase: boot
on test machine:
On Mon, Jun 4, 2018 at 8:33 AM, Thomas Gleixner wrote:
> The generic pending interrupt mechanism moves interrupts from the interrupt
> handler on the original target CPU to the new destination CPU. This is
> required for x86 and ia64 due to the way the interrupt delivery and
> acknowledge works
On Mon, Jun 4, 2018 at 8:33 AM, Thomas Gleixner wrote:
> Several people observed the WARN_ON() in irq_matrix_free() which triggers
> when the caller tries to free an vector which is not in the allocation
> range. Song provided the trace information which allowed to decode the root
> cause.
>
>
On Mon, May 28, 2018 at 1:25 PM, Paolo Bonzini wrote:
> On 26/05/2018 11:29, Dmitry Vyukov wrote:
>> KASAN: stack-out-of-bounds Read in do_general_protection
>> KASAN: slab-out-of-bounds Read in vmx_vcpu_run
>> KASAN: use-after-scope Read in vmx_vcpu_run
>> KASAN: stack-out-of-bounds Write in
On Sun, May 20, 2018 at 12:07:16AM +0200, Maciej S. Szmigiero wrote:
> Add verify_container(), verify_equivalence_table(), verify_patch_section()
> and verify_patch() functions to the AMD microcode update driver.
>
> These functions check whether a passed buffer contains the relevant
> structure,
On Sun, May 20, 2018 at 12:07:19AM +0200, Maciej S. Szmigiero wrote:
> Convert the late loader in the AMD microcode update driver to use newly
> introduced microcode container data checking functions as it was previously
> done for the early loader.
>
> Signed-off-by: Maciej S. Szmigiero
> ---
>
On Sun, May 20, 2018 at 12:07:17AM +0200, Maciej S. Szmigiero wrote:
> Convert the early loader in the AMD microcode update driver to use the
> container data checking functions introduced by the previous commit.
>
> We have to be careful to call these functions with 'early' parameter set,
> so
1 - 100 of 1606 matches
Mail list logo
