On 24/06/2019 15:07, Peter Rosin wrote:
On 2019-06-24 10:34, Suzuki K Poulose wrote:
Hi Peter,
On 22/06/2019 06:25, Peter Rosin wrote:
On 2019-06-14 19:54, Suzuki K Poulose wrote:
Add a wrapper to class_find_device() to search for a device
by the of_node pointer, reusing the generic match
On Sun, Jun 23, 2019 at 09:34:55PM -0700, Paul E. McKenney wrote:
> On Sun, Jun 23, 2019 at 11:15:06AM -0400, Alan Stern wrote:
> > On Sun, 23 Jun 2019, Akira Yokosawa wrote:
> >
> > > Hi Paul and Alan,
> > >
> > > On 2019/06/22 8:54, Paul E. McKenney wrote:
> > > > On Fri, Jun 21, 2019 at 10:25:
Hi Vignesh,
On Mon, Jun 24, 2019 at 6:37 PM Vignesh Raghavendra wrote:
>
>
>
> On 24/06/19 6:10 PM, Sagar Kadam wrote:
> > Hello Vignesh,
> >
> > On Mon, Jun 24, 2019 at 3:04 PM Vignesh Raghavendra wrote:
> >>
> >> Hi,
> >>
> >> On 21/06/19 3:58 PM, Sagar Kadam wrote:
> >>> Hello Vignesh,
> >>>
On 24/06/2019 at 11:57, Palmer Dabbelt wrote:
> External E-Mail
>
>
> On Mon, 24 Jun 2019 02:40:21 PDT (-0700), nicolas.fe...@microchip.com wrote:
>> On 24/06/2019 at 08:16, Palmer Dabbelt wrote:
>>> External E-Mail
>>>
>>>
>>> The patch to add support for the FU540-C000 added a dependency on
>>>
Hi Andrew,
The 06/24/2019 16:26, Andrew Lunn wrote:
> > > Yeah, there are 2 ethernet controller ports (managed by the enetc driver)
> > > connected inside the SoC via SGMII links to 2 of the switch ports, one of
> > > these switch ports can be configured as CPU port (with follow-up patches).
> >
On Mon, 24 Jun 2019, Thomas Gleixner wrote:
>
> +#ifdef CONFIG_X86_LOCAL_APIC
> + .align 8
> +ENTRY(spurious_entries_start)
> +vector=FIRST_SYSTEM_VECTOR
> +.rept (NR_VECTORS - FIRST_SYSTEM_VECTOR)
> + pushl $(~vector+0x80) /* Note: always in signed byte
> range
On 24.06.19 10:42, Geert Uytterhoeven wrote:
CC gpio
This is now commit d99482673f950817 ("serial: mctrl_gpio: Check if GPIO
property exisits before requesting it") in tty-next.
On Thu, Jun 20, 2019 at 8:24 AM Stefan Roese wrote:
This patch adds a check for the GPIOs property existence, befor
On Mon, Jun 24, 2019 at 2:59 PM Bjørn Mork wrote:
>
> syzbot writes:
>
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit:9939f56e usb-fuzzer: main usb gadget fuzzer driver
> > git tree: https://github.com/google/kasan.git usb-fuzzer
> > console output: https://
On Mon, Jun 24, 2019 at 04:06:58PM +0100, Sudeep Holla wrote:
> On Wed, Jun 19, 2019 at 01:10:57PM +0100, Sudeep Holla wrote:
> > Hi Russell,
> >
> > On Mon, Jun 17, 2019 at 11:59:17AM -0700, Atish Patra wrote:
> > > Currently, ARM32 and ARM64 uses different data structures to represent
> > > their
stable-rc/linux-4.14.y boot: 116 boots: 0 failed, 109 passed with 7 offline
(v4.14.129-52-g57f3c9aebc30)
Full Boot Summary:
https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.14.y/kernel/v4.14.129-52-g57f3c9aebc30/
Full Build Summary:
https://kernelci.org/build/stable-rc/branch/linux-4.
On Mon, Jun 24, 2019 at 04:30:33PM +0100, Russell King - ARM Linux admin wrote:
> On Mon, Jun 24, 2019 at 04:06:58PM +0100, Sudeep Holla wrote:
> > On Wed, Jun 19, 2019 at 01:10:57PM +0100, Sudeep Holla wrote:
> > > Hi Russell,
> > >
> > > On Mon, Jun 17, 2019 at 11:59:17AM -0700, Atish Patra wrote
Hi Stefan,
On Mon, Jun 24, 2019 at 5:29 PM Stefan Roese wrote:
> On 24.06.19 10:42, Geert Uytterhoeven wrote:
> > On Thu, Jun 20, 2019 at 8:24 AM Stefan Roese wrote:
> >> This patch adds a check for the GPIOs property existence, before the
> >> GPIO is requested. This fixes an issue seen when th
On Sun, 23 Jun 2019 14:54:13 +0200 (CEST)
Thomas Gleixner wrote:
> Octavio,
>
> On Sat, 22 Jun 2019, Thomas Gleixner wrote:
> > On Wed, 19 Jun 2019, Octavio Alvarez wrote:
> > > On 6/13/19 3:45 PM, Thomas Gleixner wrote:
> > > > Can you please provide the content of /proc/interrupts with the
On 06/19/2019 06:27 PM, Colin King wrote:
> From: Colin Ian King
>
> There are several spelling mistakes in pr_warning messages. Fix these.
>
> Signed-off-by: Colin Ian King
Applied, thanks!
On 06/22/2019 02:03 AM, Matthew Garrett wrote:
> From: David Howells
>
> There are some bpf functions can be used to read kernel memory:
Nit: that
> bpf_probe_read, bpf_probe_write_user and bpf_trace_printk. These allow
Please explain how bpf_probe_write_user reads kernel memory ... ?!
> pri
On 23/05/2019 at 22:50, Rob Herring wrote:
> On Thu, May 23, 2019 at 6:46 AM Yash Shah wrote:
>>
>> Add the compatibility string documentation for SiFive FU540-C
>> interface.
>> On the FU540, this driver also needs to read and write registers in a
>> management IP block that monitors or drive
On Mon, 24 Jun 2019, Paul E. McKenney wrote:
> On Sun, Jun 23, 2019 at 09:34:55PM -0700, Paul E. McKenney wrote:
> > On Sun, Jun 23, 2019 at 11:15:06AM -0400, Alan Stern wrote:
> > > On Sun, 23 Jun 2019, Akira Yokosawa wrote:
> > >
> > > > Hi Paul and Alan,
> > > >
> > > > On 2019/06/22 8:54, Pa
On 6/21/19 6:23 AM, Masahiro Yamada wrote:
> With commit d8e8fd0ebf8b ("mtd: rawnand: denali: decouple controller
> and NAND chips"), the Denali NAND controller driver migrated to the
> new controller/chip representation.
>
> Update DT for it.
>
> Signed-off-by: Masahiro Yamada
> ---
>
> ar
On Mon, 24 Jun 2019, Stephen Hemminger wrote:
> On Sun, 23 Jun 2019 14:54:13 +0200 (CEST)
> Thomas Gleixner wrote:
> > > > I will keep trying 4.14, unless you say otherwise.
> > >
> > > It would be interesting though I don't expect too much data.
> > >
> > > So all of the above use PCI/MSI. Th
Document support for ADF4372 SPI Wideband Synthesizer.
Signed-off-by: Stefan Popa
---
Documentation/devicetree/bindings/iio/frequency/adf4371.yaml | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/iio/frequency/adf4371.yaml
b/Documentati
On 24/06/2019 at 11:57, Palmer Dabbelt wrote:
> External E-Mail
>
>
> On Mon, 24 Jun 2019 02:49:16 PDT (-0700), nicolas.fe...@microchip.com wrote:
>> On 24/06/2019 at 08:16, Palmer Dabbelt wrote:
>>> External E-Mail
>>>
>>>
>>> When touching the Kconfig for this driver I noticed that both the
>>>
On Mon, Jun 24, 2019 at 05:48:34AM -0700, Guenter Roeck wrote:
> On 6/24/19 2:55 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.1.15 release.
> > There are 121 patches in this series, all will be posted as a response
> > to this one. If anyone has any issu
On Mon, Jun 24, 2019 at 07:52:52AM +0200, Christoph Hellwig wrote:
> Takes the xfs writeback code and move it to iomap.c. A new structure
> with three methods is added as the abstraction from the generic
> writeback code to the file system. These methods are used to map
> blocks, submit an ioend,
On Mon, 24 Jun 2019 at 15:29, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.14.130 release.
> There are 51 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
For architectures using __WARN_TAINT, the WARN_ON macro did not
print out the "cut here" string. The other WARN_XXX macros would
print "cut here" inside __warn_printk, which is not called for
WARN_ON since it doesn't have a message to print.
Fixes: a7bed27af194 ("bug: fix "cut here" location for _
Changelog v4
- Rewrote patch to return all quota when cfs_b has very litte.
- Removed documentation changes, as bursting is no longer possible with this
new solution.
After the suggestion from Ben Segall to set min_cfs_rq_runtime=0, I came up
this in an attempt to balance the desire leave r
It has been observed, that highly-threaded, user-interactive
applications running under cpu.cfs_quota_us constraints can hit a high
percentage of periods throttled while simultaneously not consuming the
allocated amount of quota. This impacts user-interactive non-cpu bound
applications, such as tho
On Mon, Jun 24, 2019 at 07:52:46AM +0200, Christoph Hellwig wrote:
> In preparation for moving the XFS writeback code to fs/iomap.c, switch
> it to use struct iomap instead of the XFS-specific struct xfs_bmbt_irec.
>
> Signed-off-by: Christoph Hellwig
Looks ok,
Reviewed-by: Darrick J. Wong
--D
On Mon, Jun 24, 2019 at 10:01:04AM -0400, Mathieu Desnoyers wrote:
> - On Jun 24, 2019, at 5:18 AM, Peter Zijlstra pet...@infradead.org wrote:
>
> > While auditing all module notifiers I noticed a whole bunch of fail
> > wrt the return value. Notifiers have a 'special' return semantics.
> >
>
On Mon, Jun 24, 2019 at 07:52:42AM +0200, Christoph Hellwig wrote:
> +/**
> + * list_pop - delete the first entry from a list and return it
> + * @list:the list to take the element from.
> + * @type:the type of the struct this is embedded in.
> + * @member: the name of the list_head within
Hi,
On Thu, Jun 13, 2019 at 8:28 AM Marc Gonzalez wrote:
>
> readl_poll_timeout() calls usleep_range() to sleep between reads.
> usleep_range() doesn't work efficiently for tiny values.
>
> Raise the polling delay in qcom_qmp_phy_enable() to bring it in line
> with the delay in qcom_qmp_phy_com_i
On 21/06/2019 at 17:26, Antoine Tenart wrote:
> This patch fixes the MAC address setup in the probe. The MAC address
> retrieved using of_get_mac_address was checked for not containing an
> error, but it may also be NULL which wasn't tested. Fix it by replacing
> IS_ERR with IS_ERR_OR_NULL.
>
> Fi
Another feature of the ADF4371/ADF4372 is that the supply current to the
RF8P and RF8N output stage can shut down until the ADF4371 achieves lock
as measured by the digital lock detect circuitry. The mute to lock
detect bit (MUTE_LD) in REG25 enables this function.
Signed-off-by: Stefan Popa
---
From: Antoine Tenart
Date: Fri, 21 Jun 2019 17:26:35 +0200
> This patch fixes the MAC address setup in the probe. The MAC address
> retrieved using of_get_mac_address was checked for not containing an
> error, but it may also be NULL which wasn't tested. Fix it by replacing
> IS_ERR with IS_ERR_O
On Mon, Jun 24, 2019 at 09:48:31AM -0600, Drew Davenport wrote:
> For architectures using __WARN_TAINT, the WARN_ON macro did not
> print out the "cut here" string. The other WARN_XXX macros would
> print "cut here" inside __warn_printk, which is not called for
> WARN_ON since it doesn't have a mes
On 21/06/2019 at 17:28, Antoine Tenart wrote:
> Use NAPI_POLL_WEIGHT, the default NAPI poll() weight instead of
> redefining our own value (which turns out to be 64 as well).
>
> Signed-off-by: Antoine Tenart
Acked-by: Nicolas Ferre
> ---
> drivers/net/ethernet/cadence/macb_main.c | 2 +-
>
On Mon, Jun 24, 2019 at 07:52:47AM +0200, Christoph Hellwig wrote:
> Instead of a magic flag for xfs_trans_alloc, just ensure all callers
> that can't relclaim through the file system use memalloc_nofs_save to
> set the per-task nofs flag.
>
> Signed-off-by: Christoph Hellwig
Hmm this finally fi
On Mon, Jun 24, 2019 at 07:52:49AM +0200, Christoph Hellwig wrote:
> Compare the block layer status directly instead of converting it to
> an errno first.
>
> Signed-off-by: Christoph Hellwig
Looks ok,
Reviewed-by: Darrick J. Wong
--D
> ---
> fs/xfs/xfs_aops.c | 14 ++
> 1 file c
IS25LP256 gets BFPT_DWORD1_ADDRESS_BYTES_3_ONLY from BFPT table for
address width. But in actual fact the flash can support 4-byte address.
Use a post bfpt fixup hook to overwrite the address width advertised by
the BFPT.
Suggested-by: Tudor Ambarus
Signed-off-by: Liu Xiang
---
Changes in v4:
Hi,
I'd appreciate feedback on the patch. Seems like we can solve a stupid
"hiding" technique, more "advanced" than just marking an executable
with suid, that leads to privilege escalation. Please tell me if I
miss something.
On Mon, Jun 17, 2019 at 9:58 PM Carmeli Tamir wrote:
>
> The misc form
On Mon, Jun 24, 2019 at 07:52:50AM +0200, Christoph Hellwig wrote:
> Introduce two nicely abstracted helper, which can be moved to the
> iomap code later. Also use list_pop and list_first_entry_or_null
> to simplify the code a bit.
>
> Signed-off-by: Christoph Hellwig
Looks ok,
Reviewed-by: Dar
On Mon, 11 Feb 2019, Andy Shevchenko wrote:
> Swap PMIC and MULTIFUNCTION words in the title to:
> - show that this is about Intel PMICs
> - keep MAINTAINERS properly sorted
>
> Signed-off-by: Andy Shevchenko
> ---
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied,
I am in the military unit here in Afghanistan, we have some amount of funds
that we want to move out of the country. My partners and I need a good partner
someone we can trust. It is risk free and legal. Reply to this email:
hornbeckmajordennis...@gmail.com
Regards,
Major Dennis Hornbeck.
On 24.06.19 г. 8:52 ч., Christoph Hellwig wrote:
> Introduce two nicely abstracted helper, which can be moved to the
> iomap code later. Also use list_pop and list_first_entry_or_null
> to simplify the code a bit.
>
> Signed-off-by: Christoph Hellwig
> ---
> fs/xfs/xfs_aops.c | 66 ++
On Mon, Jun 24, 2019 at 2:18 PM Will Deacon wrote:
> On Mon, Jun 17, 2019 at 02:47:05PM +0200, Arnd Bergmann wrote:
> >
> > +unsigned long nr_stack_trace_entries;
> > +
> > +#if defined(CONFIG_TRACE_IRQFLAGS) && defined(CONFIG_PROVE_LOCKING)
>
> Is this necessary, given that CONFIG_PROVE_LOCKING
On Mon, Jun 24, 2019 at 07:52:51AM +0200, Christoph Hellwig wrote:
> In preparation for moving the writeback code to iomap.c, replace the
> XFS-specific COW fork concept with the iomap IOMAP_F_SHARED flag.
>
> Signed-off-by: Christoph Hellwig
Looks ok,
Reviewed-by: Darrick J. Wong
--D
> ---
>
On Mon, Jun 24, 2019 at 4:42 PM Roman Penyaev wrote:
>
> epoll_create2() is needed to accept EPOLL_USERPOLL flags
> and size, i.e. this patch wires up polling from userspace.
Can you explain in the patch description more what it's needed for?
The man page only states that "Since Linux 2.6.8, the
On Wed, 12 Jun 2019, Andy Shevchenko wrote:
> Add an MFD driver for Intel Merrifield Basin Cove PMIC.
>
> Signed-off-by: Andy Shevchenko
> ---
> - updated copyright year to be 2019
> - rebased on top of latest vanilla rc
>
> drivers/mfd/Kconfig | 11 ++
> drivers/mfd/Make
On Mon, Jun 24, 2019 at 07:52:48AM +0200, Christoph Hellwig wrote:
> We have historically decided that we want to preallocate the xfs_trans
> structure at writeback time so that we don't have to allocate on in
> the I/O completion handler. But we treat unwrittent extent and COW
> fork conversions
On Mon, Jun 24, 2019 at 11:39:23AM -0400, Alan Stern wrote:
> On Mon, 24 Jun 2019, Paul E. McKenney wrote:
>
> > On Sun, Jun 23, 2019 at 09:34:55PM -0700, Paul E. McKenney wrote:
> > > On Sun, Jun 23, 2019 at 11:15:06AM -0400, Alan Stern wrote:
> > > > On Sun, 23 Jun 2019, Akira Yokosawa wrote:
>
In preparation to enabling -Wimplicit-fallthrough, mark switch
cases where we are expecting to fall through.
This patch fixes the following warnings:
arch/x86/events/intel/core.c: In function ‘intel_pmu_init’:
arch/x86/events/intel/core.c:4959:8: warning: this statement may fall through
[-Wimpli
From: Antoine Tenart
Date: Fri, 21 Jun 2019 17:28:55 +0200
> Use NAPI_POLL_WEIGHT, the default NAPI poll() weight instead of
> redefining our own value (which turns out to be 64 as well).
>
> Signed-off-by: Antoine Tenart
Applied, thanks.
From: Antoine Tenart
Date: Fri, 21 Jun 2019 17:30:02 +0200
> This patch updates the macb driver to use NAPI GRO helpers when
> receiving SKBs. This improves performances.
>
> Signed-off-by: Antoine Tenart
Applied.
On 24/06/2019 15:49, Catalin Marinas wrote:
> On Mon, Jun 24, 2019 at 03:23:46PM +0100, Russell King wrote:
>> On Mon, Jun 24, 2019 at 04:18:28PM +0200, Thomas Gleixner wrote:
>>> Vincenzo,
>>>
>>> On Mon, 24 Jun 2019, Thomas Gleixner wrote:
>>>
I did not merge the ARM and MIPS parts as they l
On 6/18/19 2:03 PM, Johannes Berg wrote:
> On Tue, 2019-06-18 at 08:45 -0500, Alex Elder wrote:
>
>> If it had a well-defined way of creating new channels to be
>> multiplexed over the connection to the modem, the IPA driver
>> (rather than the rmnet driver) could present network interfaces
>> for
On 6/18/19 1:48 PM, Johannes Berg wrote:
> Just to add to Dan's response, I think he's captured our discussions and
> thoughts well.
>
>> First, a few terms (correct or improve as you like):
>
> Thanks for defining, we don't do that nearly often enough.
>
>> - WWAN device is a hardware device (l
On 6/18/19 1:06 PM, Dan Williams wrote:
> On Tue, 2019-06-18 at 10:20 -0500, Alex Elder wrote:
>> On 6/17/19 7:25 AM, Johannes Berg wrote:
>>> On Mon, 2019-06-17 at 13:42 +0200, Johannes Berg wrote:
>>>
But anyway, as I alluded to above, I had something like this in
mind:
Sorry for the d
On 6/24/19 1:15 AM, Marc Zyngier wrote:
On Mon, 24 Jun 2019 04:02:54 +0100,
Sowjanya Komatineni wrote:
This patch allows to create separate irq_set_wake and irq_set_type
implementations for different tegra designs PMC that has different
wake models which require difference wake registers and
On 6/18/19 2:14 PM, Johannes Berg wrote:
> On Tue, 2019-06-18 at 08:16 -0500, Alex Elder wrote:
>> On 6/17/19 6:28 AM, Johannes Berg wrote:
>>> On Tue, 2019-06-11 at 13:56 +0200, Arnd Bergmann wrote:
On Tue, Jun 11, 2019 at 10:12 AM Johannes Berg
wrote:
>> As I've made clear bef
On 6/18/19 2:22 PM, Johannes Berg wrote:
> On Tue, 2019-06-18 at 09:00 -0500, Alex Elder wrote:
. . .
> Anyway, I think for now we could probably live with not having this
> configurable for the IPA driver, and if it *does* need to be
> configurable, it seems like it should be a driver configurat
Hello
My name is Eddy William I am a lawyer by profession. I wish to offer you
the next of kin to my client. You will inherit the sum of ($14.2 Million)
dollars my client left in the bank before his death.
My client is a citizen of your country who died in auto crash with his wife
and only son. I
On Mon, Jun 24, 2019 at 05:23:45PM +0200, Allan W. Nielsen wrote:
> Hi Andrew,
>
> The 06/24/2019 16:26, Andrew Lunn wrote:
> > > > Yeah, there are 2 ethernet controller ports (managed by the enetc
> > > > driver)
> > > > connected inside the SoC via SGMII links to 2 of the switch ports, one
>
On 2019-06-24 18:14, Arnd Bergmann wrote:
On Mon, Jun 24, 2019 at 4:42 PM Roman Penyaev wrote:
epoll_create2() is needed to accept EPOLL_USERPOLL flags
and size, i.e. this patch wires up polling from userspace.
Can you explain in the patch description more what it's needed for?
Sure. Will
Hillf Danton writes:
> and wonder if the following works.
>
> - info = (void *)&id->driver_info;
> + info = (void *)id->driver_info;
Doh! Right you are. Thanks to both you and Andrey for quick and good
help.
We obviously have some bad code patterns here, since this apparently
worked f
v4: resurrect snprintf_noterm as static function that uses a
fixed-size intermediate buffer.
Return -E2BIG and WARN if the formatted string exceeds temp buffer.
make getxattr_cb callbacks return ssize_t.
v3: switch to using an intermediate buffer for snprintf destination
add patch t
The getxattr_cb functions return size_t, which is unsigned and then
cast that value to int and then ssize_t before returning it. While all
of this works, it relies on implicit casting rules for signed/unsigned
conversions.
Change getxattr_cb to return ssize_t to better conform with what the
caller
The convention with xattrs is to not store the termination with string
data, given that it returns the length. This is how setfattr/getfattr
operate.
Most of ceph's virtual xattr routines use snprintf to plop the string
directly into the destination buffer, but snprintf always NULL
terminates the
The getxattr manpage states that we should return ERANGE if the
destination buffer size is too small to hold the value.
ceph_vxattrcb_layout does this internally, but we should be doing
this for all vxattrs.
Fix the only caller of getxattr_cb to check the returned size
against the buffer length an
OK I want to try to organize a little more concisely some of the
discussion on this, because there is a very large amount of volume
to date and I think we need to try to narrow the focus back down
again.
I'm going to use a few terms here. Some of these I really don't
like, but I want to be unambi
gen_compile_command.py currently assumes that the .cmd files and the
source code live in the same directory, which is not the case when
a separate KBUILD_OUTPUT directory is used.
Add a new option to specify this the kbuild output directory. If the
option is not set the kernel source directory is
On Sun, 2019-06-23 at 20:47 -0700, Jordan Hand wrote:
> For TPM2-based systems, retrieve the TCG log from the TPM2 ACPI table.
>
> Signed-off-by: Jordan Hand
Please write a proper long description that describes where such thing
is defined and used if you feel like refining this and sending v2.
> On Jun 24, 2019, at 8:15 AM, Kirill A. Shutemov wrote:
>
> On Mon, Jun 24, 2019 at 03:04:21PM +, Song Liu wrote:
>>
>>
>>> On Jun 24, 2019, at 7:54 AM, Kirill A. Shutemov
>>> wrote:
>>>
>>> On Mon, Jun 24, 2019 at 02:42:13PM +, Song Liu wrote:
> On Jun 24, 2019,
From: Colin Ian King
Field ia_valid is being debugged with the field name iavalid, fix this.
Signed-off-by: Colin Ian King
---
fs/cifs/inode.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/cifs/inode.c b/fs/cifs/inode.c
index d7cc62252634..06a4892e9973 100644
--- a/fs/
On Mon, Jun 24, 2019 at 6:21 PM Alex Elder wrote:
> On 6/18/19 2:03 PM, Johannes Berg wrote:
>
> > Really there are two possible ways (and they intersect to some extent).
> >
> > One is the whole multi-function device, where a single WWAN device is
> > composed of channels offered by actually diff
Luke Nelson writes:
> From: Luke Nelson
>
> This is an eBPF JIT for RV32G, adapted from the JIT for RV64G.
> Any feedback would be greatly appreciated.
>
> It passes 359 out of 378 tests in test_bpf.ko. The failing tests are
> features that are not supported right now:
> - ALU64 DIV/MOD:
>
> > The other hypervisors are relatively obscure, but eventually
> > someone will hit problems.
>
> any idea if there's any other flag/way we could use to detect those?
I'm not aware of a generic way to detect any hypervisor unfortunately.
There are hypervisor reserved cpuid ranges, in theory yo
On 2019/06/21 2:22, Vignesh Raghavendra wrote:
HyperFlash devices are compliant with CFI AMD/Fujitsu Extended Command
Set (0x0002) for flash operations, therefore
drivers/mtd/chips/cfi_cmdset_0002.c can be used as is. But these devices
do not support DQ polling method of determining chip ready/
On Mon, Jun 24, 2019 at 05:27:32PM +0900, Byungchul Park wrote:
> Hello rcu folks,
>
> I thought it'd better to announce it if those spawnings fail because of
> !rcu_scheduler_fully_active.
>
> Of course, with the current code, it never happens though.
>
> Thoughts?
It seems in the right spirit
On 13-06-19, 10:13, Peng Ma wrote:
> DPPA2(Data Path Acceleration Architecture 2) qDMA
> supports channel virtualization by allowing DMA
typo virtualization
> jobs to be enqueued into different frame queues.
> Core can initiate a DMA transaction by preparing a frame
> descriptor(FD) for each DMA
On Fri, Jun 21, 2019 at 03:35:53PM +0100, Steve Capper wrote:
> Hi Anshuman,
>
> On Wed, Jun 19, 2019 at 09:47:40AM +0530, Anshuman Khandual wrote:
> > The arch code for hot-remove must tear down portions of the linear map and
> > vmemmap corresponding to memory being removed. In both cases the pa
On 6/13/19 10:13 AM, Yang Shi wrote:
On 6/13/19 4:39 AM, Kirill A. Shutemov wrote:
On Thu, Jun 13, 2019 at 05:56:47AM +0800, Yang Shi wrote:
The later patch would make THP deferred split shrinker memcg aware, but
it needs page->mem_cgroup information in THP destructor, which is
called
af
Add the PMIC regulator suspend configuration to entire Odroid
XU3/XU4/HC1 family of boards to reduce power usage during suspend. The
configuration is based on vendor (Hardkernel) reference kernel with
additional buck9 suspend configuration (for USB hub suspend and proper
reset).
Energy consumptio
Sorry, I neglected to add Dan and Johannes--who have been
primary contributors in this discussion--to this. Adding now.
-Alex
On 6/24/19 11:30 AM, Alex Elder wrote:
> OK I want to try to organize a little more concisely some of the
> discussion on this, be
On 6/23/19 7:54 AM, Thomas Gleixner wrote:
I will keep trying 4.14, unless you say otherwise.
It would be interesting though I don't expect too much data.
So all of the above use PCI/MSI. That's at least a data point. I need to
stare into that driver again to figure out why this might make a
d
> On 24-Jun-2019, at 8:12 PM, David Hildenbrand wrote:
>
> On 24.06.19 16:09, Sachin Sant wrote:
>> Latest -next fails to boot on POWER9 PowerVM LPAR due to RCU stalls.
>>
>> This problem was introduced with next-20190620 (dc636f5d78).
>> next-20190619 was last good kernel.
>>
>> Reverting f
On Mon, Jun 24, 2019 at 04:29:39PM +0200, Ard Biesheuvel wrote:
> On Mon, 24 Jun 2019 at 13:23, Ard Biesheuvel wrote:
> > On 6/24/19 1:16 PM, Will Deacon wrote:
> > > On Tue, May 28, 2019 at 11:04:20AM +0100, Will Deacon wrote:
> > >> On Thu, May 23, 2019 at 11:22:52AM +0100, Ard Biesheuvel wrote:
On Mon, 24 Jun 2019 at 19:14, Catalin Marinas wrote:
>
> On Mon, Jun 24, 2019 at 04:29:39PM +0200, Ard Biesheuvel wrote:
> > On Mon, 24 Jun 2019 at 13:23, Ard Biesheuvel wrote:
> > > On 6/24/19 1:16 PM, Will Deacon wrote:
> > > > On Tue, May 28, 2019 at 11:04:20AM +0100, Will Deacon wrote:
> > >
Hi,
On Mon, Jun 24, 2019 at 6:26 PM Bjørn Mork wrote:
> Doh! Right you are. Thanks to both you and Andrey for quick and good
> help.
>
> We obviously have some bad code patterns here, since this apparently
> worked for Kristian by pure luck.
Thanks a lot to everyone for spotting and fixing my m
Lee
On 6/24/19 9:42 AM, Lee Jones wrote:
On Wed, 05 Jun 2019, Dan Murphy wrote:
Hello
The v5 patchset missed adding in the new validation code.
Patch 1 of the v5 series was squashed into patch 4 of the v5 series.
So this will reduce the patchset by 1.
Sorry for the extra noise on the patchse
On Mon, Jun 17, 2019 at 05:23:04PM +0200, Mathieu Desnoyers wrote:
> This reverts commit 2b845d4b4acd9422bbb668989db8dc36dfc8f438.
>
> That commit introduces build issues for programs compiled in Thumb mode.
> Rather than try to be clever and emit a valid trap instruction on arm32,
> which require
On Mon, 24 Jun 2019, Suwan Kim wrote:
> > > + hcd->self.sg_tablesize = ~0;
> > > + hcd->self.no_sg_constraint = 1;
> >
> > You probably shouldn't do this, for two reasons. First, sg_tablesize
> > of the server's HCD may be smaller than ~0. If the client's value is
> > larger than the server's,
On 24/06/2019 14:59, Qian Cai wrote:
> Compiling a kernel with both FAIR_GROUP_SCHED=n and RT_GROUP_SCHED=n
> will generate a warning using W=1,
>
> kernel/sched/core.c: In function 'sched_init':
> kernel/sched/core.c:5906:32: warning: variable 'ptr' set but not used
> [-Wunused-but-set-variable]
On Mon, Jun 24, 2019 at 12:46:24PM -0400, Joel Fernandes wrote:
> On Mon, Jun 24, 2019 at 05:27:32PM +0900, Byungchul Park wrote:
> > Hello rcu folks,
> >
> > I thought it'd better to announce it if those spawnings fail because of
> > !rcu_scheduler_fully_active.
> >
> > Of course, with the curre
On Mon, Jun 24, 2019 at 4:34 AM Rasmus Villemoes
wrote:
>
> CONFIG_CAN_LEDS is deprecated. When trying to use the generic netdev
> trigger as suggested, there's a small inconsistency with the link
> property: The LED is on initially, stays on when the device is brought
> up, and then turns off (as
On Mon, 24 Jun 2019, Thomas Gleixner wrote:
> On Mon, 24 Jun 2019, Dmitry Vyukov wrote:
> > On Mon, Jun 24, 2019 at 2:08 PM Eric Dumazet wrote:
> > > >>> [ cut here ]
> > > >>> ODEBUG: free active (active state 0) object type: timer_list hint:
> > > >>> delayed_work_timer_f
On 22-Jun 08:03, Tejun Heo wrote:
> Hello,
Hi,
> Generally looks good to me. Some nitpicks.
>
> On Fri, Jun 21, 2019 at 09:42:13AM +0100, Patrick Bellasi wrote:
> > @@ -951,6 +951,12 @@ controller implements weight and absolute bandwidth
> > limit models for
> > normal scheduling policy and a
On Tue, Jun 11, 2019 at 03:56:27PM +0100, Sudeep Holla wrote:
> The usage of emulated and _TIF_SYSCALL_EMU flags in syscall_trace_enter
> is more complicated than required.
>
> Cc: Andy Lutomirski
> Cc: Ingo Molnar
> Cc: Borislav Petkov
> Acked-by: Oleg Nesterov
> Reviewed-by: Thomas Gleixner
Dave Chiluk writes:
> It has been observed, that highly-threaded, user-interactive
> applications running under cpu.cfs_quota_us constraints can hit a high
> percentage of periods throttled while simultaneously not consuming the
> allocated amount of quota. This impacts user-interactive non-cpu b
On 6/24/19 2:46 AM, Dmitry Osipenko wrote:
24.06.2019 6:02, Sowjanya Komatineni пишет:
This patch adds support for Tegra pinctrl driver suspend and resume.
During suspend, context of all pinctrl registers are stored and
on resume they are all restored to have all the pinmux and pad
configurat
On 22-Jun 08:07, Tejun Heo wrote:
> Hello,
Hi,
> On Fri, Jun 21, 2019 at 09:42:14AM +0100, Patrick Bellasi wrote:
> > Since it can be interesting for userspace, e.g. system management
> > software, to know exactly what the currently propagated/enforced
> > configuration is, the effective clamp v
801 - 900 of 1256 matches
Mail list logo