kobject_init() call added one more operation that has to be
done when doing the early initialization of both static and
dynamic livepatch structures.
It would have been easier when the early initialization code
was not duplicated. Let's deduplicate it for future generations
of livepatching hackers
Tobin's patch[1] uncovered that the livepatching code handles kobjects
a too complicated way.
The first patch removes the unnecessary custom kobject state handling.
The second patch is an optional code deduplication. I did something
similar already when introducing the atomic replace. But it was
On Wed, Apr 24, 2019 at 03:53:52PM +0800, Yue Haibing wrote:
> From: YueHaibing
>
> Fixes gcc '-Wunused-but-set-variable' warning:
>
> drivers/crypto/atmel-tdes.c: In function 'atmel_tdes_setkey':
> drivers/crypto/atmel-tdes.c:803:14: warning: variable 'alg_name' set but not
> used [-Wunused-bu
On Fri, 3 May 2019 11:29:59 +0200
Peter Zijlstra wrote:
> OMG, WTF, ARGH... That code is fsck'ing horrible. I'd almost argue to
> always do the INT3 thing, just to avoid games like that.
Hehe, that's almost the exact same thoughts I had when seeing this
code ;-)
>
> That said; for normal trap
On Tue, Apr 23, 2019 at 03:49:57PM +0800, Kefeng Wang wrote:
> Using dev_get_drvdata directly.
>
> Cc: Jamie Iles
> Cc: Herbert Xu
> Cc: "David S. Miller"
> Cc: linux-cry...@vger.kernel.org
> Cc: linux-arm-ker...@lists.infradead.org
> Signed-off-by: Kefeng Wang
> ---
> drivers/crypto/picoxcel
kobject_init() always succeeds and sets the reference count to 1.
It allows to always free the structures via kobject_put() and
the related release callback.
Note that the custom kobject state handling was used only
because we did not know that kobject_put() can and actually
should get called even
On Sat, Apr 27, 2019 at 12:43:13AM +0800, Yue Haibing wrote:
> From: YueHaibing
>
> Fix sparse warning:
>
> drivers/crypto/ccree/cc_driver.c:37:6: warning:
> symbol 'cc_sec_disable' was not declared. Should it be static?
>
> Signed-off-by: YueHaibing
> ---
> drivers/crypto/ccree/cc_driver.c
On Mon, 29 Apr 2019 at 12:44, Ulf Hansson wrote:
>
> On Tue, 23 Apr 2019 at 11:02, Jerome Brunet wrote:
> >
> > The purpose of this series is too improve reliability of the amlogic mmc
> > driver on new (g12a) and old ones (axg, gxl, gxbb, etc...)
> >
> > * The 3 first patches are just harmless c
On Wed, May 1, 2019 at 1:40 PM Christoph Hellwig wrote:
>
> No one is using this helper anymore.
>
> Signed-off-by: Christoph Hellwig
Acked-by: Arnd Bergmann
On 02/05/2019 16:28, Mike Rapoport wrote:
um allocates PTE pages with __get_free_page() and uses
GFP_KERNEL | __GFP_ZERO for the allocations.
Switch it to the generic version that does exactly the same thing for the
kernel page tables and adds __GFP_ACCOUNT for the user PTEs.
The pte_free()
On Mon, 29 Apr 2019 at 19:32, Raul E Rangel wrote:
>
> The SD Physical Layer Spec says the following: Since the SD Memory Card
> shall support at least the two bus modes 1-bit or 4-bit width, then any SD
> Card shall set at least bits 0 and 2 (SD_BUS_WIDTH="0101").
>
> This change verifies the car
On Tue, 30 Apr 2019 at 14:06, Ludovic BARRE wrote:
>
>
>
> On 4/30/19 1:13 PM, Ulf Hansson wrote:
> > On Fri, 26 Apr 2019 at 09:46, Ludovic Barre wrote:
> >>
> >> From: Ludovic Barre
> >>
> >> This patch series adds busy detect for stm32 sdmmc variant.
> >> Some adaptations are required:
> >> -A
On Wed, 1 May 2019 at 22:36, Gustavo A. R. Silva wrote:
>
> In preparation to enabling -Wimplicit-fallthrough, mark switch
> cases where we are expecting to fall through.
>
> This patch fixes the following warnings:
>
> In file included from drivers/mmc/host/usdhi6rol0.c:9:
> drivers/mmc/host/usdh
On 5/3/19 8:06 AM, Peter Zijlstra wrote:
> On Sun, Apr 28, 2019 at 05:25:38PM -0400, Waiman Long wrote:
>> During my rwsem testing, it was found that after a down_read(), the
>> reader count may occasionally become 0 or even negative. Consequently,
>> a writer may steal the lock at that time and ex
On Fri, May 03, 2019 at 10:21:05AM +1000, Stephen Rothwell wrote:
> Hi David,
>
> After merging the btrfs-kdave tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> fs/btrfs/props.c: In function 'inherit_props':
> fs/btrfs/props.c:389:4: warning: 'num_bytes' may be us
On Sun, Apr 28, 2019 at 05:25:46PM -0400, Waiman Long wrote:
> + /*
> + * This waiter may have become first in the wait
> + * list after re-acquring the wait_lock. The
> + * rwsem_first_waiter() test in the main whi
From: Philippe Schenker
Add the stmpe-adc DT node as found on Toradex T30 modules
Signed-off-by: Philippe Schenker
---
arch/arm/boot/dts/tegra30-apalis-v1.1.dtsi | 22 ++
arch/arm/boot/dts/tegra30-apalis.dtsi | 22 ++
arch/arm/boot/dts/tegra30-col
Hi Christophe,
On Tue, Apr 30, 2019 at 12:36 AM Christophe Leroy
wrote:
>
>
>
> Le 23/04/2019 à 05:49, Masahiro Yamada a écrit :
> > This prepares to move CONFIG_OPTIMIZE_INLINING from x86 to a common
> > place. We need to eliminate potential issues beforehand.
>
> How did you identify the funct
AVIC doorbell is used to notify a running vCPU that interrupts
has been injected into the vCPU AVIC backing page. Current logic
checks only if a VCPU is running before sending a doorbell.
However, the doorbell is not necessary if the destination
CPU is itself.
Add logic to check currently running
Current logic does not allow VCPU to be loaded onto CPU with
APIC ID 255. This should be allowed since the host physical APIC ID
field in the AVIC Physical APIC table entry is an 8-bit value,
and APIC ID 255 is valid in system with x2APIC enabled.
Instead, do not allow VCPU load if the host APIC I
Joe Perches writes:
> On Fri, 2019-05-03 at 16:59 +1000, Michael Ellerman wrote:
>> On Thu, 2017-03-30 at 10:19:25 UTC, Joe Perches wrote:
>> > Fix fallout too.
>> >
>> > Signed-off-by: Joe Perches
>>
>> Applied to powerpc next, thanks.
>>
>> https://git.kernel.org/powerpc/c/1e496391a845210130
From: Ludovic Barre
This patch allows to define the max prescaler by compatible.
To set a large range of timeout, the prescaler should be set
dynamically (from the timeout request) to improve the resolution
in order to have a timeout close to the expected value.
Signed-off-by: Ludovic Barre
---
On Wed, May 01, 2019 at 10:56:16PM +0300, Mike Rapoport wrote:
> The only reason s390 has ARCH_SELECT_MEMORY_MODEL option in
> arch/s390/Kconfig is an ancient compile error with allnoconfig which was
> fixed by commit 97195d6b411f ("[S390] fix sparsemem related compile error
> with allnoconfig on s
This commit adds the TmFifo platform driver for Mellanox BlueField
Soc. TmFifo is a shared FIFO which enables external host machine
to exchange data with the SoC via USB or PCIe. The driver is based
on virtio framework and has console and network access enabled.
Reviewed-by: Vadim Pasternak
Signe
On Fri, May 03, 2019 at 07:35:39AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Commit
>
> b835a4a3faec ("btrfs: use the existing reserved items for our first prop
> for inheritance")
>
> is missing a Signed-off-by from its author.
Will be fixed in next for-next snapshot, thanks.
This is similar to what the BSP does and needed to e.g. determine
necessary quirks for MIPI DSI.
Signed-off-by: Guido Günther
---
>From the list discussion and changelog it's not clear to me why a
different method was chosen for the B1 silicon so I left that in place
as is and only trigger on th
On 5/3/19 8:29 AM, Ulf Hansson wrote:
> On Wed, 1 May 2019 at 22:36, Gustavo A. R. Silva
> wrote:
>>
>> In preparation to enabling -Wimplicit-fallthrough, mark switch
>> cases where we are expecting to fall through.
>>
[..]
>>
>> Warning level 3 was used: -Wimplicit-fallthrough=3
>>
>> This
On 5/3/19 9:37 AM, Peter Zijlstra wrote:
> On Sun, Apr 28, 2019 at 05:25:46PM -0400, Waiman Long wrote:
>
>> +/*
>> + * This waiter may have become first in the wait
>> + * list after re-acquring the wait_lock. The
>> +
From: Philippe Schenker
This commit will enable the interrupts of all channels handled by this
driver only once in the probe function.
This will improve performance because one byte less has to be written over
i2c on each read out of the adc. On the fastest ADC mode this will improve
read out sp
From: Philippe Schenker
Remove unnecessary assignment. This could potentially cause an issue, if
the wait function runs into a timeout. Furthermore is this assignment also
not there in stmpe_read_temp()
Signed-off-by: Philippe Schenker
---
drivers/iio/adc/stmpe-adc.c | 2 --
1 file changed, 2
From: Philippe Schenker
In some cases, the wait_completion got interrupted. This caused the
error-handling to mutex_unlock the function. The before turned on
interrupt then got called anyway. In the ISR then completion()
was called causing problems.
Making this wait_completion non interruptible
On 5/3/19 9:10 AM, Peter Zijlstra wrote:
> On Sun, Apr 28, 2019 at 05:25:45PM -0400, Waiman Long wrote:
>> +static inline bool rwsem_try_write_lock(long count, struct rw_semaphore
>> *sem,
>> +enum writer_wait_state wstate)
>> {
>> long new;
>>
>> +l
On Fri, May 3, 2019 at 2:17 AM Takashi Iwai wrote:
>
> On Thu, 02 May 2019 19:27:00 +0200,
> Ross Zwisler wrote:
> >
> > Several sound related entries in MAINTAINERS refer to the old git tree
> > at "git://git.alsa-project.org/alsa-kernel.git". This is no longer used
> > for development, and Taka
On 05/02, Will Deacon wrote:
>
> Ok, if you're happy for us to take them via arm64 with your ack, then we can
> do that as well.
Yes, yes, please!
Oleg.
On Fri, May 03, 2019 at 02:58:59PM +0800, kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
> dev.2019.04.28a
> head: a4e0e069df6e8718bf165fb009cd3a23e7a808a3
> commit: a4e0e069df6e8718bf165fb009cd3a23e7a808a3 [85/85] rcu/sync: Simplify
> t
On Thu, May 02, 2019 at 12:09:32PM +0200, Oleg Nesterov wrote:
> On 05/01, Peter Zijlstra wrote:
> >
> > Anyway; I cobbled together the below. Oleg, could you have a look, I'm
> > sure I messed it up.
>
> Oh, I will need to read this carefully. but at first glance I do not see
> any hole...
>
> >
On Fri, 03 May 2019 16:06:40 +0200,
Ross Zwisler wrote:
>
> On Fri, May 3, 2019 at 2:17 AM Takashi Iwai wrote:
> >
> > On Thu, 02 May 2019 19:27:00 +0200,
> > Ross Zwisler wrote:
> > >
> > > Several sound related entries in MAINTAINERS refer to the old git tree
> > > at "git://git.alsa-project.or
On Fri, 2019-05-03 at 09:53 +0900, Tetsuo Handa wrote:
> On 2019/05/03 1:28, Casey Schaufler wrote:
> > On 5/2/2019 8:48 AM, Mimi Zohar wrote:
> >> [Cc'ing Paul, John, Casey]
> >>
> >> On Mon, 2019-04-22 at 20:18 -0400, Mimi Zohar wrote:
> >>> [Cc'ing LSM mailing list]
> >>>
> >>> On Fri, 2019-04-1
On 4/26/19 4:39 PM, Lendacky, Thomas wrote:
> On 4/24/19 11:10 AM, Singh, Brijesh wrote:
>> The hypercall can be used by the SEV guest to notify the page encryption
>
> This hyercall is used by the SEV guest to notify a change in the page...
>
>> status to the hypervisor. The hypercall should b
On Mon, Apr 15, 2019 at 10:35:51AM +0200, Arnd Bergmann wrote:
> llvm does does not understand -march=z9-109 and older target
> specifiers, so disable the respective Kconfig settings and
> the logic to make the boot code work on old systems when
> building with clang.
>
> Part of the early boot co
On Mon, Apr 15, 2019 at 09:12:06AM -0700, Nathan Chancellor wrote:
> On Mon, Apr 15, 2019 at 10:35:52AM +0200, Arnd Bergmann wrote:
> > The purgatory and boot Makefiles do not inherit the original cflags,
> > so clang falls back to the default target architecture when building it,
> > typically thi
On Mon, Apr 15, 2019 at 10:35:53AM +0200, Arnd Bergmann wrote:
> VIRT_TO_BUS is only used for legacy device PCI and ISA drivers using
> virt_to_bus() instead of the streaming DMA mapping API, and the
> remaining drivers generally don't work on 64-bit architectures.
>
> Two of these drivers also ca
On Tue, Apr 16, 2019 at 01:37:13PM +0200, Miroslav Benes wrote:
>
> [ ... snip ... ]
>
> Quick look, but it seems quite similar to the problem we had with
> apply_alternatives(). See arch/x86/kernel/livepatch.c and the commit which
> introduced it.
That was an interesting diversion :) I think I g
On 5/2/19 11:39 PM, Mark Brown wrote:
On Fri, Apr 19, 2019 at 02:46:49PM -0500, Pierre-Louis Bossart wrote:
config REGMAP_SOUNDWIRE
tristate
- depends on SOUNDWIRE_BUS
+ select SOUNDWIRE_BUS
This now makes _SOUNDWIRE different to all the other bus types; if this
is a
The current trace documentation, the section describing histogram's "onmatch"
is not straightforward enough about how this action is applied. It is not
clear what criteria are used to "match" both events. A short note is added,
describing what exactly is compared in order to match the events.
Sign
There was NVMEM support added directly to of_get_mac_address, and it uses
nvmem_get_mac_address under the hood, so we can remove it. As
of_get_mac_address can now return ERR_PTR encoded error values, adjust to
that as well.
Signed-off-by: Petr Štetiar
---
Changes since v2:
* ERR_PTR handling
On 5/1/19 5:01 PM, Brendan Higgins wrote:
From: Avinash Kondareddy
Tests how tests interact with test managed resources in their lifetime.
Signed-off-by: Avinash Kondareddy
Signed-off-by: Brendan Higgins
---
I think this change log could use more details. It is vague on what it
does.
than
On 01/05/2019 14:58, Julien Grall wrote:
> The functions mbi_compose_m{b, s}i_msg may be called from non-preemptible
> context. However, on RT, iommu_dma_map_msi_msg() requires to be called
> from a preemptible context.
>
> A recent patch split iommu_dma_map_msi_msg in two new functions:
> one tha
When "hw->ce4100_gbe_mdio_base_virt = ioremap(...)" fails, the driver
does not free the memory allocated in e1000_sw_init(), and also calls
"iounmap(hw->ce4100_gbe_mido_base_virt)" that is unnecessary.
Besides, when e1000_sw_init() fails, the driver also calls
"iounmap(hw->ce4100_gbe_mido_base_vi
There was NVMEM support added directly to of_get_mac_address, and it uses
nvmem_get_mac_address under the hood, so we can remove it. As
of_get_mac_address can now return ERR_PTR encoded error values, adjust to
that as well.
Signed-off-by: Petr Štetiar
---
Changes since v2:
* ERR_PTR and EPROB
On Fri, May 03, 2019 at 04:27:06PM +0200, Petr Štetiar wrote:
> Many embedded devices have information such as MAC addresses stored
> inside NVMEMs like EEPROMs and so on. Currently there are only two
> drivers in the tree which benefit from NVMEM bindings.
>
> Adding support for NVMEM into every o
There was NVMEM support added to of_get_mac_address, so it could now return
ERR_PTR encoded error values, so we need to adjust all current users of
of_get_mac_address to this new fact.
Signed-off-by: Petr Štetiar
---
Changes since v3:
* IS_ERR_OR_NULL -> IS_ERR
arch/arm/mach-mvebu/kirkwood
There was NVMEM support added to of_get_mac_address, so it could now return
ERR_PTR encoded error values, so we need to adjust all current users of
of_get_mac_address to this new fact.
Signed-off-by: Petr Štetiar
---
Changes since v3:
* IS_ERR_OR_NULL -> IS_ERR
drivers/net/usb/smsc75xx.c |
From: Peter Zijlstra
> Sent: 03 May 2019 14:11
> To: Waiman Long
...
> I've changed that like so.
>
> --- a/kernel/locking/rwsem.c
> +++ b/kernel/locking/rwsem.c
> @@ -406,19 +406,23 @@ static inline bool rwsem_try_write_lock(
> long new;
>
> lockdep_assert_held(&sem->wait_lock);
> +
On 5/1/19 5:01 PM, Brendan Higgins wrote:
Add myself as maintainer of KUnit, the Linux kernel's unit testing
framework.
Signed-off-by: Brendan Higgins
---
MAINTAINERS | 10 ++
1 file changed, 10 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 5c38f21aee787..c78ae95c56b80
From: Philippe Schenker
> Sent: 03 May 2019 14:57
> In some cases, the wait_completion got interrupted. This caused the
> error-handling to mutex_unlock the function. The before turned on
> interrupt then got called anyway. In the ISR then completion()
> was called causing problems.
>
> Making thi
On Tue, Apr 30, 2019 at 01:25:09PM -0700, Nick Desaulniers wrote:
> On Tue, Apr 23, 2019 at 2:01 PM Nick Desaulniers
> wrote:
> >
> > Towards the goal of removing cc-ldoption, it seems that --hash-style=
> > was added to binutils 2.17.50.0.2 in 2006. The minimal required version
> > of binutils fo
On Tue, Apr 30, 2019 at 12:08:43AM +0800, Pu Wen wrote:
> The Hygon Dhyana CPU has the SMBus device with PCI device ID 0x790b,
> which is the same as AMD CZ SMBus device. So add Hygon Dhyana support
> to the i2c-piix4 driver by using the code path of AMD.
>
> Signed-off-by: Pu Wen
> Reviewed-by:
On Thu, May 02, 2019 at 01:42:59PM +0200, Oleg Nesterov wrote:
> On 05/02, Oleg Nesterov wrote:
> >
> > But this all is cosmetic, it seems that we can remove ->rw_sem altogether
> > but I am not sure...
>
> I mean, afaics percpu_down_read() can just do
>
> wait_event(readers_block == 0);
>
From: Vladimir Oltean
Date: Thu, 2 May 2019 23:23:28 +0300
> This patchset adds a DSA driver for the SPI-controlled NXP SJA1105
> switch.
Series applied, thank you.
On Tue, Apr 30, 2019 at 07:00:02AM +, Anson Huang wrote:
> Use __maybe_unused for power management related functions
> instead of #if CONFIG_PM_SLEEP to simply the code.
>
> Signed-off-by: Anson Huang
Applied to for-next, thanks!
signature.asc
Description: PGP signature
Hello, Alan,
Just following up on the -rcu commit below. I believe that it needs
some adjustment given Peter Zijlstra's addition of "memory" to the x86
non-value-returning atomics, but thought I should double-check.
Thanx, Paul
---
Hi Thomas,
Here's the set of irqchip (and related) updates for 5.2. The main
offenders are the TI SCI drivers, which we've finally managed to fit
in the MSI framework. It comes with its own firmware interface, hence
some touching some files outside of the usual areas. Another one is
the revamp of
Hi Manivannan,
thank you for the patch. A few issues below:
On Thu, 2019-04-25 at 18:25 +0530, Manivannan Sadhasivam wrote:
> Add reset controller support for Bitmain BM1880 SoC reusing the
> reset-simple driver. While we are at it, this driver has also been
> modified to make use of the SPDX lic
On Fri, 3 May 2019 17:35:37 +0300
Tzvetomir Stoyanov wrote:
> The current trace documentation, the section describing histogram's "onmatch"
> is not straightforward enough about how this action is applied. It is not
> clear what criteria are used to "match" both events. A short note is added,
>
On 05/03, Paul E. McKenney wrote:
>
> > >> kernel/rcu/sync.c:74: warning: Function parameter or member 'rcu' not
> > >> described in 'rcu_sync_func'
> >kernel/rcu/sync.c:74: warning: Excess function parameter 'rhp'
> > description in 'rcu_sync_func'
>
> Good catch! I will be folding in the d
Leo,
On 12/04/2019 11:27, Leo Yan wrote:
Since CoreSight hardware topology can use a 'hidden' funnel in the
trace data path, this kind funnel doesn't have register for accessing
and is used by default from hardware design perspective. Below is an
example for related hardware topology:
+---
On Wed, May 01, 2019 at 11:54:56AM -0600, Raul E Rangel wrote:
> I am running into a kernel panic. A task gets stuck for more than 120
> seconds. I keep seeing blkdev_close in the stack trace, so maybe I'm not
> calling something correctly?
>
> Here is the panic:
> https://privatebin.net/?8ec48c1
hi Ulf
On 5/3/19 3:29 PM, Ulf Hansson wrote:
On Tue, 30 Apr 2019 at 14:06, Ludovic BARRE wrote:
On 4/30/19 1:13 PM, Ulf Hansson wrote:
On Fri, 26 Apr 2019 at 09:46, Ludovic Barre wrote:
From: Ludovic Barre
This patch series adds busy detect for stm32 sdmmc variant.
Some adaptations ar
On Mon, Apr 15, 2019 at 10:35:54AM +0200, Arnd Bergmann wrote:
> The arch/s390/boot directory is built with its own set of compiler
> options that does not include -Wno-pointer-sign like the rest of
> the kernel does, this causes a lot of harmess but correct warnings
> when building with clang.
>
On Fri, May 03, 2019 at 07:53:26AM -0700, Paul E. McKenney wrote:
> Hello, Alan,
>
> Just following up on the -rcu commit below. I believe that it needs
> some adjustment given Peter Zijlstra's addition of "memory" to the x86
> non-value-returning atomics, but thought I should double-check.
Righ
On Sun, Apr 28, 2019 at 05:25:49PM -0400, Waiman Long wrote:
> Bit 1 of sem->owner (RWSEM_ANONYMOUSLY_OWNED) is used to designate an
> anonymous owner - readers or an anonymous writer. The setting of this
> anonymous bit is used as an indicator that optimistic spinning cannot
> be done on this rwse
On Fri, May 03, 2019 at 04:50:59PM +0200, Peter Zijlstra wrote:
> So how about something like so then?
> --- a/kernel/locking/percpu-rwsem.c
> +++ b/kernel/locking/percpu-rwsem.c
> @@ -63,7 +66,7 @@ int __percpu_down_read(struct percpu_rw_
>* If !readers_block the critical section starts
On 5/3/19 11:21 AM, Peter Zijlstra wrote:
> On Sun, Apr 28, 2019 at 05:25:49PM -0400, Waiman Long wrote:
>> Bit 1 of sem->owner (RWSEM_ANONYMOUSLY_OWNED) is used to designate an
>> anonymous owner - readers or an anonymous writer. The setting of this
>> anonymous bit is used as an indicator that op
On Thu, May 02, 2019 at 05:51:12PM +, Goetz, Patrick G wrote:
>
>
> On 5/2/19 12:44 PM, Andreas Gruenbacher wrote:
> > On Thu, 2 May 2019 at 19:27, Goetz, Patrick G
> > wrote:
> >> On 5/1/19 10:57 PM, NeilBrown wrote:
> >>> Support some day support for nfs4 acls were added to ext4 (not a to
Hi Boris,
On 4/17/19 12:24 PM, Dave Hansen wrote:
...
>
> The comment here is missing one key point:
> kernel_physical_mapping_init() can only be used to populate non-present
> entries. It kinda infers that from "Create...", but I really think we
> need to be explicit.
>
> Anyway, it's better
On Thu, May 02, 2019 at 12:02:33PM +1000, NeilBrown wrote:
> On Tue, Dec 06 2016, J. Bruce Fields wrote:
>
> > On Tue, Dec 06, 2016 at 02:18:31PM +0100, Andreas Gruenbacher wrote:
> >> On Tue, Dec 6, 2016 at 11:08 AM, Miklos Szeredi wrote:
> >> > On Tue, Dec 6, 2016 at 12:24 AM, Andreas Grünbache
On 05/03, Peter Zijlstra wrote:
>
> On Thu, May 02, 2019 at 12:09:32PM +0200, Oleg Nesterov wrote:
>
> > > +static void readers_block(struct percpu_rw_semaphore *sem)
> > > +{
> > > + wait_event_cmd(sem->writer, !sem->readers_block,
> > > +__up_read(&sem->rw_sem), __down_read(&sem-
On Fri, May 03, 2019 at 03:26:23PM +0200, Petr Mladek wrote:
> Tobin's patch[1] uncovered that the livepatching code handles kobjects
> a too complicated way.
>
> The first patch removes the unnecessary custom kobject state handling.
>
> The second patch is an optional code deduplication. I did s
On Fri, May 3, 2019 at 7:20 AM David Laight wrote:
> Shouldn't this say what the value is?
> ISTR a recent patch to change the was the 'used to be constant' TASK_SIZE is
> defined.
> I think it might be 'The highest userspace virtual address the current
> process can use.' But I might be wrong.
This variable is no longer used and the compiler rightly complains that
it should be removed.
../drivers/rtc/rtc-imxdi.c: In function ‘dryice_rtc_set_alarm’:
../drivers/rtc/rtc-imxdi.c:633:16: warning: unused variable ‘now’
[-Wunused-variable]
unsigned long now;
^~~
Rework to r
On Fri, May 03, 2019 at 05:37:48PM +0200, Oleg Nesterov wrote:
> (And if we change this code to use wait_event(xchg(readers_block) == 0) we
> can remove rw_sem altogether).
That patch you just saw and didn't look at did just that.
> The main problem is that this is sub-optimal. We can have a lot
On 03/05/2019 17:42:17+0200, Anders Roxell wrote:
> This variable is no longer used and the compiler rightly complains that
> it should be removed.
>
> ../drivers/rtc/rtc-imxdi.c: In function ‘dryice_rtc_set_alarm’:
> ../drivers/rtc/rtc-imxdi.c:633:16: warning: unused variable ‘now’
> [-Wunused-v
Quoting Stephen Rothwell (2019-05-02 16:25:11)
> Hi all,
>
> After merging the clk tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> arch/arm/mach-omap2/omap_hwmod.c: In function '_get_clkdm':
> arch/arm/mach-omap2/omap_hwmod.c:669:35: error: 'CLK_IS_BASIC' undeclare
Quoting Aisheng Dong (2019-05-02 19:38:34)
> > From: Stephen Boyd [mailto:sb...@kernel.org]
> > Sent: Thursday, May 2, 2019 5:01 AM
> >
> > The Content-transfer-encoding header is still base64. I guess it can't be
> > fixed.
> >
>
> How can we know it's base64?
> As I saw from the 'Headers' in
The following changes since commit 79a3aaa7b82e3106be97842dedfd8429248896e6:
Linux 5.1-rc3 (2019-03-31 14:39:29 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/johan/gnss.git
tags/gnss-5.2-rc1
for you to fetch changes up to 7cc10c5cb14397d61d2
On Fri, 2019-05-03 at 14:39 +, David Laight wrote:
> From: Philippe Schenker
> > Sent: 03 May 2019 14:57
> > In some cases, the wait_completion got interrupted. This caused the
> > error-handling to mutex_unlock the function. The before turned on
> > interrupt then got called anyway. In the ISR
Quoting Aisheng Dong (2019-05-02 19:38:34)
> > From: Stephen Boyd [mailto:sb...@kernel.org]
> > Sent: Thursday, May 2, 2019 5:01 AM
> >
> > The Content-transfer-encoding header is still base64. I guess it can't be
> > fixed.
> >
>
> How can we know it's base64?
> As I saw from the 'Headers' in
Quoting Gustavo A. R. Silva (2019-04-30 07:32:06)
> In preparation to enabling -Wimplicit-fallthrough, mark switch
> cases where we are expecting to fall through.
>
> This patch fixes the following warnings:
>
> drivers/clk/imx/clk-pllv3.c: In function ‘imx_clk_pllv3’:
> drivers/clk/imx/clk-pllv3
We find the current CPU using smp_processor_id() if the event is not bound
to a CPU, to find the node for memory allocation. Use the safe numa_node_id()
instead to avoid BUG().
BUG: using smp_processor_id() in preemptible [] code: perf/1743
caller is tmc_alloc_etr_buffer+0x1bc/0x1f0
CPU
Instead of using smp_processor_id() to figure out the node,
use the numa_node_id() for the current CPU node to avoid
splats like :
BUG: using smp_processor_id() in preemptible [] code: perf/1743
caller is alloc_etr_buf.isra.6+0x80/0xa0
CPU: 1 PID: 1743 Comm: perf Not tainted 5.1.0-rc6-1
On Fri, May 03, 2019 at 08:34:57PM +0800, kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git sched/core
> head: 65874bd36e6ae3028539e989bfb5c28ad457368e
> commit: c2cb30bfceceba8a2a0d5713230a250dd6140e22 [24/27] power/suspend: Add
> function to disable
On Fri, May 03, 2019 at 05:58:05PM +0200, Johan Hovold wrote:
> The following changes since commit 79a3aaa7b82e3106be97842dedfd8429248896e6:
>
> Linux 5.1-rc3 (2019-03-31 14:39:29 -0700)
>
> are available in the Git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/johan/gns
On Fri, May 03, 2019 at 11:44:53AM +0300, Alexander Shishkin wrote:
> With the addition of dynamically loadable buffer drivers, there needs
> to be a way of knowing the currently available ones without having to
> scan the list of loaded modules or trial and error.
>
> Add a sysfs file that lists
On Fri, May 03, 2019 at 11:44:45AM +0300, Alexander Shishkin wrote:
> @@ -1481,7 +1501,7 @@ nr_pages_show(struct device *dev, struct
> device_attribute *attr, char *buf)
> else if (msc->mode == MSC_MODE_MULTI) {
> list_for_each_entry(win, &msc->win_list, entry) {
>
> * David Laight wrote:
>
> > It has already been measured - it is far too slow.
>
> I don't think proper buffering was tested, was it? Only a per syscall
> RDRAND overhead which I can imagine being not too good.
>
Well, I have some numbers, but I am struggling to understand one
aspect there.
On Fri, 3 May 2019, Peter Zijlstra wrote:
> On Fri, May 03, 2019 at 07:53:26AM -0700, Paul E. McKenney wrote:
> > Hello, Alan,
> >
> > Just following up on the -rcu commit below. I believe that it needs
> > some adjustment given Peter Zijlstra's addition of "memory" to the x86
> > non-value-retu
On Fri, May 03, 2019 at 11:44:52AM +0300, Alexander Shishkin wrote:
> Introduces a concept of buffer drivers, which is a mechanism for creating
> trace sinks that would receive trace data from MSC buffers and transfer it
> elsewhere.
>
> A buffer driver can implement its own window allocation/deal
The pull request you sent on Thu, 2 May 2019 13:46:40 -0700:
> https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git
> tags/clk-fixes-for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/8f76216c80c299ab8074b8658b73faa3815c6f39
Thank you!
--
Deet-doot-
The pull request you sent on Thu, 02 May 2019 20:35:52 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git tags/sound-5.1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/46572f785fb41949665ef4665563db5346f7cb30
Thank you!
--
Deet-doot-dot, I am a b
201 - 300 of 542 matches
Mail list logo
