From: Gabriel Fernandez
This patch adds the RTC clock.
Signed-off-by: Gabriel Fernandez
---
drivers/clk/clk-stm32mp1.c | 17 +
1 file changed, 17 insertions(+)
diff --git a/drivers/clk/clk-stm32mp1.c b/drivers/clk/clk-stm32mp1.c
index 5a1142c..1cb06b0 100644
--- a/drivers/clk/
From: Gabriel Fernandez
STMP32MP1 has 4 PLLs.
PLL supports integer and fractional mode.
Each PLL has 3 output dividers (p, q, r)
Signed-off-by: Gabriel Fernandez
---
drivers/clk/clk-stm32mp1.c | 209 +
1 file changed, 209 insertions(+)
diff --git a/
From: Gabriel Fernandez
This patch adds the clock binding entry for STM32MP1
Signed-off-by: Gabriel Fernandez
---
include/dt-bindings/clock/stm32mp1-clks.h | 248 ++
1 file changed, 248 insertions(+)
create mode 100644 include/dt-bindings/clock/stm32mp1-clks.h
dif
From: Gabriel Fernandez
MP1 Gate is a gate with a set and a clear register.
This patch also introduces divider and fixed factor clocks.
Signed-off-by: Gabriel Fernandez
---
drivers/clk/clk-stm32mp1.c | 186 +
1 file changed, 186 insertions(+)
diff -
On Fri, Feb 02, 2018 at 01:46:47PM +0100, Peter Zijlstra wrote:
> +static void __intel_pstate_hwp_set_desired(int val)
> +{
> + u64 value;
> +
> + value = rdmsrl(MSR_HWP_REQUEST);
> + value &= ~GENMASK_ULL(23, 16);
> + value |= (val & 0xff) << 16;
> + wrmsrl(MSR_HWP_REQUEST, va
On 02/02/18 13:25, Smitha T Murthy wrote:
> Add HEVC encoder support and necessary registers, V4L2 CIDs,
> and hevc encoder parameters
>
> Signed-off-by: Smitha T Murthy
> Acked-by: Hans Verkuil
Not quite, one last comment:
> ---
> drivers/media/platform/s5p-mfc/regs-mfc-v10.h | 28 +-
> d
On 31.01.2018 19:42, Quentin Schulz wrote:
Hi Philipp,
On Mon, Jan 29, 2018 at 12:29:09AM +0100, Philipp Rossak wrote:
For adding newer sensor some basic rework of the code is necessary.
This patch reworks the driver to be able to handle more than one
thermal sensor. Newer SoC like the A80 h
On 2/1/2018 9:29 PM, ebied...@xmission.com wrote:
> Khalid Aziz writes:
>
>> V11 changes:
>> This series is same as v10 and was simply rebased on 4.15 kernel. Can
>> mm maintainers please review patches 2, 7, 8 and 9 which are arch
>> independent, and include/linux/mm.h and mm/ksm.c changes in pa
On Saturday 20 January 2018 10:43 PM, David Lechner wrote:
> void __init da830_init_time(void)
> {
> +#ifdef CONFIG_COMMON_CLK
> + void __iomem *pll0, *psc0, *psc1;
> + struct clk *clk;
> +
> + pll0 = ioremap(DA8XX_PLL0_BASE, SZ_4K);
> + psc0 = ioremap(DA8XX_PSC0_BASE, SZ_4K);
> +
I was planning to annotate the opaque calculation in
__fragmentation_index() but on closer inspection I think there may be a
bug. I could use some feedback.
Firstly, for the case of fragmentation and ignoring the scaling,
__fragmentation_index() purports to return a value in the range 0 to 1.
Gen
Hi Mathieu,
On Thu, 1 Feb 2018 09:51:02 -0700
Mathieu Poirier wrote:
> This is the follow-up patchset to [1] that attempt to fix a problem
> reported by Steve Rostedt [2] where DL bandwidth accounting is not
> recomputed after CPUset and CPU hotplug operations. When CPU hotplug and
> some CUPs
On Fri 2018-02-02 13:17:08, Petr Mladek wrote:
> On Thu 2018-02-01 11:46:47, Sergey Senozhatsky wrote:
> > On (01/30/18 13:23), Petr Mladek wrote:
> > [..]
> > > > If the system is in "big troubles" then what makes irq_work more
> > > > possible? Local IRQs can stay disabled, just like preemption.
From: Markus Elfring
Date: Fri, 2 Feb 2018 15:18:29 +0100
Two update suggestions were taken into account
from static source code analysis.
Markus Elfring (2):
Delete an error message for a failed memory allocation
Improve a size determination
drivers/i2c/busses/i2c-sh7760.c | 3 +--
1 file
From: Markus Elfring
Date: Fri, 2 Feb 2018 11:46:02 +0100
Omit an extra message for a memory allocation failure in this function.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
drivers/i2c/busses/i2c-sh7760.c | 1 -
1 file changed, 1 deletion(-)
d
On Saturday 20 January 2018 10:44 PM, David Lechner wrote:
> void __init da850_init_time(void)
> {
> +#ifdef CONFIG_COMMON_CLK
> + void __iomem *pll0, *pll1, *psc0, *psc1;
> + struct regmap *cfgchip;
> + struct clk *clk;
> + struct clk_hw *parent;
> +
> + pll0 = ioremap(DA8XX_
From: Markus Elfring
Date: Fri, 2 Feb 2018 14:50:09 +0100
Replace the specification of a data structure by a pointer dereference
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding style convention.
This issue was dete
From: Archana Sathyakumar
Log key PDC pin configuration in FTRACE.
Cc: Steven Rostedt
Signed-off-by: Archana Sathyakumar
Signed-off-by: Lina Iyer
---
drivers/irqchip/qcom-pdc.c | 7 ++
include/trace/events/pdc.h | 55 ++
2 files changed, 62 in
Changes in v2:
- Drviers will specify PDC pin as their interrupt and PDC as interrupt parent
- Updated driver to pick up PDC pin mappings from DT
- Cleanup driver per Marc's suggestions
- Addressed DT bindings comments from Rob H
- Addressed FTRACE comments from Steven R
On newer Qualcomm Techono
From: Archana Sathyakumar
Add device binding documentation for the PDC Interrupt controller on
QCOM SoC's like the SDM845. The interrupt-controller can be used to
sense edge low interrupts and wakeup interrupts when the GIC is
non-operational.
Cc: devicet...@vger.kernel.org
Signed-off-by: Archan
>From : Archana Sathyakumar
The Power Domain Controller (PDC) on QTI SoCs like SDM845 houses an
interrupt controller along with other domain control functions to handle
interrupt related functions like handle falling edge or active low which
are not detected at the GIC and handle wakeup interrupt
Em Thu, Jan 18, 2018 at 01:26:27PM -0800, kan.li...@intel.com escreveu:
> From: Kan Liang
>
> perf top need it to handle overwrite fallback later.
>
> Signed-off-by: Kan Liang
> ---
> tools/perf/util/evsel.c | 5 +
> tools/perf/util/evsel.h | 2 ++
> 2 files changed, 7 insertions(+)
>
> d
On 02/02/2018 15:04, Wei Xu wrote:
> Hi Daniel,
>
> On 2018/2/2 13:53, Daniel Lezcano wrote:
>> On 02/02/2018 14:48, Wei Xu wrote:
>>> Hi Daniel,
>>>
>>> On 2018/2/2 13:34, Daniel Lezcano wrote:
On 02/02/2018 13:10, Wei Xu wrote:
> Hi Daniel,
>
> On 2018/2/2 12:05, Daniel Lezcano
On 02/02/2018 11:42, Viresh Kumar wrote:
> Hi Daniel,
Hi Viresh,
> I have gone through the other review comments, specially from Daniel T..
> While I
> share some of his concerns, I have few more of mine.
>
> On 23-01-18, 16:34, Daniel Lezcano wrote:
>> +late_initcall(cpu_cooling_init);
>
> F
On 31.01.2018 20:07, Quentin Schulz wrote:
Hi Philipp,
On Mon, Jan 29, 2018 at 12:29:11AM +0100, Philipp Rossak wrote:
This patch rewors the driver to support interrupts for the thermal part
of the sensor.
This is only available for the newer sensor (currently H3 and A83T).
The interrupt wil
We still officially support the ancient i486 cpu. First generation
versions of this processor do not have the CPUID instruction, though
later versions do. Therefore you must check that the cpu supports
it before using it. At present it fails with an "Illegal Instruction"
signal on the early process
Hi Mathieu,
On 01/02/18 09:51, Mathieu Poirier wrote:
> When considering to move a task to the DL policy we need to make sure
> the CPUs it is allowed to run on matches the CPUs of the root domains of
> the runqueue it is currently assigned to. Otherwise the task will be
> allowed to roam on CPUs
On Saturday 20 January 2018 10:44 PM, David Lechner wrote:
> This adds the new board-specific clock init in mach-davinci/dm355.c
> using the new common clock framework drivers.
>
> The #ifdefs are needed to prevent compile errors until the entire
> ARCH_DAVINCI is converted.
>
> Also clean up the
On Fri, 02 Feb 2018, Greg KH wrote:
> On Fri, Feb 02, 2018 at 12:44:38PM +0200, Jani Nikula wrote:
>>
>> +Knut, Fengguang
>>
>> On Fri, 02 Feb 2018, Greg KH wrote:
>> >- If clang now builds the kernel "cleanly", yes, I want to take
>> > warning fixes in the stable tree. And even bette
On Fri, Feb 02, 2018 at 09:30:51AM -0500, Matthew Whitehead wrote:
> We still officially support the ancient i486 cpu. First generation
> versions of this processor do not have the CPUID instruction, though
> later versions do. Therefore you must check that the cpu supports
> it before using it. At
On Saturday 20 January 2018 10:44 PM, David Lechner wrote:
> This adds the new board-specific clock init in mach-davinci/dm365.c
> using the new common clock framework drivers.
>
> The #ifdefs are needed to prevent compile errors until the entire
> ARCH_DAVINCI is converted.
>
> Also clean up the
On Saturday 20 January 2018 10:44 PM, David Lechner wrote:
> This adds the new board-specific clock init in mach-davinci/dm644x.c
> using the new common clock framework drivers.
>
> The #ifdefs are needed to prevent compile errors until the entire
> ARCH_DAVINCI is converted.
>
> Also clean up th
>
> What is the goal of these types of emails?
>
even more so on this mailing list. It almost feels like guerilla
advertising for Clang.
> thanks,
>
> greg k-h
>
> ___
> Kernelnewbies mailing list
> kernelnewb...@kernelnewbies.org
> https://lists.
On 01/02/2018 00:04, daniel.m.jor...@oracle.com wrote:
> A common case in release_pages is for the 'pages' list to be in roughly
> the same order as they are in their LRU. With LRU batch locking, when a
> sentinel page is removed, an adjacent non-sentinel page must be promoted
> to a sentinel pa
On 31.01.2018 20:23, Quentin Schulz wrote:
Hi Philipp,
On Mon, Jan 29, 2018 at 12:29:12AM +0100, Philipp Rossak wrote:
This patch adds support for the H3 ths sensor.
The H3 supports interrupts. The interrupt is configured to update the
the sensor values every second. The calibration data is
Hi Daniel,
On 2018/2/2 14:29, Daniel Lezcano wrote:
> On 02/02/2018 15:04, Wei Xu wrote:
>> Hi Daniel,
>>
>> On 2018/2/2 13:53, Daniel Lezcano wrote:
>>> On 02/02/2018 14:48, Wei Xu wrote:
Hi Daniel,
On 2018/2/2 13:34, Daniel Lezcano wrote:
> On 02/02/2018 13:10, Wei Xu wrote:
>
On Fri, 2018-02-02 at 21:07 +1100, James Morris wrote:
> On Thu, 1 Feb 2018, Mimi Zohar wrote:
>
> > Hi James,
> >
> > Included in this pull request are three bug fixes, assuming the 2 FUSE
> > patches are considered bugs and not new features, and a maintainer update.
> > I'd appreciate your send
On 2/2/18 1:07 AM, kemi wrote:
> Hi, Jens
> Could you help to merge this patch to your tree? Thanks
Yes, I'll queue it up, thanks.
--
Jens Axboe
> Em Thu, Jan 18, 2018 at 01:26:27PM -0800, kan.li...@intel.com escreveu:
> > From: Kan Liang
> >
> > perf top need it to handle overwrite fallback later.
> >
> > Signed-off-by: Kan Liang
> > ---
> > tools/perf/util/evsel.c | 5 +
> > tools/perf/util/evsel.h | 2 ++
> > 2 files changed, 7 in
Here are three bugfixes for x86 that I needed to get LTO-enabled
kernels to build reliably. I'm not sure abouto that first one
though.
None of these are urgent, as they don't show up in mainline
kernels and they don't indicate serious problems.
Arnd Bergmann (3):
x86: dumpstack: avoid uninitial
On Fri, 2018-02-02 at 12:00 +0100, Rafael J. Wysocki wrote:
> On Thursday, February 1, 2018 2:18:12 PM CET Srinivas Pandruvada
> wrote:
> >
> > On Thu, 2018-02-01 at 10:11 +0100, Peter Zijlstra wrote:
> > >
> > > On Thu, Feb 01, 2018 at 08:50:28AM +0100, Rafael J. Wysocki
> > > wrote:
> > > >
>
Em Fri, Feb 02, 2018 at 09:30:51AM -0500, Matthew Whitehead escreveu:
> We still officially support the ancient i486 cpu. First generation
> versions of this processor do not have the CPUID instruction, though
> later versions do. Therefore you must check that the cpu supports
> it before using it.
Em Fri, Feb 02, 2018 at 03:37:31PM +0100, Borislav Petkov escreveu:
> On Fri, Feb 02, 2018 at 09:30:51AM -0500, Matthew Whitehead wrote:
> > We still officially support the ancient i486 cpu. First generation
> > versions of this processor do not have the CPUID instruction, though
> > later versions
On Saturday 20 January 2018 10:44 PM, David Lechner wrote:
> void __init dm646x_init_time(unsigned long ref_clk_rate,
>unsigned long aux_clkin_rate)
> {
> +#ifdef CONFIG_COMMON_CLK
> + void __iomem *pll1, *pll2, *psc;
> + struct clk *clk;
> +
> + pll1 = ior
In some configurations, 'partial' does not get initialized,
as shown by this gcc-8 warning:
arch/x86/kernel/dumpstack.c: In function 'show_trace_log_lvl':
arch/x86/kernel/dumpstack.c:156:4: error: 'partial' may be used uninitialized
in this function [-Werror=maybe-uninitialized]
show_regs_if_
The declaration for swsusp_arch_resume marks it as 'asmlinkage',
but the definition in x86-32 does not, and it fails to include
the header with the declaration. This leads to a warning when
building with link-time-optimizations:
kernel/power/power.h:108:23: error: type of 'swsusp_arch_resume' does
With retpoline, tight loops of "call this function for every XXX" are
very much pessimised by taking a prediction miss *every* time.
This one showed up very high in our early testing, and it only has five
things it'll ever call so make it take an 'op' enum instead of a
function pointer and let's s
With link time optimizations enabled, I get a link failure:
./ccLbOEHX.ltrans19.ltrans.o: In function `override_function_with_return':
:(.text+0x7f3): undefined reference to `just_return_func'
Marking the symbol .globl makes it work as expected.
Fixes: 540adea3809f ("error-injection: Separate er
On 02/01/2018 07:29 PM, ebied...@xmission.com wrote:
Khalid Aziz writes:
V11 changes:
This series is same as v10 and was simply rebased on 4.15 kernel. Can
mm maintainers please review patches 2, 7, 8 and 9 which are arch
independent, and include/linux/mm.h and mm/ksm.c changes in patch 10
and
gcc discovered that the memcpy() arguments in kdbnearsym() overlap, so
we should really use memmove(), which is defined to handle that correctly:
In function 'memcpy',
inlined from 'kdbnearsym' at
/git/arm-soc/kernel/debug/kdb/kdb_support.c:132:4:
/git/arm-soc/include/linux/string.h:353:9: er
From: Markus Elfring
Date: Fri, 2 Feb 2018 15:54:32 +0100
Two update suggestions were taken into account
from static source code analysis.
Markus Elfring (2):
Delete an error message for a failed memory allocation
Improve a size determination
drivers/i2c/busses/i2c-puv3.c | 3 +--
1 file c
On Saturday 20 January 2018 10:44 PM, David Lechner wrote:
> This adds the new SATA REFCLK clock init in mach-davinci/devices-da8xx.c
> using the new common clock framework drivers.
>
> The #ifdefs are needed to prevent compile errors until the entire
> ARCH_DAVINCI is converted.
>
> Also, the #i
From: Markus Elfring
Date: Fri, 2 Feb 2018 15:41:26 +0100
Omit an extra message for a memory allocation failure in this function.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
drivers/i2c/busses/i2c-puv3.c | 1 -
1 file changed, 1 deletion(-)
dif
Building with LTO enabled reveals some functions whose prototypes
in the header are different from the definition:
drivers/video/fbdev/sis/sis_main.h:765:0: error: type of 'SiS_SetCH70xxANDOR'
does not match original declaration [-Werror=lto-type-mismatch]
extern void SiS_SetCH70xxANDOR(struct
From: Markus Elfring
Date: Fri, 2 Feb 2018 15:43:21 +0100
Replace the specification of a data structure by a pointer dereference
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding style convention.
This issue was dete
There are two incompatible definitions of 'vchiq_instance_struct', so
passing them through vchiq_initialise(), vchiq_connect() or another
such interface is broken, as shown by building the driver with link-time
optimizations:
drivers/staging/vc04_services/interface/vchiq_arm/vchiq_if.h:129:0: erro
skd includes slab_def.h to get access to the slab cache object size.
However, including this header breaks when we use SLUB or SLOB instead of
the SLAB allocator, since the structure layout is completely different,
as shown by this warning when we build this driver in one of the invalid
configurati
On Saturday 20 January 2018 10:44 PM, David Lechner wrote:
> The common clock framework will take care of disabling unused clocks when
> we switch from the legacy davinci clocks and having this enabled will
> cause compile errors after we switch, so remove it now.
>
> Signed-off-by: David Lechner
On Saturday 20 January 2018 10:44 PM, David Lechner wrote:
> This removes CONFIG_DAVINCI_RESET_CLOCKS. The option has been removed from
> the kernel.
>
> Signed-off-by: David Lechner
Reviewed-by: Sekhar Nori
Thanks,
Sekhar
On Thu, Feb 01, 2018 at 04:46:56PM +0200, Andy Shevchenko wrote:
> On Thu, Feb 1, 2018 at 3:48 PM, Mark Brown wrote:
> >> >> > Signed-off-by: Junichi Wakasugi
> >> >> > Signed-off-by: Mihai Serban
> >> >> > Signed-off-by: Shengjiu Wang
> >> >> > Signed-off-by: Daniel Baluta
> > Honestly the
On 2/2/18 8:03 AM, Arnd Bergmann wrote:
> skd includes slab_def.h to get access to the slab cache object size.
> However, including this header breaks when we use SLUB or SLOB instead of
> the SLAB allocator, since the structure layout is completely different,
> as shown by this warning when we bui
In banked-sr.c, we use a top-level '__asm__(".arch_extension virt")'
statement to allow compilation of a multi-CPU kernel for ARMv6
and older ARMv7-A that don't normally support access to the banked
registers.
This is considered to be a programming error by the gcc developers
and will no longer wo
On 02/02/2018 08:59 AM, Arnd Bergmann wrote:
gcc discovered that the memcpy() arguments in kdbnearsym() overlap, so
we should really use memmove(), which is defined to handle that correctly:
In function 'memcpy',
inlined from 'kdbnearsym' at
/git/arm-soc/kernel/debug/kdb/kdb_support.c:132:
We use a hack in xscale-cp0.c to allow building it for ARMv4 while
also using ARMv5TE and iWMMXt specific inline assembly, by
adding a top-level asm statement.
Unfortunately that hack no longer works with gcc-8, since it will
revert back to the normal architecture. The recommended way of
handling
On Thu, 2018-02-01 at 15:37 +0100, Mike Galbraith wrote:
> On Thu, 2018-02-01 at 13:37 +0100, Sergio Lopez wrote:
> > Compared against "isolcpus", "restrict_smt" presents the following
> > advantages:
> > - Doesn't require prior knowledge of the CPU topology, making it
> > more friendly to both en
Building with link-time-optimizations revealed that the cxgb4 driver does
a fixed-size memcpy() from a variable-length constant string into the
network interface name:
In function 'memcpy',
inlined from 'cfg_queues_uld.constprop' at
drivers/net/ethernet/chelsio/cxgb4/cxgb4_uld.c:335:2,
in
gcc-8 points out that a string is copied to itself here:
In file included from
drivers/staging/media/atomisp/pci/atomisp2/css2400/hive_isp_css_include/platform_support.h:25,
from
drivers/staging/media/atomisp/pci/atomisp2/css2400/hive_isp_css_include/memory_access/memory_access.
Hi Miklos,
On Tue, 2018-01-30 at 19:06 +0100, Dongsu Park wrote:
> From: Alban Crequy
>
> This new fs_type flag FS_IMA_NO_CACHE means files should be re-measured,
> re-appraised and re-audited each time. Cached integrity results should
> not be used.
>
> It is useful in FUSE because the userspa
On 01/02/2018 00:04, daniel.m.jor...@oracle.com wrote:
> Now that release_pages is scaling better with concurrent removals from
> the LRU, the performance results (included below) showed increased
> contention on lru_lock in the add-to-LRU path.
>
> To alleviate some of this contention, do more wo
/* prevents concurrent reads of temperature and ADC */
struct mutexmutex;
struct thermal_zone_device *tzd;
@@ -561,6 +569,9 @@ static int sun4i_gpadc_probe_dt(struct platform_device
*pdev,
struct resource *mem;
void __iomem *bas
On Fri, 2 Feb 2018, Haiqing Bai wrote:
> From: Shigeru Yoshida
>
> Running io_watchdog_func() while ohci_urb_enqueue() is running can
> cause a race condition where ohci->prev_frame_no is corrupted and the
> watchdog can mis-detect following error:
>
> ohci-platform 664a0800.usb: frame counte
gcc points out a buffer that is clearly too small to be used
in a meaningful way, as the 'sizeof(*args) + argc > sizeof(stack)'
will always fail:
In function 'memcpy',
inlined from 'nvif_vmm_map' at drivers/gpu/drm/nouveau/nvif/vmm.c:55:2:
include/linux/string.h:353:9: error: '__builtin_memcpy
gcc-8 warns about some obviously incorrect code:
net/mac80211/cfg.c: In function 'cfg80211_beacon_dup':
net/mac80211/cfg.c:2896:3: error: 'memcpy' source argument is the same as
destination [-Werror=restrict]
>From the context, I conclude that we want to copy from beacon into
new_beacon, as we d
The legacy hypercall handlers were originally added with
a comment explaining that "copying the argument structures in
HYPERVISOR_event_channel_op() and HYPERVISOR_physdev_op() into the local
variable is sufficiently safe" and only made sure to not write
past the end of the argument structure, the
> -Original Message-
> From: Shawn Guo [mailto:shawn...@kernel.org]
> Sent: Friday, February 02, 2018 1:18 AM
> To: Sebastian Reichel
> Cc: Sascha Hauer ; Frank Li ;
> Fabio Estevam ; Ian Ray ; Rob
> Herring ; Mark Rutland ;
> devicet...@vger.kernel.org; linux-kernel@vger.kernel.org
> Su
On Fri, 2018-02-02 at 10:20 -0500, Mimi Zohar wrote:
> Hi Miklos,
>
> On Tue, 2018-01-30 at 19:06 +0100, Dongsu Park wrote:
> > From: Alban Crequy
> >
> > This new fs_type flag FS_IMA_NO_CACHE means files should be re-measured,
> > re-appraised and re-audited each time. Cached integrity results
On Fri, 2 Feb 2018, Lina Iyer wrote:
> +static inline void pdc_enable_intr(struct irq_data *d, bool on)
> +{
> + int pin_out = d->hwirq;
> + u32 index, mask;
> + u32 enable;
> + unsigned long flags;
> +
> + index = pin_out / 32;
> + mask = pin_out % 32;
> +
> + spin_lock
Hi,
Il 02/02/2018 14:35, Maxime Ripard ha scritto:
On Fri, Feb 02, 2018 at 11:57:20AM +0100, Giulio Benetti wrote:
Il 02/02/2018 11:53, Maxime Ripard ha scritto:
Hi,
On Thu, Feb 01, 2018 at 05:17:11PM +0100, Giulio Benetti wrote:
What kernel version did you use?
Latest mainline.
I guess
From: Markus Elfring
Date: Fri, 2 Feb 2018 16:34:56 +0100
Two update suggestions were taken into account
from static source code analysis.
Markus Elfring (2):
Delete an error message for a failed memory allocation
Improve a size determination
drivers/i2c/busses/i2c-nomadik.c | 3 +--
1 fil
On 2018-02-02 07:31 AM, Arnd Bergmann wrote:
> Building the amd display driver with link-time optimizations revealed a bug
Curious how I'd go about building with link-time optimizations.
> that caused dal_cmd_tbl_helper_dce80_get_table() and
> dal_cmd_tbl_helper_dce110_get_table() get called with
From: Markus Elfring
Date: Fri, 2 Feb 2018 16:25:14 +0100
Omit an extra message for a memory allocation failure in this function.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
drivers/i2c/busses/i2c-nomadik.c | 1 -
1 file changed, 1 deletion(-)
Add SPDX license tag check based on the rules defined in
Documentation/process/license-rules.rst. To summarize, SPDX license tags
should be on the 1st line (or 2nd line in scripts) using the appropriate
comment style for the file type.
Cc: Andy Whitcroft
Cc: Joe Perches
Cc: Thomas Gleixner
Cc:
From: Markus Elfring
Date: Fri, 2 Feb 2018 16:28:20 +0100
Replace the specification of a data structure by a pointer dereference
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding style convention.
This issue was dete
Moving the qrwlock struct definition into a header file introduced
a subtle bug on all little-endian machines, where some files in some
configurations would see the fields in an incorrect order. This was
found by building with an LTO enabled compiler that warns every time we
try to link together f
Build testing with LTO found a couple of files that get compiled
differently depending on whether asm/byteorder.h gets included early
enough or not. In particular, include/asm-generic/qrwlock_types.h is
affected by this, but there are probably others as well.
The symptom is a series of LTO link ti
The new crc32c logic in gfs2_log_header_v2 causes a link
error without libcrc32c:
ERROR: "crc32c" [fs/gfs2/gfs2.ko] undefined!
While the original patch selected CONFIG_CRYPTO_CRC32C to deal
with this issue, it turned out to be the wrong symbol.
Fixes: c1696fb85d33 ("GFS2: Introduce new gfs2_log_
> On 2. Feb 2018, at 15:59, David Woodhouse wrote:
>
> With retpoline, tight loops of "call this function for every XXX" are
> very much pessimised by taking a prediction miss *every* time.
>
> This one showed up very high in our early testing, and it only has five
> things it'll ever call so m
passing the strlen() of the source string as the destination
length is pointless, and gcc-8 now warns about it:
drivers/net/ethernet/qlogic/qed/qed_debug.c: In function 'qed_grc_dump':
include/linux/string.h:253: error: 'strncpy' specified bound depends on the
length of the source argument [-Werr
gcc-8 points out that the skb_copy_to_linear_data() argument points to
the skb itself, which makes it run into a problem with overlapping
memcpy arguments:
In file included from include/linux/ip.h:20,
from drivers/net/ethernet/qlogic/qlge/qlge_main.c:26:
drivers/net/ethernet/qlogi
gcc-8 notices that the memcpy in mlx5_core_query_xsrq() makes no
sense because the source and destination variables are identical:
drivers/net/ethernet/mellanox/mlx5/core/transobj.c: In function
'mlx5_core_query_xsrq':
drivers/net/ethernet/mellanox/mlx5/core/transobj.c:347:3: error: 'memcpy'
sou
When link-time optimizations are enabled, vxfs fails to build:
fs/freevxfs/vxfs_lookup.c: In function 'vxfs_readdir':
fs/freevxfs/vxfs_subr.c:50:1: error: inlining failed in call to always_inline
'vxfs_put_page': function not declared inline and code size would grow
vxfs_put_page(struct page *pp
Hi Linus,
Sorry to bother you with a second merge request for GFS2, but we found
a couple regressions and want to get them fixed in this merge window.
Please consider pulling the following changes for the GFS2 file system.
Regards,
Bob Peterson
--
gcc-8 complains about the prototype for this function:
lib/ubsan.c:432:1: error: ignoring attribute 'noreturn' in declaration of a
built-in function '__ubsan_handle_builtin_unreachable' because it conflicts
with attribute 'const' [-Werror=attributes]
This removes the noreturn attribute.
Signed
This bug was fixed before, but came up again with the latest
compiler in another function:
fs/cifs/cifssmb.c: In function 'CIFSSMBSetEA':
fs/cifs/cifssmb.c:6362:3: error: 'strncpy' offset 8 is out of the bounds [0, 4]
[-Werror=array-bounds]
strncpy(parm_data->list[0].name, ea_name, name_len);
Gidday,
The Linux man-pages maintainer proudly announces:
man-pages-4.15 - man pages for Linux
This release resulted from patches, bug reports, reviews, and comments
from 26 contributors. Over 200 commits changed around 75 pages.
In addition, 3 new manual pages were added.
Tarball download
On 02/02/18 17:40, Rob Herring wrote:
> Add SPDX license tag check based on the rules defined in
Shouldn't it also check that the license is compatible?
[...]
> + } elsif ($realfile =~ /\.rst$/) {
> + $comment = '..';
What is the c
On Fri, Feb 02, 2018 at 04:37:55PM +0200, Jani Nikula wrote:
> On Fri, 02 Feb 2018, Greg KH wrote:
> > On Fri, Feb 02, 2018 at 12:44:38PM +0200, Jani Nikula wrote:
> >>
> >> +Knut, Fengguang
> >>
> >> On Fri, 02 Feb 2018, Greg KH wrote:
> >> > - If clang now builds the kernel "cleanly", yes, I
From: Jack Stocker
Following on from this patch: https://lkml.org/lkml/2017/11/3/516,
Corsair K70 RGB keyboards also require the DELAY_INIT quirk to
start correctly at boot.
Device ids found here:
usb 3-3: New USB device found, idVendor=1b1c, idProduct=1b13
usb 3-3: New USB device strings: Mfr=1
Hi Arnd,
2018-02-02 16:43 GMT+01:00 Arnd Bergmann :
> The new crc32c logic in gfs2_log_header_v2 causes a link
> error without libcrc32c:
>
> ERROR: "crc32c" [fs/gfs2/gfs2.ko] undefined!
>
> While the original patch selected CONFIG_CRYPTO_CRC32C to deal
> with this issue, it turned out to be the w
On Fri, Feb 02, 2018 at 04:38:13PM +0100, Giulio Benetti wrote:
> Hi,
>
> Il 02/02/2018 14:35, Maxime Ripard ha scritto:
> > On Fri, Feb 02, 2018 at 11:57:20AM +0100, Giulio Benetti wrote:
> > > Il 02/02/2018 11:53, Maxime Ripard ha scritto:
> > > > Hi,
> > > >
> > > > On Thu, Feb 01, 2018 at 05:
On Fri, Feb 02, 2018 at 04:32:31PM +0100, Arnd Bergmann wrote:
> The legacy hypercall handlers were originally added with
> a comment explaining that "copying the argument structures in
> HYPERVISOR_event_channel_op() and HYPERVISOR_physdev_op() into the local
> variable is sufficiently safe" and o
201 - 300 of 975 matches
Mail list logo
