On 02/01/2018 08:57 AM, Jassi Brar wrote:
> On Thu, Feb 1, 2018 at 12:10 AM, Georgi Djakov
> wrote:
>>
>> Hi Jassi,
>>
>> On 01/27/2018 05:44 AM, Jassi Brar wrote:
>>> On Thu, Jan 4, 2018 at 10:26 PM, Georgi Djakov
>>> wrote:
Hi Jassi,
On 12/29/2017 08:14 AM, Jassi Brar wrote:
>>
On Saturday 20 January 2018 10:43 PM, David Lechner wrote:
> This adds a new driver for mach-davinci PLL clocks. This is porting the
> code from arch/arm/mach-davinci/clock.c to the common clock framework.
> Additionally, it adds device tree support for these clocks.
>
> The ifeq ($(CONFIG_COMMON_
Just now, I tried with fixed limit. But not work always.
For example: set the limit as 4GB on my platform with 8GB system memory, it can
pass.
But when run with platform with 16GB system memory, it failed since OOM.
And I guess it also depends on app's behavior.
I mean some apps make OS to use
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 255442c93843f52b6891b21d0b485bf2c97f93c3
commit: c1696fb85d33194cf65c7ebfc82a75696299c3a3 GFS2: Introduce new
gfs2_log_header_v2
date: 9 days ago
config: x86_64-randconfig-a0-02011154 (attached as .config)
dmi_init() rightfully checks if dmi is available at all, and errors out
if not. This leads to harmless errors being printed during boot on
non-efi systems, even when these are booted quietly.
Avoid this error-print by returning directly from dmi_init() if dmi
isn't available, instead of jumping to
On Saturday 20 January 2018 10:43 PM, David Lechner wrote:
> This adds platform-specific declarations for the PLL clocks on TI DA830/
> OMAP-L137/AM17XX SoCs.
>
> Signed-off-by: David Lechner
Reviewed-by: Sekhar Nori
Thanks,
Sekhar
On Wed, Jan 31, 2018 at 10:54 AM, tip-bot for Thomas Gleixner
wrote:
> Commit-ID: 55595980acc3232b018ba30df8ee6e0ac40ad184
> Gitweb:
> https://git.kernel.org/tip/55595980acc3232b018ba30df8ee6e0ac40ad184
> Author: Thomas Gleixner
> AuthorDate: Tue, 30 Jan 2018 19:36:32 +0100
> Committer:
On Thu 01-02-18 06:13:20, He, Roger wrote:
> Hi Michal:
>
> How about only
> EXPORT_SYMBOL_GPL(total_swap_pages) ?
I've already expressed that messing up with the amount of swap pages is
a wrong approach. You should scale your additional buffers according the
the current memory pressure. There
On 01.02.2018 00:55, Josh Poimboeuf wrote:
On Fri, Jan 26, 2018 at 01:33:04PM +0300, Evgenii Shatokhin wrote:
+ The callbacks from the replaced patches are not called. It would be
pretty hard to define a reasonable semantic and implement it.
At least, it surely simplifies error handl
On Wed, Jan 31, 2018 at 04:06:37AM -0500, Paul Moore wrote:
> On Tue, Jan 30, 2018 at 5:46 PM, Greg KH wrote:
> > On Tue, Jan 30, 2018 at 11:00:04AM -0800, Mark Salyzyn wrote:
> >> On 01/19/2018 09:41 AM, Stephen Smalley wrote:
> >> > If we can't safely dereference the sock in these hooks, then th
On 01.02.2018 08:50, Krzysztof Kozlowski wrote:
> On Wed, Jan 31, 2018 at 4:57 PM, Andrzej Hajda wrote:
>> OF graph describes USB data lanes between USB-PHY and respective MUIC.
>> Since graph is present and DWC driver can use it to get extcon, obsolete
>> extcon property can be removed.
>>
>> Sig
On Tue, Jan 30, 2018 at 10:12:51AM +0100, Marta Rybczynska wrote:
> Hello Mellanox maintainers,
> I'd like to ask you to OK backporting two patches in mlx5 driver to 4.9 stable
> tree (they're in master for some time already).
>
> We have multiple deployment in 4.9 that are running into the bug fi
On Wed, Jan 31, 2018 at 09:39:51PM -0800, Quytelda Kahja wrote:
> Removed parenthesis causing a coding style warning.
>
> Signed-off-by: Quytelda Kahja
> ---
> drivers/staging/fwserial/dma_fifo.c | 2 +-
> drivers/staging/fwserial/fwserial.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletion
Replace the original license statement with the SPDX identifier.
Add also one line of description as recommended by the COPYING
file.
Signed-off-by: Andi Shyti
---
drivers/input/touchscreen/mms114.c | 13 +
1 file changed, 5 insertions(+), 8 deletions(-)
diff --git a/drivers/input/t
The driver has been released with GNU Public License v2 as stated
in the header, but the module license information has been tagged
as "GPL" (GNU Public License v2 or later).
Fix the module license information so that it matches the one in
the header as "GPL v2".
Fixes: 07b8481d4aff ("Input: add
Hi Dmitry,
I will send this two as a new patchset. The first one is the
messed SPDX patch that you reverted, the second one is about the
license incohorency that Marcus has pointed out.
Andi
Andi Shyti (2):
Input: mms114 - add SPDX identifier
Input: mms114 - fix license module information
On Wed, Jan 31, 2018 at 08:03:00AM +0100, Dominik Brodowski wrote:
> On Tue, Jan 30, 2018 at 02:39:45PM -0800, tip-bot for Tim Chen wrote:
> > Commit-ID: 18bf3c3ea8ece8f03b6fc58508f2dfd23c7711c7
> > Gitweb:
> > https://git.kernel.org/tip/18bf3c3ea8ece8f03b6fc58508f2dfd23c7711c7
> > Author:
On 01/02/2018 08:57, Vincent Guittot wrote:
> On 31 January 2018 at 16:27, Daniel Lezcano wrote:
>> On 31/01/2018 10:56, Vincent Guittot wrote:
>>> On 31 January 2018 at 10:50, Daniel Lezcano
>>> wrote:
On 31/01/2018 10:46, Vincent Guittot wrote:
> On 31 January 2018 at 10:33, Daniel Le
On Wed, Jan 31, 2018 at 02:47:53PM +, Liviu Dudau wrote:
> On Wed, Jan 31, 2018 at 08:42:12AM +0100, Maxime Ripard wrote:
> > On Wed, Jan 31, 2018 at 03:08:08AM +, Liviu Dudau wrote:
> > > On Fri, Jan 26, 2018 at 11:00:41AM +0800, Yong wrote:
> > > > Hi Maxime,
> > > >
> > > > On Fri, 26 J
On Wed, 2018-01-31 at 08:03 +0100, Dominik Brodowski wrote:
> Whether a process needs protection by IBPB on context switches is a
> different question to whether a process should be allowed to be dumped,
> though the former may be a superset of the latter. Enable IBPB on all
> context switches to a
On 02/01/2018 02:02 AM, Michal Hocko wrote:
> On Wed 31-01-18 12:12:17, Andrew Morton wrote:
>> On Wed, 31 Jan 2018 08:58:52 +0100 Michal Hocko wrote:
>>
>>> On Wed 31-01-18 07:55:05, Anshuman Khandual wrote:
On 01/30/2018 01:29 PM, Michal Hocko wrote:
> On Tue 30-01-18 08:37:14, Anshuman
On Wed, Jan 31, 2018 at 07:58:01AM -0800, syzbot wrote:
> Hello,
>
> syzbot hit the following crash on upstream commit
> 72906f38934a49faf4d2d38ea9ae32adcf7d5d0c (Tue Jan 30 21:04:50 2018 +)
> Merge branch 'x86-hyperv-for-linus' of
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
>
> S
On Wed, 2018-01-31 at 15:01 -0800, Stephen Hemminger wrote:
> On Wed, 31 Jan 2018 12:16:49 +0100
> Mohammed Gamal wrote:
>
> > On Tue, 2018-01-30 at 11:29 -0800, Stephen Hemminger wrote:
> > > On Tue, 23 Jan 2018 10:34:04 +0100
> > > Mohammed Gamal wrote:
> > >
> > > > Split each of the funct
Stephane reported that we don't set properly PERIOD
sample type for events with period term defined.
Before:
$ perf record -e cpu/cpu-cycles,period=1000/u ls
$ perf evlist -v
cpu/cpu-cycles,period=1000/u: ... sample_type: IP|TID|TIME|PERIOD, ...
After:
$ perf record -e cpu/cpu-cycles,peri
Stephan reported we don't unset PERIOD sample type
when --no-period is specified. Adding the unset
check and reset PERIOD if --no-period is specified.
Reported-by: Stephane Eranian
Link: http://lkml.kernel.org/n/tip-b89ggszz9x26hm7ztor29...@git.kernel.org
Signed-off-by: Jiri Olsa
---
tools/perf
Stephan reported that we don't support period for
enabling large PEBS data, which there's no reason
for. Adding PERF_SAMPLE_PERIOD into freerunning
flags.
Reported-by: Stephane Eranian
Link: http://lkml.kernel.org/n/tip-hx5yqua1c9u7iewm3h8fr...@git.kernel.org
Signed-off-by: Jiri Olsa
---
arch/x
hi,
Stephan reported that we don't support period for
enabling large PEBS data, which there's no reason
for. Sending fix for that plus related perf tool
period fixes Stephan reported.
thanks,
jirka
---
Jiri Olsa (3):
perf tools: Fix period/freq terms setup
perf record: Fix period opt
On Thu, Feb 1, 2018 at 9:19 AM, Andrzej Hajda wrote:
> On 01.02.2018 08:50, Krzysztof Kozlowski wrote:
>> On Wed, Jan 31, 2018 at 4:57 PM, Andrzej Hajda wrote:
>>> OF graph describes USB data lanes between USB-PHY and respective MUIC.
>>> Since graph is present and DWC driver can use it to get ex
>
> On Fri, Jan 19, 2018 at 07:38:22AM +, 冯锐 wrote:
> > > On Wed, Dec 27, 2017 at 05:37:50PM -0600, Bjorn Helgaas wrote:
> > > > On Tue, Dec 19, 2017 at 08:15:24AM +, 冯锐 wrote:
> > > > > > On Fri, Dec 15, 2017 at 09:42:45AM +, 冯锐 wrote:
> > > > > > > > [+cc Hans, Dave, linux-pci]
> > >
On 01/29/2018, 01:56 PM, Greg Kroah-Hartman wrote:
> 4.4-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Rafael J. Wysocki
>
> commit c2a6bbaf0c5f90463a7011a295bbdb7e33c80b51 upstream.
>
> The way acpi_find_child_device() works currently
---
v2->v3
- Update the KCS phase state machine.
- Fix the race condition of read/write.
v1->v2
- Divide the driver into two parts, one handles the BMC KCS IPMI 2.0 state;
the other handles the BMC KCS controller such as AST2500 IO accessing.
- Use the spin lock APIs to handle the device file
The KCS (Keyboard Controller Style) interface is used to perform in-band
IPMI communication between a server host and its BMC (BaseBoard Management
Controllers).
This driver exposes the KCS interface on ASpeed SOCs (AST2400 and AST2500)
as a character device. Such SOCs are commonly used as BMCs an
On 01/02/18 02:40, Hanjun Guo wrote:
> On 2018/1/31 23:05, Marc Zyngier wrote:
>> On 31/01/18 14:38, Ard Biesheuvel wrote:
>>> On 31 January 2018 at 14:35, Ard Biesheuvel
>>> wrote:
On 31 January 2018 at 14:11, Marc Zyngier wrote:
> On 31/01/18 13:56, Hanjun Guo wrote:
>> Hi Marc,
>
Hi,
On 1/31/2018 6:39 PM, Robin Murphy wrote:
On 19/01/18 11:43, Vivek Gautam wrote:
From: Sricharan R
Finally add the device link between the master device and
smmu, so that the smmu gets runtime enabled/disabled only when the
master needs it. This is done from add_device callback which get
On Thu, Feb 01, 2018 at 10:51:14AM +1100, Stephen Rothwell wrote:
> Hi Bjorn,
>
> After merging the pci tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> drivers/pci/dwc/pcie-designware-ep.c: In function 'dw_pcie_ep_raise_msi_irq':
> drivers/pci/dwc/pcie-designware-e
Add of dependency for STM32 ASoC drivers.
DFSDM of dependency is already inherited
from STM32_DFSDM_ADC dependency.
Signed-off-by: olivier moysan
---
sound/soc/stm/Kconfig | 3 +++
1 file changed, 3 insertions(+)
diff --git a/sound/soc/stm/Kconfig b/sound/soc/stm/Kconfig
index 3ad881f..b5375f9
From: Oleksandr Andrushchenko
Hi, all!
While working on DRM PV frontend driver I faced an issue with
driver removal, e.g. when driver's .remove callback is called
the driver is already disconnected form the xenbus and it is not
possible to synchronize the process of removal with the backend.
Bac
On 02/01/2018, 09:46 AM, Jiri Slaby wrote:
> On 01/29/2018, 01:56 PM, Greg Kroah-Hartman wrote:
>> 4.4-stable review patch. If anyone has any objections, please let me know.
>>
>> --
>>
>> From: Rafael J. Wysocki
>>
>> commit c2a6bbaf0c5f90463a7011a295bbdb7e33c80b51 upstream.
>>
>
From: Oleksandr Andrushchenko
Current xenbus frontend driver removal flow first disconnects
the driver from xenbus and then calls driver's remove callback.
This makes it impossible for the driver to listen to backend's
state changes and synchronize the removal procedure.
Fix this by removing oth
On 01/31/18 22:45, Chintan Pandya wrote:
>
>
> On 2/1/2018 1:35 AM, frowand.l...@gmail.com wrote:
>> From: Frank Rowand
>
>> +
>> +static void of_populate_phandle_cache(void)
>> +{
>> + unsigned long flags;
>> + phandle max_phandle;
>> + u32 nodes = 0;
>> + struct device_node *np;
>
On Saturday 20 January 2018 10:43 PM, David Lechner wrote:
> This adds platform-specific declarations for the PLL clocks on TI DA850/
> OMAP-L138/AM18XX SoCs.
>
> Signed-off-by: David Lechner
> +static const struct davinci_pll_clk_info da850_pll1_info __initconst = {
> + .name = "pll1",
> +
On Wed, Jan 31, 2018 at 08:03:10AM -0800, Andy Lutomirski wrote:
> flush_tlb_single() and flush_tlb_one() sound almost identical, but
> they really mean "flush one user translation" and "flush one kernel
> translation". Rename them to flush_tlb_one_user() and
> flush_tlb_one_kernel() to make the s
Hi Fabio, Andy,
Thanks a lot for your comments. I will address them and send v2.
Few comments inline.
On Mi, 2018-01-31 at 18:12 +0200, Andy Shevchenko wrote:
> On Wed, Jan 31, 2018 at 2:57 PM, Daniel Baluta wrote:
> >
> > AK5558 is a 32-bit, 768 kHZ sampling, differential input ADC
> > for di
This is a fix against the issue that crash dump kernel may hang up
during booting, which can happen on any ACPI-based system with "ACPI
Reclaim Memory."
(kernel messages after panic kicked off kdump)
(snip...)
Bye!
(snip...)
ACPI: Core revision 20170728
On Thu, Feb 01, 2018 at 09:54:41AM +0100, Olivier Moysan wrote:
> Add of dependency for STM32 ASoC drivers.
> DFSDM of dependency is already inherited
> from STM32_DFSDM_ADC dependency.
>
> Signed-off-by: olivier moysan
> ---
> sound/soc/stm/Kconfig | 3 +++
> 1 file changed, 3 insertions(+)
>
On Wed, Jan 31, 2018 at 09:44:18AM -0800, Srinivas Pandruvada wrote:
> Much more throttling required compared to PERF_CTL. MSR_HWP_REQUEST is
> much slower compared to PERF_CTL (as high as 10:1).
Still much better than what other architectures have to deal with ;-)
On Thu, Feb 01, 2018 at 08:50:28AM +0100, Rafael J. Wysocki wrote:
> On Wednesday, January 31, 2018 11:17:10 AM CET Peter Zijlstra wrote:
> > On Wed, Jan 31, 2018 at 10:22:49AM +0100, Rafael J. Wysocki wrote:
> > > On Tuesday, January 30, 2018 2:15:31 PM CET Peter Zijlstra wrote:
> >
> > > > IA32_
On Saturday 20 January 2018 10:43 PM, David Lechner wrote:
> +void __init dm355_pll_clk_init(void __iomem *pll1, void __iomem *pll2)
> +{
> + const struct davinci_pll_sysclk_info *info;
> +
> + davinci_pll_clk_register(&dm355_pll1_info, "ref_clk", pll1);
> +
> + for (info = dm355_pll1_s
On Thu, Feb 1, 2018 at 9:32 AM, Maxime Ripard
wrote:
> On Wed, Jan 31, 2018 at 02:47:53PM +, Liviu Dudau wrote:
>> On Wed, Jan 31, 2018 at 08:42:12AM +0100, Maxime Ripard wrote:
>> > On Wed, Jan 31, 2018 at 03:08:08AM +, Liviu Dudau wrote:
>> > > On Fri, Jan 26, 2018 at 11:00:41AM +0800, Y
On Thu, Jun 16, 2016 at 11:03 AM, Arnd Bergmann wrote:
> A newly introduced function has 'const int' as the return type,
> but as "make W=1" reports, that has no meaning:
>
> drivers/md/dm-raid.c:510:18: error: type qualifiers ignored on function
> return type [-Werror=ignored-qualifiers]
>
> Thi
On Saturday 20 January 2018 10:43 PM, David Lechner wrote:
> +
> +void __init dm365_pll_clk_init(void __iomem *pll1, void __iomem *pll2)
> +{
> + const struct davinci_pll_sysclk_info *info;
> +
> + davinci_pll_clk_register(&dm365_pll1_info, "ref_clk", pll1);
> +
> + davinci_pll_auxclk_r
With the removal of AVR platforms, code related to platform stuff
is useless.
Signed-off-by: Ludovic Desroches
---
drivers/usb/gadget/udc/atmel_usba_udc.c | 73 +
1 file changed, 2 insertions(+), 71 deletions(-)
diff --git a/drivers/usb/gadget/udc/atmel_usba_udc.
From: Markus Elfring
Date: Thu, 1 Feb 2018 10:20:47 +0100
The deletion for a call of the function "memset" depends on
the specification that a size determination is passed by
the expression "E1".
The function "kmem_cache_alloc" was specified despite of the technical
detail that this function does
Use GPIO descriptors instead of relying on the old method.
Include irq.h header since it is needed and was indirectly
included through of_gpio.h.
Signed-off-by: Ludovic Desroches
---
drivers/usb/gadget/udc/atmel_usba_udc.c | 51 ++---
drivers/usb/gadget/udc/atmel_usba
On Wed, Jan 31, 2018 at 09:38:46PM -0800, Nadav Amit wrote:
> I used ftrace to measure the execution time of flush_tlb_func_remote() on a
> 2-socket Haswell machine, using a microbenchmark I wrote for some research
> project.
However cool ftrace is, it is _really_ bad for such uses. The cost of
u
On 01/31/2018 07:44 AM, Michael S. Tsirkin wrote:
On Fri, Jan 26, 2018 at 11:31:19AM +0800, Wei Wang wrote:
On 01/26/2018 10:42 AM, Michael S. Tsirkin wrote:
On Fri, Jan 26, 2018 at 09:40:44AM +0800, Wei Wang wrote:
On 01/25/2018 09:49 PM, Michael S. Tsirkin wrote:
On Thu, Jan 25, 2018 at 05:
On Thu, 1 Feb 2018, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Thu, 1 Feb 2018 10:20:47 +0100
>
> The deletion for a call of the function "memset" depends on
> the specification that a size determination is passed by
> the expression "E1".
> The function "kmem_cache_alloc" was spec
Correct spelling of "coccinelle".
Signed-off-by: Julia Lawall
---
scripts/coccicheck |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/coccicheck b/scripts/coccicheck
index ecfac64..9fedca6 100755
--- a/scripts/coccicheck
+++ b/scripts/coccicheck
@@ -177,7 +177,7 @@
On Mon, Jan 29, 2018 at 01:01:30PM -0600, Rob Herring wrote:
> On Mon, Jan 22, 2018 at 09:37:38AM +0100, Linus Walleij wrote:
> > On Thu, Jan 18, 2018 at 5:02 PM, Ludovic Desroches
> > wrote:
> >
> > > Add support for the drive-strength property. Usually its value is
> > > expressed in mA. Since
On Tue, 30 Jan 2018 23:30:17 +0530
Shreeya Patel wrote:
> iio_dev->mlock is to be used only by the IIO core for protecting
> device mode changes between INDIO_DIRECT and INDIO_BUFFER.
>
> This patch replaces the use of mlock with the already established
> buf_lock mutex.
>
> Introducing 'unlock
On Thu, 1 Feb 2018, Geert Uytterhoeven wrote:
> On Wed, Jan 31, 2018 at 10:54 AM, tip-bot for Thomas Gleixner
> > -void irq_activate_and_startup(struct irq_desc *desc, bool resend)
> > +int irq_activate_and_startup(struct irq_desc *desc, bool resend)
> > {
> > if (WARN_ON(irq_activate(desc
On Saturday 20 January 2018 10:43 PM, David Lechner wrote:
> This adds a new driver for mach-davinci PSC clocks. This is porting the
> code from arch/arm/mach-davinci/psc.c to the common clock framework and
> is converting it to use regmap to simplify the code. Additionally, it
> adds device tree s
Commit-ID: 9bc43be5151aaf1aa87f832128f1687341f07483
Gitweb: https://git.kernel.org/tip/9bc43be5151aaf1aa87f832128f1687341f07483
Author: Thomas Gleixner
AuthorDate: Tue, 30 Jan 2018 19:36:32 +0100
Committer: Thomas Gleixner
CommitDate: Thu, 1 Feb 2018 10:54:48 +0100
genirq: Make legacy
Commit-ID: 085331dfc6bbe3501fb936e657331ca943827600
Gitweb: https://git.kernel.org/tip/085331dfc6bbe3501fb936e657331ca943827600
Author: Dan Williams
AuthorDate: Wed, 31 Jan 2018 17:47:03 -0800
Committer: Thomas Gleixner
CommitDate: Thu, 1 Feb 2018 10:59:10 +0100
x86/kvm: Update spectre
I have just created since-4.15 branch in mm git tree
(http://git.kernel.org/?p=linux/kernel/git/mhocko/mm.git;a=summary). It
is based on v4.15 tag in Linus tree and mmotm-2018-01-31-16-51 +
I have pulled libnvdimm-for-next branch from the nvdim tree. Let me know
if I should pull some other trees t
On Wed, Jan 31, 2018 at 05:09:48PM -0800, Nitin Gupta wrote:
> >
> > It's non-trivial to do this because at minimum a page fault has to check
> > if there is a potential promotion candidate by checking the PTEs around
> > the faulting address searching for a correctly-aligned base page that is
> >
On Wed, 31 Jan 2018, Michal Hocko wrote:
> > > > > root
> > > > > / | \
> > > > > A B C
> > > > >/ \/ \
> > > > > D E F G
> > > > >
> > > > > Assume A: cgroup, B: oom_group=1, C: tree, G: oom_group=1
> > > > >
> > > >
> > > > At each level o
From: Sean Wang
document the binding for enabling SCPSYS on MediaTek MT7623 and MT7623A
SoC. Where MT7623 SoC has the same definition about power domains with
MT2701, so it's fine to using MT2701 ones as MT7623's fallback.
Signed-off-by: Sean Wang
---
Documentation/devicetree/bindings/soc/medi
From: Sean Wang
Add SCPSYS power domain driver for MT7623A SoC. The MT7623A's power
domains are the subset of MT7623 SoC's ones. As MT7623 SoC has full
features whereas MT7623A is being designed just for router applications.
Thus, MT7623A doesn't include those power domains multimedia function
be
> > The question you need to ask is 'can it overflow 32bit maths', otherwise
> > you are potentially making the system do extra work for no reason.
> >
>
> Yeah, I get your point and it seems that in this particular case there
> is no risk of a 32bit overflow, but in general and IMHO as the code
>
On Sat, Jan 27, 2018 at 11:07:09PM +0100, Giulio Benetti wrote:
> > > > > I don't really know what the polarity of D0 would be just by
> > > > > judging at that capture, but we would have noticed if the colors
> > > > > were inverted for quite some time now.
> > > >
> > > > D0-D23 are correct.
> >
Commit-ID: 1beaeacdc88b537703d04d5536235d0bbb36db93
Gitweb: https://git.kernel.org/tip/1beaeacdc88b537703d04d5536235d0bbb36db93
Author: Thomas Gleixner
AuthorDate: Tue, 30 Jan 2018 19:36:32 +0100
Committer: Thomas Gleixner
CommitDate: Thu, 1 Feb 2018 11:09:40 +0100
genirq: Make legacy
On Thu, Feb 01, 2018 at 03:19:56PM +0800, Baoquan He wrote:
> In sparse_init(), we allocate usemap_map and map_map which are pointer
> array with the size of NR_MEM_SECTIONS. The memory consumption can be
> ignorable in 4-level paging mode. While in 5-level paging, this costs
> much memory, 512M. K
Some files use both a non-devm allocation and a devm_allocation. Don't
complain about a free when the same function contains a non-devm
allocation.
Signed-off-by: Julia Lawall
---
scripts/coccinelle/free/devm_free.cocci | 55 +++-
1 file changed, 54 insertions(+),
>> The function "kmem_cache_alloc" was specified despite of the technical
>> detail that this function does not get a parameter passed which would
>> correspond to such a size information.
>>
>> Thus remove it from the first two SmPL rules and omit the rule "r4".
>
> Nack.
I find such a rejection
With gcc-4.1.2:
crypto/sha3_generic.c:39: warning: ‘__optimize__’ attribute directive
ignored
Use the newly introduced __optimize macro to fix this.
Fixes: 83dee2ce1ae791c3 ("crypto: sha3-generic - rewrite KECCAK transform to
help the compiler optimize")
Signed-off-by: Geert Uytterhoeven
Create a new function attribute __optimize, which allows to specify an
optimization level on a per-function basis.
Signed-off-by: Geert Uytterhoeven
---
I assume this is supported as of gcc-4.4:
- gcc version 4.3.3 (GCC): warning: ‘__optimize__’ attribute directive
ignored
- gcc version 4
Gcc versions before 4.4 do not recognize the __optimize__ compiler
attribute:
warning: ‘__optimize__’ attribute directive ignored
Fixes: 7375ae3a0b79ea07 ("compiler-gcc.h: Introduce __nostackprotector function
attribute")
Signed-off-by: Geert Uytterhoeven
---
Can anyone please verify this?
With gcc-4.1.2:
fs/xfs/scrub/agheader.c: In function ‘xfs_scrub_agfl’:
fs/xfs/scrub/agheader.c:770: warning: missing braces around initializer
fs/xfs/scrub/agheader.c:770: warning: (near initialization for ‘sai.oinfo’)
The first member of struct xfs_scrub_agfl_info is no longer an int
With gcc-4.1.2.:
net/bridge/br_fdb.c: In function ‘br_fdb_sync_static’:
net/bridge/br_fdb.c:996: warning: ‘err’ may be used uninitialized in this
function
Indeed, if the list is empty, err will be uninitialized, and will be
propagated up as the function return value.
Fix this by preinit
With gcc-4.1.2:
net/ipv4/inet_hashtables.c: In function ‘inet_unhash’:
net/ipv4/inet_hashtables.c:628: warning: ‘ilb’ may be used uninitialized in
this function
While this is a false positive, it can easily be avoided by using the
pointer itself as the canary variable.
Signed-off-by: Ge
On Thu, 1 Feb 2018, SF Markus Elfring wrote:
> >> The function "kmem_cache_alloc" was specified despite of the technical
> >> detail that this function does not get a parameter passed which would
> >> correspond to such a size information.
> >>
> >> Thus remove it from the first two SmPL rules a
On Thu, Jan 25, 2018 at 09:13:03PM +, Mel Gorman wrote:
> On Thu, Jan 25, 2018 at 11:41:03AM -0800, Nitin Gupta wrote:
> > >> It's not really about memory scarcity but a more efficient use of it.
> > >> Applications may want hugepage benefits without requiring any changes to
> > >> app code whi
On Thu, Feb 01, 2018 at 01:04:45AM +, Jolly Shah wrote:
> > > +Xilinx Zynq MPSoC Firmware Device Tree Bindings
> > > +
> > > +The zynqmp-firmware node describes the interface to platform firmware.
> >
> > Is there any documentation for this that can be referred to?
> >
>
> Will add more infor
On Thu, Feb 01, 2018 at 09:57:21AM +0100, Jiri Slaby wrote:
> On 02/01/2018, 09:46 AM, Jiri Slaby wrote:
> > On 01/29/2018, 01:56 PM, Greg Kroah-Hartman wrote:
> >> 4.4-stable review patch. If anyone has any objections, please let me know.
> >>
> >> --
> >>
> >> From: Rafael J. Wys
On Thu, Feb 1, 2018 at 9:34 AM, Steffen Klassert
wrote:
> On Wed, Jan 31, 2018 at 07:58:01AM -0800, syzbot wrote:
>> Hello,
>>
>> syzbot hit the following crash on upstream commit
>> 72906f38934a49faf4d2d38ea9ae32adcf7d5d0c (Tue Jan 30 21:04:50 2018 +)
>> Merge branch 'x86-hyperv-for-linus' of
On Thu, Feb 01, 2018 at 10:48:52AM +0100, Julia Lawall wrote:
> Some files use both a non-devm allocation and a devm_allocation. Don't
> complain about a free when the same function contains a non-devm
> allocation.
>
> Signed-off-by: Julia Lawall
>
That's surprising... Do you have an example
Anyways, will fix this locally and share test results.
Thanks, I look forward to the results.
Set up for this time was slightly different. So, taken all the numbers
again.
Boot to shell time (in ms): Experiment 2
[1] Base: 14.843805 14.784842 14.842338
[2] 64 size
The documentation was mentioning the "future SCHED EDF" as the
solution for fine-grained control of deadline/period. This patch
updates this citing the (now) existing SCHED_DEADLINE.
Signed-off-by: Daniel Bristot de Oliveira
Cc: Jonathan Corbet
Cc: Juri Lelli
Cc: Luca Abeni
Cc: Tommaso Cucinot
On Thu, Feb 01, 2018 at 01:23:48AM +, Jolly Shah wrote:
> Hi Mark,
> Thanks for the review,
>
> > -Original Message-
> > From: Mark Rutland [mailto:mark.rutl...@arm.com]
> > Sent: Wednesday, January 31, 2018 10:20 AM
> > To: Jolly Shah
> > Cc: ard.biesheu...@linaro.org; mi...@kernel.o
Hi Shanker,
On Wed, Jan 31, 2018 at 06:03:42PM -0600, Shanker Donthineni wrote:
> A DMB instruction can be used to ensure the relative order of only
> memory accesses before and after the barrier. Since writes to system
> registers are not memory operations, barrier DMB is not sufficient
> for obs
On Tue, Jan 16, 2018 at 03:22:18PM +, Don Brace wrote:
> > -Original Message-
> > From: Laurence Oberman [mailto:lober...@redhat.com]
> > Sent: Tuesday, January 16, 2018 7:29 AM
> > To: Thomas Gleixner ; Ming Lei
> > Cc: Christoph Hellwig ; Jens Axboe ;
> > linux-bl...@vger.kernel.org;
Commit fd8aa9095a95 ("xen: optimize xenbus driver for multiple concurrent
xenstore accesses") optimized xenbus concurrent accesses but in doing so
may have broke UABI of /dev/xen/xenbus. Through /dev/xen/xenbus
applications are in charge of exchange xenbus message exchange with the
correct header a
We treat most of the feature bits in the ID registers as STRICT,
implying that all CPUs should match it the boot CPU state. However,
for most of the features, we can handle if there are any mismatches
by using the safe value. e.g, HWCAPs and other features used by the
kernel. Relax the constraint o
Expose the new features introduced by Arm v8.4 extensions to
Arm v8-A profile.
These include :
1) Data indpendent timing of instructions. (DIT, exposed as HWCAP_DIT)
2) Unaligned atomic instructions and Single-copy atomicity of loads
and stores. (AT, expose as HWCAP_USCAT)
3) LDAPR and STL
On Thu, Feb 01, 2018 at 03:43:58PM +0800, kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
> rcu/dev
> head: 32860a6da7c75039afea229ba396aeac3b708d6b
> commit: 32860a6da7c75039afea229ba396aeac3b708d6b [48/48] EXP rcu: Add
> trace_printk()s
On Thu, Feb 1, 2018 at 11:30 AM, Dmitry Vyukov wrote:
> On Thu, Feb 1, 2018 at 9:34 AM, Steffen Klassert
> wrote:
>> On Wed, Jan 31, 2018 at 07:58:01AM -0800, syzbot wrote:
>>> Hello,
>>>
>>> syzbot hit the following crash on upstream commit
>>> 72906f38934a49faf4d2d38ea9ae32adcf7d5d0c (Tue Jan 3
Most callers of put_cmsg() use a "sizeof(foo)" for the length argument.
Within put_cmsg(), a copy_to_user() call is made with a dynamic size, as a
result of the cmsg header calculations. This means that hardened usercopy
will examine the copy, even though it was technically a fixed size and
should
This patchset adds non-alpha color format support taking into
account older hw versions.
Philippe Cornu (2):
drm/stm: ltdc: add non-alpha color formats
drm/stm: ltdc: remove non-alpha color formats on layer 2 for older hw
drivers/gpu/drm/stm/ltdc.c | 53 ++
ltdc supports natively some color formats with alpha (like
ARGB, ARGB1555, ARGB...). Related non-alpha formats are
supported too (ARGB->XRGB, ARGB->XRGB...) by
adjusting ltdc blending factors.
Note: Wayland/Weston requests by default the non-alpha XRGB
color format.
Si
1 - 100 of 788 matches
Mail list logo
