On Wed, Nov 07, 2018 at 05:06:08PM -0800, Vito Caputo wrote:
> In reading the news today, I stumbled across an article talking about a
> $20 "linux-based distro" app for Windows 10.
>
> This is just a bundled userspace for WSL, there is no actual Linux in
> this thing, yet the trademarked Linux na
Hi Greg,
After merging the staging tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
In file included from include/linux/printk.h:336,
from include/linux/kernel.h:14,
from include/linux/clk.h:16,
from drivers/staging/med
Hi, Fabio
Best Regards!
Anson Huang
> -Original Message-
> From: Fabio Estevam [mailto:feste...@gmail.com]
> Sent: 2018年11月8日 10:21
> To: Anson Huang
> Cc: Rob Herring ; Mark Rutland
> ; Shawn Guo ; Sascha
> Hauer ; Sascha Hauer ;
> Fabio Estevam ; open list:OPEN FIRMWARE AND
> FLATTENED
On (11/07/18 19:52), Tetsuo Handa wrote:
> > A question.
> >
> > How bad would it actually be to:
> >
> > - Allocate seq_buf 512-bytes buffer (GFP_ATOMIC) just-in-time, when we
> > need it.
> > // How often systems cannot allocate a 512-byte buffer? //
>
> It is a very bad thing to do GFP_
On Wed, Nov 7, 2018 at 5:30 PM Brian Norris wrote:
>
> cros_ec_get_next_event() is documented to return 0 for success and
> negative for errors. It currently returns negative for some errors, and
> non-negative (number of bytes received) for success (including some "no
> data available" responses
On 11/7/18 4:24 PM, kernel test robot wrote:
FYI, we noticed the following commit (built with gcc-7):
commit: 1431aa42b3afc1dd50b292abcc68ccdc3193da63 ("drivers/base: Verify struct
device locking requirements at runtime")
https://github.com/bvanassche/linux for-next
in testcase: boot
on test
Hi Mathieu,
On Thu, Nov 8, 2018 at 4:48 AM Mathieu Malaterre wrote:
>
> Hi Yamada-san,
>
> Since commit:
>
> 80463f1b7bf9 kbuild: add --include-dir flag only for out-of-tree build
>
> I can no longer run the bindeb-pkg rule. For example:
>
> $ make O=wii ARCH=powerpc wii_defconfig
> $ make -j8 O=
On (11/07/18 11:21), Petr Mladek wrote:
> > [..]
> > - The printk-fallback sounds like a hint that the existing 'cont' handling
> > better stay in the kernel. I don't see how the existing 'cont' is
> > significantly worse than
> > bpr_warn(NULL, ...)->printk() // no 'cont' support
>
Hi Anson,
On Wed, Nov 7, 2018 at 11:24 PM Anson Huang wrote:
> Regarding the fec2 settings in imx7d-sdb.dts, originally it uses Rev-A board
> (but some nodes are
> using Rev-B board), in this patch, I clean up all the settings in
> imx7d-sdb.dts using Rev-B board,
> so below is added to imx7d-
Hi Peter,
Thanks for your review.
Peter Zijlstra 于2018年11月8日周四 上午1:31写道：
>
> On Thu, Nov 08, 2018 at 12:15:05AM +0800, Muchun Song wrote:
> > We use a value to represent the priority of the RT task. But a smaller
> > value corresponds to a higher priority. If there are two RT task A and B,
> > t
On Wed, 2018-11-07 at 23:18 +0530, Manivannan Sadhasivam wrote:
> Add devicetree bindings for Mediatek MT6797 SoC Pin Controller.
>
> Signed-off-by: Manivannan Sadhasivam
> ---
> .../bindings/pinctrl/pinctrl-mt6797.txt | 83 +
> include/dt-bindings/pinctrl/mt6797-pinfunc.h | 1368 ++
On Wed, 07 Nov 2018 13:09:39 PST (-0800), Arnd Bergmann wrote:
On Wed, Nov 7, 2018 at 7:30 PM David Abdurachmanov
wrote:
On Wed, Nov 7, 2018 at 1:08 AM Palmer Dabbelt wrote:
> On Mon, 05 Nov 2018 12:56:15 PST (-0800), Arnd Bergmann wrote:
> The target is still the next glibc release (Feb 1s
On Wed, Nov 07, 2018 at 11:03:06AM +0100, Miklos Szeredi wrote:
> On Wed, Nov 7, 2018 at 12:48 AM, Andrew Morton
> wrote:
> > On Mon, 29 Oct 2018 23:04:45 + Daniel Colascione
> > wrote:
> >
> >> On Mon, Oct 29, 2018 at 7:25 PM, Davidlohr Bueso wrote:
> >> > This patch introduces a new /proc
On Wed, Nov 7, 2018 at 9:17 PM Marc Gonzalez wrote:
>
> Commit a930d8bd94d8 ("usb: chipidea: Always build ULPI code") made
> USB_CHIPIDEA select USB_ULPI_BUS, and removed USB_CHIPIDEA_ULPI.
>
> Signed-off-by: Marc Gonzalez
Reviewed-by: Fabio Estevam
On 11/03/2018 11:29 AM, Thomas Gleixner wrote:
> Tim,
>
> On Tue, 30 Oct 2018, Tim Chen wrote:
>
>> Change the SMT code paths check from using cpu_smt_control to
>> cpu_smt_enabled static key. This saves a branching check.
>
> and adds extra size to the kernel for the patching. The only reason
On Wed, Nov 07 2018, Chuck Lever wrote:
> Hi Neil-
>
>
>> On Nov 6, 2018, at 11:12 PM, NeilBrown wrote:
>>
>> 1/ discard 'struct unx_cred'. We don't need any data that
>> is not already in 'struct rpc_cred'.
>> 2/ Don't keep these creds in a hash table. When a credential
>> is needed, simp
Hi Joerg,
After merging the iommu tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
In file included from include/linux/bitmap.h:10,
from drivers/iommu/intel-iommu.c:24:
drivers/iommu/intel-iommu.c: In function 'iommu_calculate_agaw':
include/linux/kerne
EC_MKBP_EVENT_SENSOR_FIFO events can be triggered for a variety of
reasons, and there are very few cases in which they should be treated as
wakeup interrupts (particularly, when a certain
MOTIONSENSE_MODULE_FLAG_* is set, but this is not even supported in the
mainline cros_ec_sensor driver yet). Mo
cros_ec_get_next_event() is documented to return 0 for success and
negative for errors. It currently returns negative for some errors, and
non-negative (number of bytes received) for success (including some "no
data available" responses as zero). This works out OK, because the
callers were more or
Hi, Fabio
Best Regards!
Anson Huang
> -Original Message-
> From: Fabio Estevam [mailto:feste...@gmail.com]
> Sent: 2018年11月7日 18:03
> To: Anson Huang
> Cc: Rob Herring ; Mark Rutland
> ; Shawn Guo ; Sascha
> Hauer ; Sascha Hauer ;
> Fabio Estevam ; open list:OPEN FIRMWARE AND
> FLATTENED
On Wed, Nov 07 2018, Jeff Layton wrote:
> On Wed, 2018-11-07 at 16:54 +0100, Thierry Reding wrote:
>> On Wed, Nov 07, 2018 at 07:01:29AM -0500, Jeff Layton wrote:
>> > On Wed, 2018-11-07 at 16:43 +0800, kernel test robot wrote:
>> > > FYI, we noticed the following commit (built with gcc-7):
>> > >
This patch fix the following build warnings which because of missing
include file:
arch/x86/kernel/cpu/cacheinfo.c:647:6: warning: no previous prototype for
‘cacheinfo_amd_init_llc_id’ [-Wmissing-prototypes]
arch/x86/kernel/cpu/cacheinfo.c:686:6: warning: no previous prototype for
‘cacheinfo_hyg
In reading the news today, I stumbled across an article talking about a
$20 "linux-based distro" app for Windows 10.
This is just a bundled userspace for WSL, there is no actual Linux in
this thing, yet the trademarked Linux name is used throughout.
Did Microsoft license the trademark or somethin
> On 7 Nov 2018, at 5:15 PM, Greg Kroah-Hartman wrote:
>
> On Wed, Nov 07, 2018 at 10:30:43AM +0800, Jerry Lin wrote:
>> Add a attribute called permissions under vsoc device node for examining
>> current granted permissions in vsoc_device.
>>
>> This file will display permissions in following
Expose the per-task cpu specific thread state value, it's helpful
for userland to classify and schedule the tasks by different policies
Signed-off-by: Aubrey Li
Cc: Peter Zijlstra
Cc: Andi Kleen
Cc: Tim Chen
Cc: Arjan van de Ven
---
arch/x86/kernel/fpu/xstate.c | 13 +
fs/proc/ba
XSAVES and its variants use init optimization to reduce the amount of
data that they save to memory during context switch. Init optimization
uses the state component bitmap to denote if a component is in its init
configuration. We use this information to detect if a task contains AVX
instructions.
On 2018/11/8 1:41, Tim Chen wrote:
> On 11/06/2018 10:23 AM, Aubrey Li wrote:
>
>> +static inline void update_avx_state(struct avx_state *avx)
>> +{
>> +/*
>> + * Check if XGETBV with ECX = 1 supported. XGETBV with ECX = 1
>> + * returns the logical-AND of XCR0 and XINUSE. XINUSE is a
Thomas,
>
> The goal is to glue the mitigation decision on dumpable. That's debatable,
> but understandable, so let's not go into that discussion.
>
> There are two ways to modify dumpable:
>
> 1) prctl(PR_SET_DUMPABLE)
>
> 2) operations which change UID/GID and end up in commit_creds()
>
Quoting Abel Vesa (2018-11-07 12:26:25)
> On Wed, Nov 07, 2018 at 11:01:02AM -0800, Stephen Boyd wrote:
> >
> >
> > What's the plan to clean it up?
>
> So I'm doing this in our internal tree first to make sure I don't break the
> other (newer) socs.
>
> I already have a prototype in testing but
Boris Brezillon writes:
> Hello Michael,
>
> On Thu, 01 Nov 2018 21:18:28 +1100
> Michael Ellerman wrote:
>
>> Mark Brown writes:
>>
>> > On Fri, Oct 26, 2018 at 12:36:14PM -0500, Rob Herring wrote:
>> >> On Thu, Oct 25, 2018 at 9:14 AM Linus Torvalds
>> >> wrote:
>> >
>> >> > Are there
On Tue, 23 Oct 2018 08:30:04 +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 d50d82faa0c964e31f7a946ba8aba7c715ca7ab0
> Author:
On Tue, Sep 18, 2018 at 05:15:00PM -0500, Alexandru Gagniuc wrote:
> When a PCI device is gone, we don't want to send IO to it if we can
> avoid it. We expose functionality via the irq_chip structure. As
> users of that structure may not know about the underlying PCI device,
> it's our responsibili
On Tue, 23 Oct 2018 09:08:02 +0200 Uwe Kleine-König
wrote:
> Without this change the following happens when using Python3 (3.6.6):
>
> $ echo "GPL-2.0" | python3 scripts/spdxcheck.py -
> FAIL: 'str' object has no attribute 'decode'
> Traceback (most recent call last):
>
Quoting Andy Tang (2018-11-06 16:52:19)
> Hi Stephen,
>
> > -Original Message-
> > From: Stephen Boyd
> > Sent: 2018年11月7日 1:25
> > To: Andy Tang ; mturque...@baylibre.com
> > Cc: linux-...@vger.kernel.org; linux-kernel@vger.kernel.org; Andy Tang
> >
> > Subject: Re: [PATCH v3] clk: qori
SND_SOC_RK3399_GRU_SOUND selects SND_SOC_DA7219, SND_SOC_MAX98357A,
SND_SOC_RT5514, SND_SOC_RT5514_SPI.
SND_SOC_ROCKCHIP_RT5645 selects SND_SOC_RT5645.
SND_SOC_RL6231 is pulled in for SND_SOC_RT5514 and SND_SOC_RT5645.
Signed-off-by: Marc Gonzalez
---
arch/arm64/configs/defconfig | 6 --
1
SCSI_UFS_HISI depends on SCSI_UFSHCD_PLATFORM=m
Signed-off-by: Marc Gonzalez
---
arch/arm64/configs/defconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index e4957df18f23..75d5ed7ea53d 100644
--- a/arch/arm64/c
Commit e8342cc7954e ("enable CAAM crypto engine on QorIQ DPAA2 SoCs")
enabled CRYPTO_DEV_FSL_DPAA2_CAAM, which depends on FSL_MC_DPIO,
which is not set.
Signed-off-by: Marc Gonzalez
---
arch/arm64/configs/defconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm64/configs/defconfig b
Run the platform defconfig through kbuild, and handle the trivial case
where options merely move around.
Signed-off-by: Marc Gonzalez
---
arch/arm64/configs/defconfig | 90 ++--
1 file changed, 45 insertions(+), 45 deletions(-)
diff --git a/arch/arm64/configs/def
Commit a7314405d83c ("drop ARM_BIG_LITTLE_CPUFREQ support for ARM64")
dropped ARM_BIG_LITTLE_CPUFREQ support for ARM64.
Signed-off-by: Marc Gonzalez
---
arch/arm64/configs/defconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
ind
SND_SOC_ROCKCHIP_RT5645 selects SND_SOC_ROCKCHIP_I2S
Signed-off-by: Marc Gonzalez
---
arch/arm64/configs/defconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index 725b9471b21c..8e181cca0a05 100644
--- a/arch/arm64/configs/defco
Commit e78d57b2f87c ("pinctrl: mediatek: add pinctrl-moore that
implements the generic pinctrl dt-bindings") made PINCTRL_MT7622
depend on PINCTRL_MTK_MOORE.
Signed-off-by: Marc Gonzalez
---
arch/arm64/configs/defconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm
Commit a0ae2562c6c4 ("netfilter: conntrack: remove l3proto abstraction")
folded NF_CONNTRACK_IPV4 and NF_CONNTRACK_IPV6 into NF_CONNTRACK.
Signed-off-by: Marc Gonzalez
---
arch/arm64/configs/defconfig | 2 --
1 file changed, 2 deletions(-)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/
Commit a930d8bd94d8 ("usb: chipidea: Always build ULPI code") made
USB_CHIPIDEA select USB_ULPI_BUS, and removed USB_CHIPIDEA_ULPI.
Signed-off-by: Marc Gonzalez
---
arch/arm64/configs/defconfig | 2 --
1 file changed, 2 deletions(-)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs
Hello ARM maintainers,
v2: Improve commit message for a few patches
The set of Kconfig options slowly changes with every kernel version.
This patch series regenerates the arm64 defconfig for v4.20
No functional change intended, except adding PINCTRL_MTK_MOORE to
keep PINCTRL_MT7622.
Marc Gonzale
On 11/07/2018 10:33 AM, Waiman Long wrote:
> On 11/06/2018 07:18 PM, Tim Chen wrote:
>> Thomas,
>>
> 2) Add _TIF_UPDATE_SPEC_CTRL to the SYSCALL_EXIT_WORK_FLAGS and handle it
>in the slow work path.
There can be tasks that don't do any syscalls, and it seems like we can
have M
Following in the footstep of what was done for other CoreSight devices,
add CLAIM tag support to ETB10 in order to synchronise access to the
HW between the kernel and an external agent.
Signed-off-by: Mathieu Poirier
Reviewed-by: Suzuki K Poulose
---
drivers/hwtracing/coresight/coresight-etb10.
This patch rectifies the sequence of events in function
tmc_etb_disable_hw() by disabling the HW first and then releasing the
CLAIM tag. Otherwise we could be corrupting the configuration done by an
external agent that would have claimed the device after we have released
it.
Signed-off-by: Mathie
This patch moves access to the CLAIM tag so that no modification to the HW
happens before and after the CLAIM operation has been carried.
Signed-off-by: Mathieu Poirier
---
drivers/hwtracing/coresight/coresight-etm3x.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff
This patch deals with the release of the CLAIM tag when the ETM is
operated from perf. Otherwise the tag is left asserted and subsequent
requests to use the device fail.
Signed-off-by: Mathieu Poirier
---
drivers/hwtracing/coresight/coresight-etm3x.c | 1 +
1 file changed, 1 insertion(+)
diff
This set addresses problems observed with the CLAIM tag feature. The first
patch adds support for CLAIM tags to the ETB10 drivers. The remaining 3
patches deal with properly handling the tags on ETF and ETM3x devices.
Regards,
Mathieu
Changes since V1:
* Added Suzuki's review tags to patch 1 a
On Wed, Nov 7, 2018 at 8:36 AM Schrempf Frieder
wrote:
>
> Hi Olof,
>
> On 07.11.18 17:20, Olof Johansson wrote:
> > On Wed, Nov 7, 2018 at 6:44 AM Frieder Schrempf
> > wrote:
> >>
> >> From: Frieder Schrempf
> >>
> >> The new driver at spi/spi-fsl-qspi.c replaces the old SPI NOR driver
> >> at
Tim,
On Tue, 6 Nov 2018, Tim Chen wrote:
> >>> 2) Add _TIF_UPDATE_SPEC_CTRL to the SYSCALL_EXIT_WORK_FLAGS and handle it
> >>>in the slow work path.
> >>
> >> There can be tasks that don't do any syscalls, and it seems like we can
> >> have MSRs getting out of sync?
> >
> > Setting the TIF fl
The cros_ec_keyb_bs array lists buttons and switches together, expecting
that its users will match the appropriate type and bit fields. But
cros_ec_keyb_register_bs() only checks the 'bit' field, which causes
misreported input capabilities in some cases. For example, tablets
(e.g., Scarlet -- a.k.a
On Mon, 29 Oct 2018 13:27:36 +0100 Vitaly Wool wrote:
> Hi Andrew,
>
> Den tors 25 okt. 2018 kl 21:42 skrev Andrew Morton <
> a...@linux-foundation.org>:
>
> > On Thu, 25 Oct 2018 11:28:21 +0200 Vitaly Wool
> > wrote:
> >
> > > Reclaim and free can race on an object (which is basically ok) but
Hello!
The header comment for for_each_domain() talks about a call to
synchronize_sched() within detach_destroy_domains(), but I am not
seeing any such call. Because synchronize_sched() is now folded into
synchronize_rcu(), I have a patch that edits the comment, but it looks
like a larger change
On Sun, 4 Nov 2018, Yangtao Li wrote:
> WARN_ON() already contains an unlikely(), so it's not necessary to use
> unlikely.
>
> Signed-off-by: Yangtao Li
Acked-by: David Rientjes
From: Thomas Gleixner Sent: Wednesday, November 7, 2018
12:23 PM
>
> There is another interesting property of managed interrupts vs. CPU
> hotplug. When the last CPU in the affinity mask goes offline, then the core
> code shuts down the interrupt and the device driver and related layers
> exclu
On Dienstag, 6. November 2018 21:24:11 CET Andi Kleen wrote:
> > Where would I look for the source to change here? So far, I only
> > concentrated on the userspace side of perf in tools/perf.
>
> Kind of similar to
>
> a405bad5ad20 perf/x86: Add Haswell specific transaction flag reporting
> fdfbb
On 06/11/2018 21:21, Tony Krowiak wrote:
On 10/31/18 2:12 PM, Pierre Morel wrote:
Register to the GIB Alert list and retrieve the GAL_ISC
to pass to the GISA registration.
Unregister on error and when clearing the interrupt.
Signed-off-by: Pierre Morel
Signed-off-by: Michael Mueller
---
dr
On Mon, Nov 05 2018 at 22:19 -0700, Stephen Boyd wrote:
Quoting Lina Iyer (2018-11-01 10:16:30)
On Wed, Oct 31 2018 at 18:13 -0600, Stephen Boyd wrote:
>
[...]
Ok. I don't see why we need to limit ourselves here. If a GPIO interrupt
isn't routed through PDC physically why does it matter? It s
On Wed, 7 Nov 2018 01:48:12 + chouryzhou(周威) wrote:
> > > --- a/ipc/namespace.c
> > > +++ b/ipc/namespace.c
> > > @@ -56,6 +56,9 @@ static struct ipc_namespace *create_ipc_ns(struct
> > user_namespace *user_ns,
> > > ns->ucounts = ucounts;
> > >
> > > err = mq_init_ns(ns);
> >
From: Wei Wang
commit ff140fea847e ("Thermal: handle thermal zone device properly
during system sleep") added PM hook to call thermal zone reset during
sleep. However reseting thermal zone will also clear the passive state
and thus cancel the polling queue which leads the passive cooling device
s
The iregs output was missing the newline at end as well as the leading
ABI output. This made it hard to compare the iregs and uregs values.
Instead, use a single function to output the register values and use
it for both, iregs and uregs, to ensure the output is consistent.
Before:
```
perf 7049
The function leon_trans_init is unused. Remove it and save us from
figuring out what to do with a '' node name.
Cc: "David S. Miller"
Cc: sparcli...@vger.kernel.org
Signed-off-by: Rob Herring
---
arch/sparc/include/asm/leon.h | 1 -
arch/sparc/kernel/leon_kernel.c | 14 --
2 file
All other platforms have been converted to only store the local node name
in device_node.full_name except Sparc. Sparc was complicated by having a
path_component_name in addition to full_name and name. By switching
full_name to just the local node name, path_component_name becomes
redundant and can
In preparation to remove struct device_node.path_component_name, use
full_name instead. kbasename is used so full_name can be used whether it
is the full path or just the node's name and unit-address.
Cc: "David S. Miller"
Cc: sparcli...@vger.kernel.org
Signed-off-by: Rob Herring
---
fs/openpro
Convert string compares of DT node names to use of_node_name_eq helper
instead. This removes direct access to the node name pointer.
Cc: "David S. Miller"
Cc: sparcli...@vger.kernel.org
Signed-off-by: Rob Herring
---
arch/sparc/kernel/auxio_64.c | 4 ++--
arch/sparc/kernel/central.c
In preparation to remove the node name pointer from struct device_node,
convert printf users to use the %pOFn format specifier.
This was originally applied for 4.19, but reverted. The problematic
changes to prom_{32,64}.c have been dropped.
Cc: "David S. Miller"
Cc: sparcli...@vger.kernel.org
Si
In preparation to remove direct accesses to the device_node.name
pointer, retrieve the node name from the "name" property instead.
Cc: "David S. Miller"
Cc: sparcli...@vger.kernel.org
Signed-off-by: Rob Herring
---
arch/sparc/kernel/prom_32.c | 20 ++--
arch/sparc/kernel/prom_64.c |
Remove directly accessing device_node.type pointer and use the accessors
instead. This will eventually allow removing the type pointer.
Replace the open coded iterating over child nodes with
for_each_child_of_node() while we're here.
Cc: "David S. Miller"
Cc: sparcli...@vger.kernel.org
Signed-of
On 06/11/2018 21:21, Tony Krowiak wrote:
On 10/31/18 2:12 PM, Pierre Morel wrote:
This is the implementation of the VFIO ioctl calls to handle
the AQIC interception and use GISA to handle interrupts.
Signed-off-by: Pierre Morel
---
drivers/s390/crypto/vfio_ap_ops.c | 95 +
Now that we have a custom printf format specifier, convert users of
full_name to use %pOF instead. This is preparation to remove storing
of the full path string for each node.
Cc: "David S. Miller"
Cc: sparcli...@vger.kernel.org
Signed-off-by: Rob Herring
---
arch/sparc/kernel/auxio_64.c |
Now that there are no more users of path_component_name outside of
the PDT code and users of device_node.full_name are converted to use
"%pOF" printf specifier, we can align Sparc with other arches and store
just the base node name and unit address in full_name. This makes
path_component_name redun
On 11/7/18 2:47 AM, Geert Uytterhoeven wrote:
> libata.git no longer exists. Replace the remaining pointers to it by
> pointers to the block tree, which is where all libata development
> happens now.
Thanks, applied.
--
Jens Axboe
The cros_ec_keyb_bs array lists buttons and switches together, expecting
that its users will match the appropriate type and bit fields. But
cros_ec_keyb_register_bs() only checks the 'bit' field, which causes
misreported input capabilities in some cases. For example, tablets
(e.g., Scarlet -- a.k.a
On 07/11/2018 10:46, Cornelia Huck wrote:
On Wed, 31 Oct 2018 19:12:54 +0100
Pierre Morel wrote:
This is the implementation of the VFIO ioctl calls to handle
the AQIC interception and use GISA to handle interrupts.
Signed-off-by: Pierre Morel
---
drivers/s390/crypto/vfio_ap_ops.c | 95
Using UBI_IOCRPEB and UBI_IOCSPEB userspace can force
reading and scrubbing of PEBs.
In case of bitflips UBI will automatically take action
and move data to a different PEB.
This interface allows a daemon to foster your NAND.
Signed-off-by: Richard Weinberger
---
drivers/mtd/ubi/cdev.c |
This function works like in_wl_tree() but checks whether an ubi_wl_entry
is currently in the protection queue.
We need this function to query the current state of an ubi_wl_entry.
Signed-off-by: Richard Weinberger
---
drivers/mtd/ubi/wl.c | 30 +++---
1 file changed, 23 i
On 10/16/2018 8:11 AM, Srinath Mannam wrote:
> These patches adds the stingray thermal driver and its
> corresponding DT nodes with documentation.
Can we get feedback from the thermal maintains whether this is
acceptable or not?
>
> Changes from v4
> - Addressed Rob Herring comments on DT p
On Wed, 7 Nov 2018 08:21:07 +0200 Alexey Skidanov
wrote:
> > Why does this need "fixing"? Are there current callers which can
> > misalign chunk_start_addr? Or is there a requirement that future
> > callers can misalign chunk_start_addr?
> >
> I work on adding aligned allocation support for I
> On 7 Nov 2018, at 20:58, syzbot
> wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:7438a3b20295 kmsan: print user address when reporting info..
> git tree:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_google_kmsan.git_master&d=DwIB
On Wed, 2018-11-07 at 16:54 +0100, Thierry Reding wrote:
> On Wed, Nov 07, 2018 at 07:01:29AM -0500, Jeff Layton wrote:
> > On Wed, 2018-11-07 at 16:43 +0800, kernel test robot wrote:
> > > FYI, we noticed the following commit (built with gcc-7):
> > >
> > > commit: dee160df820de41ff2f59a715643680
On Wed, 7 Nov 2018 08:27:31 +0200 Alexey Skidanov
wrote:
>
>
> On 11/7/18 12:15 AM, Andrew Morton wrote:
> > On Tue, 6 Nov 2018 14:20:53 +0200 Alexey Skidanov
> > wrote:
> >
> >> On success, gen_pool_first_fit_align() returns the bit number such that
> >> chunk_start_addr + (bit << order)
On Fri, Nov 02, 2018 at 12:04:47PM +0100, Rasmus Villemoes wrote:
> Since the definition of struct crng_state is private to random.c, and
> primary_crng is neither declared or used elsewhere, there's no reason
> for that symbol to have external linkage.
>
> Signed-off-by: Rasmus Villemoes
Thanks
On Fri, Nov 02, 2018 at 12:04:45PM +0100, Rasmus Villemoes wrote:
> Never modified, might as well be put in .rodata.
>
> Signed-off-by: Rasmus Villemoes
Thanks, applied.
- Ted
On Fri, Nov 02, 2018 at 12:04:46PM +0100, Rasmus Villemoes wrote:
> This field is never used, might as well remove it.
>
> Signed-off-by: Rasmus Villemoes
Thanks, applied.
- Ted
On 11/07/2018 12:18 AM, Yi Wang wrote:
This fixes the following warning:
kernel/cgroup/cpuset.c: In function ‘cpuset_cancel_attach’:
kernel/cgroup/cpuset.c:1501:17: warning: variable ‘cs’ set but not used
[-Wunused-but-set-variable]
struct cpuset *cs;
^
Signed-off-by: Yi Wa
UBIFS's recovery code strictly assumes that a deleted inode will never
come back, therefore it removes all data which belongs to that inode
as soon it faces an inode with link count 0 in the replay list.
Before O_TMPFILE this assumption was perfectly fine. With O_TMPFILE
it can lead to data loss up
To initialize the its nodes at a later point during boot, we need to
split probing from initialization. Collect all information required
for initialization in struct its_node. We can then use the its node
list for initialization.
Signed-off-by: Robert Richter
---
drivers/irqchip/irq-gic-v3-its.c
This patch separates its initialization from the gic. Probing and
initialization of its nodes is separate now. There is an own cpu
notifier for its now.
Signed-off-by: Robert Richter
---
drivers/irqchip/irq-gic-v3-its.c | 58 +-
drivers/irqchip/irq-gic-v3.c
On Wed, 7 Nov 2018 11:18:29 +0100 Michal Hocko wrote:
> From: Michal Hocko
>
> The memory offlining failure reporting is inconsistent and insufficient.
> Some error paths simply do not report the failure to the log at all.
> When we do report there are no details about the reason of the failur
ATM the last discovered node is initialized first. Though this order
should work too, change the initialization of nodes to probe order as
one would expect it.
Signed-off-by: Robert Richter
---
drivers/irqchip/irq-gic-v3-its.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/d
Since ITS is initialized with with the subsys_initcall now, we don't
need to enable ITS children earlier. Due to the use of irq_domain_
request_host_*() there are no order dependencies when initializing irq
domains.
Signed-off-by: Robert Richter
---
drivers/irqchip/irq-gic-v3-its-fsl-mc-msi.c
Use new irq_domain_request_host_*() interface which allows independent
parent and child initialization using an irq domain request handler.
This makes it possible to move its initialization to a later point
during boot. All domains can be initialized in the same initcall level
then.
Signed-off-by:
Use new irq_domain_request_host_*() interface which allows independent
parent and child initialization using an irq domain request handler.
This makes it possible to move its initialization to a later point
during boot. All domains can be initialized in the same initcall level
then.
Signed-off-by:
Use an initcall to initialize its. This allows us to use the device
framework during initialization that is up at this point. We use
subsys_initcall() here since we need the arch to be initialized
first. It is before pci and platform device probe where devices are
bound to msi interrupts.
Signed-o
This patch series is a rework of the gic-v3-its initialization. It is
in preparation of a further series that uses CMA memory allocation for
ITS tables. For this the CMA framework must be available and thus ITS
needs to be initialized after the arch_initcalls. This requires two
major reworks.
Firs
Use new irq_domain_request_host_*() interface which allows independent
parent and child initialization using an irq domain request handler.
This makes it possible to move its initialization to a later point
during boot. All domains can be initialized in the same initcall level
then.
Signed-off-by:
On Tue, Nov 06, 2018 at 10:39:15AM -0800, Luck, Tony wrote:
> On Tue, Nov 06, 2018 at 03:32:53PM +0100, Borislav Petkov wrote:
> > On Tue, Nov 06, 2018 at 02:44:42PM +0100, Arnd Bergmann wrote:
> > > No, it was unintentional, the 'if ACPI' can be dropped when we add
> > > 'depends on ACPI'.
> >
>
This patch introduces a new interface to allow irq domain
initialization regardless of order dependencies. This is done by
requesting a domain and registering a callback function that is called
as soon as a domain becomes available.
A typical irq domain initialization code is the following:
Paren
101 - 200 of 730 matches
Mail list logo
