On Mon, Apr 02, 2018 at 02:52:31PM -0600, Shuah Khan wrote:
> vhci_hcd module can be removed even when devices are attached. Fix to
> prevent module removal when devices are still attached.
>
> Signed-off-by: Shuah Khan
> ---
> drivers/usb/usbip/vhci_sysfs.c | 25 +
> 1 f
On Mon, Apr 02, 2018 at 02:52:32PM -0600, Shuah Khan wrote:
> vhci_hcd fails to do reset to put usb device and sockfd in the
> module remove/stop paths. Fix the leak.
>
> Signed-off-by: Shuah Khan
Should this be marked for the stable kernels?
thanks,
greg k-h
On Tue, Apr 3, 2018 at 2:18 PM, Mylène Josserand
wrote:
> To add the support for SMP on sun8i-a83t, we will use some
> definitions in an assembly file so move definitions into
> another file to separate C functions and macro defintions.
Instead of moving the definitions, you could guard all the C
On Mon, Apr 2, 2018 at 4:26 PM, Robert Jarzmik wrote:
> +
> +static const struct dma_slave_map pxa_slave_map[] = {
> + /* PXA25x, PXA27x and PXA3xx common entries */
> + { "pxa-pcm-audio", "ac97_mic_mono", PDMA_FILTER_PARAM(LOWEST, 8) },
> + { "pxa-pcm-audio", "ac97_aux_mono_in",
On 2018-04-02 22:20, Boris Brezillon wrote:
> On Mon, 2 Apr 2018 21:28:43 +0200
> Boris Brezillon wrote:
>
>> On Mon, 2 Apr 2018 19:59:39 +0200
>> Peter Rosin wrote:
>>
>>> On 2018-04-02 14:22, Boris Brezillon wrote:
On Thu, 29 Mar 2018 16:27:12 +0200
Peter Rosin wrote:
>>
On Tue, Apr 3, 2018 at 2:18 PM, Mylène Josserand
wrote:
> Add CCI-400 node and control-port on CPUs needed by SMP bringup.
>
> Signed-off-by: Mylène Josserand
Reviewed-by: Chen-Yu Tsai
On Tue, Apr 3, 2018 at 2:18 PM, Mylène Josserand
wrote:
> As we found in sun9i-a80, CPUCFG is a collection of registers that are
> mapped to the SoC's signals from each individual processor core and
> associated peripherals.
>
> These registers are used for SMP bringup and CPU hotplugging.
>
> Sig
As we found in sun9i-a80, CPUCFG is a collection of registers that are
mapped to the SoC's signals from each individual processor core and
associated peripherals.
These registers are used for SMP bringup and CPU hotplugging.
Signed-off-by: Mylène Josserand
---
arch/arm/boot/dts/sun8i-a83t.dtsi
The R_CPUCFG is a collection of registers needed for SMP bringup
on clusters and cluster's reset.
For the moment, documentation about this register is found in
Allwinner's code only.
Signed-off-by: Mylène Josserand
---
arch/arm/boot/dts/sun8i-a83t.dtsi | 5 +
1 file changed, 5 insertions(+)
Add CCI-400 node and control-port on CPUs needed by SMP bringup.
Signed-off-by: Mylène Josserand
---
arch/arm/boot/dts/sun8i-a83t.dtsi | 41 +++
1 file changed, 41 insertions(+)
diff --git a/arch/arm/boot/dts/sun8i-a83t.dtsi
b/arch/arm/boot/dts/sun8i-a83t.dt
The CNTVOFF register from arch timer is uninitialized.
It should be done by the bootloader but it is currently not the case,
even for boot CPU because this SoC is booting in secure mode.
It leads to an random offset value meaning that each CPU will have a
different time, which isn't working very we
Add the initialization of CNTVOFF for sun8i-a83t.
For boot CPU, Create a new machine that handles this
function's call in an "init_early" callback.
For secondary CPUs, add this function into secondary_startup
assembly entry.
Signed-off-by: Mylène Josserand
---
arch/arm/mach-sunxi/headsmp.S | 1
Move the CPU resume assembly function into the assembly file
to remove all assembly code from C code.
Signed-off-by: Mylène Josserand
---
arch/arm/mach-sunxi/headsmp.S | 5 +
arch/arm/mach-sunxi/mc_smp.c | 11 +--
2 files changed, 6 insertions(+), 10 deletions(-)
diff --git a/arch
To add the support for SMP on sun8i-a83t, we will use some
definitions in an assembly file so move definitions into
another file to separate C functions and macro defintions.
Signed-off-by: Mylène Josserand
---
arch/arm/include/asm/cputype.h | 94 +---
arch/ar
To prepare the support of sun8i-a83t, add a field in the smp_data
structure to enable the case of sun9i.
Start to handle the differences between sun9i-a80 and sun8i-a83t
by using this variable.
Add an index to retrieve which structures we are using.
Signed-off-by: Mylène Josserand
---
arch/arm/
Move the assembly code for cluster cache enabling
into an assembly file instead of having it directly in C code.
Remove the CFLAGS because we are using the ARM directive "arch"
instead.
Signed-off-by: Mylène Josserand
---
arch/arm/mach-sunxi/Makefile | 4 +--
arch/arm/mach-sunxi/headsmp.S | 7
Add the support for A83T.
A83T SoC has an additional register than A80 to handle CPU configurations:
R_CPUS_CFG. Information about the register comes from Allwinner's BSP
driver.
An important difference is the Power Off Gating register for clusters
which is BIT(4) in case of SUN9I-A80 and BIT(0) i
To prepare the support for sun8i-a83t, rename the variable name
that handles the power-off of clusters because it is different from
sun9i-a80 to sun8i-a83t.
The power off register for clusters are different from a80 and a83t.
Signed-off-by: Mylène Josserand
Acked-by: Maxime Ripard
---
arch/arm
To prepare the support for sun8i-a83t, move some structures
at the beginning of the file.
Signed-off-by: Mylène Josserand
---
arch/arm/mach-sunxi/mc_smp.c | 48 +++-
1 file changed, 25 insertions(+), 23 deletions(-)
diff --git a/arch/arm/mach-sunxi/mc_smp
Add the use of enable-method property for SMP support which allows
to handle the SMP support for this specific SoC.
This commit adds enable-method properties to all CPU nodes.
Signed-off-by: Mylène Josserand
---
arch/arm/boot/dts/sun8i-a83t.dtsi | 8
1 file changed, 8 insertions(+)
di
Hello everyone,
This is a V5 of my series that adds SMP support for Allwinner sun8i-a83t.
Based on sunxi's tree, sunxi/for-next branch.
For boot CPU, I tried to add the CNTVOFF initialization in mc_smp.c file
(in sunxi_mc_smp_init function) but it is not working.
Instead of adding it in timer's f
On 2018-04-02 22:20, Boris Brezillon wrote:
> On Mon, 2 Apr 2018 21:28:43 +0200
> Boris Brezillon wrote:
>
>> On Mon, 2 Apr 2018 19:59:39 +0200
>> Peter Rosin wrote:
>>
>>> On 2018-04-02 14:22, Boris Brezillon wrote:
On Thu, 29 Mar 2018 16:27:12 +0200
Peter Rosin wrote:
>>
There would be so many same lines printed by frequent printk if one
disk went wrong, like,
[ 546.185242] sd 0:1:0:0: rejecting I/O to offline device
[ 546.185258] sd 0:1:0:0: rejecting I/O to offline device
[ 546.185280] sd 0:1:0:0: rejecting I/O to offline device
[ 546.185307] sd 0:1:0:0: reje
On Friday 30 March 2018 03:11 PM, Arkadiusz Kwiatkowski wrote:
> This commit fixes the order of parameters passed to regmap_update_bits
> function inside spi-ti-qspi driver. Accidentally the code worked
> correctly when cs=0, but it is not the case for other values.
>
Add:
Fixes: 4dea6c9b0b64 (
Hi Corey,
The 4.17 merge window is opened now, this patch is not yet in linux-next
tree,
so it will be merged into 4.18 ?
Thanks & Regards,
Haiyue
On 2018-03-15 20:20, Haiyue Wang wrote:
Allocate a continuous memory block for the three KCS data buffers with
related index assignment.
Signe
ping,
this week is a merge window. Any chance to get it in to 4.17?
On 05.03.2018 11:25, Oleksij Rempel wrote:
> This patch series is providing power off support for Freescale/NXP iMX6 based
> boards with external power management integrated circuit (PMIC).
> As a first step the PMIC is configure
On Thu, 29 Mar 2018 20:08:36 +0200
Peter Zijlstra wrote:
> On Thu, Mar 29, 2018 at 04:53:43PM +0200, Martin Schwidefsky wrote:
> > The lowcore optimization for softirq_pending field is not really needed,
> > just nice to have. But if there is a strong reason to make a common
> > definition for it
2018-04-03 0:04 GMT+08:00 Linus Torvalds :
> On Sun, Apr 1, 2018 at 11:01 PM, Greentime Hu wrote:
>>
>> This tag contains the core nds32 Linux port(including interrupt controller
>> driver and timer driver), which has been through 7 rounds of review on
>> mailing
>> list.
>
> Can I get an overvie
On Monday 02 April 2018 09:45 PM, David Lechner wrote:
> On 04/02/2018 06:12 AM, Sekhar Nori wrote:
>> On Friday 16 March 2018 10:50 PM, David Lechner wrote:
>>> On 03/15/2018 09:52 PM, David Lechner wrote:
This adds clock provider nodes for da850 and wires them up to all of
the
devi
On 4/2/2018 12:12 PM, Jiri Pirko wrote:
Fri, Mar 30, 2018 at 05:11:29PM CEST, and...@lunn.ch wrote:
Please see:
http://patchwork.ozlabs.org/project/netdev/list/?series=36524
I bevieve that the solution in the patchset could be used for
your usecase too.
Hi Jiri
https://lkml.org/lkml/2018/3/
Hi all,
After merging the tip tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
net/rxrpc/call_object.c: In function 'rxrpc_rcu_destroy_call':
net/rxrpc/call_object.c:661:3: error: implicit declaration of function
'wake_up_atomic_t'; did you mean 'wake_up_bit'?
[-Werror=imp
On Tuesday 03 April 2018 01:07 AM, Niklas Cassel wrote:
> On Thu, Mar 29, 2018 at 03:17:11PM +0530, Kishon Vijay Abraham I wrote:
>> Hi,
>>
>> On Wednesday 28 March 2018 05:20 PM, Niklas Cassel wrote:
>>> Since a 64-bit BAR consists of a BAR pair, we need to write to both
>>> BARs in the BAR pair
Commit cc6b741c6f63 ("drm: sti: remove useless fields from vtg
structure") reworked some code inside of this driver and made it select
CONFIG_OF. This results in the entire OF layer being enabled when
building an allmodconfig on ia64. OF on ia64 is completely unsupported
so this isn't a great state
On 04/03, Chao Yu wrote:
> On 2018/3/31 0:30, Jaegeuk Kim wrote:
> > Change log from v1:
> > - add more description
> >
> > This fixes xfstests/generic/392.
> >
> > The failure was caused by different times between 1) one marked in the last
> > fsync(2) call and 2) the other given by roll-forwar
Change log from v2:
- update do_read_inode
Change log from v1:
- add more description
This fixes xfstests/generic/392.
The failure was caused by different times between 1) one marked in the last
fsync(2) call and 2) the other given by roll-forward recovery after power-cut.
The reason was that
On 04/03/18 02:57, Pierre-Louis Bossart wrote:
>
>
> On 04/02/2018 04:17 PM, Kirill Marinushkin wrote:
>> Hello Pierre-Louis,
>>
>> I explicitly clarified with Takashi: to have this patch series merged, we
>> need a
>> tag "Reviewed-by" from you.
> I am fine with the changes, but maybe while we ar
On Mon, Apr 02, 2018 at 12:06:14PM -0500, Pierre-Louis Bossart wrote:
> The split between ACPI and PCI platforms generated issues with randconfig:
>
> with SND_SST_ATOM_HIFI2_PLATFORM_PCI=y and
> SND_SST_ATOM_HIFI2_PLATFORM=m, we get this module link failure:
>
> ERROR: "sst_context_init"
> [soun
Hi Linus,
Here's the first round of fixes for XFS for 4.17. The biggest new
features this time around are the addition of lazytime support, further
enhancement of the on-disk inode metadata verifiers, and a patch to
smooth over some of the AGFL padding problems that have intermittently
plagued us
My testing for the latest kernel supporting thp migration found out an
infinite loop in offlining the memory block that is filled with shmem
thps. We can get out of the loop with a signal, but kernel should
return with failure in this case.
What happens in the loop is that scan_movable_pages() re
Hi Paul,
Today's linux-next merge of the selinux tree got a conflict in:
include/linux/lsm_hooks.h
between commit:
22402b0b736d ("security: convert security hooks to use hlist")
from the security tree and commit:
72e89f50084c ("security: Add support for SCTP security hooks")
from the s
On Mon, Apr 02, 2018 at 07:01:02PM -0700, syzbot wrote:
> Hello,
>
> syzbot hit the following crash on upstream commit
> 86bbbebac1933e6e95e8234c4f7d220c5ddd38bc (Mon Apr 2 18:47:07 2018 +)
> Merge branch 'ras-core-for-linus' of
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
> syzbot
Hi Ran,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on powerpc/next]
[also build test WARNING on v4.16 next-20180329]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/
On Mon, Apr 2, 2018 at 12:04 PM, Dominik Brodowski
wrote:
>
> This patchset removes all in-kernel calls to syscall functions in the
> kernel with the exception of arch/.
Ok, this finished off my arch updates for today, I'll probably move on
to driver pulls tomorrow.
Anyway, it's in my tree, will
On 03-04-18, 08:11, Sricharan R wrote:
> Right, i was adding a similar one for krait cores [1]. There is code common
> in the
> init sequence across both (little). Do you suggest to make them common ?
It may make sense as we are talking about one SoC family here :)
--
viresh
On 02-04-18, 11:49, Suman Anna wrote:
> The ti_cpufreq_probe() function uses regular kzalloc to allocate
> the ti_cpufreq_data structure and kfree for freeing this memory
> on failures. Simplify this code by using the devres managed
> API.
>
> Cc: Zumeng Chen
> Signed-off-by: Suman Anna
> ---
>
On 02-04-18, 11:49, Suman Anna wrote:
> Commit 05829d9431df ("cpufreq: ti-cpufreq: kfree opp_data when
> failure") has fixed a memory leak in the failure path, however
> the patch returned a positive value on get_cpu_device() failure
> instead of the previous negative value. Fix this incorrect erro
No. Only the first crash (WARNING in refcount_dec) is reproduced by
the attached reproducer.
The second crash (kernel bug at af_packet.c:3107) is reproduced by
another reproducer.
We reported it here.
http://lkml.iu.edu/hypermail/linux/kernel/1803.3/05324.html
On Sun, Apr 1, 2018 at 4:38 PM, Will
On Mon, Apr 2, 2018 at 12:17 AM, Arnd Bergmann wrote:
>
> The series is rather long and conflicts in trivial ways with lots
> of subsystem trees. You probably want to pull it either really
> early in the merge window or really late.
Ok, I've been pulling arch updates, so it went in now.
Side not
On Tue, Apr 03, 2018 at 01:41:26PM +1000, NeilBrown wrote:
>
> Do we really need a rhashtable_walk_peek() interface?
> I imagine that a seqfile ->start function can do:
>
> if (*ppos == 0 && last_pos != 0) {
> rhashtable_walk_exit(&iter);
> rhashtable_walk_enter(&table, &iter);
>
On Fri, Mar 30 2018, Herbert Xu wrote:
> On Thu, Mar 29, 2018 at 06:52:34PM +0200, Andreas Gruenbacher wrote:
>>
>> Should rhashtable_walk_peek be kept around even if there are no more
>> users? I have my doubts.
>
> Absolutely. All netlink dumps using rhashtable_walk_next are buggy
> and need to
The movable_node option is a boot-time switch to make sure the physical
NUMA nodes can be hot-added/removed when ACPI table can't be parsed to
provide the memory hotplug information.
As we all know, there is always one node, called "home node", which
can't be movabled and the kernel image resides
On Sun, Apr 01, 2018 at 03:32:37PM -0700, Matthew Wilcox wrote:
> From: Matthew Wilcox
>
> The entire point of printing the pointers in list_debug is to see if
> there's any useful information in them (eg poison values, ASCII, etc);
> obscuring them to see if they compare equal makes them much le
On Mon, Mar 19, 2018 at 08:04:34PM +0200, Ido Schimmel wrote:
>On Mon, Mar 19, 2018 at 03:48:00PM +, Sasha Levin wrote:
>> From: Ido Schimmel
>>
>> [ Upstream commit 5609b80a37f69f796548339e675256188b29c17d ]
>>
>> It is valid to install routes with a nexthop device that does not have a
>> car
On Mon, Mar 19, 2018 at 04:56:49PM +0100, Florian Westphal wrote:
>Sasha Levin wrote:
>> From: Florian Westphal
>>
>> [ Upstream commit f92b40a8b2645af38bd6814651c59c1e690db53d ]
>
>This patch is broken and a fix is not in any tree yet.
Removed for now, thanks!
On Mon, Mar 19, 2018 at 10:55:16AM -0500, David Lechner wrote:
>On 03/19/2018 10:48 AM, Sasha Levin wrote:
>>From: David Lechner
>>
>>[ Upstream commit a12aa8a68dfef5de181f2e555aa950a0ab05411f ]
>>
>>Reentrant calls to clk_enable() are not working on UP systems. This is
>>caused by the fact spin_t
On Mon, Mar 26, 2018 at 09:12:03AM +, mario.limoncie...@dell.com wrote:
>> -Original Message-
>> From: Sasha Levin [mailto:alexander.le...@microsoft.com]
>> Sent: Monday, March 19, 2018 10:48 AM
>> To: linux-kernel@vger.kernel.org; sta...@vger.kernel.org
>> Cc: Limonciello, Mario ; Bob
On Mon, 02 Apr 2018 05:31:22 PDT (-0700), alan...@andestech.com wrote:
This implements the baseline PMU for RISC-V platforms.
To ease future PMU portings, a guide is also written, containing
perf concepts, arch porting practices and some hints.
Changes in v2:
- Fix the bug reported by Alex, wh
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
drivers/net/ethernet/mellanox/mlx5/core/en_main.c
between commit:
2907938d2375 ("net/mlx5e: Use pcie_bandwidth_available() to compute
bandwidth")
from the pci tree and commit:
0608d4dbaf4e ("net/mlx5e: Unify slow
On Mon, Apr 02, 2018 at 06:00:57PM -0500, Eric W. Biederman wrote:
> syzbot writes:
>
> > Hello,
> >
> > syzbot hit the following crash on upstream commit
> > 9dd2326890d89a5179967c947dab2bab34d7ddee (Fri Mar 30 17:29:47 2018 +)
> > Merge tag 'ceph-for-4.16-rc8' of git://github.com/ceph/ceph-
On 4/2/2018 3:53 PM, Ard Biesheuvel Wrote:
On 2 April 2018 at 09:49, Jia He wrote:
On 4/2/2018 2:55 PM, Ard Biesheuvel Wrote:
On 2 April 2018 at 04:30, Jia He wrote:
Commit b92df1de5d28 ("mm: page_alloc: skip over regions of invalid pfns
where possible") optimized the loop in memmap_init_
Hello,
syzbot hit the following crash on upstream commit
86bbbebac1933e6e95e8234c4f7d220c5ddd38bc (Mon Apr 2 18:47:07 2018 +)
Merge branch 'ras-core-for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
syzbot dashboard link:
https://syzkaller.appspot.com/bug?extid=cef9473c7
Hello,
syzbot hit the following crash on upstream commit
86bbbebac1933e6e95e8234c4f7d220c5ddd38bc (Mon Apr 2 18:47:07 2018 +)
Merge branch 'ras-core-for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
syzbot dashboard link:
https://syzkaller.appspot.com/bug?extid=695623534
On Mon, 02 Apr 2018 00:17:30 PDT (-0700), Arnd Bergmann wrote:
- openrisc, risc-v and nds32 are still in the process of finishing their
support or getting it added to mainline gcc in the first place.
They all have patched gcc-7.3 ports that work to some degree, but
complete upstream support
On 2018/4/2 20:22, Yunlong Song wrote:
> In make_dentry_ptr_block, it is confused with "&" for t->dentry_bitmap
> but without "&" for t->dentry, so delete "&" to make code more readable.
>
> Signed-off-by: Yunlong Song
Reviewed-by: Chao Yu
Thanks,
Hi Viresh,
On 4/2/2018 8:37 PM, Sricharan R wrote:
> Hi Viresh,
>
> On 4/2/2018 3:00 PM, Viresh Kumar wrote:
>> +Sricharan,
>>
>> On 30-03-18, 00:26, Ilia Lin wrote:
>>> In Certain Qualcomm Technologies, Inc. SoCs like apq8096 and msm8996
>>> that have KRYO processors, the CPU ferequencies subset
On 2018/3/31 9:57, Jaegeuk Kim wrote:
> If write is failed, we must deallocate the blocks that we couldn't write.
>
> Cc: sta...@vger.kernel.org
> Signed-off-by: Jaegeuk Kim
Reviewed-by: Chao Yu
Thanks,
This patch adds support for HP LT4220.
Signed-off-by: Edward Chang
---
drivers/usb/serial/option.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/usb/serial/option.c b/drivers/usb/serial/option.c
index 2d8d915..a8988d5 100644
--- a/drivers/usb/serial/option.c
+++ b/drivers/u
From: NeilBrown
Date: Tue, 03 Apr 2018 12:23:40 +1000
> I'm sorry if I've caused some confusion, but I didn't think that I was
> submitting patches to you and know nothing about your two trees.
> I was submitting patches to Thomas and Herbert, the registered
> maintainers of rhashtable. I as
Hi Bjorn,
Today's linux-next merge of the pci tree got a conflict in:
drivers/pci/quirks.c
between commit:
7dcf688d4c78 ("PCI/cxgb4: Extend T3 PCI quirk to T4+ devices")
from Linus' tree and commit:
996058573b22 ("PCI/VPD: Move VPD quirks to vpd.c")
from the pci tree.
I fixed it up (I
Hi all,
Ping?
On Wed, 14 Mar 2018 10:17:04 +1100 Stephen Rothwell
wrote:
>
> On Thu, 1 Feb 2018 09:25:51 +1100 Stephen Rothwell
> wrote:
> >
> > On Tue, 30 Jan 2018 16:25:35 -0800 Jaegeuk Kim wrote:
> > >
> > > On 01/31, Stephen Rothwell wrote:
> > > >
> > > > On Tue, 30 Jan 2018 14:3
On 3/22/2018 12:26 PM, Sinan Kaya wrote:
> @@ -860,7 +860,7 @@ static void doorbell_cq(struct qedr_cq *cq, u32 cons, u8
> flags)
> wmb();
> cq->db.data.agg_flags = flags;
> cq->db.data.value = cpu_to_le32(cons);
> - writeq(cq->db.raw, cq->db_addr);
> + writeq_relaxed(cq->
On 2018/3/31 0:30, Jaegeuk Kim wrote:
> Change log from v1:
> - add more description
>
> This fixes xfstests/generic/392.
>
> The failure was caused by different times between 1) one marked in the last
> fsync(2) call and 2) the other given by roll-forward recovery after power-cut.
> The reason
Hi Al,
On Mon, 19 Mar 2018 17:06:27 +1100 Stephen Rothwell
wrote:
>
> After merging the vfs tree, today's linux-next build (x86_64 allnoconfig)
> failed like this:
>
> fs/super.c: In function 'do_thaw_all_callback':
> fs/super.c:942:3: error: implicit declaration of function
> 'emergency_thaw_
On Fri, Mar 30 2018, David Miller wrote:
> From: NeilBrown
> Date: Thu, 29 Mar 2018 12:19:09 +1100
>
>> These two patches apply on top of my previous "rhashtable: reset iter
>> when rhashtable_walk_start sees new table" patch.
>>
>> The first fixes a bug that I found in rhltable_insert().
>>
>>
On Mon, 2018-04-02 at 16:24 -0700, Florian Fainelli wrote:
> We would be passing 0 instead of NULL as the rsp argument to
> mt7530_fdb_cmd(), fix that.
>
Acked-by: Sean Wang
BTW, does the part of the commit message should be updated with "passing
NULL instead of 0"?
> Fixes: b8f126a8d543 ("ne
Hi all,
Today's linux-next merge of the pci tree got a conflict in:
arch/cris/arch-v32/drivers/pci/bios.c
between commits:
c690eddc2f3b ("CRIS: Drop support for the CRIS port")
fd8773f9f544 ("arch: remove frv port")
739d875dd698 ("mn10300: Remove the architecture")
from the asm-generic
On 04/02/2018 02:26 PM, Lyude Paul wrote:
While enabling/disabling DPMS before link training with MST hubs is
perfectly valid; unfortunately disabling DPMS results in some devices
disabling their AUX CH block as well. For SST this isn't as much of a
problem, but for MST we need to be able to cont
Hi David,
>>>
> On Thu, Mar 22, 2018 at 10:27:56PM -0600, Gang He wrote:
>> Hello David,
>>
>> Do you agree to add this prompt to the user?
>> Since sometimes customers attempted to setup SCTP protocol with two rings,
>> but they could not get the expected result, then it maybe bring some
>
Hi all,
Today's linux-next merge of the pci tree got a conflict in:
drivers/bus/Makefile
between commit:
1888d3ddc3d6 ("drivers/bus: Move Arm CCN PMU driver")
from the arm-soc tree and commit:
38e3446c5d06 ("HISI LPC: Support the LPC host on Hip06/Hip07 with DT
bindings")
from the pci
Hello,
syzbot hit the following crash on upstream commit
86bbbebac1933e6e95e8234c4f7d220c5ddd38bc (Mon Apr 2 18:47:07 2018 +)
Merge branch 'ras-core-for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
syzbot dashboard link:
https://syzkaller.appspot.com/bug?extid=dc5ab2bab
Hello,
syzbot hit the following crash on upstream commit
86bbbebac1933e6e95e8234c4f7d220c5ddd38bc (Mon Apr 2 18:47:07 2018 +)
Merge branch 'ras-core-for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
syzbot dashboard link:
https://syzkaller.appspot.com/bug?extid=84a679536
On Mon, Apr 2, 2018 at 3:41 AM, Ingo Molnar wrote:
>
> - Use efi_switch_mm() on x86 instead of manipulating %cr3 directly
This seems to cause new warnings, both on my laptop and my desktop.
I'm surprised you don't see them.
Looks like this:
WARNING: CPU: 0 PID: 0 at arch/x86/include/asm/tl
I am a banker and am writing you today in full confidence, i want to know if
you have a valid bank account that can accept millions of US Dollars. If you
do, respond quickly so that i can intimate you on this deal that is absolutely
risk-free but highly secret. It is only between me and you. No
On Mon, Apr 02, 2018 at 02:06:56PM -0500, Alan Tull wrote:
> On Sun, Apr 1, 2018 at 11:22 PM, Wu Hao wrote:
> > On Thu, Mar 29, 2018 at 04:57:22PM -0500, Alan Tull wrote:
> >> On Mon, Mar 26, 2018 at 9:35 PM, Wu Hao wrote:
> >>
> >> Hi Hao,
> >>
> >> Currently there is one set of functions that h
> On Apr 2, 2018, at 5:59 PM, Kees Cook wrote:
>
>> On Mon, Apr 2, 2018 at 5:37 PM, Andy Lutomirski wrote:
>>> On 03/30/2018 05:46 PM, James Morris wrote:
>>>
On Sat, 31 Mar 2018, David Howells wrote:
Date: Thu, 26 Oct 2017 17:37:38 +0100
Hi James,
Can you
On Mon, Apr 02, 2018 at 12:32:44AM +, Sasha Levin wrote:
> On Sun, Apr 01, 2018 at 08:02:45AM +1000, Dave Chinner wrote:
> >On Fri, Mar 30, 2018 at 02:47:05AM +, Sasha Levin wrote:
> >> On Thu, Mar 29, 2018 at 10:05:35AM +1100, Dave Chinner wrote:
> >> >On Wed, Mar 28, 2018 at 07:30:06PM +0
On Sat, Mar 31, 2018 at 11:46:40AM +0300, Dan Carpenter wrote:
> On Fri, Mar 30, 2018 at 11:08:51PM -0700, Quytelda Kahja wrote:
> > Setting a dummy address during the driver probe is not necessary.
> > The dev_addr field is already zeroed out from alloc_etherdev().
> >
> > Signed-off-by: Quytelda
This works for cycle and instruction counts.
Alex
On Mon, Apr 2, 2018 at 5:31 AM, Alan Kao wrote:
>
> This patch provide a basic PMU, riscv_base_pmu, which supports two
> general hardware event, instructions and cycles. Furthermore, this
> PMU serves as a reference implementation to ease the po
Some protocols over I2C are designed for bi-directional transferring
messages by using I2C Master Write protocol. Like the MCTP (Management
Component Transport Protocol) and IPMB (Intelligent Platform Management
Bus), they both require that the userspace can receive messages from
I2C dirvers under
Hi kernel community,
We have an external PCIe board with a custom coprocessor on it. We also
have code for a kernel driver for it. We have thought about upstreaming it,
but we realized that we can instead convert the driver to a userspace
driver using UIO.
However, there's one aspect of the syste
El Mon, Apr 02, 2018 at 03:38:21PM -0700 Matthias Kaehlcke ha dit:
> El Mon, Apr 02, 2018 at 02:44:48PM -0700 Linus Torvalds ha dit:
>
> > On Mon, Apr 2, 2018 at 2:50 AM, Ingo Molnar wrote:
> > >
> > > The biggest change is the forcing of asm-goto support on x86, which
> > > effectively
> > > i
On 4/3/2018 12:47 AM, Arnaldo Carvalho de Melo wrote:
Em Fri, Mar 30, 2018 at 05:27:14PM +0800, Jin Yao escreveu:
This patch checks the values passed by CFLAGS (-DHAVE_XXX) and then
print the status of libraries.
For example, if HAVE_DWARF_SUPPORT is defined, that means the
library "dwarf" is
[+Cc Lorenzo]
Hi Neil,
On 2018/4/3 1:59, Neil Leeder wrote:
> Hi Hanjun,
>
> On 4/2/2018 10:24 AM, Hanjun Guo wrote:
>
>>
>> I think we need to wait for the new version of IORT spec,
>> which includes the fix for the two base address for SMMUv3
>> PMCG (now just represent one).
>>
>> Thanks
>>
On (04/02/18 17:15), Andy Shevchenko wrote:
> >
> > Hmm, I have never seen the error code in this form.
>
> We have limited space to print it and error numbers currently can be up
> to 0xfff (4095). So, I have no better idea how to squeeze them while
> thinking that "(efault)" is much harder to p
On Mon, Apr 2, 2018 at 5:37 PM, Andy Lutomirski wrote:
> On 03/30/2018 05:46 PM, James Morris wrote:
>>
>> On Sat, 31 Mar 2018, David Howells wrote:
>>
>>> Date: Thu, 26 Oct 2017 17:37:38 +0100
>>>
>>> Hi James,
>>>
>>> Can you pull this patchset into security/next please? It has been in
>>> linu
On 04/02/2018 04:17 PM, Kirill Marinushkin wrote:
Hello Pierre-Louis,
I explicitly clarified with Takashi: to have this patch series merged, we need a
tag "Reviewed-by" from you.
I am fine with the changes, but maybe while we are at it, we should
clarify what mclk_direction means?
__u8
On 04/02/2018 07:03 AM, Christophe JAILLET wrote:
When extending the rmi_spi buffers, we must check that no out of memory
error occurs, otherwise we may access data above the currently allocated
memory.
Propagate the error code returned by 'rmi_spi_manage_pools()' instead.
Yep, that definitely
Hi Hans,
I love your patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.16 next-20180329]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Hans-
On 11/10/2017 01:02 PM, Mimi Zohar wrote:
If the kernel is locked down and IMA-appraisal is not enabled, prevent
loading of unsigned firmware.
diff --git a/security/fw_lockdown/Kconfig b/security/fw_lockdown/Kconfig
new file mode 100644
index ..d6aef6ce8fee
--- /dev/null
+++ b/secu
On 03/30/2018 05:46 PM, James Morris wrote:
On Sat, 31 Mar 2018, David Howells wrote:
Date: Thu, 26 Oct 2017 17:37:38 +0100
Hi James,
Can you pull this patchset into security/next please? It has been in
linux-next since the beginning of March.
It adds kernel lockdown support for EFI secure
1 - 100 of 588 matches
Mail list logo
