On Mon, Oct 15, 2018 at 09:03:40AM -0700, Andy Lutomirski wrote:
> On Mon, Oct 15, 2018 at 8:31 AM Josh Poimboeuf wrote:
> >
> > On Mon, Oct 15, 2018 at 08:22:21AM -0700, Nathan Chancellor wrote:
> > > > >>> @@ -760,9 +760,11 @@ no_context(struct pt_regs *regs, unsigned long
> > > > >>> error_cod
On Mon, Oct 15, 2018 at 3:55 AM, Christian Brauner wrote:
> Currently, when writing
>
> echo 18446744073709551616 > /proc/sys/fs/file-max
>
> /proc/sys/fs/file-max will overflow and be set to 0. That quickly
> crashes the system.
> This commit explicitly caps the value for file-max to ULONG_MAX.
>
Hi Leonard,
> -Original Message-
> From: Leonard Crestez
> Sent: Monday, October 15, 2018 9:28 PM
[...]
> Subject: [PATCH v2 0/4] Port mxs-dcp to imx6ull and imx6sll
>
> The DCP block is present on 6sll and 6ull but not enabled. The hardware is
> mostly compatible with 6sl, the only im
Stefan Wahren writes:
> Hi Tuomas,
>
>> Tuomas Tynkkynen hat am 4. Oktober 2018 um 11:37
>> geschrieben:
>>
>>
>> Drop various pieces of dead code from here and there to get rid of
>> the remaining users of VCHI_CONNECTION_T. After that we get to drop
>> entire header files worth of unused co
On Mon, Oct 15, 2018 at 3:55 AM, Christian Brauner wrote:
> proc_get_long() is a funny function. It uses simple_strtoul() and for a
> good reason. proc_get_long() wants to always succeed the parse and return
> the maybe incorrect value and the trailing characters to check against a
> pre-defined l
On Mon, Oct 15, 2018 at 09:03:40AM -0700, Andy Lutomirski wrote:
> That being said, the generic macro is:
>
> # define unreachable() do { annotate_reachable(); do { } while (1); } while
> (0)
>
> I'm probably missing some subtlety here, but shouldn't that be
> annotate_*un*reachable()?
That cod
On Mon, Oct 15, 2018 at 09:11:51AM -0700, Kees Cook wrote:
> On Mon, Oct 15, 2018 at 3:55 AM, Christian Brauner
> wrote:
> > Currently, when writing
> >
> > echo 18446744073709551616 > /proc/sys/fs/file-max
> >
> > /proc/sys/fs/file-max will overflow and be set to 0. That quickly
> > crashes the
The axg does not require the FW memory region for all we know.
This seems to be something we carried for the gx family for no
reason.
Fixes: 9d59b708500f ("arm64: dts: meson-axg: add initial A113D SoC DT support")
Signed-off-by: Jerome Brunet
---
arch/arm64/boot/dts/amlogic/meson-axg.dtsi | 3 --
On Tue, Sep 25, 2018 at 11:03:06AM +0200, Daniel Lezcano wrote:
> Add the interrupt names for the sensors, so the code can rely on them
> instead of dealing with index which are prone to error.
>
> The name comes from the Hisilicon documentation found on internet.
>
> Signed-off-by: Daniel Lezcan
Since commit 50d7ba36b916 ("arm64: export memblock_reserve()d regions via
/proc/iomem")
was merged Amlogic's boards using mainline u-boot started showing the
following warning:
WARNING: CPU: 0 PID: 1 at arch/arm64/kernel/setup.c:271
reserve_memblock_reserved_regions+0xd8/0x144
Modules linked in:
This patcheset provide updates regarding reserved memory on
Amlogic platforms.
Jerome Brunet (2):
arm64: dts: meson: fix reserve memory regions
arm64: dts: meson-axg: drop FW reserved memory
arch/arm64/boot/dts/amlogic/meson-axg.dtsi | 21 +++--
arch/arm64/boot/dts/amlogic/meson-
On Mon, Oct 15, 2018 at 09:18:40AM -0700, Kees Cook wrote:
> On Mon, Oct 15, 2018 at 3:55 AM, Christian Brauner
> wrote:
> > proc_get_long() is a funny function. It uses simple_strtoul() and for a
> > good reason. proc_get_long() wants to always succeed the parse and return
> > the maybe incorrec
On Tue, Sep 25, 2018 at 11:03:08AM +0200, Daniel Lezcano wrote:
> Add the missing interrupts for the temperature sensors as well as
> their names.
>
> Signed-off-by: Daniel Lezcano
> ---
> Documentation/devicetree/bindings/thermal/hisilicon-thermal.txt | 8 ++--
Combine this and the previous
On Mon, Oct 15, 2018 at 11:33:48PM +0800, Boqun Feng wrote:
> On Mon, Oct 15, 2018 at 05:09:03PM +0200, Sebastian Andrzej Siewior wrote:
> > On 2018-10-15 23:07:15 [+0800], Boqun Feng wrote:
> > > Hi, Sebastian
> > Hi Boqun,
> >
> > > On Mon, Oct 15, 2018 at 04:42:17PM +0200, Sebastian Andrzej Sie
Quoting Charles Keepax (2018-10-15 03:49:05)
> On Fri, Oct 12, 2018 at 08:59:56AM -0700, Stephen Boyd wrote:
> > Quoting Charles Keepax (2018-10-11 06:26:02)
> > > On Thu, Oct 11, 2018 at 12:00:46AM -0700, Stephen Boyd wrote:
> > > > Quoting Charles Keepax (2018-10-08 06:25:40)
> > > > > +struct lo
On Mon, Oct 15, 2018 at 06:28:32PM +0200, Jerome Brunet wrote:
> Since commit 50d7ba36b916 ("arm64: export memblock_reserve()d regions via
> /proc/iomem")
> was merged Amlogic's boards using mainline u-boot started showing the
> following warning:
>
> WARNING: CPU: 0 PID: 1 at arch/arm64/kernel/se
Greetings,
the first test patch to fix the pgtable_bytes mis-accounting on s390
still had a few problems. For one it didn't work for x86 ..
Changes v1 -> v2:
- Split the patch into three parts, one patch to add the mm_pxd_folded
helpers, one patch to use to the helpers in mm_[dec|inc]_nr_[pm
Add three architecture overrideable function to test if the
p4d, pud, or pmd layer of a page table is folded or not.
Signed-off-by: Martin Schwidefsky
---
include/linux/mm.h | 40
1 file changed, 40 insertions(+)
diff --git a/include/linux/mm.h b/include
The common mm code calls mm_dec_nr_pmds() and mm_dec_nr_puds()
in free_pgtables() if the address range spans a full pud or pmd.
If mm_dec_nr_puds/mm_dec_nr_pmds are non-empty due to configuration
settings they blindly subtract the size of the pmd or pud table from
pgtable_bytes even if the pud or p
In case a fork or a clone system fails in copy_process and the error
handling does the mmput() at the bad_fork_cleanup_mm label, the
following warning messages will appear on the console:
BUG: non-zero pgtables_bytes on freeing mm: 16384
The reason for that is the tricks we play with mm_inc_nr_
Quoting Anson Huang (2018-10-15 02:33:35)
> > > > >
> > > >
> > > > Why can't we add clks to the op-tee node in DT's /firmware container?
> > > > Then any clks in there can be turned on forever and left enabled by
> > > > the linux driver?
> > >
> > > I did NOT run op-tee with Linux-next kernel bef
On 10/11/18 7:00 PM, Cyrill Gorcunov wrote:
On Fri, Oct 12, 2018 at 12:30:06AM +0300, Alexey Dobriyan wrote:
On Fri, Oct 12, 2018 at 12:02:56AM +0300, Cyrill Gorcunov wrote:
On Thu, Oct 11, 2018 at 11:56:01PM +0300, Alexey Dobriyan wrote:
As the comment in the beginning says this test is spec
On Mon, Oct 15, 2018 at 09:39:59AM -0700, Stephen Boyd wrote:
> Ok if there's going to be read/volatile regs and defaults then it makes
> sense to leave the defines in some shared header file, which is
> unfortunate for the independent merge of driver bits. Either way, I
Kconfig dependencies take
On Mon, Oct 15, 2018 at 9:03 AM Andy Lutomirski wrote:
>
> On Mon, Oct 15, 2018 at 8:31 AM Josh Poimboeuf wrote:
> >
> > On Mon, Oct 15, 2018 at 08:22:21AM -0700, Nathan Chancellor wrote:
> > > > >>> @@ -760,9 +760,11 @@ no_context(struct pt_regs *regs, unsigned long
> > > > >>> error_code,
> >
Hi Joel,
On 08-10-18, 22:47, Joel Fernandes (Google) wrote:
> Hi Greg,
>
> While looking at android-4.14, I found a NULL pointer deref with
> stm32-dma driver using Coccicheck errors. I found that upstream had a
> bunch of patches on stm32-dma that have fixed this and other issues, I
> applied th
Add device bindings for cpuidle states for cpu devices.
Cc:
Signed-off-by: Raju P.L.S.S.S.N
---
arch/arm64/boot/dts/qcom/sdm845.dtsi | 62
1 file changed, 62 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/sdm845.dtsi
b/arch/arm64/boot/dts/qcom/sdm845.
On 12-10-18, 01:27, Masahiro Yamada wrote:
> On Sun, Oct 7, 2018 at 1:23 AM Vinod wrote:
> > > > > +static int uniphier_mdmac_probe(struct platform_device *pdev)
> > > > > +{
> > > > > + struct device *dev = &pdev->dev;
> > > > > + struct uniphier_mdmac_device *mdev;
> > > > > + struct
Hello,
syzbot found the following crash on:
HEAD commit:bab5c80b2110 Merge tag 'armsoc-fixes-4.19' of git://git.ke..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=138e5f7640
kernel config: https://syzkaller.appspot.com/x/.config?x=88e9a8a39dc0be2d
da
On Sat, 2018-10-13 at 18:08 +0200, Michael Turquette wrote:
> Quoting Christian Hewitt (2018-10-13 12:04:46)
> > On the Khadas VIM2 (GXM) and LePotato (GXL) board there are problems
> > with reboot; e.g. a ~60 second delay between issuing reboot and the
> > board power cycling (and in some OS confi
On 13/09/2018 19:05, Vitaly Kuznetsov wrote:
> It is perfectly valid for a guest to do VMXON and not do VMPTRLD. This
> state needs to be preserved on migration.
>
> Signed-off-by: Vitaly Kuznetsov
Please cover this in state-test.c too.
Paolo
> ---
> arch/x86/kvm/vmx.c | 15 ---
>
On 08-10-18, 22:46, Manivannan Sadhasivam wrote:
> Following warnings are generated when compiled with W=1,
>
> drivers/dma/owl-dma.c:170: warning: Function parameter or member 'cyclic'
> not described in 'owl_dma_txd'
> drivers/dma/owl-dma.c:198: warning: Function parameter or member 'cfg' not
>
From: Nagarathnam Muthusamy
Following commit disables the creation of user namespace inside
the chroot environment.
userns: Don't allow creation if the user is chrooted
commit 3151527ee007b73a0ebd296010f1c0454a919c7d
Consider a system in which a non-root user creates a combination
of user, pid
On 04/10/2018 17:45, Peng Hao wrote:
> From: Peng Hao
>
> Signed-off-by: Peng Hao
> ---
> arch/x86/kvm/mmu.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c
> index d7e9bce..281e20e 100644
> --- a/arch/x86/kvm/mmu.c
> +++ b/a
On 08/10/2018 04:25, Wei Yang wrote:
> On Mon, Oct 08, 2018 at 09:04:34AM +0800, peng.h...@zte.com.cn wrote:
>>> On Sat, Oct 06, 2018 at 11:31:04AM +0800, peng.h...@zte.com.cn wrote:
> On Thu, Oct 04, 2018 at 01:47:18PM -0400, Peng Hao wrote:
>>
>> From: Peng Hao
>>
>> modify
On Mon, Oct 15, 2018 at 2:45 PM, Jan Kara wrote:
> Hi Dmirty!
>
> On Mon 15-10-18 14:29:14, Dmitry Vyukov wrote:
>> On Mon, Oct 15, 2018 at 2:15 PM, Jan Kara wrote:
>> > Hello,
>> >
>> > On Mon 15-10-18 04:32:02, syzbot wrote:
>> >> syzbot found the following crash on:
>> >>
>> >> HEAD commit:
On 09/10/2018 04:51, peng.h...@zte.com.cn wrote:
> ping
> patch ;https://patchwork.kernel.org/patch/10604977/
> test case :https://patchwork.kernel.org/patch/10631781/
I need to understand the double fault I'm seeing before applying this patch.
Paolo
On 10-10-18, 09:02, Pierre Yves MORDRET wrote:
>
>
> On 10/10/2018 06:03 AM, Vinod wrote:
> > On 09-10-18, 10:40, Pierre Yves MORDRET wrote:
> >>
> >>
> >> On 10/07/2018 06:00 PM, Vinod wrote:
> >>> On 28-09-18, 15:01, Pierre-Yves MORDRET wrote:
> This patch adds support of DMA/MDMA chaining
On 10/7/18 6:04 PM, peng.h...@zte.com.cn wrote:
\>
> #define AVIC_LOGICAL_ID_ENTRY_GUEST_PHYSICAL_ID_MASK(0xFF)
> -#define AVIC_LOGICAL_ID_ENTRY_VALID_MASK(1 << 31)
> +#define AVIC_LOGICAL_ID_ENTRY_VALID_MASK(1UL << 31)
>>>
It is reasonable to change to unsi
Steven Peter Walker(Esq)
Stone Chambers, 4 Field Court,
Gray's Inn, London,
WC1R 5EF..
Email: stevenwalkerchamb...@workmail.co.za
Greetings To You,
This is a personal email directed to you and I request that it be
treated as such. I am Steven Walker, a personal attorney/sole
executor to the lat
On Tue, 16 Oct 2018 00:09:43 +0800 (CST)
wrote:
> >We only do the check if the immediate double_lock_balance() released
> >the current task rq lock, but we don't take into account if it was
> >released earlier, which means it could have migrated and we never
> >noticed!
> >
> double_lock_balanc
On Mon, Oct 15, 2018 at 01:55:14PM -0300, Rafael David Tinoco wrote:
> That is what I also had in mind, thus the patch. I just realized we had
> another issue on LKFT (our functional tests tool) for
> proc-self-map-files-001.c. Test 001 does pretty much the same as 002, but
> without the MAP_FIXED
On 14/10/2018 01:09, Peng Hao wrote:
> Coalesced pio is based on coalesced mmio and can be used for some port
> like rtc port, pci-host config port and so on.
>
> Specially in case of rtc as coalesced pio, some versions of windows guest
> access rtc frequently because of rtc as system tick. guest
Fixes the objtool warning seen with Clang:
arch/x86/mm/fault.o: warning: objtool: no_context()+0x220: unreachable
instruction
Fixes commit 815f0ddb346c ("include/linux/compiler*.h: make compiler-*.h
mutually exclusive")
Josh noted that the fallback definition was meant to work around a
pre-gcc-4.
On Mon, Oct 15, 2018 at 7:10 PM wrote:
> Following commit disables the creation of user namespace inside
> the chroot environment.
>
> userns: Don't allow creation if the user is chrooted
>
> commit 3151527ee007b73a0ebd296010f1c0454a919c7d
>
> Consider a system in which a non-root user creates a c
On 15/10/2018 19:16, H. Peter Anvin wrote:
> On 10/7/18 6:04 PM, peng.h...@zte.com.cn wrote:
> \>
>> #define AVIC_LOGICAL_ID_ENTRY_GUEST_PHYSICAL_ID_MASK(0xFF)
>> -#define AVIC_LOGICAL_ID_ENTRY_VALID_MASK(1 << 31)
>> +#define AVIC_LOGICAL_ID_ENTRY_VALID_MASK(1UL
On Mon, Oct 15, 2018 at 9:57 AM Nick Desaulniers
wrote:
> I broke this myself in commit 815f0ddb346c
> ("include/linux/compiler*.h: make compiler-*.h mutually exclusive").
> Thanks for the suggestion, will verify then send a patch with your
> suggested by tag. Thanks everyone for helping us sort
Vivek,
On Mon, Oct 15, 2018 at 8:23 AM Vivek Gautam
wrote:
>
> Hi Doug,
>
> On Sat, Oct 13, 2018 at 3:09 AM Douglas Anderson
> wrote:
> >
> > If you look at the bindings for the UFS Host Controller it says:
> >
> > - compatible: must contain "jedec,ufs-1.1" or "jedec,ufs-2.0", may
> >
On Mon, Oct 15, 2018 at 10:22 AM Jann Horn wrote:
>
> On Mon, Oct 15, 2018 at 7:10 PM wrote:
> > Following commit disables the creation of user namespace inside
> > the chroot environment.
> >
> > userns: Don't allow creation if the user is chrooted
> >
> > commit 3151527ee007b73a0ebd296010f1c045
Hi,
On 15.10.2018 11:34, Peter Zijlstra wrote:
> On Mon, Oct 15, 2018 at 10:26:06AM +0300, Alexey Budankov wrote:
>> Hi,
>>
>> On 10.10.2018 13:45, Peter Zijlstra wrote:
>>> Hi all,
>>>
>>> There have been various issues and limitations with the way perf uses
>>> (task) contexts to track events.
Hello,
Business proposition for you.
I have a client from Syrian who will like to invest with your
company. My client is willing to invest $4 Million. Can I have
your company website to show to my client your company so that
they will check and decide if they will invest there funds with
you
On 10/15/18 10:23 AM, Paolo Bonzini wrote:
>
> Even for a value from a 32-bit register? That would be _BIT, which
> doesn't exist.
>
Just use _BITUL(). gcc is smart enough to know that that the resulting value
is representable in 32 bits.
Or if you really care, submit a patch to create _BITU()
On Sun, Oct 14, 2018 at 07:29:42PM -0700, Joel Fernandes (Google) wrote:
> The code listing under this section has a quick quiz that says line 19
> uses rcu_access_pointer, but the code listing itself does not. Fix this.
>
> Signed-off-by: Joel Fernandes (Google)
Good eyes! Queued for the merge
On Thu, 11 Oct 2018 05:18:20 PDT (-0700), sba...@raithlin.com wrote:
Palmer
I don't really know anything about this, but you're welcome to add a
Reviewed-by: Palmer Dabbelt
Thanks. I think it would be good to get someone who's familiar with linux/mm to
take a look.
if you think
Have you considered using pivot_root to drop all of the pieces of the
filesystem you don't want to be visible? That should be a much better
solution overall.
It is must a matter of:
mount --bind /path/you/would/chroot/to
pivot_root /path/you/would/chroot/to /put/old
umount -l /put/old
You migh
Cleanup the arm64_memory_present() function seeing it's very
similar to other arches.
memblocks_present() is a direct replacement of arm64_memory_present()
Signed-off-by: Logan Gunthorpe
Acked-by: Catalin Marinas
Cc: Will Deacon
---
arch/arm64/mm/init.c | 20 +---
1 file chang
This patchset implements sparsemem on RISC-V. The first few patches
move some code in existing architectures into common helpers
so they can be used by the new RISC-V implementation. The final
patch actually adds sparsmem support to RISC-V.
This is the first small step in supporting P2P on RISC-V.
Cleanup the arm_memory_present() function seeing it's very
similar to other arches.
The new memblocks_present() helper checks for node ids which the
arm version did not. However, this is equivalent seeing
HAVE_MEMBLOCK_NODE_MAP should be false in this arch and therefore
memblock_get_region_node()
Cleanup the open coded for_each_memblock() loop that is equivalent
to the new memblocks_present() helper.
Signed-off-by: Logan Gunthorpe
Cc: Yoshinori Sato
Cc: Rich Felker
Cc: Dan Williams
Cc: Rob Herring
---
arch/sh/mm/init.c | 7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
diff
Presently the arches arm64, arm and sh have a function which loops through
each memblock and calls memory present. riscv will require a similar
function.
Introduce a common memblocks_present() function that can be used by
all the arches. Subsequent patches will cleanup the arches that
make use of
This define is used by arm64 to calculate the size of the vmemmap
region. It is defined as the log2 of the upper bound on the size
of a struct page.
We move it into mm_types.h so it can be defined properly instead of
set and checked with a build bug. This also allows us to use the same
define for
From: Eric Biggers
In preparation for adding XChaCha12 support, rename/refactor the NEON
implementation of ChaCha20 to support different numbers of rounds.
Signed-off-by: Eric Biggers
---
arch/arm/crypto/Makefile | 4 +-
...hacha20-neon-core.S => chacha-neon-core.S} | 36
This patch implements sparsemem support for risc-v which helps pave the
way for memory hotplug and eventually P2P support.
We introduce Kconfig options for virtual and physical address bits which
are used to calculate the size of the vmemmap and set the
MAX_PHYSMEM_BITS.
The vmemmap is located di
Hi Rob,
thanks for the review.
On 15/10/2018 18:28, Rob Herring wrote:
> On Tue, Sep 25, 2018 at 11:03:06AM +0200, Daniel Lezcano wrote:
>> Add the interrupt names for the sensors, so the code can rely on them
>> instead of dealing with index which are prone to error.
>>
>> The name comes from
On 15/10/2018 18:31, Rob Herring wrote:
> On Tue, Sep 25, 2018 at 11:03:08AM +0200, Daniel Lezcano wrote:
>> Add the missing interrupts for the temperature sensors as well as
>> their names.
>>
>> Signed-off-by: Daniel Lezcano
>> ---
>> Documentation/devicetree/bindings/thermal/hisilicon-thermal.
Hi Marcel,
please let me know if any changes are needed to get this patch applied
to bluetooth-next.
Thanks
Matthias
On Thu, Oct 04, 2018 at 10:33:38AM -0700, Matthias Kaehlcke wrote:
> On Thu, Sep 27, 2018 at 10:13:05AM -0700, Matthias Kaehlcke wrote:
> > On Thu, Sep 27, 2018 at 12:47:06PM -04
Hi Matthias,
void bt_sock_reclassify_lock(struct sock *sk, int proto);
+int device_get_bd_address(struct device *dev, bdaddr_t *bd_addr);
>>>
>>> Maybe change the API name to start with bt_ and get rid of device_?
>>
>> device_ indicates that we get the BD_ADDR for a 'struct dev
On 10/15/2018 10:42 AM, ebied...@xmission.com wrote:
Have you considered using pivot_root to drop all of the pieces of the
filesystem you don't want to be visible? That should be a much better
solution overall.
It is must a matter of:
mount --bind /path/you/would/chroot/to
pivot_root /path/y
Jann Horn writes:
> On Mon, Oct 15, 2018 at 7:10 PM wrote:
>> @@ -1281,7 +1285,7 @@ static int userns_install(struct nsproxy *nsproxy,
>> struct ns_common *ns)
>> return -ENOMEM;
>>
>> put_user_ns(cred->user_ns);
>> - set_cred_user_ns(cred, get_user_ns(user_ns));
>
On Mon, Oct 15, 2018 at 03:22:42PM +0200, Dmitry Vyukov wrote:
> Now that you mention EXT4_IOC_SWAP_BOOT, I think I looked at the wrong
> program, there is a subsequent one that does ioctl(0x6611) where
> 0x6611 is in fact EXT4_IOC_SWAP_BOOT. So I think it's this one:
>
> 05:23:28 executing progra
On 10/15/18 01:24, Geert Uytterhoeven wrote:
> Hi Frank,
>
> On Mon, Oct 15, 2018 at 3:36 AM wrote:
>> From: Frank Rowand
>>
>> When an overlay is applied or removed, the live devicetree visible in
>> /proc/device-tree/, aka /sys/firmware/devicetree/base/, reflects the
>> changes. There is no m
Hi, Greg:
> Shouldn't there also be a manpage update, and a kselftest added for this
> new user/kernel api that is being created?
>
I will submit a patch for manpage update once the code is accepted.
Regarding the kselftest, I am not sure. Once the prctl() is limited to
self (which I will do),
On Sat, Oct 13, 2018 at 10:06:18AM -0700, Randy Dunlap wrote:
> From: Randy Dunlap
>
> Loading then unloading wm97xx-ts.ko when CONFIG_AC97_BUS=m
> causes a WARNING: from drivers/base/driver.c:
>
> Unexpected driver unregister!
> WARNING: CPU: 0 PID: 1709 at ../drivers/base/driver.c:193
> drive
On Mon, Oct 08, 2018 at 07:03:55PM +0200, Gustavo A. R. Silva wrote:
> In preparation to enabling -Wimplicit-fallthrough, mark switch cases
> where we are expecting to fall through.
>
> Signed-off-by: Gustavo A. R. Silva
Applied, thank you.
> ---
> drivers/input/touchscreen/atmel_mxt_ts.c | 2
On Mon, Oct 15, 2018 at 7:22 PM wrote:
>
> Fixes the objtool warning seen with Clang:
> arch/x86/mm/fault.o: warning: objtool: no_context()+0x220: unreachable
> instruction
>
> Fixes commit 815f0ddb346c ("include/linux/compiler*.h: make compiler-*.h
> mutually exclusive")
>
> Josh noted that the f
On Mon, Oct 08, 2018 at 05:38:24PM +0200, Gustavo A. R. Silva wrote:
> In preparation to enabling -Wimplicit-fallthrough, mark switch cases
> where we are expecting to fall through.
>
> Notice that in this particular case, I replaced the "Fallthrough state"
> commern with a proper "Fall through",
I'll try to bisect later.
ALl ppc qemu tests (including big endian pseries) also generate a warning.
WARNING: CPU: 0 PID: 0 at mm/memblock.c:1301 .memblock_alloc_range_nid+0x20/0x68
Modules linked in:
CPU: 0 PID: 0 Comm: swapper Not tainted 4.19.0-rc7-next-20181015 #1
NIP: c0f99198 L
On Sat, Oct 13, 2018 at 03:44:45PM -0700, Guenter Roeck wrote:
> On Fri, Oct 12, 2018 at 9:04 AM Ross Zwisler wrote:
>
> > This series contains some Google specific firmware patches that we've
> > been carrying out of tree. I've updated the changelog for each so that
> > it is suitable for upstr
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger
crash:
Reported-and-tested-by:
syzbot+24a30223a4b609bb8...@syzkaller.appspotmail.com
Tested on:
commit: f0a7d1883d9f afs: Fix clearance of reply
git tree: upstream
kernel config: https://syzkall
Hi,
On Mon, Oct 15, 2018 at 10:29 AM Alexey Budankov
wrote:
>
>
> Hi,
> On 15.10.2018 11:34, Peter Zijlstra wrote:
> > On Mon, Oct 15, 2018 at 10:26:06AM +0300, Alexey Budankov wrote:
> >> Hi,
> >>
> >> On 10.10.2018 13:45, Peter Zijlstra wrote:
> >>> Hi all,
> >>>
> >>> There have been various i
On Wed, Oct 03, 2018 at 06:52:36PM +0100, Srinivas Kandagatla wrote:
> From: Niklas Cassel
>
> QCOM_QMI_HELPERS is a hidden kconfig, so the proper usage is
> to select it, not depend upon it.
>
> Signed-off-by: Niklas Cassel
> Reviewed-by: Alex Elder
> Reviewed-by: Bjorn Andersson
> Signed-of
On Fri, 2018-10-12 at 10:23 +0100, Phil Elwell wrote:
> The SPI configuration state includes an SPI_NO_CS flag that disables
> all CS line manipulation, for applications that want to manage their
> own chip selects. However, this flag is ignored by the GPIO CS code
> in the SPI framework.
> @@ -72
On Mon, Oct 15, 2018 at 10:42:23AM +0800, Honghui Zhang wrote:
> On Fri, 2018-10-12 at 09:12 -0500, Bjorn Helgaas wrote:
> > On Fri, Oct 12, 2018 at 11:22:30AM +0100, Lorenzo Pieralisi wrote:
> > > On Fri, Oct 12, 2018 at 04:01:29PM +0800, Honghui Zhang wrote:
> > >> On Thu, 2018-10-11 at 12:38 +01
On Wed, Oct 03, 2018 at 10:17:11AM -0700, r...@google.com wrote:
> From: Roman Kiryanov
>
> There will be two separate init functions for v1 and v2
> (different driver versions) and they will allocate different
> state.
You should only allocate memory at probe time, not init time as what
happens
On Thu, Sep 27, 2018 at 07:03:47PM +0200, Krzysztof Kozlowski wrote:
> Replace GPL license statements with SPDX license identifiers (GPL-2.0).
>
> Signed-off-by: Krzysztof Kozlowski
> Acked-by: Chanwoo Choi
> Reviewed-by: Rob Herring
> ---
> include/dt-bindings/clock/exynos3250.h | 5 +
On Thu, Sep 27, 2018 at 07:04:40PM +0200, Krzysztof Kozlowski wrote:
> Replace GPL license statement with SPDX license identifier (GPL-2.0+).
>
> Signed-off-by: Krzysztof Kozlowski
>
> ---
>
> We postponed this patch because in previous discussion [1] Bartlomiej
> expressed willingness to chang
On Wed, Oct 03, 2018 at 10:17:12AM -0700, r...@google.com wrote:
> From: Roman Kiryanov
>
> This way deinit will have a chance to report an error.
>
> Signed-off-by: Roman Kiryanov
> ---
> Changes in v3:
> - No change.
> Changes in v2:
> - No change.
>
> drivers/platform/goldfish/goldfish_p
On Mon, Oct 15, 2018 at 04:08:53PM +0800, honghui.zh...@mediatek.com wrote:
> From: Honghui Zhang
>
> The commit 101c92dc80c8 ("PCI: mediatek: Set up vendor ID and class
> type for MT7622") have set the class type for MT7622 as un-properly
> value of PCI_CLASS_BRIDGE_HOST.
>
> The PCIe controlle
On Wed, Oct 03, 2018 at 10:17:14AM -0700, r...@google.com wrote:
> From: Roman Kiryanov
>
> This is the v2 driver. v1 will be added later.
This does not make any sense. Why are you renaming a driver that has
been in the tree already? It's not "v2", it is what we have today.
If you want to add
There were mismatches between number of vmstat keys and number of
vmstat values. They were fixed recently by:
commit 58bc4c34d249 ("mm/vmstat.c: skip NR_TLB_REMOTE_FLUSH* properly")
commit 28e2c4bb99aa ("mm/vmstat.c: fix outdated vmstat_text")
Add a BUILD_BUG_ON to detect such mismatch and hop
Hi, Christian:
As I replied to Jann, I will remove the code that does the setting on others
to make the code simpler and more secure.
Thanks. -- Enke
>> +static bool set_predump_signal_perm(struct task_struct *p)
>> +{
>> +const struct cred *cred = current_cred(), *pcred = __task_cred(p);
>
qcs404 has 10 sensors connected to the single TSENS IP. Define a thermal
zone for each of those sensors to expose the temperature of each zone.
Signed-off-by: Amit Kucheria
---
arch/arm64/boot/dts/qcom/qcs404.dtsi | 206 +++
1 file changed, 206 insertions(+)
diff --git a
qcs404 uses v1 of the TSENS IP block. Create a fallback DT property
"qcom,tsens-v1" to gather common code.
Signed-off-by: Amit Kucheria
---
Documentation/devicetree/bindings/thermal/qcom-tsens.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings/thermal/qc
qcs404 has a single TSENS IP block with 10 sensors. It uses version 1.4
of the TSENS IP, functionality for which is encapsulated inside
qcom,tsens-v1 compatible.
Signed-off-by: Amit Kucheria
---
drivers/thermal/qcom/Makefile | 2 +-
drivers/thermal/qcom/tsens-v1.c | 196 +
Add support for the Qualcomm QCS404 platform that contains v1 of the TSENS
IP. Introduce a fallback binding to handle "v1" functionality.
These patches apply on top of previous tsens-related patches sent to the
list pending merge along with various qcs404 patches under review
(available in this br
qcs404 has a single TSENS IP block with 10 sensors. The calibration data
is stored in an eeprom (qfprom) that is accessed through the nvmem
framework. We add the qfprom node to allow the tsens sensors to be
calibrated correctly.
Signed-off-by: Amit Kucheria
---
arch/arm64/boot/dts/qcom/qcs404.dt
On Mon, Oct 15, 2018 at 8:38 PM Yu Zhao wrote:
> There were mismatches between number of vmstat keys and number of
> vmstat values. They were fixed recently by:
> commit 58bc4c34d249 ("mm/vmstat.c: skip NR_TLB_REMOTE_FLUSH* properly")
> commit 28e2c4bb99aa ("mm/vmstat.c: fix outdated vmstat_te
On Wed, Oct 10, 2018 at 2:14 PM Laurence Rochfort
wrote:
>
> Remove the coherent buffer __iomem cookie because the buffer is
> allocated from dma_alloc_coherent().
>
> warning: incorrect type in assignment (different address spaces)
>expected unsigned char [noderef] [usertype] *virt_base
>
On Mon, Oct 15, 2018 at 11:16:36AM -0700, Enke Chen wrote:
> Hi, Greg:
>
> > Shouldn't there also be a manpage update, and a kselftest added for this
> > new user/kernel api that is being created?
> >
>
> I will submit a patch for manpage update once the code is accepted.
Writing a manpage upda
On Mon, Oct 15, 2018 at 08:41:52PM +0200, Jann Horn wrote:
> On Mon, Oct 15, 2018 at 8:38 PM Yu Zhao wrote:
> > There were mismatches between number of vmstat keys and number of
> > vmstat values. They were fixed recently by:
> > commit 58bc4c34d249 ("mm/vmstat.c: skip NR_TLB_REMOTE_FLUSH* prope
Hi, Jann:
Thanks a lot for you detailed review. Please see my replied/comments inline.
On 10/13/18 11:27 AM, Jann Horn wrote:
> On Sat, Oct 13, 2018 at 2:33 AM Enke Chen wrote:
>> For simplicity and consistency, this patch provides an implementation
>> for signal-based fault notification prior t
1 - 100 of 876 matches
Mail list logo
