On 31/12/18 11:40 AM, Rafael J. Wysocki wrote:
> On Sun, Dec 30, 2018 at 7:57 PM Sinan Kaya wrote:
>>
>> On Wed, Dec 26, 2018 at 12:41 PM Rafael J. Wysocki wrote:
>>>
>>> On Mon, Dec 24, 2018 at 12:26 AM Sinan Kaya wrote:
Select IOSF_MBI only when PCI is set.
Signed-off-by:
Support power domain performance state, add header file for scp event.
Signed-off-by: Henry Chen
---
drivers/soc/mediatek/mtk-scpsys.c | 60 +++
drivers/soc/mediatek/mtk-scpsys.h | 22 ++
2 files changed, 82 insertions(+)
create mode 100644
Add a header to collect SIPs and add one SIP call to initialize power
management hardware for the SIP interface defined to access the SPM
handling vcore voltage and ddr rate changes on mt8183 (and most likely
later socs).
Signed-off-by: Henry Chen
---
include/soc/mediatek/mtk_sip.h | 17
Add dvfsrc driver for MT8183
Signed-off-by: Henry Chen
---
drivers/soc/mediatek/Kconfig | 15 ++
drivers/soc/mediatek/Makefile | 1 +
drivers/soc/mediatek/mtk-dvfsrc.c | 473 ++
3 files changed, 489 insertions(+)
create mode 100644
Add support for performance state of scpsys on mt8183 platform.
Signed-off-by: Henry Chen
---
arch/arm64/boot/dts/mediatek/mt8183.dtsi | 21 +
1 file changed, 21 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt8183.dtsi
b/arch/arm64/boot/dts/mediatek/mt8183.dtsi
Enable dvfsrc on mt8183 platform.
Signed-off-by: Henry Chen
---
arch/arm64/boot/dts/mediatek/mt8183.dtsi | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt8183.dtsi
b/arch/arm64/boot/dts/mediatek/mt8183.dtsi
index e396410..06206fd 100644
---
Add opp table on scpsys dt-bindings for Mediatek SoC.
Signed-off-by: Henry Chen
---
Documentation/devicetree/bindings/opp/mtk-opp.txt | 24 +
.../devicetree/bindings/soc/mediatek/scpsys.txt| 42 ++
2 files changed, 66 insertions(+)
create mode 100644
Document the binding for enabling DVFSRC on MediaTek SoC.
Signed-off-by: Henry Chen
---
.../devicetree/bindings/soc/mediatek/dvfsrc.txt| 26 ++
include/dt-bindings/soc/mtk,dvfsrc.h | 18 +++
2 files changed, 44 insertions(+)
create mode 100644
The patchsets add support for MediaTek hardware module named DVFSRC
(dynamic voltage and frequency scaling resource collector). The DVFSRC is
a HW module which is used to collect all the requests from both software
and hardware and turn into the decision of minimum operating voltage and
minimum
The prototype of that function was already hoisted up in
commit 3b1baa6496e6 ("sched/fair: Add 'group_misfit_task' load-balance type")
but that seems to have been missed. Get rid of the extra prototype.
Fixes: 2802bf3cd936 ("sched/fair: Add over-utilization/tipping point indicator")
On Wed, Jan 02, 2019 at 11:28:43AM +0800, Jason Wang wrote:
>
> On 2018/12/31 上午2:45, Michael S. Tsirkin wrote:
> > On Thu, Dec 27, 2018 at 06:00:36PM +0800, Jason Wang wrote:
> > > On 2018/12/26 下午11:19, Michael S. Tsirkin wrote:
> > > > On Thu, Dec 06, 2018 at 04:17:36PM +0800, Jason Wang
On Wed, 2 Jan 2019 10:53:14 +0100
Cornelia Huck wrote:
> On Tue, 1 Jan 2019 00:40:19 +0100
> Halil Pasic wrote:
>
> > On Mon, 31 Dec 2018 06:03:51 +
> > "Wang, Wei W" wrote:
> >
> > > On Sunday, December 30, 2018 2:06 PM, Halil Pasic wrote:
> > > >
> > > > I guess you are the first
On Wed, Jan 02, 2019 at 11:30:11AM +0800, Jason Wang wrote:
>
> On 2018/12/31 上午2:48, Michael S. Tsirkin wrote:
> > On Thu, Dec 27, 2018 at 06:04:53PM +0800, Jason Wang wrote:
> > > On 2018/12/26 下午11:22, Michael S. Tsirkin wrote:
> > > > On Thu, Dec 06, 2018 at 04:17:36PM +0800, Jason Wang
Em Fri, Dec 21, 2018 at 02:06:15PM +0200, Adrian Hunter escreveu:
> In preparation for fixing thread stack processing for the idle task,
> avoid direct reference to the thread's stack. The thread stack will change
> to an array of thread stacks, at which point the meaning of the direct
> reference
Em Tue, Jan 01, 2019 at 07:28:52PM +0100, Jiri Olsa escreveu:
> On Fri, Dec 21, 2018 at 02:06:18PM +0200, Adrian Hunter wrote:
> > In preparation for fixing thread stack processing for the idle task,
> > allocate an array of thread stacks.
> >
> > Signed-off-by: Adrian Hunter
> > ---
> >
On Fri, Dec 28, 2018 at 11:13 PM Joey Pabalinas wrote:
>
> On Fri, Dec 28, 2018 at 10:43:11AM +0100, 'Dmitry Vyukov' via syzkaller wrote:
> > On Thu, Dec 27, 2018 at 6:00 PM Linus Torvalds
> > wrote:
> > > Nobody reads the kernel mailing list directly - there's just too much
> > > traffic.
> >
On Sun, Dec 30, 2018 at 4:46 PM Andrea Arcangeli wrote:
>
> Hello,
>
> On Sun, Dec 30, 2018 at 08:48:05AM +0100, Dmitry Vyukov wrote:
> > On Wed, Dec 12, 2018 at 10:58 AM Dmitry Vyukov wrote:
> > >
> > > On Wed, Dec 12, 2018 at 10:45 AM syzbot
> > > wrote:
> > > >
> > > > Hello,
> > > >
> > > >
On Wed, Jan 02, 2019 at 11:48:00AM +0800, Junchang Wang wrote:
> On Wed, Jan 2, 2019 at 1:54 AM Paul E. McKenney wrote:
> >
> > On Tue, Jan 01, 2019 at 10:03:20PM +0800, Junchang Wang wrote:
> > > Torture types "rcu_bh" and "sched" were removed in commit "c770c82a23".
> > > The name of torture
On Wed, 2 Jan 2019 10:53:14 +0100
Cornelia Huck wrote:
> On Tue, 1 Jan 2019 00:40:19 +0100
> Halil Pasic wrote:
> > As I said, at the moment I don't have a preference regarding the fix,
> > partly because I'm not sure if "reading config inside the handler" is OK
> > or not. Maybe Connie or
> Hi Andrew/Heiner
>
>Thanks for the feedback. This patch
> fixes a case where ndo_change_mtu function is provided but the callback
> function is not storing mtu to netdevice structure.
Hi Murali
At the moment, any driver which implements ndo_change_mtu
On 31/12/2018 15:03, Joseph Myers wrote:
> On Fri, 28 Dec 2018, Adhemerval Zanella wrote:
>
Currently we only have nios2 and csky (unfortunately). But since generic
definition for off_t and off64_t still assumes non-LFS support, all new
32-bits ports potentially might carry
Hello,
syzbot found the following crash on:
HEAD commit:28e8c4bc8eb4 Merge tag 'rtc-4.21' of git://git.kernel.org/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=122355bf40
kernel config: https://syzkaller.appspot.com/x/.config?x=c2ab9708c613a224
From: Rafał Miłecki
So far we never had any device registered for the SoC. This resulted in
some small issues that we kept ignoring like:
1) Not working GPIOLIB_IRQCHIP (gpiochip_irqchip_add_key() failing)
2) Lack of proper tree in the /sys/devices/
3) mips_dma_alloc_coherent() silently handling
On 1/2/19 9:51 AM, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:f346b0becb1b Merge branch 'akpm' (patches from Andrew)
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=1510cefd40
> kernel config:
On Sat, 2018-12-22 at 18:28 +0100, Martin Blumenstingl wrote:
> Hi Jerome,
>
> On Thu, Dec 6, 2018 at 4:18 PM Jerome Brunet wrote:
> > The goal of the patchset was mainly to address the following warning:
> >
> > WARNING: CPU: 0 PID: 0 at /usr/src/kernel/drivers/mmc/host/meson-gx-
> >
On 2019/1/1 9:22, dann frazier wrote:
On Mon, Nov 26, 2018 at 06:43:00PM +, Salil Mehta wrote:
From: Peng Li
Port 0/1 of HiP08 supports 10G and 25G. This patch adds a
change to configure NIC port speed same as that of optical
module(SFP/QFSP). Driver gets the optical module speed and
Hi Peter,
On 02/01/19 5:19 PM, Peter Ujfalusi wrote:
On 27/12/2018 8.13, Lokesh Vutla wrote:
Texas Instruments' K3 generation SoCs has an IP Interrupt Aggregator
which is an interrupt controller that does the following:
- Converts events to interrupts that can be understood by
an
On Wed, Dec 26, 2018 at 07:50:29PM -0800, Matthew Wilcox wrote:
> On Wed, Dec 26, 2018 at 01:42:56PM -0600, Aditya Pakki wrote:
> > In sysctl_extfrag_handler(), proc_dointvec_minmax() can return an
> > error. The fix propagates the error upstream in case of failure.
>
> Why not just ...
>
> Mel,
Hi,
I was not aware that CONFIG_JUMP_LABEL Kconfig setting depends on the
support of asm-goto.
Currently, I am doing experiments with clang-7 and a snapshot of
clang-8 on Linux/x86.
These compilers have no asm-goto support.
What is your recommendation for Linux >= v4.20?
I am asking as it is
Hello, Tejun.
[ 1100.561812] FAULT_INJECTION: forcing a failure.
[ 1100.561812] name failslab, interval 1, probability 0, space 0, times 0
[ 1100.625231] CPU: 1 PID: 29677 Comm: syz-executor0 Not tainted 4.20.0+ #396
[ 1100.632289] Hardware name: Google Google Compute Engine/Google Compute
Hello,
syzbot found the following crash on:
HEAD commit:195303136f19 Merge tag 'kconfig-v4.21-2' of git://git.kern..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=118961fd40
kernel config: https://syzkaller.appspot.com/x/.config?x=5e7dc790609552d7
On Sat, Dec 22, 2018 at 12:43:33PM +, Colin King wrote:
> From: Colin Ian King
>
> The macro to_software_mode can potentially return NULL, so also add
> a null check on the swnode before dereferencing it to avoid any null
> pointer dereferences.
>
> Detected by CoverityScan, CID#1476052
On 27/12/2018 8.08, Lokesh Vutla wrote:
> TI AM65x SoC based on K3 architecture, introduced support for Events
> which are message based interrupts with minimal latency. These events
> are not compatible with regular interrupts and are valid only through
> an event transport lane. An Interrupt
On Wed, Jan 2, 2019 at 12:36 PM syzbot
wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:903b77c63167 Merge tag 'linux-kselftest-4.21-rc1' of git:/..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=133428e340
> kernel config:
On Wed, Jan 2, 2019 at 12:12 AM Bernard Pidoux wrote:
>
> Hi David,
>
> In my previous message I should have reported the following patch rather than
> the one I reported.
>
> The reason is that the bug is better explained here :
>
> https://marc.info/?l=linux-hams=154478673812818=2
>
> and I
On 27/12/2018 8.13, Lokesh Vutla wrote:
> Texas Instruments' K3 generation SoCs has an IP Interrupt Aggregator
> which is an interrupt controller that does the following:
> - Converts events to interrupts that can be understood by
> an interrupt router.
> - Allows for multiplexing of events
On Tue, Jan 1, 2019 at 1:53 PM Bernard Pidoux wrote:
>
> Hi Dmitry,
>
> We noticed your message on Linux kernel, netdev and ham lists.
>
> Thank you for pointing GPF due to a null pointer bug in rose module.
>
> Although I committed a patch about this AX25 NULL pointer in
> rose_route_frame, it
On 2019/1/2 18:55, Dan Carpenter wrote:
> On Fri, Dec 28, 2018 at 09:58:04AM +0100, Michal Hocko wrote:
>> On Fri 28-12-18 02:46:30, YueHaibing wrote:
>>> Fixes gcc '-Wunused-but-set-variable' warning when
>>> CONFIG_VMAP_STACK is not set:
>>
>> Isn't this warning disabled? I can see the following
On 2018/12/31 上午2:30, Michael S. Tsirkin wrote:
On Thu, Dec 27, 2018 at 05:39:21PM +0800, Jason Wang wrote:
On 2018/12/26 下午11:02, Michael S. Tsirkin wrote:
On Wed, Dec 26, 2018 at 11:57:32AM +0800, Jason Wang wrote:
On 2018/12/25 下午8:50, Michael S. Tsirkin wrote:
On Tue, Dec 25, 2018 at
Hello,
syzbot found the following crash on:
HEAD commit:903b77c63167 Merge tag 'linux-kselftest-4.21-rc1' of git:/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=133428e340
kernel config: https://syzkaller.appspot.com/x/.config?x=53a2f2aa0b1f7606
On Fri, Dec 21, 2018 at 03:26:26PM -0800, Amir Mahdi Ghorbanian wrote:
> Replaced bool in struct with unsigned int bitfield to conserve space and
> more clearly define size of varibales
>
> Signed-off-by: Amir Mahdi Ghorbanian
> ---
> drivers/staging/iio/adc/ad7192.h | 14 +++---
> 1
Since binderfs can be mounted by userns root in non-initial user namespaces
some precautions are in order. First, a way to set a maximum on the number
of binder devices that can be allocated per binderfs instance and second, a
way to reserve a reasonable chunk of binderfs devices for the initial
On 01.01.2019 20:57, Nathan Royce wrote:
Kernel 4.19.13
00:14.0 USB controller: Intel Corporation 9 Series Chipset Family USB
xHCI Controller
Around 400 "unknown event type 37" messages logged in a 2 second span.
*
Jan 01 02:08:07 computername tvheadend[2370]: linuxdvb: Auvitek AU8522
The binderfs instance in the initial ipc namespace will always have a
reserve of 4 binder devices unless explicitly capped by specifying a lower
value via the "max" mount option.
This ensures when binder devices are removed (on accident or on purpose)
they can always be recreated without risking
On Thu, Dec 20, 2018 at 02:00:01PM -0600, Kangjie Lu wrote:
> When ms_read_extra_data fails, the data read in "extra" buffer is
> just incorrect and thus should be used. However, "extra" is used
> in multiple places no matter ms_read_extra_data() fails or not.
> The fix checks the status of
On 01/02/2019 02:41 AM, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit: 28e8c4bc8eb4 Merge tag 'rtc-4.21' of git://git.kernel.org/..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=10c040d340
> kernel config:
Hello,
syzbot found the following crash on:
HEAD commit:b71acb0e3721 Merge branch 'linus' of git://git.kernel.org/..
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1222797740
kernel config: https://syzkaller.appspot.com/x/.config?x=4b137b8ba637eb77
On Wed, Jan 2, 2019 at 11:59 AM syzbot
wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:903b77c63167 Merge tag 'linux-kselftest-4.21-rc1' of git:/..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=1424673b40
> kernel config:
Masahiro Yamada writes:
> Currently, CONFIG_JUMP_LABEL just means "I _want_ to use jump label".
>
> The jump label is controlled by HAVE_JUMP_LABEL, which is defined
> like this:
>
> #if defined(CC_HAVE_ASM_GOTO) && defined(CONFIG_JUMP_LABEL)
> # define HAVE_JUMP_LABEL
> #endif
>
> We can
On Wed, Jan 02, 2019 at 04:23:15PM +0530, Souptick Joarder wrote:
> On Mon, Dec 24, 2018 at 6:53 PM Souptick Joarder wrote:
> >
> > Convert to use vm_insert_range to map range of kernel memory
> > to user vma.
> >
> > Signed-off-by: Souptick Joarder
> > Reviewed-by: Matthew Wilcox
> > Acked-by:
On Wed, Jan 02, 2019 at 12:17:31PM +0300, Dan Carpenter wrote:
> On Sun, Dec 23, 2018 at 03:35:49PM +0100, Christian Brauner wrote:
> > static inline struct binderfs_info *BINDERFS_I(const struct inode *inode)
> > @@ -110,10 +132,16 @@ static int binderfs_binder_device_create(struct inode
> >
From: Rafael J. Wysocki
Update the MAINTAINERS entry for cpufreq by making it clear that it
is not just drivers and adding current documentation records to it.
Signed-off-by: Rafael J. Wysocki
---
MAINTAINERS |4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
Index:
Hello,
syzbot found the following crash on:
HEAD commit:f12e840c819b Merge branch 'for-linus' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17b03ee740
kernel config: https://syzkaller.appspot.com/x/.config?x=76d28549be7c27cf
On Sat, Dec 29, 2018 at 11:59:52PM +0100, Petr Sedlák wrote:
> Replace variable uDelayUnit with u_delay_unit. Issue found by
> checkpatch.
>
> Signed-off-by: Petr Sedlák
> ---
> drivers/staging/vt6655/upc.h | 8
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git
Hello,
syzbot found the following crash on:
HEAD commit:7418e6520f22 isdn: hisax: hfc_pci: Fix a possible concurre..
git tree: net
console output: https://syzkaller.appspot.com/x/log.txt?x=137658e740
kernel config: https://syzkaller.appspot.com/x/.config?x=fbee5876573727cd
Hello,
syzbot found the following crash on:
HEAD commit:903b77c63167 Merge tag 'linux-kselftest-4.21-rc1' of git:/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1424673b40
kernel config: https://syzkaller.appspot.com/x/.config?x=53a2f2aa0b1f7606
On Fri, Dec 28, 2018 at 09:58:04AM +0100, Michal Hocko wrote:
> On Fri 28-12-18 02:46:30, YueHaibing wrote:
> > Fixes gcc '-Wunused-but-set-variable' warning when
> > CONFIG_VMAP_STACK is not set:
>
> Isn't this warning disabled? I can see the following
> # These warnings generated too much noise
Hi Stephen,
Stephen Boyd wrote on Thu, 20 Dec 2018 13:09:19
-0800:
> Quoting Miquel Raynal (2018-12-19 00:03:31)
> > Hi Stephen,
> >
> > Stephen Boyd wrote on Tue, 18 Dec 2018 16:03:29
> > -0800:
> >
> > > Quoting Miquel Raynal (2018-12-04 11:24:37)
> > > > Currently, the core->dev entry
On machines where the GART aperture is mapped over physical RAM,
/proc/kcore contains the GART aperture range and reading it may lead
to kernel panic.
In 'commit 2a3e83c6f96c ("x86/gart: Exclude GART aperture from vmcore")',
a special workaround is applied for vmcore to let /proc/vmcore return
On Mon, Dec 24, 2018 at 6:53 PM Souptick Joarder wrote:
>
> Convert to use vm_insert_range to map range of kernel memory
> to user vma.
>
> Signed-off-by: Souptick Joarder
> Reviewed-by: Matthew Wilcox
> Acked-by: Marek Szyprowski
> Acked-by: Mauro Carvalho Chehab
> ---
>
On Thu, Dec 27, 2018 at 01:35:53PM -0600, Aditya Pakki wrote:
> In ms_copy_page, the function ms_read_extra_data may fail for many
> reasons. The fix adds a check similar to other invocation to return
> error upstream.
>
> Signed-off-by: Aditya Pakki
Yup. It doesn't make sense to use stale
On Sat, 2018-12-22 at 18:01 +0100, Martin Blumenstingl wrote:
> Hi Jerome,
>
> On Thu, Dec 20, 2018 at 5:11 PM Jerome Brunet wrote:
> > While some 3.3v eMMC 4.0 are available from libretech, the default
> > option for the aml-s905x-cc seems to 1.8v 5.0 modules.
> nit-pick:
> can you please state
Hello,
syzbot found the following crash on:
HEAD commit:195303136f19 Merge tag 'kconfig-v4.21-2' of git://git.kern..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14fcd2e740
kernel config: https://syzkaller.appspot.com/x/.config?x=5e7dc790609552d7
On Sat, 29 Dec 2018 at 07:43, Aisheng Dong wrote:
>
> > From: Ulf Hansson [mailto:ulf.hans...@linaro.org]
> > Sent: Friday, December 28, 2018 11:37 PM
> >
> > On Thu, 27 Dec 2018 at 18:14, Aisheng Dong
> > wrote:
> > >
> > > Currently attach_dev() in power domain infrastructure still does not
>
Hi Florian,
On Thu, 2018-12-20 at 17:34 -0800, Florian Fainelli wrote:
> Add support for resetting blocks through the Linux reset controller
> subsystem when reset lines are provided through a SW_INIT-style reset
> controller on Broadcom STB SoCs.
>
> Signed-off-by: Florian Fainelli
Thank you,
On 29/12/2018 13:10, Stefan Wahren wrote:
Hi,
during development i noticed that hns3_enet.c is compiled even without any
changes to this file.
I think the reason for this is the usage of VERMAGIC_STRING in this file. So it
would be nice if you could somehow replace this define.
Kind regards
Hello,
syzbot found the following crash on:
HEAD commit:195303136f19 Merge tag 'kconfig-v4.21-2' of git://git.kern..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17fd7ae740
kernel config: https://syzkaller.appspot.com/x/.config?x=5e7dc790609552d7
Hello,
syzbot found the following crash on:
HEAD commit:e1ef035d272e Merge tag 'armsoc-defconfig' of git://git.ker..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1674b0bb40
kernel config: https://syzkaller.appspot.com/x/.config?x=9c6a26e22579190b
Hello,
syzbot found the following crash on:
HEAD commit:28e8c4bc8eb4 Merge tag 'rtc-4.21' of git://git.kernel.org/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10c040d340
kernel config: https://syzkaller.appspot.com/x/.config?x=c2ab9708c613a224
On 12/27/18 6:26 AM, Peng Hao wrote:
> Remove unneeded semicolon.
>
> Signed-off-by: Peng Hao
> ---
> arch/arm/mm/pmsa-v8.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/mm/pmsa-v8.c b/arch/arm/mm/pmsa-v8.c
> index 617a83d..0d7d5fb 100644
> ---
On Tue, Dec 25, 2018 at 08:39:53PM -0600, Kangjie Lu wrote:
> register_netdev() may fail, so let's check its return value, and if it
> fails, issue an error message.
>
> Signed-off-by: Kangjie Lu
> ---
> drivers/staging/rtl8712/hal_init.c | 5 +++--
> 1 file changed, 3 insertions(+), 2
Hello,
syzbot found the following crash on:
HEAD commit:6a1d293238c1 Add linux-next specific files for 20181224
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=100ff080c0
kernel config: https://syzkaller.appspot.com/x/.config?x=af046212050aa3ac
Hi Linus,
Please pull from the tag
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
devprop-4.21-rc1-2
with top-most commit f4747b9c68b8864cac32cddc45fdcfdfafb3397c
drivers: base: swnode: check if swnode is NULL before dereferencing it
on top of commit
On Wed, Jan 2, 2019 at 11:24 AM Vlastimil Babka wrote:
>
> On 1/2/19 11:03 AM, Dmitry Vyukov wrote:
> > On Wed, Jan 2, 2019 at 10:47 AM Vlastimil Babka wrote:
> >>
> >> Actually the fix was folded into the patch that caused the bug, and was
> >> already sent to and merged by Linus, commit
> >>
On Fri, Dec 28, 2018 at 12:36:21AM -0800, Christoph Hellwig wrote:
> Please try this patch:
>
The error type change to "DMA-API: gem :00:0f.0: device driver failed to
check map error" (I will send patch for fixing this).
Note that I used the patch from your just sent DMA series (since the
Hello,
syzbot found the following crash on:
HEAD commit:195303136f19 Merge tag 'kconfig-v4.21-2' of git://git.kern..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10abf75740
kernel config: https://syzkaller.appspot.com/x/.config?x=5e7dc790609552d7
Hello,
syzbot found the following crash on:
HEAD commit:e1ef035d272e Merge tag 'armsoc-defconfig' of git://git.ker..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16bb4c4b40
kernel config: https://syzkaller.appspot.com/x/.config?x=9c6a26e22579190b
Hello,
syzbot found the following crash on:
HEAD commit:e1ef035d272e Merge tag 'armsoc-defconfig' of git://git.ker..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=159934e340
kernel config: https://syzkaller.appspot.com/x/.config?x=9c6a26e22579190b
On Tue, Dec 25, 2018 at 02:33:32AM -0600, Kangjie Lu wrote:
> sd_init_power() could fail. The fix inserts a check of its status. If it
> fails, returns STATUS_FAIL.
>
> Signed-off-by: Kangjie Lu
> ---
> drivers/staging/rts5208/sd.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
>
RK809 and RK817 are power management IC chips for multimedia products.
most of their functions and registers are same, including the clkout
funciton.
Signed-off-by: Tony Xie
Acked-by: Stephen Boyd
---
drivers/clk/Kconfig | 9 +++---
drivers/clk/clk-rk808.c | 64
The RK809 and RK817 are a Power Management IC (PMIC) for multimedia
and handheld devices. They contains the following components:
- Regulators
- RTC
- Clocking
Both RK809 and RK817 chips are using a similar register map,
so we can reuse the RTC and Clocking functionality.
Most of regulators
Add support for the rk809 and rk817 regulator driver.
Their specifications are as follows：
1. The RK809 and RK809 consist of 5 DCDCs, 9 LDOs
and have the same registers for these components except dcdc5.
2. The dcdc5 is a boost dcdc for RK817 and is a buck for RK809.
3.
Add device tree bindings documentation for Rockchip's RK809 & RK817 PMIC.
Signed-off-by: Tony Xie
Reviewed-by: Rob Herring
Acked-for-MFD-by: Lee Jones
---
.../devicetree/bindings/mfd/rk808.txt | 44 +++
1 file changed, 44 insertions(+)
diff --git
Most of functions and registers of the rk817 and rk808 are the same,
so they can share allmost all codes.
Their specifications are as follows:
1) The RK809 and RK809 consist of 5 DCDCs, 9 LDOs and have the same
registers
for these components except dcdc5.
2) The dcdc5 is a boost dcdc for
Remove the id_table because it's not used.
Signed-off-by: Tony Xie
---
drivers/mfd/rk808.c | 9 -
1 file changed, 9 deletions(-)
diff --git a/drivers/mfd/rk808.c b/drivers/mfd/rk808.c
index 216fbf6adec9..94377782d208 100644
--- a/drivers/mfd/rk808.c
+++ b/drivers/mfd/rk808.c
@@ -568,14
RK809 and RK817 are power management IC chips for multimedia products.
Most of their functions and registers are same, including the rtc.
Signed-off-by: Tony Xie
Acked-by: Alexandre Belloni
---
drivers/rtc/Kconfig | 4 +--
drivers/rtc/rtc-rk808.c | 68
Hi,
On 21/12/2018 07:27, Andrey Smirnov wrote:
> Default implementation of pcie_rd_other_conf() and
> dw_pcie_wd_other_conf() share more than 80% of their code. Move shared
> code into a dedicated subroutine and convert pcie_rd_other_conf() and
> dw_pcie_wd_other_conf() to use it. No functional
On 1/2/19 11:03 AM, Dmitry Vyukov wrote:
> On Wed, Jan 2, 2019 at 10:47 AM Vlastimil Babka wrote:
>>
>> Actually the fix was folded into the patch that caused the bug, and was
>> already sent to and merged by Linus, commit
>> 7635d9cbe8327e131a1d3d8517dc186c2796ce2e
>
>
> But the email thread
On Tue, Dec 18, 2018 at 06:25:27PM +0100, David Hildenbrand wrote:
> On 18.12.18 18:13, Cornelia Huck wrote:
> > On Mon, 17 Dec 2018 14:56:38 +
> > Stefan Hajnoczi wrote:
> >
> >> On Mon, Dec 17, 2018 at 11:53:46AM +0100, David Hildenbrand wrote:
> >>> On 14.12.18 14:44, Stefan Hajnoczi
Hello,
syzbot found the following crash on:
HEAD commit:e1ef035d272e Merge tag 'armsoc-defconfig' of git://git.ker..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=166315fd40
kernel config: https://syzkaller.appspot.com/x/.config?x=9c6a26e22579190b
On 01/02/19 at 11:27am, Mike Rapoport wrote:
> On Wed, Jan 02, 2019 at 02:47:34PM +0800, Pingfan Liu wrote:
> > On Mon, Dec 31, 2018 at 4:40 PM Mike Rapoport wrote:
> > >
> > > On Fri, Dec 28, 2018 at 11:00:01AM +0800, Pingfan Liu wrote:
> > > > The bottom-up allocation style is introduced to
Hi,
On 19/12/2018 12:42, Kishon Vijay Abraham I wrote:
> Now that Keystone started using it's own msi_irq_chip, remove
> Keystone specific callback function defined in dw_pcie_host_ops.
>
> Signed-off-by: Kishon Vijay Abraham I
> ---
> .../pci/controller/dwc/pcie-designware-host.c | 45
Hi,
On 19/12/2018 12:42, Kishon Vijay Abraham I wrote:
> Platforms using Designware IP uses dw_pci_msi_bottom_irq_chip for
> configuring the MSI controller logic within the Designware IP. However
> certain platforms like Keystone (K2G) which uses Desingware IP has
> it's own MSI controller logic.
Hi,
On 19/12/2018 12:42, Kishon Vijay Abraham I wrote:
> Platforms which populate msi_host_init, has it's own MSI controller
> logic. Writing to MSI control registers on platforms which doesn't use
> Designware's MSI controller logic might have side effects. To
> be safe, do not write to MSI
Hi all,
(and, happy new year to everyone!)
this looks similar to a bug we have seen some time ago (a task
switching from SCHED_OTHER to SCHED_DEADLINE while inheriting a
deadline from a SCHED_DEADLINE task triggers the warning)...
Juri, I think you found a fix for such a bug; has it been
On Wed, Dec 19, 2018 at 2:23 PM Jens Axboe wrote:
>
> On 12/19/18 3:23 AM, Alexander Potapenko wrote:
> > On Thu, Sep 13, 2018 at 11:23 AM Alexander Potapenko
> > wrote:
> >>
> >> On Thu, Sep 13, 2018 at 11:18 AM syzbot
> >> wrote:
> >>>
> >>> Hello,
> >>>
> >>> syzbot found the following
Hi Arnd,
On Sun, Dec 16, 2018 at 8:50 PM Arnd Bergmann wrote:
> This is one of only two files that initialize a semaphore to a negative
> value. We don't really need the two semaphores here at all, but can do
> the same thing in more conventional and more effient way, by using a
> single
On Wed, Jan 2, 2019 at 10:47 AM Vlastimil Babka wrote:
>
> On 1/2/19 10:42 AM, Dmitry Vyukov wrote:
> > On Wed, Jan 2, 2019 at 8:42 AM Vlastimil Babka wrote:
> >>
> >> On 12/24/18 4:48 PM, syzbot wrote:
> >>> Hello,
> >>>
> >>> syzbot found the following crash on:
> >>>
> >>> HEAD commit:
On Wed, Jan 02, 2019 at 09:15:12AM +0800, kernel test robot wrote:
> Greetings,
>
> 0day kernel testing robot got the below dmesg and the first bad commit is
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>
> commit bea5b158ff0da9c7246ff391f754f5f38e34577a
>
On 12/19/18 10:24 AM, Greg KH wrote:
> On Fri, Dec 07, 2018 at 01:28:52PM +0100, Peter Rajnoha wrote:
>> On 12/7/18 1:01 PM, Greg KH wrote:
>>> On Fri, Dec 07, 2018 at 12:46:07PM +0100, Peter Rajnoha wrote:
This patch adds /sys/kernel/uevent_features file which currently lists
401 - 500 of 547 matches
Mail list logo
