* Qian Cai wrote:
> The commit 585a4c1f9978 ("kasan: remove use after scope bugs
> detection.") removed KASAN_EXTRA, so tidy up leftovers.
>
> Signed-off-by: Qian Cai
> ---
> arch/x86/include/asm/page_64_types.h | 4
> 1 file changed, 4 deletions(-)
>
> diff --git
Hi Thomas:
Thanks for your review.
On Mon, Feb 11, 2019 at 5:48 AM Thomas Gleixner wrote:
>
> On Thu, 7 Feb 2019, lantianyu1...@gmail.com wrote:
>
> > From: Lan Tianyu
> >
> > Hyper-V doesn't provide irq remapping for IO-APIC. To enable x2apic,
> > set x2apic destination mode to
On Mon, 2019-02-11 at 07:26 +0100, Christophe Leroy wrote:
>
> Le 11/02/2019 à 01:21, Benjamin Herrenschmidt a écrit :
> > On Fri, 2019-02-08 at 12:52 +, Christophe Leroy wrote:
> > > /*
> > > + * MSR_KERNEL is > 0x8000 on 4xx/Book-E since it include MSR_CE.
> > > + */
> > > +.macro
On Mon, Feb 11, 2019 at 7:28 AM Randy Dunlap wrote:
> From: Randy Dunlap
>
> Fix markup warning: insert a blank line before the list.
>
> Documentation/driver-api/gpio/board.rst:209: WARNING: Unexpected indentation.
>
> Signed-off-by: Randy Dunlap
> Cc: Linus Walleij
> Cc: Bartosz Golaszewski
Hi Alex:
Thanks for your review.
On Fri, Feb 8, 2019 at 2:15 AM Alex Williamson
wrote:
>
> On Thu, 7 Feb 2019 23:33:48 +0800
> lantianyu1...@gmail.com wrote:
>
> > From: Lan Tianyu
> >
> > On the bare metal, enabling X2APIC mode requires interrupt remapping
> > function which helps
On Mon, Feb 11, 2019 at 09:54:01AM +0200, Adrian Hunter wrote:
>
> Which is not really a real use-case.
..
> > perf analysis with PT becomes inaccurate and main goal
> > of retaining accurate instruction info is not achieved.
>
> For the majority of real use-cases, yes it is.
In our fleet not a
On Fri, Feb 8, 2019 at 1:15 AM Vitaly Kuznetsov wrote:
>
> lantianyu1...@gmail.com writes:
>
> > From: Lan Tianyu
> >
> > On the bare metal, enabling X2APIC mode requires interrupt remapping
> > function which helps to deliver irq to cpu with 32-bit APIC ID.
> > Hyper-V doesn't provide interrupt
On Wed, Feb 6, 2019 at 4:32 AM Chen-Yu Tsai wrote:
> The A80 SoC has configuration registers for I/O bias voltage. Incorrect
> settings would make the affected peripherals inoperable in some cases,
> such as Ethernet RGMII signals biased at 2.5V with the settings still
> at 3.3V. However low
On Saturday, February 9, 2019 10:33:53 PM CET Andrew Lunn wrote:
> > +static int ocores_poll_wait(struct ocores_i2c *i2c)
> > +{
> > + u8 mask;
> > + int err;
> > +
> > + if (i2c->state == STATE_DONE || i2c->state == STATE_ERROR) {
> > + /* transfer is over */
> > + mask
Hi Olaf:
Thanks for your review.
On Fri, Feb 8, 2019 at 10:52 PM Olaf Hering wrote:
>
> On Thu, Feb 07, lantianyu1...@gmail.com wrote:
>
> > +++ b/drivers/iommu/Kconfig
> > +config HYPERV_IOMMU
> > + bool "Hyper-V x2APIC IRQ Handling"
> > + depends on HYPERV
> > + select
Mauro and Maxime,
On Mon, Jan 28, 2019 at 2:29 PM Jagan Teki wrote:
>
> Add CSI support for Allwinner A64. Here is previous series[1]
>
> Changes for v8:
> - update proper enable and disable sequnce for clk_mod
> - fix warning for patch "media: sun6i: Add A64 CSI block support"
> - collect
On 11/02/19 10:18 AM, Alexei Starovoitov wrote:
> On Mon, Feb 11, 2019 at 09:54:01AM +0200, Adrian Hunter wrote:
>>
>> Which is not really a real use-case.
> ..
>>> perf analysis with PT becomes inaccurate and main goal
>>> of retaining accurate instruction info is not achieved.
>>
>> For the
Dear Greg,
This is extcon-next pull request for v5.1. I add detailed description of
this pull request on below. Please pull extcon with following updates.
Best Regards,
Chanwoo Choi
The following changes since commit d13937116f1e82bf508a6325111b322c30c85eb9:
Linux 5.0-rc6 (2019-02-10
On Sun, Feb 10, 2019 at 6:31 PM Jonathan Neuschäfer
wrote:
> When using the mmc_spi driver with a card-detect pin, I noticed that the
> card was not detected immediately after probe, but only after it was
> unplugged and plugged back in (and the CD IRQ fired).
>
> The call tree looks something
Hi Sven,
On Sun, Feb 10, 2019 at 12:43:21PM -0500, Sven Van Asbroeck wrote:
> Hi Dmitry,
>
> On Thu, Feb 7, 2019 at 5:46 PM Dmitry Torokhov
> wrote:
> >
> > We should be using flush_delayed_work() instead of flush_work() in
> > matrix_keypad_stop() to ensure that we are not missing work that is
On Fri, Feb 08, 2019 at 05:53:12PM -0200, Shayenne Moura wrote:
> Remove KMS cleanup task from documentation solved by patchset
> https://patchwork.freedesktop.org/series/54310/
>
> Signed-off-by: Shayenne Moura
Thanks for your patch, applied to drm-misc-next.
-Daniel
> ---
>
On Sun, Feb 10, 2019 at 01:13:53PM +0100, Lukas Wunner wrote:
> On Wed, Feb 06, 2019 at 04:17:22PM +0300, Mika Westerberg wrote:
> > Each port has a separate path configuration space that is used for
> > finding the next hop (switch) in the path. Hop ID is an index to this
> > configuration space
If the Interrupt Flag (IF) is not set, we should not handle the IRQ:
- the line can be shared with other devices
- it can be a spurious interrupt
To avoid reading twice the status register, the ocores_process() function
expects it to be read by the caller.
Signed-off-by: Federico Vaga
Acked-by:
It adds the SPDX tag and it removes the old text about the GPLv2.
Signed-off-by: Federico Vaga
Reviewed-by: Andrew Lunn
---
drivers/i2c/busses/i2c-ocores.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/i2c/busses/i2c-ocores.c b/drivers/i2c/busses/i2c-ocores.c
This driver assumes that an interrupt line is always available for
the I2C master. This is not always the case and this patch adds support
for a polling version.
Report from Andrew Lunn:
I did some timing tests for this. On my box, we request a udelay of
80uS. The kernel actually delays for
Detecting a timeout is ok, but we also need to assert a STOP command on
the bus in order to prevent it from generating interrupts when there are
no on going transfers.
Example: very long transmission.
1. ocores_xfer: START a transfer
2. ocores_isr : handle byte by byte the transfer
3.
This patch set provides improvements to the i2c-ocore driver.
[V3 -> V4]
- add reviews-by/tested-by
- add comment to justify the formula in
udelay((8 * 1000) / i2c->bus_clock_khz);
[V2 -> V3]
- fix particular error condition on platform_get_irq(). Copied from
Miscellaneous style fixes from checkpatch
Signed-off-by: Federico Vaga
Reviewed-by: Andrew Lunn
---
drivers/i2c/busses/i2c-ocores.c | 19 ---
1 file changed, 12 insertions(+), 7 deletions(-)
diff --git a/drivers/i2c/busses/i2c-ocores.c b/drivers/i2c/busses/i2c-ocores.c
index
On Mon, Jan 28, 2019 at 04:46:53PM +0100, Loys Ollivier wrote:
>
> On Fri 25 Jan 2019 at 09:07, Johan Hovold wrote:
>
> > On Thu, Jan 17, 2019 at 05:54:32PM +0100, Loys Ollivier wrote:
> >> Add binding for Mediatek-based GNSS receivers.
> >>
> >> Signed-off-by: Loys Ollivier
> >> ---
> >>
>
Hi Justin,
thanks for your patch!
On Fri, Feb 8, 2019 at 8:25 PM wrote:
> From: Justin Chen
>
> The ADS79XX has GPIO pins that can be used. Add support for the GPIO
> pins using the GPIO chip framework.
>
> Signed-off-by: Justin Chen
(...)
> @@ -56,11 +61,17 @@ struct ti_ads7950_state {
>
On Mon, Feb 11, 2019 at 05:26:52PM +0900, Chanwoo Choi wrote:
> Dear Greg,
>
> This is extcon-next pull request for v5.1. I add detailed description of
> this pull request on below. Please pull extcon with following updates.
>
> Best Regards,
> Chanwoo Choi
>
> The following changes since
On Sat, Feb 09, 2019 at 08:59:06PM +, Sudip Mukherjee wrote:
> - return bus_register(_bus_type);
> + int retval;
> +
> + retval = bus_register(_bus_type);
> + if (retval)
> + return retval;
> +#ifdef CONFIG_PARPORT_1284
> + daisy_drv_init();
> +#endif
Shouldn't
From: Huang Ying
When swapin is performed, after getting the swap entry information from
the page table, system will swap in the swap entry, without any lock held
to prevent the swap device from being swapoff. This may cause the race
like below,
CPU 1 CPU 2
-
Hello!
On 11.02.2019 5:13, Ryder Lee wrote:
There is no need to retun 0 in mt76_dma_attach(), so switch it to void.
^ r missing :-)
Signed-off-by: Ryder Lee
[...]
MBR, Sergei
Hi Andy,
On Thu, Jan 31, 2019 at 03:35:37PM +0200, Heikki Krogerus wrote:
> On Wed, Jan 30, 2019 at 06:51:56PM +0200, Andy Shevchenko wrote:
> > On Wed, Jan 30, 2019 at 6:03 PM Heikki Krogerus
> > wrote:
> > >
> > > When the connections are defined in firmware, struct
> > > device_connection
The cpufreq core doesn't remove the cpufreq policy anymore on CPU
offline operation, rather that happens when the CPU device gets
unregistered from the kernel. This allows faster recovery when the CPU
comes back online. This is also very useful during system wide
suspend/resume where we offline
Implement the light-weight tear down helper to reduce the amount of work
to do on CPU offline/online operation.
Signed-off-by: Viresh Kumar
---
drivers/cpufreq/cpufreq-dt.c | 19 +++
1 file changed, 19 insertions(+)
diff --git a/drivers/cpufreq/cpufreq-dt.c
The cpufreq core doesn't remove the cpufreq policy anymore on CPU
offline operation, rather that happens when the CPU device gets
unregistered from the kernel. This allows faster recovery when the CPU
comes back online. This is also very useful during system wide
suspend/resume where we offline
On Fri 08-02-19 22:06:59, Steve Magnani wrote:
> On 2/8/19 11:34 AM, Steve Magnani wrote:
> > In cases where the next unique ID or file/directory count of the
> > in-core Logical Volume Integrity Descriptor have been updated,
> > a sync() causes a (corrupt) LVID with a stale CRC to be written to
On 07-02-19, 13:22, Marek Szyprowski wrote:
> Dear All,
>
> Recent commit 9ac6cb5fbb17 ("i2c: add suspended flag and accessors for
> i2c adapters") added a visible warning for an attempt to do i2c transfer
> over a suspended i2c bus. This revealed a long standing issue in the
> cpufreq-dt driver,
+++ Thomas Gleixner [08/02/19 17:02 +0100]:
The original MODULE_LICENSE string for kernel modules licensed under the
GPL v2 (only / or later) was simply "GPL", which was - and still is -
completely sufficient for the purpose of module loading and checking
whether the module is free software or
* Mark Brown wrote:
> In preparation for a change to make this test run repeatedly which
> would generate huge amounts of output as is indirect all the printf()
> calls in the program through a wrapper and add a quiet flag which can
> be used to suppress the output. This is fairly quick and
On Sun, Feb 10, 2019 at 04:33:28PM +0100, Lukas Wunner wrote:
> On Wed, Feb 06, 2019 at 04:17:24PM +0300, Mika Westerberg wrote:
> > Now that we can allocate hop IDs per port on a path, we can take
> > advantage of this and create tunnels covering longer paths than just
> > between two adjacent
On Sun, 10 Feb 2019 at 23:51, Stuart Menefy
wrote:
>
> When debugging suspend problems on Exynos 5260, I had a large number
> of debugging prints going to the serial port after interrupts
> had been disabled but before the timer interrupt was shutdown. This
> was long enough for a timer tick to
Hello Axel,
Le 02/09/2019 05:39 AM, Axel Lin a écrit :
> At the context with *rdev available, there is no problem to get regulator
> id and *regmap, so no need to store them in struct stpmic1_regulator.
>
> Signed-off-by: Axel Lin
> ---
> drivers/regulator/stpmic1_regulator.c | 10 ++
>
On 08-02-19, 17:41, Sudeep Holla wrote:
> Based on Rafael's suggestion, I cooked up something. See if this helps ?
> The policy to cpu dance can be removed and we can just run through the
> online cpumask I think.
>
> Regards,
> Sudeep
>
> -->8
>
> diff --git i/drivers/cpufreq/cpufreq.c
On Sun, 10 Feb 2019 at 23:51, Stuart Menefy
wrote:
>
> When shutting down the timer, ensure that after we have stopped the
> timer any pending interrupts are cleared. This fixes a problem when
> suspending, as interrupts are disabled before the timer is stopped,
> so the timer interrupt may still
On Sun, 10 Feb 2019 at 23:51, Stuart Menefy
wrote:
>
> When a timer tick occurs and the clock is in one-shot mode, the timer
> needs to be stopped to prevent it triggering subsequent interrupts.
> Currently this code is in exynos4_mct_tick_clear(), but as it is
> only needed when an ISR occurs
On Mon, 2019-02-11 at 11:38 +0300, Sergei Shtylyov wrote:
> Hello!
>
> On 11.02.2019 5:13, Ryder Lee wrote:
>
> > There is no need to retun 0 in mt76_dma_attach(), so switch it to void.
>^ r missing :-)
> >
> > Signed-off-by: Ryder Lee
> [...]
>
> MBR, Sergei
>
I
* Mark Brown wrote:
> In automated testing it has been found that on many systems the fsgsbase
> test fails intermittently. This was reported and discussed a while
> back:
>
> https://lore.kernel.org/lkml/20180126153631.ha7yc33fj5uhitjo@xps/
>
> with the analysis concluding that this is
On 11.02.19 at 08:56, David Engraf wrote:
On 09.02.19 at 11:35, Andy Shevchenko wrote:
On Sat, Feb 9, 2019 at 12:08 AM Andrew Morton
wrote:
On Fri, 8 Feb 2019 21:45:21 +0200 Andy Shevchenko
wrote:
On Tue, Oct 30, 2018 at 5:22 PM David Engraf
wrote:
Unpacking an external initrd may fail
On Mon, 11 Feb 2019 06:35:29 +,
Seiya Wang wrote:
>
> On Thu, 2019-02-07 at 15:52 +, Marc Zyngier wrote:
> > On 07/02/2019 15:47, Marc Zyngier wrote:
> > > On 07/02/2019 15:20, Matthias Brugger wrote:
> > >>
> > >>
> > >> On 24/01/2019 09:07, Erin Lo wrote:
> > >>> From: Seiya Wang
> >
On 02/08/2019 08:34 PM, Bean Huo (beanhuo) wrote:
> From: Bean Huo
>
> Change SNOR_HWCPAS_READ_OCTAL to SNOR_HWCAPS_READ_OCTAL.
>
> Signed-off-by: Bean Huo
Reviewed-by: Tudor Ambarus
> ---
> include/linux/mtd/spi-nor.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff
On Mon, Feb 11, 2019 at 07:35:55AM +0100, Lukas Wunner wrote:
> On Wed, Feb 06, 2019 at 04:17:25PM +0300, Mika Westerberg wrote:
> > We can't be sure the paths are actually properly deactivated when a
> > tunnel is restarted after resume.
>
> Why can't we be sure? Please provide proper
On Sat 2019-02-09 14:47:28, Kamalesh Babulal wrote:
> While the consistency model was introduced, architectures without the
> reliable stack trace implementation could use the immediate flag for
> livepatching but with its own limitations.
>
> After removal of the immediate flag by commit
On 8/02/19 8:41 PM, Alamy Liu wrote:
> The IP I'm using has fixed 32 slots for CQ once CQE is enabled in RTL.
> There is no other RO register to say the slot number & which slot that
> DCMD would use.
>
> I agree that most host controller would have 32 slots for CQ, and use
> the last one for
On 08.02.19 10:06, Oscar Salvador wrote:
> isolate_huge_page() expects we pass the head of hugetlb page to it:
>
> bool isolate_huge_page(...)
> {
> ...
> VM_BUG_ON_PAGE(!PageHead(page), page);
> ...
> }
>
> While I really cannot think of any situation where we end up with a
>
Hi Lukas,
I have tested your patch with LLVM/Clang from Git (will get version 9)
with (RFC) asm-goto support.
I was able to build with CONFIG_FCOE=m and CONFIG_LIBFCOE=m and boot
on bare metal.
Feel free to add my...
Tested-by: Sedat Dilek
If you want to send out a v2 please feel free
On 08/02/2019 at 19:44, Gustavo A. R. Silva wrote:
> In preparation to enabling -Wimplicit-fallthrough, mark switch
> cases where we are expecting to fall through.
>
> Notice that, in this particular case, the /* fall through */
> comments are placed at the bottom of the case statement, which
>
On 11/02/2019 08:15, Seiya Wang wrote:
> Change cpu clock name from ca57 to ca72 since MT8173 does use cortex-a72.
>
> Signed-off-by: Seiya Wang
Reviewed-by: Matthias Brugger
> ---
> drivers/clk/mediatek/clk-mt8173.c | 4 ++--
> include/dt-bindings/clock/mt8173-clk.h | 2 +-
> 2
Use the IO memcpy() functions when copying from/to IO memory.
These locations were found via sparse.
Signed-off-by: Wen Yang
Suggested-by: Kishon Vijay Abraham I
CC: Lorenzo Pieralisi
CC: Bjorn Helgaas
CC: Gustavo Pimentel
CC: Niklas Cassel
CC: Greg Kroah-Hartman
CC: Cyrille Pitchen
CC:
On 02/10/2019 10:23 PM, Thomas Gleixner wrote:
On Fri, 25 Jan 2019, Alexandre Chartre wrote:
Note that this issue has been observed and reproduced with a custom kernel
with some code mapped to different virtual addresses and using jump labels
As jump labels use text_poke_bp(), crashes were
On 01/30/19 at 05:40pm, Julian Stecklina wrote:
> diff --git a/arch/x86/boot/compressed/kaslr.c
> b/arch/x86/boot/compressed/kaslr.c
> index 9ed9709..5657e34 100644
> --- a/arch/x86/boot/compressed/kaslr.c
> +++ b/arch/x86/boot/compressed/kaslr.c
> @@ -155,6 +155,12 @@ parse_memmap(char *p,
On 10. 02. 19 21:24, Stephen Rothwell wrote:
Hi Bartlomiej,
In commit
7d7e58d30e04 ("dt-bindings: display: ssd1307fb: Remove reset-active-low from
examples")
Fixes tag
Fixes: 519b4db ("fbdev: ssd1307fb: Remove reset-active-low from the DT binding
document")
has these problem(s):
On Mon, 11 Feb 2019, Alexandre Chartre wrote:
> On 02/10/2019 10:23 PM, Thomas Gleixner wrote:
> > On Fri, 25 Jan 2019, Alexandre Chartre wrote:
> > > Note that this issue has been observed and reproduced with a custom kernel
> > > with some code mapped to different virtual addresses and using
On 09-02-19, 20:02, Chen Yu wrote:
> On Dell Inc. XPS13 9333, the BIOS changes the value of
> MSR_IA32_MISC_ENABLE_TURBO_DISABLE at runtime (e.g., when
> the power source changes), the maximum frequency of the
> CPU is not updated accordingly. This is due to the policy's
> cpuinfo.max is not
Ryder Lee writes:
> There is no need to return 0 in mt76_dma_attach(), so switch it to void.
>
> Signed-off-by: Ryder Lee
When you send a new version mark it as v2:
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches#patch_version_missing
And add a changelog:
On 11/02/2019 05:48, Kishon Vijay Abraham I wrote:
> Hi Lorenzo,
>
> On 08/02/19 5:50 PM, Lorenzo Pieralisi wrote:
>> On Thu, Dec 06, 2018 at 08:52:25PM +0800, Wen Yang wrote:
>>> kmemdup has implemented the function that kmalloc() + memcpy().
>>> We prefer to kmemdup rather than code opened
When facility.76 MSAX3 is present for the guest we must issue a validity
interception if the CRYCBD is not valid.
The bit CRYCBD.31 is an effective field and tested at each guest
level and has for effect to mask the facility.76
It follows that if CRYCBD.31 is clear and AP is not in use we do
Add compatible string for Allwinner suniv timer which is similar to
sun4i timer.
Signed-off-by: Mesih Kilinc
Acked-by: Maxime Ripard
Reviewed-by: Rob Herring
---
Documentation/devicetree/bindings/timer/allwinner,sun4i-timer.txt | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff
This is followup series for F1C100s initial support patchset.
All patches merged except patch 1 ~ 2 which is related to timer.
I am resending those since they are already have Acked tags.
Our dt-bindings for F1C100s are merged, we can now use them at our
device tree source - patch 3.
Also this
The suniv (new F-series) chip has a timer with less functionality than
the A10 timer, e.g. it has only 3 channels.
Add a new compatible for it. As we didn't use the extra channels on A10
either now, the code needn't to be changed.
The suniv chip is based on ARM926EJ-S CPU, thus it has no
Allwinner suniv F1C100s has similar SPI controllers as sun8i H3.
Add compatible string for it.
Signed-off-by: Mesih Kilinc
---
Documentation/devicetree/bindings/spi/spi-sun6i.txt | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git
PC0~PC4 is pin group for SPI0. PA0~PA4 is pin group for SPI1.
Add device tree nodes for this groups.
Signed-off-by: Mesih Kilinc
---
arch/arm/boot/dts/suniv-f1c100s.dtsi | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/suniv-f1c100s.dtsi
dt-binding headers for F1C100s merged now. So add them back to dtsi.
Signed-off-by: Mesih Kilinc
---
arch/arm/boot/dts/suniv-f1c100s.dtsi | 17 ++---
1 file changed, 10 insertions(+), 7 deletions(-)
diff --git a/arch/arm/boot/dts/suniv-f1c100s.dtsi
The Lichee Pi Nano board has a Winbond W25Q128FVSIQ 128Mbit SPI NOR flash
connected to the SPI0 controller of F1C100s SoC, via the pinmux group at
PC bank; so it's bootable.
Enable this SPI flash.
Signed-off-by: Mesih Kilinc
---
arch/arm/boot/dts/suniv-f1c100s-licheepi-nano.dts | 13
Allwinner suniv F1C100s has similar SPI controller as sun8i H3.
F1C100s has no dedicated mod clock, instead it uses AHB bus clock.
Add support for both SPI0 and SPI1.
Signed-off-by: Mesih Kilinc
---
arch/arm/boot/dts/suniv-f1c100s.dtsi | 26 ++
1 file changed, 26
On Wed, Jan 30, 2019 at 09:50:16AM -0600, Rob Herring wrote:
> On Mon, Jan 28, 2019 at 05:37:59PM +0100, Loys Ollivier wrote:
> > Add binding for Mediatek-based GNSS receivers.
> >
> > Signed-off-by: Loys Ollivier
> > ---
> >
> > v3:
> > Removed the I2C and SPI interfaces references.
> >
On 11/02/2019 04:31, Stephen Rothwell wrote:
Hi all,
Today's linux-next merge of the scsi-mkp tree got a conflict in:
drivers/scsi/hisi_sas/hisi_sas_v3_hw.c
between commit:
7bb25a89aad2 ("scsi: hisi_sas: Set protection parameters prior to adding SCSI
host")
from Linus' tree and commit:
On 10.02.19 01:38, Michael S. Tsirkin wrote:
> On Fri, Feb 08, 2019 at 02:05:09PM -0800, Alexander Duyck wrote:
>> On Fri, Feb 8, 2019 at 1:38 PM Michael S. Tsirkin wrote:
>>>
>>> On Fri, Feb 08, 2019 at 03:41:55PM -0500, Nitesh Narayan Lal wrote:
>> I am also planning to try Michael's
The init code path have several execeptions where the module can decide not to
load.
As CONFIG_X86_INTEL_PSTATE is generally set to Y, the return code is not
reachable.
The initialisation code is neither verbose of the reason why it did choose to
prematurely exit.
This situation leads to
On Thu, Feb 07, 2019 at 04:16:06PM +0530, Viresh Kumar wrote:
> @@ -6081,10 +6082,14 @@ static int select_idle_core(struct task_struct *p,
> struct sched_domain *sd, int
> for_each_cpu_wrap(core, cpus, target) {
> bool idle = true;
>
> - for_each_cpu(cpu,
On Fri, Feb 08, 2019 at 11:02:48AM -0800, Guenter Roeck wrote:
>Hi,
>
>On Fri, Feb 01, 2019 at 03:01:11AM -0800, tip-bot for Chao Fan wrote:
>> Commit-ID: 3a63f70bf4c3a17f5d9c9bf3bc3288a23bdfefce
>> Gitweb:
>> https://git.kernel.org/tip/3a63f70bf4c3a17f5d9c9bf3bc3288a23bdfefce
>> Author:
The init code path have several execeptions where the module can decide not to
load.
As CONFIG_X86_INTEL_PSTATE is generally set to Y, the return code is not
reachable.
The initialisation code is neither verbose of the reason why it did choose to
prematurely exit.
This situation leads to
On Fri, Jan 18, 2019 at 03:03:03PM +0100, Johan Hovold wrote:
> This series fix up some minor issues found through inspection.
>
> Note that the fourth patch changes which cpu (hart) devicetree nodes
> are enabled by following the Linux convention of considering nodes
> without a status property
On Sun, Feb 10, 2019 at 09:00:50PM -0500, Waiman Long wrote:
> diff --git a/kernel/locking/rwsem.h b/kernel/locking/rwsem.h
> index bad2bca..067e265 100644
> --- a/kernel/locking/rwsem.h
> +++ b/kernel/locking/rwsem.h
> @@ -32,6 +32,26 @@
> # define DEBUG_RWSEMS_WARN_ON(c)
> #endif
>
> +/*
> +
On Thu, Dec 20, 2018 at 05:17:50PM +0100, Johan Hovold wrote:
> Fix "gpiio5" typo in the (currently unused) blsp2_uart1 4-pin sleep
> config.
>
> Fixes: 22e6789f9493 ("arm64: dts: msm8996: add blsp2_uart1 pinctrl")
> Cc: Srinivas Kandagatla
> Signed-off-by: Johan Hovold
I can't seem to find
Le 11/02/2019 à 04:54, Callum Sinclair a écrit :
> v1 -> v2:
> Implemented additional flags for static entries
> v2 -> v3:
> Cleaned up flag logic so any combination of routes can be cleared.
> Fixed style errors
> Fixed incorrect flag values
nit: those lines are usually put after the '---', thus
On Mon, Feb 11, 2019 at 10:36:01AM +0100, Peter Zijlstra wrote:
> On Sun, Feb 10, 2019 at 09:00:50PM -0500, Waiman Long wrote:
> > +static inline int __down_read_trylock(struct rw_semaphore *sem)
> > +{
> > + long tmp;
> > +
> > + while ((tmp = atomic_long_read(>count)) >= 0) {
> > +
On Mon, 11 Feb 2019 at 01:22, Borislav Petkov wrote:
>
> On Fri, Feb 08, 2019 at 10:53:22PM +0100, Borislav Petkov wrote:
> > On Fri, Feb 08, 2019 at 12:44:51PM -0800, Guenter Roeck wrote:
> > > Yes, the kernel boots if I comment out that function and have it return 0.
> >
> > Thanks, this
On Mon, 11 Feb 2019 10:20:49 +0100
Pierre Morel wrote:
> When facility.76 MSAX3 is present for the guest we must issue a validity
> interception if the CRYCBD is not valid.
>
> The bit CRYCBD.31 is an effective field and tested at each guest
> level and has for effect to mask the facility.76
>
>>> On 08.02.19 at 20:58, wrote:
> In preparation to enabling -Wimplicit-fallthrough, mark switch
> cases where we are expecting to fall through.
>
> Warning level 3 was used: -Wimplicit-fallthrough=3
>
> This patch is part of the ongoing efforts to enabling
> -Wimplicit-fallthrough.
>
>
Hi Viresh,
On 2019-02-11 09:44, Viresh Kumar wrote:
> On 07-02-19, 13:22, Marek Szyprowski wrote:
>> Dear All,
>>
>> Recent commit 9ac6cb5fbb17 ("i2c: add suspended flag and accessors for
>> i2c adapters") added a visible warning for an attempt to do i2c transfer
>> over a suspended i2c bus. This
On Mon, Feb 11, 2019 at 07:16:00AM +0100, Lukas Wunner wrote:
> On Wed, Feb 06, 2019 at 04:17:23PM +0300, Mika Westerberg wrote:
> > We need to be able to walk from one port to another when we are creating
> > paths where there are multiple switches between two ports. For this
> > reason introduce
Baoquan He writes:
> On 01/30/19 at 05:40pm, Julian Stecklina wrote:
>> diff --git a/arch/x86/boot/compressed/kaslr.c
>> b/arch/x86/boot/compressed/kaslr.c
>> index 9ed9709..5657e34 100644
>> --- a/arch/x86/boot/compressed/kaslr.c
>> +++ b/arch/x86/boot/compressed/kaslr.c
>> @@ -155,6 +155,12
On 11-02-19, 10:52, Marek Szyprowski wrote:
> Hi Viresh,
>
> On 2019-02-11 09:44, Viresh Kumar wrote:
> > On 07-02-19, 13:22, Marek Szyprowski wrote:
> >> Dear All,
> >>
> >> Recent commit 9ac6cb5fbb17 ("i2c: add suspended flag and accessors for
> >> i2c adapters") added a visible warning for an
On Mon, Feb 11, 2019 at 09:46:03AM +, Ard Biesheuvel wrote:
>On Mon, 11 Feb 2019 at 01:22, Borislav Petkov wrote:
>>
>> On Fri, Feb 08, 2019 at 10:53:22PM +0100, Borislav Petkov wrote:
>> > On Fri, Feb 08, 2019 at 12:44:51PM -0800, Guenter Roeck wrote:
>> > > Yes, the kernel boots if I
On Mon, 11 Feb 2019 at 10:56, Chao Fan wrote:
>
> On Mon, Feb 11, 2019 at 09:46:03AM +, Ard Biesheuvel wrote:
> >On Mon, 11 Feb 2019 at 01:22, Borislav Petkov wrote:
> >>
> >> On Fri, Feb 08, 2019 at 10:53:22PM +0100, Borislav Petkov wrote:
> >> > On Fri, Feb 08, 2019 at 12:44:51PM -0800,
On 02/11/2019 10:15 AM, Thomas Gleixner wrote:
On Mon, 11 Feb 2019, Alexandre Chartre wrote:
On 02/10/2019 10:23 PM, Thomas Gleixner wrote:
On Fri, 25 Jan 2019, Alexandre Chartre wrote:
Note that this issue has been observed and reproduced with a custom kernel
with some code mapped to
Hi Heikki,
> @@ -84,7 +85,12 @@ enum usb_role usb_role_switch_get_role(struct
> usb_role_switch *sw) } EXPORT_SYMBOL_GPL(usb_role_switch_get_role);
>
> -static int __switch_match(struct device *dev, const void *name)
> +static int switch_fwnode_match(struct device *dev, const void *fwnode)
>
On Fri, 2019-02-08 at 17:47 -0800, Steve Longerbeam wrote:
> The ycbcr2rgb and inverse rgb2ycbcr matrices define the BT.601 encoding
> coefficients, so rename them to indicate that. And add some comments
> to make clear these are BT.601 coefficients encoding between YUV limited
> range and RGB
On Fri, 2019-02-08 at 17:47 -0800, Steve Longerbeam wrote:
> Simplify the selection of the Y'CbCr encoding matrices in init_csc().
> A side-effect of this change is that init_csc() now allows YUV->YUV
> using the identity matrix, intead of returning error.
>
> Signed-off-by: Steve Longerbeam
Hi Matthias,
My apologize for late response, I did not have access to mailbox.
Thank you for review, please check the comments below.
On 2/5/19 1:39 AM, Matthias Kaehlcke wrote:
> Hi Lukasz,
>
> On Fri, Feb 01, 2019 at 07:38:03PM +0100, Lukasz Luba wrote:
>> This patch removes devfreq's custom
On IBM z13 machine types 2964 and 2965 the descriptor
sizes for sampling and diagnostic sampling entries
might be missing in the trailer entry and are set to zero.
This leads to a perf report failure when processing diagnostic
sampling entries.
This patch adds missing descriptor sizes when the
On Mon, Feb 11, 2019 at 05:30:33PM +0800, Chao Fan wrote:
> Yes, I download your ovmf file in linux-build-test/rootfs/firmware/ from
> your link. There are two files, efi32 and efi64. Then I try to run:
You need both OVMF-pure-efi-32.fd and rootfs.squashfs from the repo. And
then this works here.
1 - 100 of 2376 matches
Mail list logo
