Hi Catalin
> -Original Message-
> From: Catalin Marinas
> Sent: 2019年9月24日 0:07
> To: Justin He (Arm Technology China)
> Cc: Will Deacon ; Mark Rutland
> ; James Morse ; Marc
> Zyngier ; Matthew Wilcox ; Kirill A.
> Shutemov ; linux-arm-
> ker...@lists.infradead.org; linux-kernel@vger.ke
On 2019-9-19 22:30 Philipp Puschmann wrote
> For some years and since many kernel versions there are reports that the RX
> UART SDMA channel stops working at some point. The workaround was to
> disable DMA for RX. This commit tries to fix the problem itself.
>
> Due to its license i wasn't abl
On Mon, 2019-09-23 at 14:25 +0200, Michal Hocko wrote:
> On Tue 17-09-19 11:07:47, Alastair D'Silva wrote:
> > From: Alastair D'Silva
> >
> > On PowerPC, the address ranges allocated to OpenCAPI LPC memory
> > are allocated from firmware. These address ranges may be higher
> > than what older ker
On (09/23/19 14:58), Petr Mladek wrote:
>
> If I understand it correctly then this is the re-appearing problem.
> The only systematic solution with the current approach is to
> take port->lock in printk_safe/printk_deferred context.
It probably is.
We have a number of reverse paths. TTY invokes M
On 24/09/19 03:00, Andrea Arcangeli wrote:
> Before and after this specific commit there is a difference with gcc 8.3.
>
> full patchset applied
>
> 753699 879719616 851286 cfd56 build/arch/x86/kvm/kvm-intel.ko
>
> git revert
>
> 753739 879719616 851326 cfd7e build/arch/x86
The pull request you sent on Mon, 23 Sep 2019 10:24:21 -0700:
> https://github.com/cschaufler/smack-next.git smack-for-5.4
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/e94f8ccde4710f9a3e51dd3bc6134c96e33f29b3
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.w
On 24/09/19 02:51, Andrea Arcangeli wrote:
> This was covered in the commit header of patch 2:
Oops, sorry.
> Lot more patches are needed to get rid of kvm_x86_ops entirely because
> there are lots of places checking the actual value of the method
> before making the indirect call. I tried to sta
On Mon, Sep 23, 2019 at 2:50 PM Casey Schaufler wrote:
>
> On 9/9/2019 1:46 PM, Arnd Bergmann wrote:
> > In some randconfig builds, the lack of an explicit #include
> > in smack_lsm.c causes a build failure:
>
> What tree/branch are you working with? I don't see this.
It was in the latest linux-n
I have done a very simple comparison with gdb disassemble:
By applying this patch, there was a reduction in the function size from
882 to 878 instructions.
(It's a resend, due to not having all the correct lists on my previous
mail)
On Mon, 2019-09-23 at 18:30 -0300, Leonardo Bras wrote:
> Reduc
> -Original Message-
> From: Austin Kim [mailto:austindh@gmail.com]
> Sent: Monday, September 23, 2019 9:35 PM
> To: Pkshih; kv...@codeaurora.org; da...@davemloft.net
> Cc: linux-wirel...@vger.kernel.org; net...@vger.kernel.org;
> linux-kernel@vger.kernel.org
> Subject: Re: [PATCH] rt
Hi, Andy
> On Mon, 2019-09-23 at 09:24 +, Andy Tang wrote:
> > Hi Rui, Edubezval,
> >
> > Would you please review this patch?
> >
> CC Anson Huang.
> I'd prefer all the qoriq thermal patches go through his review first.
>
> thanks,
> rui
>
> > BR,
> > Andy
> >
> > > -Original Message---
>Subject: RE: [Patch v4] storvsc: setup 1:1 mapping between hardware queue
>and CPU queue
>
>>Subject: Re: [Patch v4] storvsc: setup 1:1 mapping between hardware
>>queue and CPU queue
>>
>>On Fri, Sep 06, 2019 at 10:24:20AM -0700, lon...@linuxonhyperv.com wrote:
>>>From: Long Li
>>>
>>>storvsc doe
From: Peng Fan
V8:
Add missed arm-smccc-mbox.h
V7:
Typo fix
#mbox-cells changed to 0
Add a new header file arm-smccc-mbox.h
Use ARM_SMCCC_IS_64
Andre,
The function_id is still kept in arm_smccc_mbox_cmd, because arm,func-id
property is optional, so clients could pass function_id to mbox drive
From: Peng Fan
The ARM SMC/HVC mailbox binding describes a firmware interface to trigger
actions in software layers running in the EL2 or EL3 exception levels.
The term "ARM" here relates to the SMC instruction as part of the ARM
instruction set, not as a standard endorsed by ARM Ltd.
Signed-off
From: Peng Fan
This mailbox driver implements a mailbox which signals transmitted data
via an ARM smc (secure monitor call) instruction. The mailbox receiver
is implemented in firmware and can synchronously return data when it
returns execution to the non-secure world again.
An asynchronous recei
On 9/23/19 7:06 PM, Tejun Heo wrote:
> finish_writeback_work() reads @done->waitq after decrementing
> @done->cnt. However, once @done->cnt reaches zero, @done may be freed
> (from stack) at any moment and @done->waitq can contain something
> unrelated by the time finish_writeback_work() tries to
On (09/23/19 18:45), He Zhe wrote:
> I think it is NOT necessary to inform user-space, when it just wants to read
> from the beginning of the buffer, that the buffer has changed since the time
> point when it issues the action of reading.
The point here is not to notify user space that the logbuf
finish_writeback_work() reads @done->waitq after decrementing
@done->cnt. However, once @done->cnt reaches zero, @done may be freed
(from stack) at any moment and @done->waitq can contain something
unrelated by the time finish_writeback_work() tries to read it. This
led to the following crash.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
The following changes since commit 5f9e832c137075045d15cd6899ab0505cfb2ca4b:
Linus 5.3-rc1 (2019-07-21 14:05:38 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git
tags/hyperv-next-sig
On Mon, Sep 23, 2019 at 12:19:12PM +0200, Paolo Bonzini wrote:
> On 20/09/19 23:25, Andrea Arcangeli wrote:
> > They can be called directly more efficiently, so we can as well mark
> > some of them inline in case gcc doesn't decide to inline them.
>
> What is the output of size(1) before and after
On Mon, 2019-09-23 at 23:14 +0200, Sven Schnelle wrote:
> Hi,
>
> On Fri, Feb 15, 2019 at 03:45:54PM +0100, Christoph Hellwig wrote:
> > Hi all,
> >
> > this series finishes off converting our dma mask model to split
> > between device capabilities (dev->dma_mask and dev-
> > >coherent_dma_mask)
>Thanks for the clarification.
>
>The problem with what Ming is proposing in my mind (and its an existing
>problem that exists today), is that nvme is taking precedence over anything
>else until it absolutely cannot hog the cpu in hardirq.
>
>In the thread Ming referenced a case where today if the
On Mon, Sep 23, 2019 at 12:21:43PM +0200, Paolo Bonzini wrote:
> On 20/09/19 23:25, Andrea Arcangeli wrote:
> > Cleanup after this was finally left fully unused.
> >
> > Signed-off-by: Andrea Arcangeli
> > ---
> > arch/x86/include/asm/kvm_host.h | 3 ---
> > arch/x86/kvm/pmu.h | 19
On Tue, Sep 24, 2019 at 02:15:39AM +0200, Paolo Bonzini wrote:
> On 23/09/19 22:23, Sean Christopherson wrote:
> >
> > +int nested_vmx_handle_vmx_instruction(struct kvm_vcpu *vcpu)
> > +{
> > + switch (to_vmx(vcpu)->exit_reason) {
> > + case EXIT_REASON_VMCLEAR:
> > + return handle_
On Mon, Sep 23, 2019 at 4:35 PM James Morris wrote:
>
> My understanding is that SafeSetID is shipping in ChromeOS -- this was
> part of the rationale for merging it.
Well, if even the developer didn't test it for two months, I don't
think "it's in upstream" makes any sense or difference.
On Mon, Sep 23, 2019 at 4:30 PM Paul E. McKenney wrote:
>
> I pushed some (untested) commits out to the dev branch of -rcu, the
> overall effect of which is shown in the patch below. The series
> adds a new rcu_replace() to avoid confusion with swap(), replaces
> uses of rcu_swap_protected() with
On 9/23/19 6:59 PM, Kees Cook wrote:
> On Mon, Sep 23, 2019 at 03:42:27PM +, James Dingwall wrote:
>> On Thu, Sep 19, 2019 at 12:37:40PM -0400, Boris Ostrovsky wrote:
>>> On 9/19/19 12:14 PM, James Dingwall wrote:
On Thu, Sep 19, 2019 at 03:51:33PM +, Luck, Tony wrote:
>> I have be
On Mon, 2019-09-23 at 09:24 +, Andy Tang wrote:
> Hi Rui, Edubezval,
>
> Would you please review this patch?
>
CC Anson Huang.
I'd prefer all the qoriq thermal patches go through his review first.
thanks,
rui
> BR,
> Andy
>
> > -Original Message-
> > From: Andy Tang
> > Sent: 2019年
Hi Paolo,
On Tue, Sep 24, 2019 at 02:15:39AM +0200, Paolo Bonzini wrote:
> Do you really need that? Why couldn't the handle_* functions simply be
> exported from nested.c to vmx.c?
I prefer the direct call too indeed.
If Sean doesn't want to export those generic names to the whole kernel
it wou
On 24/09/19 02:35, Sean Christopherson wrote:
>> I agree. I think the way Andrea did it in his patch may not the nicest
>> but is (a bit surprisingly) the easiest and most maintainable.
> Heh, which patch? The original patch of special casing the high
> priority exits?
Yes.
Paolo
On Tue, Sep 24, 2019 at 02:16:36AM +0200, Paolo Bonzini wrote:
> On 23/09/19 23:08, Andrea Arcangeli wrote:
> > The two most attractive options to me remains what I already have
> > implemented under #ifdef CONFIG_RETPOLINE with direct calls
> > (optionally replacing the "if" with a small "switch"
On Mon, Sep 23, 2019 at 11:22:31AM +0200, Peter Zijlstra wrote:
>On Thu, Sep 19, 2019 at 10:08:44AM +0800, Wei Yang wrote:
>> There is only one place to use good_area jump, which could be reduced by
>> merging the following two if clause.
>>
>> Signed-off-by: Wei Yang
>> ---
>> arch/x86/mm/fault
On Mon, Sep 23, 2019 at 04:45:00PM -0700, Sean Christopherson wrote:
> With a straight rename to kvm_x86_() instead of wrappers, we
> shouldn't need kvm_ops.c. kvm_ops.h might be helpful, but it'd be just
> as easy to keep them in kvm_host.h and would likely yield a more
> insightful diff[*].
Yes
On 2019/9/23 22:37, rain.1986.08...@gmail.com wrote:
From: Rain River
Yanjun has been spending quite a lot of time fixing bugs
in FORCEDETH source code. I'd like to add Yanjun to maintainers
list.
Signed-off-by: Rain River
Acked-by: Zhu Yanjun
Thanks a lot.
Zhu Yanjun
---
MAINTAINE
On 23/09/19 23:08, Andrea Arcangeli wrote:
> The two most attractive options to me remains what I already have
> implemented under #ifdef CONFIG_RETPOLINE with direct calls
> (optionally replacing the "if" with a small "switch" still under
> CONFIG_RETPOLINE if we give up the prioritization of the
On 23/09/19 22:23, Sean Christopherson wrote:
>
> +int nested_vmx_handle_vmx_instruction(struct kvm_vcpu *vcpu)
> +{
> + switch (to_vmx(vcpu)->exit_reason) {
> + case EXIT_REASON_VMCLEAR:
> + return handle_vmclear(vcpu);
> + case EXIT_REASON_VMLAUNCH:
> + retur
Hi Daniel,
Thanks for sending this.
On Wed, Sep 18, 2019 at 02:43:16PM -0600, Daniel Campello wrote:
> This change introduces a new debugfs file 'test_event' that when written
> to causes the EC to generate a test event.
Please mention that this adds a second sub cmd for the test event, and
pull
> -Original Message-
> From: Ingo Molnar on Sunday, September 22, 2019 1:26 AM
>
> * Linus Torvalds wrote:
>
> > On Fri, Sep 20, 2019 at 9:35 AM Brendan Higgins
> > wrote:
> > >
> > > Sorry about that. I am surprised that none of the other reviewers
> > > brought this up.
> >
> > I thin
On Mon, Sep 23, 2019 at 07:43:07PM -0400, Andrea Arcangeli wrote:
> On Mon, Sep 23, 2019 at 02:24:35PM -0700, Sean Christopherson wrote:
> > An extra CALL+RET isn't going to be noticeable, especially on modern
> > hardware as the high frequency VMWRITE/VMREAD fields should hit the
> > shadow VMCS.
On Mon, Sep 23, 2019 at 09:34:46PM +0200, Borislav Petkov wrote:
> On Mon, Sep 23, 2019 at 11:41:59AM -0700, Andy Lutomirski wrote:
> > On Mon, Sep 23, 2019 at 2:49 AM Borislav Petkov wrote:
> > >
> > > On Fri, Sep 20, 2019 at 03:19:09PM +0200, Christian Brauner wrote:
> > > > While touching secco
On Fri, Aug 30, 2019 at 12:36:28PM -0400, Joel Fernandes (Google) wrote:
> Hi,
>
> This is a series on top of the patch "rcu/tree: Add basic support for
> kfree_rcu() batching".
>
> It adds performance tests, some clean ups and removal of "lazy" RCU callbacks.
>
> Now that kfree_rcu() is handle
On Mon, Sep 23, 2019 at 07:06:26PM -0400, Andrea Arcangeli wrote:
> On Mon, Sep 23, 2019 at 03:35:26PM -0700, Sean Christopherson wrote:
> > On Fri, Sep 20, 2019 at 05:24:55PM -0400, Andrea Arcangeli wrote:
> > > request_immediate_exit is one of those few cases where the pointer to
> > > function o
On Mon, Sep 23, 2019 at 02:24:35PM -0700, Sean Christopherson wrote:
> An extra CALL+RET isn't going to be noticeable, especially on modern
> hardware as the high frequency VMWRITE/VMREAD fields should hit the
> shadow VMCS.
In your last email with regard to the inlining optimizations made
possibl
On Mon, 23 Sep 2019, Linus Torvalds wrote:
> Should we just remove safesetid again? It's not really maintained, and
> it's apparently not used. It was merged in March (with the first
> commit in January), and here we are at end of September and this
> happens.
My understanding is that SafeSetID
From: Andi Kleen
Make sure to not free the name passed in by the caller, but free
all the allocated ids when parsing expressions.
The loop at the end knows that the first entry shouldn't be freed,
so make sure the caller name is the first entry.
Fixes
% perf stat -M
IpB,IpCall,IpTB,IPC,Retiri
From: Andi Kleen
My "compile perf statically" setup doesn't like this assert
for unknown reasons. Replace it with a standard BUG_ON
Signed-off-by: Andi Kleen
---
tools/perf/util/expr.y | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/perf/util/expr.y b/tools/perf/u
From: Andi Kleen
I'm not fully sure if this is the correct fix, but without this
I get crashes on more complex perf stat metric usages. The problem
is that part of the state gets freed when a weak group fails,
but then is later still used. Just don't free the ids, we're
going to reuse them anyway
On Mon, Sep 23, 2019 at 12:01:49PM -0700, Linus Torvalds wrote:
> On Wed, Sep 18, 2019 at 10:41 AM Micah Morton wrote:
> >
> > Fix for SafeSetID bug that was introduced in 5.3
>
> So this seems to be a good fix, but the bug itself came from the fact that
>
> rcu_swap_protected(..)
>
> is so
On Fri, Sep 13, 2019 at 02:14:02PM -0700, Sami Tolvanen wrote:
> We call native_set_fixmap indirectly through the function pointer
> struct pv_mmu_ops::set_fixmap, which expects the first parameter to be
> 'unsigned' instead of 'enum fixed_addresses'. This patch changes the
> function type for nati
tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/tip/tip.git
WIP.core/toplevel
head: 166a63584297d3e1e1d7d380ee13dfe1a871ab04
commit: 7eff58ad913615232613491bec0f54d34ce73bda [4/6] toplevel: Fix up
drivers/sound/ movement effects
reproduce:
# apt-get install sparse
On Mon, Sep 09, 2019 at 09:52:40AM +0200, David Hildenbrand wrote:
> On 28.08.19 09:42, Yi Wang wrote:
> > We get two warnings when build kernel W=1:
> > mm/shuffle.c:36:12: warning: no previous prototype for ‘shuffle_show’
> > [-Wmissing-prototypes]
> > mm/sparse.c:220:6: warning: no previous prot
On Fri, Sep 06, 2019 at 10:34:47AM -0700, Ard Biesheuvel wrote:
> On Fri, 6 Sep 2019 at 03:44, Will Deacon wrote:
> >
> > On Wed, Sep 04, 2019 at 01:38:04PM -0700, Kees Cook wrote:
> > > On Wed, Sep 04, 2019 at 11:38:03AM +0100, Will Deacon wrote:
> > > > On Wed, Aug 14, 2019 at 01:55:50PM -0700,
On Sun, Aug 25, 2019 at 04:18:56PM -0700, Kees Cook wrote:
> As we've done with VFS, string operations, etc, reject usercopy sizes
> larger than INT_MAX, which would be nice to have for catching bugs
> related to size calculation overflows[1].
>
> This adds 10 bytes to x86_64 defconfig text and 19
Linus,
Enjoy!
The following changes since commit 5f9e832c137075045d15cd6899ab0505cfb2ca4b:
Linus 5.3-rc1 (2019-07-21 14:05:38 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git mfd-next-5.4
for you to fetch changes up to 8391c6cb2414d9
On Mon, Sep 23, 2019 at 03:35:26PM -0700, Sean Christopherson wrote:
> On Fri, Sep 20, 2019 at 05:24:55PM -0400, Andrea Arcangeli wrote:
> > request_immediate_exit is one of those few cases where the pointer to
> > function of the method isn't fixed at build time and it requires
> > special handlin
Linus,
Enjoy!
The following changes since commit 5f9e832c137075045d15cd6899ab0505cfb2ca4b:
Linus 5.3-rc1 (2019-07-21 14:05:38 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/lee/backlight.git
tags/backlight-next-5.4
for you to fetch changes up
On Mon, Sep 23, 2019 at 03:42:27PM +, James Dingwall wrote:
> On Thu, Sep 19, 2019 at 12:37:40PM -0400, Boris Ostrovsky wrote:
> > On 9/19/19 12:14 PM, James Dingwall wrote:
> > > On Thu, Sep 19, 2019 at 03:51:33PM +, Luck, Tony wrote:
> > >>> I have been investigating a regression in our e
The following changes since commit 5f9e832c137075045d15cd6899ab0505cfb2ca4b:
Linus 5.3-rc1 (2019-07-21 14:05:38 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git
tags/pci-v5.4-changes
for you to fetch changes up to c5048a73b4770304
tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/tip/tip.git
WIP.core/toplevel
head: 166a63584297d3e1e1d7d380ee13dfe1a871ab04
commit: 7eff58ad913615232613491bec0f54d34ce73bda [4/6] toplevel: Fix up
drivers/sound/ movement effects
config: x86_64-rhel-7.6 (attached as .config)
com
On Mon, Sep 23, 2019 at 08:49:11AM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:b41dae06 Merge tag 'xfs-5.4-merge-7' of git://git.kernel.o..
> git tree: net-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=130b25ad60
> kernel
When CONFIG_UAPI_HEADER_TEST=y, exported headers are compile-tested to
make sure they can be included from user-space.
Currently, linux/netfilter_bridge/ebtables.h is excluded from the test
coverage. To make it join the compile-test, we need to fix the build
errors attached below.
For a case like
Hi,
On Mon, Sep 23, 2019 at 11:49 AM Mark Brown wrote:
>
> On Mon, Sep 23, 2019 at 11:36:11AM -0700, Doug Anderson wrote:
> > On Mon, Sep 23, 2019 at 11:14 AM Mark Brown wrote:
>
> > > Boot on means that it's powered on when the kernel starts, it's
> > > for regulators that we can't read back th
Hi Linus,
Please pull the following Kselftest update for Linux 5.4-rc1.
This Kselftest update for Linux 5.4-rc1 consists of several fixes to
existing tests.
diff is attached.
This pull has just the ksleftest patches I sent in my previous pull
request. I dropped the KUnit patches and rebased.
On Fri, Sep 20, 2019 at 05:24:55PM -0400, Andrea Arcangeli wrote:
> request_immediate_exit is one of those few cases where the pointer to
> function of the method isn't fixed at build time and it requires
> special handling because hardware_setup() may override it at runtime.
>
> Signed-off-by: An
On Mon, Sep 23, 2019 at 01:34:21PM -0400, Andrea Arcangeli wrote:
> Per subject of the patch, 14 is also an optimization that while not a
> strict requirement, is somewhat related to the monolithic conversion
> because in fact it may naturally disappear if I rename the vmx/svm
> functions directly.
On Mon, Sep 23, 2019 at 12:08:53PM -0700, Ira Weiny wrote:
>
> Since the last RFC patch set[1] much of the discussion of supporting RDMA with
> FS DAX has been around the semantics of the lease mechanism.[2] Within that
> thread it was suggested I try and write some documentation and/or tests for
Linking with ld.lld via $ make LD=ld.lld produces the warning:
ld.lld: warning: cannot find entry symbol _start; defaulting to 0x1000
Linking with ld.bfd shows the default entry is 0x1000:
$ readelf -h arch/x86/realmode/rm/realmode.elf | grep Entry
Entry point address: 0x1000
Whil
Dan,
On 9/23/19 9:29 PM, Dan Murphy wrote:
> Jacek
>
> On 9/21/19 1:06 PM, Jacek Anaszewski wrote:
>> Dan,
>>
>> On 9/20/19 7:41 PM, Dan Murphy wrote:
>>> Update the lp5523 to use the multi color framework.
>>>
>>> Signed-off-by: Dan Murphy
>>> ---
>>> drivers/leds/leds-lp5523.c
On Wed, Sep 18, 2019 at 1:58 PM Randy Dunlap wrote:
>
> From: Randy Dunlap
>
> Fix typos in drivers/ntb/hw/idt/Kconfig.
> Use consistent spelling and capitalization.
>
> Fixes: bf2a952d31d2 ("NTB: Add IDT 89HPESxNTx PCIe-switches support")
> Signed-off-by: Randy Dunlap
> Cc: Jon Mason
> Cc: Dav
On Sun, Sep 15, 2019 at 10:08 AM Mehta, Sanju wrote:
>
> From: Sanjay R Mehta
>
> The AMD new hardware uses BAR23 and BAR45 as memory windows
> as compared to previos where BAR1, BAR23 and BAR45 is used
> for memory windows.
>
> This patch add support for both AMD hardwares.
I pulled both of the
On Mon, Sep 23, 2019 at 3:06 PM Nick Desaulniers
wrote:
> Steven, Ingo, would one of you mind picking up this fix, please? See
> for multiple reports:
> https://github.com/ClangBuiltLinux/linux/issues/216
Sorry, https://github.com/ClangBuiltLinux/linux/issues/97 is the link.
--
Thanks,
~Nick Des
On Fri, Jul 12, 2019 at 10:41 AM Nathan Chancellor
wrote:
>
> On Fri, Jul 12, 2019 at 10:58:48AM +0200, Arnd Bergmann wrote:
> > clang-9 does not like the way that the is_signed_type() compares
> > function pointers deep inside of the trace even macros:
> >
> > In file included from arch/x86/xen/t
On Thu, Aug 29, 2019 at 7:29 AM Niklas Söderlund
wrote:
>
> Hi,
>
> On 2019-08-29 13:43:49 +0200, Hans Verkuil wrote:
> > Adding Niklas.
> >
> > Niklas, can you take a look at this?
>
> I'm happy to have a look at this. I'm currently moving so all my boards
> are in a box somewhere. I hope to have
Hi Adam,
On 19-09-23 16:03, Adam Thomson wrote:
> On 17 September 2019 13:43, Marco Felsch wrote:
>
> > Currently the suspend reg_field maps to the pmic voltage selection bits
> > and is used during suspend_enabe/disable() and during get_mode(). This
> > seems to be wrong for both use cases.
> >
Dan,
On 9/23/19 7:56 PM, Dan Murphy wrote:
> Jacek
>
> On 9/21/19 10:11 AM, Jacek Anaszewski wrote:
>> Dan,
>>
>> On 9/20/19 7:41 PM, Dan Murphy wrote:
>>> Introduce the LP5036/30/24/18/12/9 RGB LED driver.
>>> The difference in these parts are the number of
>>> LED outputs where the:
>>>
>>> LP5
On 9/23/19 3:03 PM, Madhuparna Bhowmik wrote:
Fixed Excess function parameters warning.
warning: Excess function parameter 'offset' description in
'dio_complete'.
Removed the description of the local variable offset from the
description for arguments of a function and added it with the
declaratio
On Mon, 23 Sep 2019 at 12:08, Thierry Reding wrote:
>
> From: Adrian Hunter
>
> Add host operation ->set_dma_mask() so that drivers can define their own
> DMA masks.
>
> Signed-off-by: Adrian Hunter
> Tested-by: Nicolin Chen
> Signed-off-by: Thierry Reding
Applied for fixes and adding a stabl
On Mon, 23 Sep 2019 at 12:08, Thierry Reding wrote:
>
> From: Nicolin Chen
>
> The SDHCI controller on Tegra186 supports 40-bit addressing, which is
> usually enough to address all of system memory. However, if the SDHCI
> controller is behind an IOMMU, the address space can go beyond. This
> hap
On Sun, Jul 07, 2019 at 01:15:41AM +0100, Dragan Cvetic wrote:
> Add SD-FEC driver documentation.
>
> Signed-off-by: Derek Kiernan
> Signed-off-by: Dragan Cvetic
> ---
> Documentation/misc-devices/index.rst | 1 +
> 1 file changed, 1 insertion(+)
Hi! It looks like Documentation/misc-devices/xi
On 9/9/2019 1:46 PM, Arnd Bergmann wrote:
> In some randconfig builds, the lack of an explicit #include
> in smack_lsm.c causes a build failure:
What tree/branch are you working with? I don't see this.
>
> security/smack/smack_lsm.c:4384:7: error: incomplete definition of type
> 'struct watch_no
On 9/22/2019 8:16 PM, zhong jiang wrote:
> I hit the following error when compile the kernel.
What tree/branch are you working with? I don't see this.
>
> security/smack/smack_lsm.c: In function smack_post_notification:
> security/smack/smack_lsm.c:4383:7: error: dereferencing pointer to incomple
Dan,
On 9/23/19 5:28 PM, Dan Murphy wrote:
> Jacek
>
> On 9/21/19 10:13 AM, Jacek Anaszewski wrote:
>> Dan,
>>
>> On 9/20/19 7:41 PM, Dan Murphy wrote:
>>> Introduce the bindings for the Texas Instruments LP5036, LP5030, LP5024,
>>> LP5018, LP5012 and LP5009 RGB LED device driver. The
>>> LP5036
On Wed, Sep 18, 2019 at 02:07:51PM +0300, Adrian Hunter wrote:
> On 18/09/19 1:47 PM, Michael K. Johnson wrote:
> > I see that the first four patches made it into Linus's kernel
> > yesterday. Is there any chance of this final patch that actually
> > enables the hardware making it into another pull
On Mon, Sep 23, 2019 at 2:35 PM Linus Torvalds
wrote:
>
> On Mon, Sep 23, 2019 at 1:14 PM Casey Schaufler
> wrote:
> >
> > Thank for the instruction. I think this is correct.
>
> Looks fine, pulled.
Oh, btw, can you get more signatures on your pgp key? I actually care
more about having a key th
Dan,
On 9/23/19 5:14 PM, Dan Murphy wrote:
> Jacek
>
> On 9/21/19 8:30 AM, Jacek Anaszewski wrote:
>> Dan,
>>
>> On 9/20/19 7:41 PM, Dan Murphy wrote:
>>> Introduce a multicolor class that groups colored LEDs
>>> within a LED node.
>>>
>>> The framework allows for dynamically setting individual L
On Mon, Sep 23, 2019 at 1:14 PM Casey Schaufler wrote:
>
> Thank for the instruction. I think this is correct.
Looks fine, pulled.
That said, when I look closer:
> Jia-Ju Bai (1):
> security: smack: Fix possible null-pointer dereferences in
> smack_socket_sock_rcv_skb()
This one seems w
On 2019-09-19 23:10, Greg KH wrote:
On Thu, Sep 19, 2019 at 08:36:51PM -0700, Bjorn Andersson wrote:
On Thu 19 Sep 15:45 PDT 2019, Greg KH wrote:
> On Thu, Sep 19, 2019 at 03:40:17PM -0700, Bjorn Andersson wrote:
> > On Thu 19 Sep 15:25 PDT 2019, Greg KH wrote:
> >
> > > On Thu, Sep 19, 2019 at
On Mon, Sep 16, 2019 at 11:56:45AM +0300, Adrian Hunter wrote:
> Support directory output that contains a regular perf.data file. This is
> preparation for adding support for putting a copy of /proc/kcore in that
> directory.
>
> Distinguish the multiple file case from the regular (single) perf.da
On 23/09/2019 09:58:47-0700, Stephen Boyd wrote:
> Quoting Alexandre Belloni (2019-09-20 08:39:06)
> > It is not allowed to sleep to early in the boot process and this may lead
> > to kernel issues if the bootloader didn't prepare the slow clock and main
> > clock.
> >
> > This results in the foll
Reduces the number of calls to get_current() in order to get the value of
current->mm by doing it once and storing the value, since it is not
supposed to change inside the same process).
Signed-off-by: Leonardo Bras
---
Re-sending to all lists involved. (I missed kvm ones)
arch/powerpc/kvm/book
On 9/6/19 10:06 AM, Alexei Starovoitov wrote:
> On Fri, Sep 6, 2019 at 3:03 AM Yonghong Song wrote:
>>
>>
>>
>> On 9/5/19 2:15 PM, Sami Tolvanen wrote:
>>> Instead of invoking struct bpf_prog::bpf_func directly, use the
>>> BPF_PROG_RUN macro.
>>>
>>> Signed-off-by: Sami Tolvanen
>>
>> Acked-b
"Michael Kerrisk (man-pages)" writes:
> Hello Christian and all,
>
> Below, I have the rendered version of the current draft of
> the pidfd_send_signal(2) manual page that I have written.
> The page source can be found in a Git branch at:
> https://git.kernel.org/pub/scm/docs/man-pages/man-pages.
On Sun, Sep 22, 2019 at 5:04 AM Michael Ellerman wrote:
>
>
>
> On 21 September 2019 4:31:16 am AEST, Dan Williams
> wrote:
> >On Fri, Sep 20, 2019 at 11:18 AM Qian Cai wrote:
> >>
> >> On Fri, 2019-09-20 at 19:55 +0530, Aneesh Kumar K.V wrote:
> >> > Qian Cai writes:
> >> >
> >> > > The linux
On 9/23/19 12:18 PM, Mina Almasry wrote:
> On Mon, Sep 23, 2019 at 10:47 AM Mike Kravetz wrote:
>>
>> On 9/19/19 3:24 PM, Mina Almasry wrote:
>>> Patch series implements hugetlb_cgroup reservation usage and limits, which
>>> track hugetlb reservations rather than hugetlb memory faulted in. Details
On Mon, Sep 23, 2019 at 05:08:38PM -0400, Andrea Arcangeli wrote:
> Hello,
>
> On Mon, Sep 23, 2019 at 01:23:49PM -0700, Sean Christopherson wrote:
> > The attached patch should do the trick.
>
> The two most attractive options to me remains what I already have
> implemented under #ifdef CONFIG_R
Michal,
Thinking about this I have a hunch about what changed. I think at some
point we changed from 4k to 8k kernel stacks. So I suspect if your
client is seeing a lower threads-max it is because the size of the
kernel data structures increased.
Eric
The patch
regulator: da9062: fix suspend_enable/disable preparation
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-5.4
All being well this means that it will be integrated into the linux-next
tree (usually sometime in th
The patch
regulator: fixed: Prevent NULL pointer dereference when !CONFIG_OF
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-5.4
All being well this means that it will be integrated into the linux-next
tree (usually somet
Dan,
On 9/23/19 4:50 PM, Dan Murphy wrote:
> Jacek
>
> Thanks for the review
>
> On 9/21/19 7:28 AM, Jacek Anaszewski wrote:
>> Dan,
>>
>> On 9/20/19 7:41 PM, Dan Murphy wrote:
>>> Add the support documentation on the multicolor LED framework.
>>> This document defines the directores and file ge
On 9/23/19 11:15 AM, Steve Wahl wrote:
> The kernel image map is created using PMD pages, which can include
> some extra space beyond what's actually needed. Round the size of the
> memory hole we search for up to the next PMD boundary, to be certain
> all of the space to be mapped is usable RAM a
101 - 200 of 783 matches
Mail list logo
