Hi all,
Today's linux-next merge of the akpm-current tree got a conflict in:
drivers/ntb/hw/mscc/ntb_hw_switchtec.c
between commit:
cfdfc14e7fb8 ("switchtec: Use generic PCI Vendor ID and Class Code")
from the pci tree and commit:
a2a35435484e ("ntb: ntb_hw_switchtec: cleanup 64bit IO d
In p9_client_getattr_dotl(), we should add '\n' at the end of printing
log.
Signed-off-by: Jun Piao
---
net/9p/client.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/9p/client.c b/net/9p/client.c
index 5c13431..8bc8b3e 100644
--- a/net/9p/client.c
+++ b/net/9p/client.c
Dave Hansen writes:
>> +#ifdef CONFIG_THP_SWAP
>> +static inline int cluster_swapcount(struct swap_cluster_info *ci)
>> +{
>> +if (!ci || !cluster_is_huge(ci))
>> +return 0;
>> +
>> +return cluster_count(ci) - SWAPFILE_CLUSTER;
>> +}
>> +#else
>> +#define cluster_swapcount(ci)
Add an interface function to set up the rtc for a power_off
mode.
Signed-off-by: Keerthy
---
Alexandre,
If you feel power_off_program will be very use case specific then
I can name this as custom_rtc_program so that even other rtc
drivers if need be can use this for a custom programming.
- Kee
v3 contains the following suggestions by Neal Cardwell:
1) Fix up units mismatch regarding msec/jiffies.
2) Address possiblility of time_remaining being negative.
3) Add a helper routine tcp_clamp_rto_to_user_timeout() to do the rto
calculation.
4) Move start_ts logic into helper routine tcp_retr
Prepare rtc driver for rtc-only with DDR in self-refresh mode.
omap_rtc_power_off now should cater to two features:
1) RTC plus DDR in self-refresh is power a saving mode where in the
entire system including the different voltage rails from PMIC are
shutdown except the ones feeding on to RTC and D
Use of_device_is_system_power_controller instead of manually reading
the system-power-controller property from the device tree node.
Signed-off-by: Keerthy
---
drivers/rtc/rtc-omap.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/rtc/rtc-omap.c b/drivers/rtc/rtc-om
Prepare rtc driver for rtc-only with DDR in self-refresh mode.
The patch series is based on top of Johan Hovald's series:
https://lkml.kernel.org/r/20180704090558.16647-1-jo...@kernel.org
Tested for suspend/resume and poweroff on am437x-gp-evm.
Keerthy (4):
rtc: omap: Cut down the shutdown tim
On 9 July 2018 at 21:41, Mimi Zohar wrote:
> On Mon, 2018-07-02 at 17:30 +0200, Ard Biesheuvel wrote:
>> On 2 July 2018 at 16:38, Mimi Zohar wrote:
>> > Some systems are memory constrained but they need to load very large
>> > firmwares. The firmware subsystem allows drivers to request this
>> >
Cut down the shutdown time from 2 seconds to 1 sec. In case of roll
over try again.
Signed-off-by: Keerthy
---
drivers/rtc/rtc-omap.c | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/drivers/rtc/rtc-omap.c b/drivers/rtc/rtc-omap.c
index 323ff55..14f2241 100644
--- a/d
Hi all,
After merging the printk tree, today's linux-next build (x86_64
allnoconfig) produced this warning:
kernel/printk/printk.c:2033:13: warning: 'suppress_message_printing' defined
but not used [-Wunused-function]
static bool suppress_message_printing(int level) { return false; }
Dave Hansen writes:
>> +static inline bool thp_swap_supported(void)
>> +{
>> +return IS_ENABLED(CONFIG_THP_SWAP);
>> +}
>
> This seems like rather useless abstraction. Why do we need it?
I just want to make it shorter, 19 vs 27 characters. But if you think
IS_ENABLED(CONFIG_THP_SWAP) is mu
On Tue, 2018-07-10 at 13:09 +0800, Ryder Lee wrote:
> Cleanup binding document to get rid of unsupported reference boards
> for MT7623N.
>
> Cc: John Crispin
> Cc: Sean Wang
> Signed-off-by: Ryder Lee
> ---
> Documentation/devicetree/bindings/arm/mediatek.txt | 3 ---
> 1 file changed, 3 delet
On Tue, 2018-07-10 at 13:09 +0800, Ryder Lee wrote:
> Normally, we didn't release this kind of baord to user. This specific
> board exists only in the early stage of development inside MediaTek -
> and that may confuse peoples.
>
> Hence this patch removes related files accordingly.
>
Acked-by:
On Mon, Jul 09, 2018 at 01:08:08PM -0700, Sujeev Dias wrote:
> +void mhi_driver_unregister(struct mhi_driver *mhi_drv)
> +{
> + driver_unregister(&mhi_drv->driver);
> +}
> +EXPORT_SYMBOL(mhi_driver_unregister);
As you are just "wrapping" a core symbol here, please use
EXPORT_SYMBOL_GPL(). Act
On Fri, Jul 6, 2018 at 6:01 PM Rafael J. Wysocki wrote:
>
> From: Rafael J. Wysocki
>
> The devices_kset_move_last() call in really_probe() is a mistake
> as it may cause parents to follow children in the devices_kset list
> which then causes system shutdown to fail. Namely, if a device has
> ch
On Mon, Jul 09, 2018 at 01:08:10PM -0700, Sujeev Dias wrote:
> +static void mhi_add_ring_element(struct mhi_controller *mhi_cntrl,
> + struct mhi_ring *ring)
> +{
> + ring->wp += ring->el_size;
> + if (ring->wp >= (ring->base + ring->len))
> + ring->
+Mark, Liam
Hi,
On Tuesday 10 July 2018 03:36 AM, Bjorn Helgaas wrote:
> [+cc Kishon]
>
> On Mon, Jul 9, 2018 at 4:35 PM Rafael J. Wysocki wrote:
>>
>> On Mon, Jul 9, 2018 at 3:57 PM, Bjorn Helgaas wrote:
>>> On Fri, Jul 6, 2018 at 5:01 AM Rafael J. Wysocki wrote:
From: Rafael J. Wy
* Keerthy [180709 00:36]:
> From: Dave Gerlach
>
> Add an argument to the sleep33xx and sleep43xx code to allow us to set
> flags to determine which portions of the code get called in order to use
> the same code for multiple power saving modes. This patch allows us to
> decide whether or not we
Mathieu Desnoyers writes:
> - On Jul 8, 2018, at 5:03 PM, Mathieu Desnoyers
> mathieu.desnoy...@efficios.com wrote:
>
>> In preparation to use __u64 for the rseq_cs pointer field, 32-bit
>> architectures need to read this 64-bit value located in user-space
>> addresses.
>>
>> __get_user is u
As we augmented the regulator core to accept a GPIO descriptor instead
of a GPIO number, we can augment the fixed GPIO regulator to look up
and pass that descriptor directly from device tree or board GPIO
descriptor look up tables.
Some boards just auto-enumerate their fixed regulator platform dev
>From 2642b4a1904259384f2018ea8df03ac49509c57a Mon Sep 17 00:00:00 2001
From: Tetsuo Handa
Date: Tue, 10 Jul 2018 15:01:20 +0900
Subject: [PATCH] locking/rwsem: Convert the other sem->count to 'atomic_long_t'
Since "locking/rwsem: Convert sem->count to 'atomic_long_t'" forgot to
convert "struct r
On Mon, Jul 09, 2018 at 02:29:28PM -0700, Andrew Morton wrote:
> On Mon, 9 Jul 2018 13:53:09 -0400 Pavel Tatashin
> wrote:
>
> > In sparse_init() we allocate two large buffers to temporary hold usemap and
> > memmap for the whole machine. However, we can avoid doing that if we
> > changed spars
On 10/07/18 07:09, Ryder Lee wrote:
Cleanup binding document to get rid of unsupported reference boards
for MT7623N.
Cc: John Crispin
Cc: Sean Wang
Signed-off-by: Ryder Lee
Acked-by: John Crispin
---
Documentation/devicetree/bindings/arm/mediatek.txt | 3 ---
1 file changed, 3 deleti
On 10/07/18 07:09, Ryder Lee wrote:
Normally, we didn't release this kind of baord to user. This specific
board exists only in the early stage of development inside MediaTek -
and that may confuse peoples.
Hence this patch removes related files accordingly.
Cc: John Crispin
Cc: Sean Wang
S
> + dev freq maintainters.
>
> On Mon, Jul 9, 2018 at 3:37 AM, noman pouigt wrote:
> > folks,
> >
> > I am trying to figure out the relationship between PM QOS
> > with devfreq framework. I see this thread[1] where MyungJoo
> > talks about QOS and devfreq but that control is through
> > sysfs but
* Keerthy [180621 01:18]:
> Deep enough power saving mode can result into losing context of the clock
> registers also, and they need to be restored once coming back from the power
> saving mode. Hence add functions to save/restore clock context.
Patches 1 to 3 look good to me:
Acked-by: Tony Li
Hey Peter,
Sorry for late response on this..
On 01-06-18, 13:24, Peter Ujfalusi wrote:
> If the DMA supports per descriptor metadata it can implement the attach,
> get_ptr/set_len callbacks.
>
> Client drivers must only use either attach or get_ptr/set_len to avoid
> miss configuration.
>
> W
* Faiz Abbas [180709 16:50]:
> Add clkctrl data for the m_can clocks and register it within the
> clkctrl driver
I'll apply patches 2 to 5 to omap-for-v4.19/ti-sysc. The clock
patch is trivial enough to not have to wait for Tero to be back
online.
And I'll apply the dts changes into omap-for-v4.
Hi Prakash,
On 07/09/2018 10:12 PM, Prakash, Prashanth wrote:
Hi George,
On 7/9/2018 4:10 AM, George Cherian wrote:
Per Section 8.4.7.1.3 of ACPI 6.2, The platform provides performance
feedback via set of performance counters. To determine the actual
performance level delivered over time, O
On Mon, Jul 09, 2018 at 04:51:08PM +0300, Jan Dakinevich wrote:
> An array of pointers to SRPT contexts in ib_device is over 30KiB even
> in default case, in which an amount of contexts is 4095. The patch
> is intended to weed out large contigous allocation for non-DMA memory.
kvmalloc* doesn't "w
On Mon, 9 Jul 2018 17:13:56 -0700
Andrew Morton wrote:
> On Sun, 8 Jul 2018 01:25:38 +1000 Nicholas Piggin wrote:
>
> > On Fri, 06 Jul 2018 13:03:55 -0400
> > Rik van Riel wrote:
> >
> > > Hello,
> > >
> > > It looks like last summer, there were 2 sets of patches
> > > in flight to fix the
Hi, SeongJae
Do you have any input for this regression? thanks
On 2018年06月04日 13:52, kernel test robot wrote:
>
> Greeting,
>
> FYI, we noticed a -11.2% regression of aim7.jobs-per-min due to commit:
>
>
> commit: 316ba5736c9caa5dbcd84085989862d2df57431d ("brd: Mark as
> non-rotational")
>
* Josh Poimboeuf wrote:
> Since we switched the x86_64 default to the ORC unwinder, a lot of
> people have switched over. But this patch will reverse (or at least
> slow down) that trend, because almost nobody has the libelf devel
> packaged installed by default. So over time, it will effecti
Dave Hansen writes:
> On 07/09/2018 06:19 PM, Huang, Ying wrote:
>> Dave Hansen writes:
>>
config THP_SWAP
def_bool y
- depends on TRANSPARENT_HUGEPAGE && ARCH_WANTS_THP_SWAP
+ depends on TRANSPARENT_HUGEPAGE && ARCH_WANTS_THP_SWAP && SWAP
help
>>>
>>> This see
> On 9 July 2018 at 08:47, Hongjie Fang wrote:
> > mmc_select_hs400es() calls mmc_select_bus_width() which will try to
> > set 4bit transfer mode if fail to set 8bit mode. The problem is that
> > the bus width should not be set to 4bit in HS400es mode.
>
> I guess it fails because there is someth
Normally, we didn't release this kind of baord to user. This specific
board exists only in the early stage of development inside MediaTek -
and that may confuse peoples.
Hence this patch removes related files accordingly.
Cc: John Crispin
Cc: Sean Wang
Signed-off-by: Ryder Lee
---
arch/arm/bo
On Tue, Jul 10, 2018 at 11:17:40AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the rdma tree got a conflict in:
>
> drivers/infiniband/core/uverbs_cmd.c
>
> between commit:
>
> 4fae7f170416 ("RDMA/uverbs: Fix slab-out-of-bounds in
> ib_uverbs_ex_create_flow")
>
> f
Cleanup binding document to get rid of unsupported reference boards
for MT7623N.
Cc: John Crispin
Cc: Sean Wang
Signed-off-by: Ryder Lee
---
Documentation/devicetree/bindings/arm/mediatek.txt | 3 ---
1 file changed, 3 deletions(-)
diff --git a/Documentation/devicetree/bindings/arm/mediatek.t
On Sun, Jul 08, 2018 at 10:44:00PM +0200, Christoph Hellwig wrote:
> On Wed, Jul 04, 2018 at 04:21:16PM +0200, Adrian Reber wrote:
> > In file included from /usr/include/linux/signal.h:5,
> > from /usr/include/linux/aio_abi.h:32,
> > from include.c:2:
> > /usr/incl
Hi Davidlohr,
On 07/09/2018 10:09 PM, Davidlohr Bueso wrote:
On Mon, 09 Jul 2018, Manfred Spraul wrote:
@Davidlohr:
Please double check that I have taken the correct patches, and
that I didn't break anything.
Everything seems ok.
Patch 8 had an alternative patch that didn't change nowarn se
Hi, Paul and Peter,
I think we find the real root cause, READ_ONCE() doesn't need any
barriers, the problematic code is queued_spin_lock_slowpath() in
kernel/locking/qspinlock.c:
if (old & _Q_TAIL_MASK) {
prev = decode_tail(old);
/* Link @node into the wai
On Tue, Jul 10, 2018 at 12:47:49PM +0900, Masahiro Yamada wrote:
> Hi.
>
>
> 2018-07-10 11:29 GMT+09:00 Josh Poimboeuf :
> > On Tue, Jul 10, 2018 at 10:35:16AM +0900, Masahiro Yamada wrote:
> >> Currently, users are allowed to enable STACK_VALIDATION regardless
> >> of the compiler capability. T
On Tue, Jul 10, 2018 at 02:05:12PM +1000, Stephen Rothwell wrote:
> Hi Jason,
>
> On Mon, 9 Jul 2018 21:41:57 -0600 Jason Gunthorpe wrote:
> >
> > What compiler is producing these? I got nothing from 0-day build
> > service or my local gcc-7..
>
> The x86 compiler is a v7.3.1 cross compiler hos
Hi Jason,
On Mon, 9 Jul 2018 21:41:57 -0600 Jason Gunthorpe wrote:
>
> What compiler is producing these? I got nothing from 0-day build
> service or my local gcc-7..
The x86 compiler is a v7.3.1 cross compiler hosted on PowerPC LE and
built from sources.
> They are false positives and I guess
On 07/09/2018 07:14 PM, H.J. Lu wrote:
>> I'd really want to see this reproduced without KASLR to make the oops
>> easier to read. It would also be handy to try your workload with all
>> the pedantic debugging: KASAN, slab debugging, DEBUG_PAGE_ALLOC, etc...
>> and see if it still triggers.
> How
Hi.
2018-07-10 11:29 GMT+09:00 Josh Poimboeuf :
> On Tue, Jul 10, 2018 at 10:35:16AM +0900, Masahiro Yamada wrote:
>> Currently, users are allowed to enable STACK_VALIDATION regardless
>> of the compiler capability. The top-level Makefile warns or breaks
>> the build if it turns out that the hos
Hi,
On 07/09/2018 04:28 PM, Rafael J. Wysocki wrote:
On Mon, Jul 9, 2018 at 10:45 PM, Jeremy Linton wrote:
Hi,
First thanks for the patch..
On 07/08/2018 04:14 AM, Rafael J. Wysocki wrote:
On Monday, July 2, 2018 11:41:42 PM CEST Jeremy Linton wrote:
Hi,
I'm experiencing two problems wi
On Tue, Jul 10, 2018 at 11:33:42AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the rdma tree, today's linux-next build (x86_64
> allmodconfig) produced these warnings:
>
> In file included from include/linux/printk.h:336:0,
> from include/linux/kernel.h:14,
>
On Mon, 2018-07-09 at 17:38 -0400, Rik van Riel wrote:
>
> I added your code, and Signed-off-By in patch
> 1 for version 5 of the series.
No objection, but no need (like taking credit for fixing a typo:).
For Synopsys DesignWare 8250 uart which version >= 4.00a, there's a
valid divisor latch fraction register. The fractional divisor width is
4bits ~ 6bits.
Now the preparation is done, it's easy to add the feature support.
This patch firstly tries to get the fractional divisor width during
probe, th
Some drivers could call serial8250_do_set_divisor() to complete its
own set_divisor routine. Export this symbol for code reusing.
Signed-off-by: Jisheng Zhang
---
drivers/tty/serial/8250/8250_port.c | 5 +++--
include/linux/serial_8250.h | 3 +++
2 files changed, 6 insertions(+), 2 delet
Add these two hooks so that they can be overridden with driver specific
implementations.
Signed-off-by: Jisheng Zhang
Reviewed-by: Andy Shevchenko
---
drivers/tty/serial/8250/8250_core.c | 4
drivers/tty/serial/8250/8250_port.c | 27 +++
include/linux/serial_core.h
For Synopsys DesignWare 8250 uart which version >= 4.00a, there's a
valid divisor latch fraction register. The fractional divisor width is
4bits ~ 6bits.
patch1 introduces necessary hooks to 8250 core.
patch2 exports serial8250_do_set_divisor()
patch3 implements the fractional divisor support for
On Mon, Jul 09, 2018 at 10:07:16PM -0400, Steven Rostedt wrote:
> On Tue, 10 Jul 2018 10:25:16 +1000
> "Tobin C. Harding" wrote:
>
> > Since I'm a massive noob I did not realise that since v7 of this set was
> > applied to random-next already that doing incremental versions was
> > pointless.
>
On 2018/7/10 1:06, Mike Christie wrote:
On 07/06/2018 08:28 PM, Xiubo Li wrote:
On 2018/7/7 2:23, Mike Christie wrote:
On 07/05/2018 09:57 PM, xiu...@redhat.com wrote:
static irqreturn_t uio_interrupt(int irq, void *dev_id)
{
struct uio_device *idev = (struct uio_device *)dev_id;
On 2018/7/10 0:40, Mike Christie wrote:
On 07/06/2018 08:47 PM, Xiubo Li wrote:
On 2018/7/7 2:58, Mike Christie wrote:
On 07/05/2018 09:57 PM, xiu...@redhat.com wrote:
void uio_event_notify(struct uio_info *info)
{
-struct uio_device *idev = info->uio_dev;
+struct uio_device *ide
On Tue, Jul 10, 2018 at 10:35:16AM +0900, Masahiro Yamada wrote:
> Currently, users are allowed to enable STACK_VALIDATION regardless
> of the compiler capability. The top-level Makefile warns or breaks
> the build if it turns out that the host compiler cannot link libelf.
>
> Move the libelf tes
From: Yandong Zhao
Operations for contexts where we do not want to do any checks for
preemptions. Unless strictly necessary, always use this_cpu_read()
instead. Because of the kernel_neon_busy here we have to make sure
that it is the current cpu.
Signed-off-by: Yandong Zhao
---
arch/arm64/in
On Wed, 2018-07-04 at 16:01 +0200, Thomas Gleixner wrote:
> On Wed, 4 Jul 2018, Yang, Bin wrote:
> > e820 table:
> > =
> >
> > [0.00] BIOS-e820: [mem 0x-
> > 0x0009fbff]
> > usable
> > [0.00] BIOS-e820: [mem 0x0009fc00-
> > 0x
syzbot has found a reproducer for the following crash on:
HEAD commit:092150a25cb7 Merge branch 'for-linus' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16627cc240
kernel config: https://syzkaller.appspot.com/x/.config?x=25856f
Andrew Morton wrote:
> On Sat, 7 Jul 2018 08:26:32 +0900 Tetsuo Handa
> wrote:
>
> > Hello Andrew,
> >
> > It seems that syzbot (experimentally ?) restarted testing linux-next.
> >
> > May I ask you to carry temporarily debug printk() patch at
> > https://groups.google.com/d/msg/syzkaller-bugs
On Mon, Jul 9, 2018 at 5:44 PM, Dave Hansen wrote:
> ... cc'ing a few folks who I know have been looking at this code
> lately. The full oops is below if any of you want to take a look.
>
> OK, well, annotating the disassembly a bit:
>
>> (gdb) disass free_pages_and_swap_cache
>> Dump of assembl
On Tue, 10 Jul 2018 10:25:19 +1000
"Tobin C. Harding" wrote:
> Recently boot parameter 'debug_boot_weak_hash' was added. Latter
> discussion on LKML developed more descriptive documentation but due to
> the programmers lack of understanding (*cough* me) on how linux-next
> works these improvemen
On Tue, 10 Jul 2018 10:25:18 +1000
"Tobin C. Harding" wrote:
> Recently boot variable 'debug_boot_weak_hash' was added (by me). In a
> classic case of cargo cult programming the novice developer added a
> macro call to EXPORT_SYMBOL(). This is wrong and was pointed out on
> LKML. As pointed ou
Hi Andy,
On Mon, 9 Jul 2018 16:32:41 +0800 Jisheng Zhang wrote:
> Hi Andy,
>
> On Mon, 9 Jul 2018 16:23:15 +0800 Jisheng Zhang wrote:
>
> > For Synopsys DesignWare 8250 uart which version >= 4.00a, there's a
> > valid divisor latch fraction register. The fractional divisor width is
> > 4bits ~
On Tue, 10 Jul 2018 10:25:16 +1000
"Tobin C. Harding" wrote:
> Since I'm a massive noob I did not realise that since v7 of this set was
> applied to random-next already that doing incremental versions was
> pointless.
I wouldn't say you are a noob anymore. You are making the same types of
mistak
On Tue, 10 Jul 2018 10:25:17 +1000
"Tobin C. Harding" wrote:
> Currently we are casting an argument to the macro min_t(). This is
> unnecessary since the macro already includes a cast.
>
> Remove unnecessary cast from argument to macro min_t()
>
> Signed-off-by: Tobin C. Harding
Reviewed-by:
On 07/09/2018 06:19 PM, Huang, Ying wrote:
> Dave Hansen writes:
>
>>> config THP_SWAP
>>> def_bool y
>>> - depends on TRANSPARENT_HUGEPAGE && ARCH_WANTS_THP_SWAP
>>> + depends on TRANSPARENT_HUGEPAGE && ARCH_WANTS_THP_SWAP && SWAP
>>> help
>>
>> This seems like a bug-fix. Is there
On Mon, 9 Jul 2018, Andrew Morton wrote:
> > When perf profiling a wide variety of different workloads, it was found
> > that vmacache_find() had higher than expected cost: up to 0.08% of cpu
> > utilization in some cases. This was found to rival other core VM
> > functions such as alloc_pages_vm
On Mon, 2018-07-09 at 17:33 -0700, Linus Torvalds wrote:
> On Mon, Jul 9, 2018 at 5:29 PM Benjamin Herrenschmidt
> wrote:
> >
> > For devices with a class, we create a "glue" directory between
> > the parent device and the new device with the class name.
> >
> > This directory is never "explicit
Currently, users are allowed to enable STACK_VALIDATION regardless
of the compiler capability. The top-level Makefile warns or breaks
the build if it turns out that the host compiler cannot link libelf.
Move the libelf test to Kconfig so that users can enable the feature
only when the host compil
Hi all,
After merging the rdma tree, today's linux-next build (x86_64
allmodconfig) produced these warnings:
In file included from include/linux/printk.h:336:0,
from include/linux/kernel.h:14,
from arch/x86/include/asm/percpu.h:45,
from arch/x86/
Hi all,
After merging the rdma tree, today's linux-next build (powerpc
ppc64_defconfig) produced this warning:
In file included from include/linux/kernel.h:14:0,
from include/asm-generic/bug.h:18,
from arch/powerpc/include/asm/bug.h:128,
from inc
This series add new regulator controller support for UniPhier SoCs.
Currently this supports USB3 VBUS controller only. This USB3 VBUS belongs to
USB3 glue layer.
Changes since v1:
- dt-bindings: add description of glue layer
- replace read/write accesses with regmap_mmio
- rewrite a header with C+
Initial commit to add support for regulators implemented in UniPhier SoCs.
This supports USB VBUS only.
Signed-off-by: Kunihiko Hayashi
---
drivers/regulator/Kconfig | 8 ++
drivers/regulator/Makefile | 1 +
drivers/regulator/uniphier-regulator.c | 247 ++
Add DT bindings for regulators implemented in UniPhier SoCs.
Signed-off-by: Kunihiko Hayashi
---
.../bindings/regulator/uniphier-regulator.txt | 57 ++
1 file changed, 57 insertions(+)
create mode 100644
Documentation/devicetree/bindings/regulator/uniphier-regulator.tx
HI Martin:
thanks for your suggestion
On 07/10/18 06:02, Martin Blumenstingl wrote:
> Hi Yixun,
>
> On Thu, Jul 5, 2018 at 4:53 AM Yixun Lan wrote:
>>
>> HI Neil
>>
>> On 07/04/18 22:57, Neil Armstrong wrote:
>>> Hi Yixun,
>>>
>>> On 05/07/2018 00:45, Yixun Lan wrote:
This patch series try
On Mon, Jul 09, 2018 at 06:17:41PM -0700, Eric Biggers wrote:
> On Mon, Jul 09, 2018 at 01:31:09PM +0100, David Howells wrote:
> > Eric Biggers wrote:
> >
> > > sys_fsmount() calls fc->ops->free() to free the data, zeroes
> > > ->fs_private, then proceeds to reuse the context. But legacy_fs_cont
Dave Hansen writes:
>> config THP_SWAP
>> def_bool y
>> -depends on TRANSPARENT_HUGEPAGE && ARCH_WANTS_THP_SWAP
>> +depends on TRANSPARENT_HUGEPAGE && ARCH_WANTS_THP_SWAP && SWAP
>> help
>
>
> This seems like a bug-fix. Is there a reason this didn't cause problems
> up to now?
Hi Stephen, Linus, Geert,
> -Original Message-
> From: Linus Walleij, Sent: Tuesday, July 10, 2018 7:46 AM
>
> Hm must have come from Geert's pull request?
>
> (I'm regularly wrong about this so not so certain...)
>
> Geert can I fix it the usual way by simply rebasing and
> adding the
On Mon, Jul 09, 2018 at 01:31:09PM +0100, David Howells wrote:
> Eric Biggers wrote:
>
> > sys_fsmount() calls fc->ops->free() to free the data, zeroes
> > ->fs_private, then proceeds to reuse the context. But legacy_fs_context
> > doesn't use ->fs_private, so we need to handle zeroing it too; o
Hi all,
Today's linux-next merge of the rdma tree got a conflict in:
drivers/infiniband/core/uverbs_cmd.c
between commit:
4fae7f170416 ("RDMA/uverbs: Fix slab-out-of-bounds in
ib_uverbs_ex_create_flow")
from the rdma-fixes tree and commit:
2cc1e3b80942 ("IB/uverbs: Replace file->uconte
This series add new USB3 core reset control support for UniPhier SoCs.
This reset line belongs to USB3 glue layer.
Changes since v1:
- dt-bindings: fix a typo, not "clock-names" but "reset-names"
- dt-bindings: add description of glue layer
- reuse soc_data for pxs2, ld20 and pxs3
- put reset_simp
Add a reset line to enable USB3 core implemented in UniPhier SoCs.
This reuses only the reset operations in reset-simple, because
the reset-simple doesn't handle any SoC-dependent clocks and resets.
This reset line is included in the USB3 glue layer, and it's necessary
to enable clocks and deasser
Add DT bindings for reset control of USB3 core implemented in UniPhier SoCs.
The reset control belongs to USB3 glue layer.
Signed-off-by: Kunihiko Hayashi
---
.../devicetree/bindings/reset/uniphier-reset.txt | 56 ++
1 file changed, 56 insertions(+)
diff --git a/Documentat
Dave Hansen writes:
> On 06/21/2018 08:51 PM, Huang, Ying wrote:
>> From: Huang Ying
>>
>> Previously, the PMD swap operations are only enabled for
>> CONFIG_ARCH_ENABLE_THP_MIGRATION. Because they are only used by the
>> THP migration support. We will support PMD swap mapping to the huge
>>
On Mon, 9 Jul 2018 17:50:03 -0700 (PDT) David Rientjes
wrote:
> When perf profiling a wide variety of different workloads, it was found
> that vmacache_find() had higher than expected cost: up to 0.08% of cpu
> utilization in some cases. This was found to rival other core VM
> functions such as
On Thu, Jul 5, 2018 at 1:44 PM, Arnd Bergmann wrote:
> On Tue, Jun 26, 2018 at 7:29 PM, Kees Cook wrote:
>> In the quest to remove all stack VLA usage from the kernel[1], this
>> uses the maximum size needed on the stack and adds a sanity check for
>> robustness: index.block_size cannot be larger
Commit 38fc42486775 ("arm64: Use aarch64elf and aarch64elfb emulation mode
variants") unfortunately breaks with some toolchains:
CHK include/generated/compile.h
LD [M] arch/arm64/crypto/sha512-ce.o
aarch64-linux-gnu-ld: cannot open linker script file ldscripts/aarch64elf.xr:
No such file
When perf profiling a wide variety of different workloads, it was found
that vmacache_find() had higher than expected cost: up to 0.08% of cpu
utilization in some cases. This was found to rival other core VM
functions such as alloc_pages_vma() with thp enabled and default
mempolicy, and the condit
Commit 0c3b7e42616f ("tools build: Add support for host programs format")
introduced host_c_flags which referenced CHOSTFLAGS. The actual name of the
variable is HOSTCFLAGS. Fix this up.
Fixes: 0c3b7e42616f ("tools build: Add support for host programs format")
Signed-off-by: Laura Abbott
---
v2:
In preparation for enabling command line CXXFLAGS, re-name HOSTCXXFLAGS to
KBUILD_HOSTCXXFLAGS as the internal use only flags. This should not have any
visible effects.
Signed-off-by: Laura Abbott
---
v2: Dropped name change for individual files (still HOSTCXXFLAGS_foo)
---
Makefile
In preparation for enabling command line CFLAGS, re-name HOSTCFLAGS to
KBUILD_HOSTCFLAGS as the internal use only flags. This should not have any
visible effects.
Signed-off-by: Laura Abbott
---
v2: Dropped name change for individual files (still CHOSTFLAGS_foo)
---
Makefile |
In preparation for enabling command line LDFLAGS, re-name HOSTLDFLAGS to
KBUILD_HOSTLDFLAGS as the internal use only flags. This should not have any
visible effects.
Signed-off-by: Laura Abbott
---
v2: No change
---
Makefile | 4 ++--
net/bpfilter/Makefile | 2 +-
scripts/Makefi
The final link of fixdep uses LDFLAGS but not the existing HOSTLDFLAGS.
Fix this.
Signed-off-by: Laura Abbott
---
v2: Switch to just using HOSTLDFLAGS instead of both LDFLAGS and
HOSTLDFLAGS.
---
tools/build/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/build
In preparation for enabling command line LDLIBS, re-name HOST_LOADLIBES to
KBUILD_HOSTLDLIBS as the internal use only flags. Also rename existing usage
to HOSTLDLIBS for consistency. This should not have any visible effects.
Signed-off-by: Laura Abbott
---
v2: Rename existing HOSTLOADLIBES to HOS
... cc'ing a few folks who I know have been looking at this code
lately. The full oops is below if any of you want to take a look.
OK, well, annotating the disassembly a bit:
> (gdb) disass free_pages_and_swap_cache
> Dump of assembler code for function free_pages_and_swap_cache:
>0xfff
On Sat, 7 Jul 2018 08:26:32 +0900 Tetsuo Handa
wrote:
> Hello Andrew,
>
> It seems that syzbot (experimentally ?) restarted testing linux-next.
>
> May I ask you to carry temporarily debug printk() patch at
> https://groups.google.com/d/msg/syzkaller-bugs/E8M8WTqt034/OpadOICfCAAJ
> for "INFO:
On Fri, 6 Jul 2018 16:53:11 -0700 Dan Williams wrote:
> On Mon, Jun 18, 2018 at 11:05 PM, Dan Williams
> wrote:
> > The routines hmm_devmem_add(), and hmm_devmem_add_resource() are
> > now wrappers around the functionality provided by devm_memremap_pages() to
> > inject a dev_pagemap instance a
1 - 100 of 801 matches
Mail list logo
