On Mon, Apr 01, 2019 at 10:42:52AM -0700, Joe Perches wrote:
> On Mon, 2019-04-01 at 19:01 +0200, Greg Kroah-Hartman wrote:
> > 4.4-stable review patch. If anyone has any objections, please let me know.
>
> If this is to be ported just for an optimization
> (which I think is dubious as it's not a
On Mon, 11 Mar 2019, Hsin-Hsiung Wang wrote:
> This adds compatible for the MediaTek MT6358 PMIC.
>
> Signed-off-by: Hsin-Hsiung Wang
> ---
> Documentation/devicetree/bindings/mfd/mt6397.txt | 11 ---
> 1 file changed, 8 insertions(+), 3 deletions(-)
For my own reference:
Acked-for-M
On Tue, Apr 02, 2019 at 02:58:53PM +0800, Pingfan Liu wrote:
>On Tue, Apr 2, 2019 at 1:20 PM Chao Fan wrote:
>>
>> On Tue, Apr 02, 2019 at 12:10:46PM +0800, Pingfan Liu wrote:
>> >crashkernel=x@y or or =range1:size1[,range2:size2,...]@offset option may
>> or or?
>> >fail to reserve the required me
On Mon, 18 Mar 2019, Maxime Ripard wrote:
> The AXP223 can be used both using the RSB proprietary bus, or a more
> traditional I2C bus. The RSB is a faster bus and provides more features
> (like some integrity checks on the messages), so it's usually preferrable
> to use it, but since it's proprie
On Mon, 25 Mar 2019, Mukesh Ojha wrote:
> On 3/25/2019 1:26 PM, Lee Jones wrote:
> > On Fri, 22 Mar 2019, Kangjie Lu wrote:
> >
> > > Hi Lee Jones,
> > >
> > > Can you review this patch?
> > Don't poke.
> >
> > I have a very long list of reviews on my TODO. Poking only surfaces
> > your patch
* Michael Ellerman:
> I'm a bit vague on what we're trying to do here.
>
> But it seems like you want some sort of "eye catcher" prior to the branch?
>
> That value is a valid instruction on current CPUs (rlwimi.
> r5,r24,6,1,9), and even if it wasn't it could become one in future.
>
> If you chan
This is needed because clang doesn't select which linker to use based on
$LD but rather -fuse-ld={bfd,gold,lld,}. This
is problematic especially for cc-ldoption, which checks for linker flag
support via invoking the compiler, rather than the linker.
Select the linker via absolute path from $PATH
On Mon, Apr 01, 2019 at 10:22:57AM -0700, Paul E. McKenney wrote:
> > > The initial solution to this problem was to use set_tsk_need_resched() and
> > > set_preempt_need_resched() to force a future context switch, which allows
> > > rcu_preempt_note_context_switch() to report the deferred quiescent
On Mon, Apr 1, 2019 at 7:13 PM Jonathan Cameron
wrote:
>
> On Mon, 1 Apr 2019 11:25:29 -0300
> Marcelo Schmitt wrote:
>
> > Hello,
> >
> > I was looking for some work on staging: iio: ad9832 and made some
> > observations while reading the driver.
> >
> > Apparently it had no devicetree documenta
On 3/30/2019 2:22 AM, Bjorn Helgaas wrote:
Hi Vidya,
Wow, there's a lot of nice work here! Thanks for that!
On Tue, Mar 26, 2019 at 08:43:26PM +0530, Vidya Sagar wrote:
Add support for Synopsys DesignWare core IP based PCIe host controller
present in Tegra194 SoC.
General comments:
- Th
On Tue, 02 Apr 2019 08:45:32 +0200,
Kailang wrote:
>
>
> Reviewed-by: Kailang Yang
Thanks, applied the patch now.
Takashi
>
> -Original Message-
> From: Takashi Iwai
> Sent: Tuesday, April 2, 2019 2:43 PM
> To: Kailang
> Cc: Jian-Hong Pan ; alsa-de...@alsa-project.org;
> Daniel
On Tue, 2 Apr 2019 at 12:58, Lee Jones wrote:
>
> On Mon, 18 Mar 2019, Baolin Wang wrote:
>
> > We should use SoC compatible string in stead of wildcard string for
> > PMIC child devices.
> >
> > Signed-off-by: Baolin Wang
> > ---
> > Hi Lee,
> >
> > Could you merge this patch into v5.1-rc if no
Dear Robin Gong,
Sorry...below another sdma patch(ad0d92d7ba6a) need to be reverted,
because spi driver may dynamically change burst length.
now I have reverted patch ad0d92d7ba6a.
Patches 0001-dma-engine-imx-sdma-add-mcu_2_ecspi-script.patch and
0002-spi-spi-imx-fix-ERR009165.patch are ap
On Mon, 18 Mar 2019, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski
>
> Add a DT binding document for max77650 ultra-low power PMIC. This
> describes the core mfd device and the GPIO module.
>
> Signed-off-by: Bartosz Golaszewski
> Reviewed-by: Rob Herring
> ---
> .../devicetree/bind
On Mon, Apr 01, 2019 at 06:24:08PM +0200, Alexander Potapenko wrote:
> diff --git a/arch/x86/include/asm/bitops.h b/arch/x86/include/asm/bitops.h
> index d153d570bb04..20e4950827d9 100644
> --- a/arch/x86/include/asm/bitops.h
> +++ b/arch/x86/include/asm/bitops.h
> @@ -111,7 +111,7 @@ clear_bit(
On Tue, Apr 02, 2019 at 12:08:58AM -0700, Nick Desaulniers wrote:
> This is needed because clang doesn't select which linker to use based on
> $LD but rather -fuse-ld={bfd,gold,lld,}. This
> is problematic especially for cc-ldoption, which checks for linker flag
> support via invoking the compiler
Hi Paul,
Paul Cercueil wrote on Tue, 02 Apr 2019 01:31:52
+0200:
> Hi Stephen,
>
> Le mar. 2 avril 2019 à 1:14, Stephen Rothwell a écrit
> :
> > Hi all,
> >
> > After merging the nand tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> >
> > drivers/mtd/nand/raw/ing
This is needed because clang doesn't select which linker to use based on
$LD but rather -fuse-ld={bfd,gold,lld,}. This
is problematic especially for cc-ldoption, which checks for linker flag
support via invoking the compiler, rather than the linker.
Select the linker via absolute path from $PATH
On Fri, Mar 22, 2019 at 03:02:11PM +, Srinivas Kandagatla wrote:
>
>
> On 20/03/2019 17:50, Gaurav Kohli wrote:
> >
> > > Is root only option not helping you in this case?
> > Yes we want to protect at root level as well, i mean it is better if we
> > can avoid exposing to userspace at all.
On Mon, 18 Mar 2019, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski
>
> Add a kernel doc for mfd_add_devices().
>
> Signed-off-by: Bartosz Golaszewski
> ---
> drivers/mfd/mfd-core.c | 14 ++
> 1 file changed, 14 insertions(+)
>
> diff --git a/drivers/mfd/mfd-core.c b/driv
On 01.04.19 22:56, Alexander Duyck wrote:
> On Mon, Apr 1, 2019 at 7:47 AM Michael S. Tsirkin wrote:
>>
>> On Mon, Apr 01, 2019 at 04:11:42PM +0200, David Hildenbrand wrote:
The interesting thing is most probably: Will the hinting size usually be
reasonable small? At least I guess a gues
On Fri, Mar 29, 2019 at 03:23:14PM -0700, Subhra Mazumdar wrote:
>
> On 3/29/19 6:35 AM, Julien Desfossez wrote:
> > On Fri, Mar 22, 2019 at 8:09 PM Subhra Mazumdar
> > wrote:
> > > Is the core wide lock primarily responsible for the regression? I ran
> > > upto patch
> > > 12 which also has the
On 1/04/19 3:58 PM, Faiz Abbas wrote:
> According to the AM654x Data Manual[1], the setup timing in lower speed
> modes can only be met if the controller uses a falling edge data launch.
>
> To ensure this, the HIGH_SPEED_ENA (HOST_CONTROL[2]) bit should be
> cleared in default speed, SD high spee
On Tue, Apr 2, 2019 at 9:09 AM 'Nick Desaulniers' via Clang Built
Linux wrote:
>
> This is needed because clang doesn't select which linker to use based on
> $LD but rather -fuse-ld={bfd,gold,lld,}. This
> is problematic especially for cc-ldoption, which checks for linker flag
> support via invok
Hi Bjorn, Alex,
On 3/30/19 3:41 PM, Bjorn Helgaas wrote:
> From: Bjorn Helgaas
>
> Use dev_printk() when possible to make messages consistent with other
> device-related messages.
>
> Signed-off-by: Bjorn Helgaas
For the vfio-platform part:
Acked-by: Eric Auger
For the rest:
Reviewed-by: Eri
On Tue, Apr 02, 2019 at 09:52:13AM +0200, Sedat Dilek wrote:
> On Tue, Apr 2, 2019 at 9:09 AM 'Nick Desaulniers' via Clang Built
> Linux wrote:
> >
> > This is needed because clang doesn't select which linker to use based on
> > $LD but rather -fuse-ld={bfd,gold,lld,}. This
> > is problematic esp
On Tue, Apr 2, 2019 at 4:51 AM Kimberly Brown wrote:
>
> The kobj_type default_attrs field is being replaced by the
> default_groups field. Replace sugov_tunables_ktype's default_attrs field
> with default groups. Change "sugov_attributes" to "sugov_attrs" and use
> the ATTRIBUTE_GROUPS macro to c
+++ Johannes Thumshirn [01/04/19 11:01 +0200]:
Over the last 20 years, the Linux kernel has accumulated hundreds if not
thousands of security vulnerabilities.
One common pattern in most of these security related reports is processes
called "syzkaller", "trinity" or "syz-executor" opening files a
On Tue, Apr 02, 2019 at 12:33:17AM -0700, Nick Desaulniers wrote:
> This is needed because clang doesn't select which linker to use based on
> $LD but rather -fuse-ld={bfd,gold,lld,}. This
> is problematic especially for cc-ldoption, which checks for linker flag
> support via invoking the compiler
Hi Adrian,
On 26/03/19 1:03 PM, Adrian Hunter wrote:
> On 18/03/19 11:33 AM, Ulf Hansson wrote:
>> + Arnd, Grygorii
>>
>> On Fri, 15 Feb 2019 at 20:17, Faiz Abbas wrote:
>>>
>>> sdhci.c has two bottom halves implemented. A threaded_irq for handling
>>> card insert/remove operations and a tasklet
Description
---
This is an RFC because I don't know if this is a bug or a normal use
case. It seems that the function `_regmap_raw_write_impl` from the regmap
framework verifies that a register is writable only using
the callback function, ignoring the other two (max allowed register,
regis
regmap provides a couple of ways to validate the register range used.
a) maxim allowed register, b) writable/readable register tables,
c) callback function that can be provided by the driver to validate
a register. regmap framework should verify if registers
are writeable before every write operati
From: Guo Ren
Linux kernel has provided some apis for arch signal's implementation.
For example:
restore_saved_sigmask()
set_current_blocked()
restore_altstack()
But in last version of csky signal.c didn't use them and some codes are
confusing, so reconstruct signal.c wit
Hi Yamada-san,
On 30/03/2019 12:04, Masahiro Yamada wrote:
> Now that Kbuild is able to start from any directory, the generated
> Makefile can simply wrap the top Makefile.
This is a really nice simplification :)
Reviewed-by: Kieran Bingham
> Signed-off-by: Masahiro Yamada
> ---
>
> scripts
From: Guo Ren
We could use regs->sr 16-24 bits to detect syscall: VEC_TRAP0 and
r11_sig is no necessary for current implementation.
In this patch, we implement the in_syscall and forget_syscall which are
inspired from arm & nds32, but csky pt_regs has no syscall_num element
and we just set zero
From: Guo Ren
The function of do_notify_resume called by entry.S could be entered
in loop when SIGPENDING was setted again before sret. So we must add
prevent code to make syscall restart (regs->sepc -= 0x4) or it may
re-execute unexpected instructions.
Just like in_syscall & forget_syscall used
On Mon, 1 Apr 2019, Kimberly Brown wrote:
> The kobj_type default_attrs field is being replaced by the
> default_groups field. Replace irq_kobj_type's default_attrs field with
> default_groups and use the ATTRIBUTE_GROUPS macro to create irq_groups.
>
> This patch was tested by verifying that the
On Tue, Mar 12, 2019 at 1:55 AM Enrico Weigelt, metux IT consult
wrote:
> Use the new helper that wraps the calls to platform_get_resource()
> and devm_ioremap_resource() together.
>
> Signed-off-by: Enrico Weigelt, metux IT consult
Patch applied.
Yours,
Linus Walleij
On Tue, Mar 12, 2019 at 1:56 AM Enrico Weigelt, metux IT consult
wrote:
> Use the new helper that wraps the calls to platform_get_resource()
> and devm_ioremap_resource() together.
>
> Signed-off-by: Enrico Weigelt, metux IT consult
Patch applied.
Yours,
Linus Walleij
> +/* handle crashkernel=x@y or =range1:size1[,range2:size2,...]@offset options
> */
> +static void mem_avoid_specified_crashkernel_region(char *option)
> +{
> + unsigned long long crash_size, crash_base = 0;
> + char*first_colon, *first_space, *cur = option;
> +
Another thing which n
wt., 2 kwi 2019 o 09:41 Lee Jones napisał(a):
>
> On Mon, 18 Mar 2019, Bartosz Golaszewski wrote:
>
> > From: Bartosz Golaszewski
> >
> > Add a kernel doc for mfd_add_devices().
> >
> > Signed-off-by: Bartosz Golaszewski
> > ---
> > drivers/mfd/mfd-core.c | 14 ++
> > 1 file changed
On 02/04/2019 01.55, Sultan Alsawaf wrote:
> On Mon, Apr 01, 2019 at 10:43:13PM +0200, Rasmus Villemoes wrote:
>> No. First, these are concerns for all arches. Second, if you can find
>> some particular place where string parsing/matching is in any way
>> performance relevant and not just done onc
Hi Ray/Wolfram,
On Tue, Apr 2, 2019 at 3:03 AM Ray Jui wrote:
>
> Hi Wolfram/Rayagonda,
>
> On 3/27/2019 3:14 PM, Wolfram Sang wrote:
> >
> >> +static void bcm_iproc_i2c_slave_init(
> >> +struct bcm_iproc_i2c_dev *iproc_i2c, bool need_reset)
> >> +{
> >> +u32 val;
> >> +
> >> +if (nee
On Mon, Apr 01, 2019 at 01:53:06PM +0200, Michal Hocko wrote:
> On Mon 01-04-19 09:59:36, Oscar Salvador wrote:
> > On Fri, Mar 29, 2019 at 02:42:43PM +0100, Michal Hocko wrote:
> > > Having a larger contiguous area is definitely nice to have but you also
> > > have to consider the other side of th
On Tue, Apr 02, 2019 at 02:46:13PM +0800, Aaron Lu wrote:
> On Mon, Feb 18, 2019 at 05:56:33PM +0100, Peter Zijlstra wrote:
> > +static struct task_struct *
> > +pick_task(struct rq *rq, const struct sched_class *class, struct
> > task_struct *max)
> > +{
> > + struct task_struct *class_pick, *
> -Original Message-
> From: Igor Plyatov
> Sent: 2019年4月2日 15:20
> To: Robin Gong ; Uwe Kleine-König
>
> Cc: linux-kernel@vger.kernel.org; linux-arm-ker...@lists.infradead.org;
> linux-...@vger.kernel.org; dl-linux-imx ; Fabio Estevam
> ; Pengutronix Kernel Team ;
> Sascha Hauer ; Shawn
On 31. 03. 19, 13:51, Fuqian Huang wrote:
> If the cmd is RCPK_GET_STRUCT, copy_to_user will copy info to
> user space. As info->port.ops is the address of a constant object
> rocket_port_ops (assigned in init_r_port), a kernel address leakage.
>
> This patch sets all the pointer fields to NULL be
On Tue, Apr 02, 2019 at 06:02:38AM +, Anup Patel wrote:
> The Maximum Physical Memory 2GiB option for 64bit systems is currently
> broken because kernel hangs at boot-time when this option is enabled
> and the underlying system has more than 2GiB memory.
>
> This issue can be easily reproduced
On 02.04.19 10:28, Oscar Salvador wrote:
> On Mon, Apr 01, 2019 at 01:53:06PM +0200, Michal Hocko wrote:
>> On Mon 01-04-19 09:59:36, Oscar Salvador wrote:
>>> On Fri, Mar 29, 2019 at 02:42:43PM +0100, Michal Hocko wrote:
Having a larger contiguous area is definitely nice to have but you also
On Monday, April 1, 2019 5:03:45 PM CEST Borislav Petkov wrote:
> From: Borislav Petkov
>
> This driver is Intel-only so loading on anything which is not Intel is
> pointless. Prevent it from doing so.
>
> While at it, correct the "not supported" print statement to say CPU
> "model" which is wha
On Monday, March 25, 2019 6:24:56 PM CEST Stephen Boyd wrote:
> These prints are useful if we're doing PM suspend debugging. Having them
> at pr_debug() level means that we need to either enable DEBUG in this
> file, or compile the kernel with dynamic debug capabilities. Both of
> these options hav
On 01/04/2019 09.34, Mark Brown wrote:
> On Wed, Mar 27, 2019 at 02:30:48PM +, Rasmus Villemoes wrote:
>> I doubt patches 3 and 4 are acceptable, but I'd still like to get
>> comments and/or alternative suggestions for making large transfers
>> faster.
>
> I see no problem with this from a fra
Return error instead of trying to unlock a mutex that is not hold.
Signed-off-by: Daniel Walter
---
arch/um/drivers/ubd_kern.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/um/drivers/ubd_kern.c b/arch/um/drivers/ubd_kern.c
index aca09be2373e..33c1cd6a12ac 100644
Commit-ID: b5dbb6799e3e5b8ebdce33b52b2d4ec9c66e15fe
Gitweb: https://git.kernel.org/tip/b5dbb6799e3e5b8ebdce33b52b2d4ec9c66e15fe
Author: Ben Dooks
AuthorDate: Sat, 30 Mar 2019 11:56:24 +
Committer: Borislav Petkov
CommitDate: Tue, 2 Apr 2019 10:38:51 +0200
x86/asm: Annotate copy_use
After early microcode update was added, microcode couldn't be configured
as a module, microcode update happens at early bootup and cpu hotplug
stage. This made the microcode update code in module loading stage
useless.
This patch remove the useless code.
Signed-off-by: Zhenzhong Duan
Cc: Borisla
On Mon, Apr 01, 2019 at 03:59:39PM -0700, Andrew Morton wrote:
> On Mon, 1 Apr 2019 13:03:47 +0200 Uladzislau Rezki wrote:
>
> > Hello, Andrew.
> >
> > >
> > > It's a lot of new code. I t looks decent and I'll toss it in there for
> > > further testing. Hopefully someone will be able to find th
On Mon, Apr 01, 2019 at 10:51:53PM -0400, Kimberly Brown wrote:
> The kobj_type default_attrs field is being replaced by the
> default_groups field. Replace sugov_tunables_ktype's default_attrs field
> with default groups. Change "sugov_attributes" to "sugov_attrs" and use
> the ATTRIBUTE_GROUPS ma
On 02/04/2019 05:35, Mark Brown wrote:
> On Mon, Apr 01, 2019 at 01:22:09PM +0100, Jon Hunter wrote:
>
>> FYI, I am seeing that the deferral of soundcards failing with v5.1-rc3
>> because the above has not been merged yet. Just wanted to let you know
>> in case this one was not marked for v5.1.
On Wed, 27 Mar 2019, Thomas Gleixner wrote:
> On Wed, 27 Mar 2019, Andi Kleen wrote:
>
> > > > I checked the code general and with the .globl in NATIVE_LABEL the
> > >
> > > With or without? I removed that as well.
> >
> > With.
> >
> > LTO would still need the .globls because the variable and
On Tue, Mar 12, 2019 at 1:55 AM Enrico Weigelt, metux IT consult
wrote:
> We already have the struct device* pointer in a local variable,
> so we can write this a bit shorter.
>
> Signed-off-by: Enrico Weigelt, metux IT consult
Thierry seems to have spotted a bug in this patch so please
resend
On Fri, Mar 29, 2019 at 09:43:58AM -0500, thor.tha...@linux.intel.com wrote:
> From: Thor Thayer
>
> Reserve ECC Double Bit Error SMC call to alert U-Boot that
> a DBE has occurred. Moving the call from local EDAC header
> file to this common file.
Is there any particular reason this needs to be
On Tue, Mar 12, 2019 at 2:00 AM Enrico Weigelt, metux IT consult
wrote:
> Use the new helper that wraps the calls to platform_get_resource()
> and devm_ioremap_resource() together.
>
> Signed-off-by: Enrico Weigelt, metux IT consult
Patch applied.
Yours,
Linus Walleij
From: RickyWu
this patch fixes rts5260 power saving parameter
make power saving function work on L1.1, L1.2
Signed-off-by: RickyWu
---
drivers/misc/cardreader/rts5260.c | 21 +++--
1 file changed, 11 insertions(+), 10 deletions(-)
diff --git a/drivers/misc/cardreader/rts5260.c
On Tue, Mar 12, 2019 at 1:55 AM Enrico Weigelt, metux IT consult
wrote:
> Use the new helper that wraps the calls to platform_get_resource()
> and devm_ioremap_resource() together.
>
> Signed-off-by: Enrico Weigelt, metux IT consult
Patch applied with Florian's ACK.
Yours,
Linus Walleij
On Tuesday, March 26, 2019 10:48:27 AM CEST Mika Westerberg wrote:
> On Mon, Mar 25, 2019 at 04:53:38PM +, Thomas Preston wrote:
> > Add an example for the magic PRP0001 device ID which allows matching
> > ACPI devices against drivers using OF Device Tree compatible property.
> >
> > Signed-of
On Mon, 1 Apr 2019 at 22:52, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.14.110 release.
> There are 107 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.
>
> Re
On Tue, Apr 2, 2019 at 9:27 AM Peter Zijlstra wrote:
>
>
>
> On Mon, Apr 01, 2019 at 06:24:08PM +0200, Alexander Potapenko wrote:
> > diff --git a/arch/x86/include/asm/bitops.h b/arch/x86/include/asm/bitops.h
> > index d153d570bb04..20e4950827d9 100644
> > --- a/arch/x86/include/asm/bitops.h
> > +
On Tue, Apr 2, 2019 at 3:57 PM Daniel Vetter wrote:
>
> On Tue, Apr 02, 2019 at 01:55:03PM +0800, Qiang Yu wrote:
> > Thanks, patch is:
> > Reviewed-by: Qiang Yu
>
> Good time to get started with committing patches? In general it's kinda
> confusing if the maintainer r-bs a patch, but doesn't say
On Tue, 2019-04-02 at 08:59 +0200, Greg Kroah-Hartman wrote:
> On Mon, Apr 01, 2019 at 10:42:52AM -0700, Joe Perches wrote:
> > On Mon, 2019-04-01 at 19:01 +0200, Greg Kroah-Hartman wrote:
> > > 4.4-stable review patch. If anyone has any objections, please let me
> > > know.
> >
> > If this is t
On Tue, Mar 12, 2019 at 1:55 AM Enrico Weigelt, metux IT consult
wrote:
> Use the new helper that wraps the calls to platform_get_resource()
> and devm_ioremap_resource() together.
>
> Signed-off-by: Enrico Weigelt, metux IT consult
Patch applied.
Yours,
Linus Walleij
On Tue, Mar 12, 2019 at 1:55 AM Enrico Weigelt, metux IT consult
wrote:
> Use the new helper that wraps the calls to platform_get_resource()
> and devm_ioremap_resource() together.
>
> Signed-off-by: Enrico Weigelt, metux IT consult
Patch applied.
Yours,
Linus Walleij
> > >> +/* RANDOM SLAVE STRETCH time - 20ms*/
> > >
> > > What is a "random stretch time"? 20ms sounds like a lot. Also, missing
> > > space before comment terminator.
> > >
> >
> > Rayagonda,
> >
> > Could you please help to comment on the choice of the 20 ms to allow
> > clock stretch from t
On 01/04/2019 18:01, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.178 release.
> There are 131 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 s
On 25/03/19 10:54 PM, Joakim Tjernlund wrote:
> On Mon, 2019-03-25 at 22:36 +0530, Vignesh Raghavendra wrote:
>>
>> On 25/03/19 7:21 PM, Joakim Tjernlund wrote:
>>> On Mon, 2019-03-25 at 18:27 +0530, Vignesh Raghavendra wrote:
CAUTION: This email originated from outside of the organization.
On Tue, Mar 12, 2019 at 1:55 AM Enrico Weigelt, metux IT consult
wrote:
> Use the new helper that wraps the calls to platform_get_resource()
> and devm_ioremap_resource() together.
>
> Signed-off-by: Enrico Weigelt, metux IT consult
Patch applied.
Yours,
Linus Walleij
On Mon, 1 Apr 2019, Ondrej Mosnacek wrote:
> On Thu, Mar 28, 2019 at 1:02 AM Thomas Gleixner wrote:
> > On Thu, 7 Mar 2019, Ondrej Mosnacek wrote:
> > > /* adjtime() is independent from ntp_adjtime() */
> > > time_adjust = txc->offset;
> > >
On 01/04/2019 18:02, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.167 release.
> There are 56 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 sh
On 01/04/2019 18:01, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.14.110 release.
> There are 107 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 01/04/2019 18:00, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.19.33 release.
> There are 134 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 s
On Tue, Mar 12, 2019 at 1:57 AM Enrico Weigelt, metux IT consult
wrote:
> Use the new helper that wraps the calls to platform_get_resource()
> and devm_ioremap_resource() together.
>
> Signed-off-by: Enrico Weigelt, metux IT consult
Patch applied with Baolin's ACK.
Yours,
Linus Walleij
Hi Mao,
On Tue, Apr 02, 2019 at 02:35:43PM +0800, Mao Han wrote:
> diff --git a/tools/arch/csky/include/uapi/asm/perf_regs.h
> b/tools/arch/csky/include/uapi/asm/perf_regs.h
> new file mode 100644
> index 000..337d8fa
> --- /dev/null
> +++ b/tools/arch/csky/include/uapi/asm/perf_regs.h
> @@ -
On 01/04/2019 18:00, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.0.6 release.
> There are 146 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 sho
On Tue, Apr 02, 2019 at 08:01:21AM +, Han Nandor wrote:
> Description
> ---
> This is an RFC because I don't know if this is a bug or a normal use
> case. It seems that the function `_regmap_raw_write_impl` from the regmap
> framework verifies that a register is writable only using
> th
On Tue, Apr 02, 2019 at 08:43:51AM +, Rasmus Villemoes wrote:
> Thanks! There's one other option I can think of: don't do the interrupts
> at all, but just busy-wait for the completion of each word transfer (in
> a cpu_relax() loop). That could be guarded by something like
> 100*bits_per_w
Hi Linus,
On Tue, 2 Apr 2019 at 17:04, Linus Walleij wrote:
>
> On Tue, Mar 12, 2019 at 1:57 AM Enrico Weigelt, metux IT consult
> wrote:
>
> > Use the new helper that wraps the calls to platform_get_resource()
> > and devm_ioremap_resource() together.
> >
> > Signed-off-by: Enrico Weigelt, metu
The "WITH Linux-syscall-note" should be added to headers exported to
the user-space.
Some kernel-space headers have "WITH Linux-syscall-note", which seems
a mistake.
[1] arch/x86/include/asm/hyperv-tlfs.h
5a4858032217 ("x86/hyper-v: move hyperv.h out of uapi") moved this file
out of uapi, but mi
On Mon, 11 Mar 2019, Chris Boyle wrote:
> Provide a complete map of axes and buttons for the Logitech Flight System
> G940, which fixes several issues:
>
> Stop conflating the stick X/Y axes with the mini-stick (hat) axes. This
> stops reported X jumping between stick X and hat X (likewise Y).
>
The purpose of this series is to improve and enhance the
handling of kernel boot arguments.
It is first focussed on powerpc but also extends the capability
for other arches.
This is based on suggestion from Daniel Walker
Christophe Leroy (9):
powerpc: enable appending of CONFIG_CMDLINE to boo
On Tue, Apr 2, 2019 at 2:05 PM Mike Rapoport wrote:
>
> On Tue, Apr 02, 2019 at 06:02:38AM +, Anup Patel wrote:
> > The Maximum Physical Memory 2GiB option for 64bit systems is currently
> > broken because kernel hangs at boot-time when this option is enabled
> > and the underlying system has
On Tue, Apr 02, 2019 at 08:37:23AM +0200, H. Nikolaus Schaller wrote:
> I have learned from Linus that the problem with legacy spi-cs-high are mostly
> embedded
> powerpc systems deployed between 2008 and 2013 where the boot-loader can't be
> changed. And where the dts is not maintained on kernel
The Maximum Physical Memory 2GiB option for 64bit systems is currently
broken because kernel hangs at boot-time when this option is enabled
and the underlying system has more than 2GiB memory.
This issue can be easily reproduced on SiFive Unleashed board where
we have 8GiB of memory.
This patch f
On 4/1/2019 8:01 PM, Thierry Reding wrote:
On Mon, Apr 01, 2019 at 04:48:42PM +0530, Vidya Sagar wrote:
On 3/31/2019 12:12 PM, Rob Herring wrote:
On Tue, Mar 26, 2019 at 08:43:22PM +0530, Vidya Sagar wrote:
Add support for Tegra194 PCIe controllers. These controllers are based
on Synopsys Desi
On Tue, Apr 2, 2019 at 4:10 PM Baolin Wang wrote:
> On Tue, 2 Apr 2019 at 17:04, Linus Walleij wrote:
> >
> > On Tue, Mar 12, 2019 at 1:57 AM Enrico Weigelt, metux IT consult
> > wrote:
> >
> > > Use the new helper that wraps the calls to platform_get_resource()
> > > and devm_ioremap_resource()
On Tue, Apr 02, 2019 at 09:52:15AM +0100, Jon Hunter wrote:
> On 02/04/2019 05:35, Mark Brown wrote:
> > I don't have this patch at all AFAICT.
> That's odd. It is definitely in -next and I did receive an 'applied'
> email from you [0]. So looks like something went wrong here. Can we get
> this i
On Tue, 2 Apr 2019 at 17:19, Linus Walleij wrote:
>
> On Tue, Apr 2, 2019 at 4:10 PM Baolin Wang wrote:
> > On Tue, 2 Apr 2019 at 17:04, Linus Walleij wrote:
> > >
> > > On Tue, Mar 12, 2019 at 1:57 AM Enrico Weigelt, metux IT consult
> > > wrote:
> > >
> > > > Use the new helper that wraps the
On Tue, Mar 12, 2019 at 1:55 AM Enrico Weigelt, metux IT consult
wrote:
> Use the new helper that wraps the calls to platform_get_resource()
> and devm_ioremap_resource() together.
>
> Signed-off-by: Enrico Weigelt, metux IT consult
> ---
> drivers/gpio/gpio-eic-sprd.c | 9 ++---
Please fix
Hi Paul,
Miquel Raynal wrote on Tue, 2 Apr 2019
09:27:47 +0200:
> Hi Paul,
>
> Paul Cercueil wrote on Tue, 02 Apr 2019 01:31:52
> +0200:
>
> > Hi Stephen,
> >
> > Le mar. 2 avril 2019 à 1:14, Stephen Rothwell a
> > écrit :
> > > Hi all,
> > >
> > > After merging the nand tree, today's l
On 18/03/2019 13:10, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski
>
> Currently the clocksource and clockevent support for davinci platforms
> lives in mach-davinci. It hard-codes many things, uses global variables,
> implements functionalities unused by any platform and has code fragme
On 02/04/2019 10:19, Mark Brown wrote:
> On Tue, Apr 02, 2019 at 09:52:15AM +0100, Jon Hunter wrote:
>> On 02/04/2019 05:35, Mark Brown wrote:
>
>>> I don't have this patch at all AFAICT.
>
>> That's odd. It is definitely in -next and I did receive an 'applied'
>> email from you [0]. So looks l
On Tue, Apr 2, 2019 at 2:05 PM Mike Rapoport wrote:
>
> On Tue, Apr 02, 2019 at 06:02:38AM +, Anup Patel wrote:
> > The Maximum Physical Memory 2GiB option for 64bit systems is currently
> > broken because kernel hangs at boot-time when this option is enabled
> > and the underlying system has
1 - 100 of 945 matches
Mail list logo
