piaojun wrote on Thu, Jul 12, 2018:
> In p9_read_work(), we use spin_lock for client->lock, but misuse
> spin_lock_irqsave for it in p9_fid_create(). As p9_client lock won't be
> locked in irq context, so spin_lock is enough. And that will improve the
> performance.
Agreed on principle, see remark
With commit eca0fa28cd0d ("perf record: Provide detailed information on s390
CPU")
s390 platform provides detailed type/model/capacitiy information
in the CPU indentifier string instead of just "IBM/S390".
This breaks perf kvm support which uses hard coded string IBM/S390 to
compare with the CPU
于 2018年7月12日 GMT+08:00 下午2:46:01, Maxime Ripard 写到:
>On Wed, Jul 11, 2018 at 11:15:50PM +0800, Icenowy Zheng wrote:
>>
>>
>> 于 2018年7月11日 GMT+08:00 下午11:05:32, Maxime Ripard
> 写到:
>> >Hi,
>> >
>> >On Wed, Jul 11, 2018 at 09:22:32PM +0800, Icenowy Zheng wrote:
>> >> Banana Pi M2 Zero board has
On 07/12/2018 09:09 AM, Thomas Richter wrote:
> With commit eca0fa28cd0d ("perf record: Provide detailed information on s390
> CPU")
> s390 platform provides detailed type/model/capacitiy information
> in the CPU indentifier string instead of just "IBM/S390".
>
> This breaks perf kvm support w
Hi Olof,
On Wed, Jul 11, 2018 at 11:46 PM Olof Johansson wrote:
> On Wed, Jul 11, 2018 at 7:26 AM, Geert Uytterhoeven
> wrote:
> > This allows to derive the kernel flavor from the kernel version at
> > runtime.
> >
> > Signed-off-by: Geert Uytterhoeven
>
> I prefer not to have this go in -- thi
On 07/09/2018 11:21 AM, Pierre Morel wrote:
On 03/07/2018 01:10, Halil Pasic wrote:
On 06/29/2018 11:11 PM, Tony Krowiak wrote:
This patch provides documentation describing the AP architecture and
design concepts behind the virtualization of AP devices. It also
includes an example of how to c
On 07/10/2018 09:03 AM, Harald Freudenberger wrote:
On 09.07.2018 16:17, Pierre Morel wrote:
On 29/06/2018 23:11, Tony Krowiak wrote:
Registers the matrix device created by the VFIO AP device
driver with the VFIO mediated device framework.
Registering the matrix device will create the sysfs
str
The stack assumes that SDHC controller which support SD3.0 (SDR104) do
support HS200. This is not the case for Tegra 3, which does support SD
3.0
but only supports eMMC spec 4.41.
Use SDHCI_QUIRK2_BROKEN_HS200 to indicate that the controller does not
support HS200.
Note that commit 156e14b126ff (
It seems that SD3.0 advertisement needs to be set for higher eMMC
speed modes (namely DDR52) as well. The TRM states that the SD3.0
advertisement bit should be set for all controller instances, even
for those not supporting UHS-I mode...
When specifying vqmmc-supply as a fixed 1.8V regulator on a
Make sure the clock is doubled when using eMMC DDR52 mode.
Signed-off-by: Stefan Agner
---
drivers/mmc/host/sdhci-tegra.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/mmc/host/sdhci-tegra.c b/drivers/mmc/host/sdhci-tegra.c
index 137df06b9b6e..888a1ad511db 100644
On Wed, Jul 11, 2018 at 02:34:21PM +0200, Andrea Parri wrote:
> Simplicity is the eye of the beholder. From my POV (LKMM maintainer), the
> simplest solution would be to get rid of rfi-rel-acq and unlock-rf-lock-po
> (or its analogous in v3) all together:
> Among other things, this would immedi
On Wed, 11 Jul 2018 16:14:13 +0100
Jon Hunter wrote:
> On 11/07/18 12:17, Peter De Schrijver wrote:
> > On Wed, Jul 11, 2018 at 09:42:20AM +0100, Jon Hunter wrote:
> >>
> >> On 11/07/18 09:00, Peter De Schrijver wrote:
> >>> On Tue, Jul 10, 2018 at 05:17:05PM +0100, Jon Hunter wrote:
>
On Wed 11-07-18 12:59:13, Mike Kravetz wrote:
> This reverts commit ee8f248d266e ("hugetlb: add phys addr to struct
> huge_bootmem_page")
>
> At one time powerpc used this field and supporting code. However that
> was removed with commit 79cc38ded1e1 ("powerpc/mm/hugetlb: Add support
> for reservi
On Wed 11-07-18 14:33:13, Cannon Matthews wrote:
> When using 1GiB pages during early boot, use the new
> memblock_virt_alloc_try_nid_raw() function to allocate memory without
> zeroing it. Zeroing out hundreds or thousands of GiB in a single core
> memset() call is very slow, and can make early b
Good day,
I am Mr. Omar Al-Bashir working with a bank here in London. I have emailed you
earlier on without any response from you. On my first email I mentioned about
my late client whose relatives I cannot get in touch with. But both of you have
the same last name so it will be very easy to f
On Wed, 11 Jul 2018 16:26:42 +0100
Jon Hunter wrote:
> On 11/07/18 16:23, Jon Hunter wrote:
> >
> > On 11/07/18 15:01, Aapo Vienamo wrote:
> >> Implement a function to query whether a pad is in deep power down mode.
> > Can you elaborate on why this public function is needed and who will be
On Thu 2018-07-12 13:25:52, Sergey Senozhatsky wrote:
> On (07/11/18 23:09), Steven Rostedt wrote:
> > > On (07/11/18 15:17), Steven Rostedt wrote:
> > > > +bool ignore_console_lock_warning __read_mostly;
> > > > +EXPORT_SYMBOL(ignore_console_lock_warning);
> > >
> > > OK. So, to recap,
> > > We
On 12 July 2018 at 13:48, Benjamin Herrenschmidt
wrote:
> The Aspeed AST2x00 can contain a ColdFire v1 coprocessor which
> is currently unused on OpenPower systems.
>
> This adds an alternative to the fsi-master-gpio driver that
> uses that coprocessor instead of bit banging from the ARM
> core it
Commit a0f97e06a43c ("kbuild: enable 'make CFLAGS=...' to add
additional options to CC") renamed CFLAGS to KBUILD_CFLAGS.
Commit 222d394d30e7 ("kbuild: enable 'make AFLAGS=...' to add
additional options to AS") renamed AFLAGS to KBUILD_AFLAGS.
Commit 06c5040cdb13 ("kbuild: enable 'make CPPFLAGS=.
$(LDFLAGS) $(ldflags-y) is equivalent to $(ld_flags).
Signed-off-by: Masahiro Yamada
---
scripts/Makefile.lib | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/scripts/Makefile.lib b/scripts/Makefile.lib
index 1bb594f..1915574 100644
--- a/scripts/Makefile.lib
+++ b/scripts/
This series renames LDFLAGS to KBUILD_LDFLAGS
after some Makefile cleanups.
Currently, the last patch does not apply to Linus' tree
due to missing pre-requisite patches.
I will resolve conflicts as needed.
Masahiro Yamada (6):
um: remove redundant 'export LDFLAGS' in arch/x86/Makefile.um
Since commit 799c43415442 ("kbuild: thin archives make default for
all archs"), $(AR) is used instead of $(LD) to combine object files.
LDFLAGS +=--no-warn-mismatch
... is unused code now.
arch/arm/Makefile already guards arch/arm/vfp/ by a boolean symbol,
CONFIG_VFP, like this:
cor
Since commit ce99d0bf312d ("kbuild: clear LDFLAGS in the top Makefile"),
the top-level Makefile caters to this.
Signed-off-by: Masahiro Yamada
---
arch/arm/Makefile | 3 ---
arch/openrisc/Makefile | 1 -
arch/riscv/Makefile| 1 -
3 files changed, 5 deletions(-)
diff --git a/arch/arm/M
This is already exported by the top-level Makefile.
Signed-off-by: Masahiro Yamada
---
arch/x86/Makefile.um | 2 --
1 file changed, 2 deletions(-)
diff --git a/arch/x86/Makefile.um b/arch/x86/Makefile.um
index 45af199..5296f8c 100644
--- a/arch/x86/Makefile.um
+++ b/arch/x86/Makefile.um
@@ -13
On Wed 11-07-18 10:04:48, Yang Shi wrote:
[...]
> One approach is to save all the vmas on a separate list, then zap_page_range
> does unmap with this list.
Just detached unmapped vma chain from mm. You can keep the existing
vm_next chain and reuse it.
--
Michal Hocko
SUSE Labs
Put $(LDFLAGS_$(@F)) into ld_flags so that $(LDFLAGS_pcap.o) and
$(LDFLAGS_vde.o) in arch/um/drivers/Makefile are absorbed.
Signed-off-by: Masahiro Yamada
---
arch/um/drivers/Makefile | 4 ++--
scripts/Makefile.lib | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/arc
On (07/12/18 09:53), Petr Mladek wrote:
> >
> > True, but at the same time nobody complained that we didn't have those
> > extra WARN_CONSOLE_UNLOCKED()-s. Just saying. Over all I agree that there
> > is probably some value in those extra WARN-s.
>
> I agree that there is some value in the extra
In some cases the link between between customer and supplier
already exist. Do not warn about already existing dependencies
because device_link_add() take care of this case.
Reported-by: Marek Szyprowski
Signed-off-by: Benjamin Gaignard
---
drivers/base/core.c | 4 ++--
1 file changed, 2 insert
In the uSDHC case (e.g. i.MX 6) clocks only get disabled if frequency
is set to 0. However, it could be that the stack asks for a frequency
change while clocks are on. In that case the function clears the
divider registers (by clearing ESDHC_CLOCK_MASK) while the clock is
enabled! This causes a sho
Fix indent. This also makes disable/enable clock blocks look
alike.
Signed-off-by: Stefan Agner
---
drivers/mmc/host/sdhci-esdhc-imx.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mmc/host/sdhci-esdhc-imx.c
b/drivers/mmc/host/sdhci-esdhc-imx.c
index acacd8481473..
On Thu, Jul 12, 2018 at 6:41 AM, Peter Rosin wrote:
> On 2018-07-11 19:12, Boris Brezillon wrote:
>> On Wed, 11 Jul 2018 17:39:56 +0200 Arnd Bergmann wrote:
>>
>> That's exactly the sort of discussion I wanted to trigger. Maybe we
>> shouldn't care and expose this use case as if it was X differen
In the uSDHC case (e.g. i.MX 6) clocks only get disabled if frequency
is set to 0. However, it could be that the stack asks for a frequency
change while clocks are on. In that case the function clears the
divider registers (by clearing ESDHC_CLOCK_MASK) while the clock is
enabled! This causes a sho
Support for immediate flag was removed by commit d0807da78e11
("livepatch: Remove immediate feature"). We bail out during
patch registration for architectures, those don't support
reliable stack trace. Remove the check in klp_try_switch_task(),
as its not required.
Signed-off-by: Kamalesh Babulal
On 12.07.2018 10:06, Stefan Agner wrote:
> In the uSDHC case (e.g. i.MX 6) clocks only get disabled if frequency
> is set to 0. However, it could be that the stack asks for a frequency
> change while clocks are on. In that case the function clears the
> divider registers (by clearing ESDHC_CLOCK_MA
Break too long line to follow kernel coding style.
Signed-off-by: Kacper Kołodziej
---
drivers/staging/rtl8188eu/core/rtw_ap.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/staging/rtl8188eu/core/rtw_ap.c
b/drivers/staging/rtl8188eu/core/rtw_ap.c
index 454a975a14
Hi Rob,
On 11.07.2018 17:54, Rob Herring wrote:
On Thu, Jul 05, 2018 at 01:15:00PM +0200, Frieder Schrempf wrote:
Move the documentation of the old SPI NOR driver to the place of the new
SPI memory interface based driver.
Signed-off-by: Frieder Schrempf
---
Changes in v2:
==
* Spl
Hi Rob,
On 11.07.2018 18:05, Rob Herring wrote:
On Thu, Jul 05, 2018 at 01:15:01PM +0200, Frieder Schrempf wrote:
Adjust the documentation of the new SPI memory interface based
driver to reflect the new drivers settings.
Bindings shouldn't change (other than new properties) due to driver
chan
On Wed 11-07-18 15:49:54, Andrew Morton wrote:
> On Wed, 11 Jul 2018 12:33:12 +0200 Michal Hocko wrote:
>
> > > Approach:
> > > Zapping pages is the most time consuming part, according to the
> > > suggestion from
> > > Michal Hocko [1], zapping pages can be done with holding read mmap_sem,
> >
On Wed, Jul 11, 2018 at 10:43:28AM +0200, Dietmar Eggemann wrote:
> On 07/11/2018 01:09 AM, Joel Fernandes wrote:
> > On Mon, Jul 09, 2018 at 05:47:53PM +0100, Dietmar Eggemann wrote:
> > > A CFS (SCHED_OTHER, SCHED_BATCH or SCHED_IDLE policy) task's
> > > se->runnable_weight must always be in sync
The ConnectCore 6UL System-On-Module has the following hardware
specification:
* Based on a NXP i.MX6UL SoC
* Industrial temperature ranges (-40ºC to +85ºC)
* Up to 1GB DDR3 memory
* Up to 2GB NAND flash
* Dual Ethernet
* On module 802.11 WiFi and Bluetooth 4.2 (QCA6564)
* On module NXP Kinetis KL
This patchset adds a device tree include for the ConnectCore 6UL
System-On-Module and a device tree for the ConnectCore 6UL SBC Express board
that includes it.
Not all the SOM hardware is supported in this initial patchset, specifically
the 802.11 WiFi and BT chipset and the extended functionality
The ConnectCore 6UL Single Board Computer (SBC) Express contains the
ConnectCore 6UL System-On-Module.
Its hardware specifications are:
* 256MB DDR3 memory
* 256MB NAND flash
* Single Ethernet
* USB Host and USB-OTG
* MicroSD external storage
* Groove connectors and Raspberry Pi Hat compatible ex
On Fri, Jul 06, 2018 at 10:42:41PM -0700, Deepa Dinamani wrote:
> As we repurpose more compat syscalls to be used in non CONFIG_COMPAT
> usecases as part of solving y2038, we need to make these basic types
> available unconditionally.
NAK. Compat code is for foreign ABIs. If this code is going t
Dear Sir,
Kindly find attached our confirmed PO as discussed.
Regards
Sarah Young
Rintusac - Perú
Av. Oscar R. Benavides
Lima, Peru
SKM_C454ePO27045.docx
Description: MS-Word 2007 document
2018-07-10 20:34 GMT+09:00 Dirk Gouders :
> Masahiro Yamada writes:
>
>> The main motivation of this patch series is to suppress the syncconfig
>> during running installation targets.
>>
>> V1 consisted of only two patches:
>> https://patchwork.kernel.org/patch/10468105/
>> https://patchwork.k
On Wed, 2018-07-11 at 16:47 -0700, Paul E. McKenney wrote:
>
> > > What changed was RCU's reactions to longish grace periods. It used to
> > > be very aggressive about forcing the scheduler to do otherwise-unneeded
> > > context switches, which became a problem somewhere between v4.9 and v4.15.
On Thu 2018-07-12 13:35:06, Kamalesh Babulal wrote:
> Support for immediate flag was removed by commit d0807da78e11
> ("livepatch: Remove immediate feature"). We bail out during
> patch registration for architectures, those don't support
> reliable stack trace. Remove the check in klp_try_switch_t
Hi Matthias,
On 2018년 07월 07일 01:36, Matthias Kaehlcke wrote:
> Hi Chanwoo,
>
> On Wed, Jul 04, 2018 at 11:20:31AM +0900, Chanwoo Choi wrote:
>> Hi Matthias,
>>
>> On 2018년 07월 04일 08:46, Matthias Kaehlcke wrote:
>>> Commit ab8f58ad72c4 ("PM / devfreq: Set min/max_freq when adding the
>>> devfreq
> All the discussion here[1] for example is about having ordering and
> doing an smp_cond_load_acquire() on a variable which is sometimes
> protected by a CPU's rq->lock and sometimes not? Isn't that one of the
> key use cases for this whole discussion?
Not a "pure" one:
http://lkml.kernel.or
Hi Matthias,
On 2018년 07월 07일 02:07, Matthias Kaehlcke wrote:
> Hi,
>
> On Wed, Jul 04, 2018 at 11:51:30AM +0900, Chanwoo Choi wrote:
>> Hi,
>>
>> On 2018년 07월 04일 08:46, Matthias Kaehlcke wrote:
>>> Move variables related with devfreq policy changes from struct devfreq
>>> to the new struct devf
On Wed, Jul 11, 2018 at 09:19:44AM -0400, Steven Rostedt wrote:
> > > protection to prevent something like the following case: a spin_lock is
> > > taken. Then lockdep_acquired is called. That does a raw_local_irq_save
> > > and then sets lockdep_recursion, and then calls __lockdep_acquired. In
>
On Wed, Jul 11, 2018 at 10:10 AM Joe Perches wrote:
>
> On Wed, 2018-07-11 at 09:53 -0700, Jae Hyun Yoo wrote:
> > On 7/10/2018 10:42 PM, Brendan Higgins wrote:
> > > On Mon, Jul 2, 2018 at 2:14 PM Jae Hyun Yoo
> > > wrote:
> > > > There are some log printing without a newline character. This
>
We also split up the regmap address space into two, for the TM and SROT
registers. This was required to deal with different address offsets for the
TM and SROT registers across different SoC families.
8996 has two TSENS IP blocks, initialise the second one too.
Since tsens-common.c/init_common()
There are two banks of registers for v2 TSENS IPs: SROT and TM. On older
SoCs these were contiguous, leading to DTs mapping them as one register
address space of size 0x2000. In newer SoCs, these two banks are not
contiguous anymore.
Add logic to init_common() to differentiate between old and new
status_field and trdy are unused in any of the tsens drivers. Remove them.
Signed-off-by: Amit Kucheria
Reviewed-by: Bjorn Andersson
Acked-by: Rajendra Nayak
Tested-by: Matthias Kaehlcke
---
drivers/thermal/qcom/tsens.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/thermal/qcom
The TSENS block inside the 8996 is internally classified as version 2 of
the IP. Several other SoC families use this block and can share this code.
We rename get_temp() to reflect that it can be used across the v2 family.
Signed-off-by: Amit Kucheria
Reviewed-by: Bjorn Andersson
Tested-by: Matt
We want to create common code for v2 of the TSENS IP block that is used in
a large number of Qualcomm SoCs. "qcom,tsens-v2" should be able to handle
most of the common functionality start with a common get_temp() function.
It is also necessary to split out the memory regions for the TM and SROT
re
This series is a mixed bag:
- Some code moves to allow code sharing between different SoCs with v2 of
the TSENS IP,
- a generic qcom,tsens-v2 property as a fallback compatible for all v2.x.y
platforms,
- new platform support (sdm845)
- a cleanup patch and
- a DT change to have a common way to d
SDM845 uses v2 of the TSENS IP block but the get_temp() function appears to
be identical across v2.x.y in code seen so far. We use the generic
get_temp() function defined as part of ops_generic_v2.
Signed-off-by: Amit Kucheria
Reviewed-by: Bjorn Andersson
Tested-by: Matthias Kaehlcke
---
drive
SDM845 has two tsens blocks, one with 13 sensors and the other with 8
sensors. It uses version 2 of the TSENS IP, so use the fallback property to
allow more common code.
Signed-off-by: Amit Kucheria
Reviewed-by: Bjorn Andersson
Tested-by: Matthias Kaehlcke
---
arch/arm64/boot/dts/qcom/sdm845.d
On Mon, Jul 2, 2018 at 2:40 PM Jae Hyun Yoo
wrote:
>
> This patch adjusts spinlock scope to make it wrap the whole irq
> handler using a single lock/unlock which covers both master and
> slave handlers.
>
> Signed-off-by: Jae Hyun Yoo
> ---
> drivers/i2c/busses/i2c-aspeed.c | 16 ++--
Hi Matthias,
On 2018년 07월 07일 02:53, Matthias Kaehlcke wrote:
> Hi Chanwoo,
>
> On Wed, Jul 04, 2018 at 03:41:46PM +0900, Chanwoo Choi wrote:
>
>> Firstly,
>> I'm not sure why devfreq needs the devfreq_verify_within_limits() function.
>>
>> devfreq already used the OPP interface as default. It m
Since the clocksource framework has introduced one suspend clocksource to
compensate the suspend time, this patch registers one always-on timer as
the suspend clocksource.
Signed-off-by: Baolin Wang
---
drivers/clocksource/timer-sprd.c | 50 ++
1 file change
On some hardware with multiple clocksources, we have course grained
clocksources that support the CLOCK_SOURCE_SUSPEND_NONSTOP flag, but
which are less ideal for timekeeping then other clocksources which
halt in suspend.
Currently, the timekeeping core only supports timing suspend using
CLOCK_SOUR
> -Original Message-
> From: Stefan Agner [mailto:ste...@agner.ch]
> Sent: Thursday, July 12, 2018 4:07 PM
> To: adrian.hun...@intel.com; ulf.hans...@linaro.org
> Cc: Fabio Estevam ; Bough Chen
> ; A.s. Dong ; linux-
> m...@vger.kernel.org; linux-kernel@vger.kernel.org; Stefan Agner
>
> Su
On 2018-07-12 10:08, Arnd Bergmann wrote:
> On Thu, Jul 12, 2018 at 6:41 AM, Peter Rosin wrote:
>> On 2018-07-11 19:12, Boris Brezillon wrote:
>>> On Wed, 11 Jul 2018 17:39:56 +0200 Arnd Bergmann wrote:
>>>
>>> That's exactly the sort of discussion I wanted to trigger. Maybe we
>>> shouldn't care
> -Original Message-
> From: Stefan Agner [mailto:ste...@agner.ch]
> Sent: Thursday, July 12, 2018 4:07 PM
> To: adrian.hun...@intel.com; ulf.hans...@linaro.org
> Cc: Fabio Estevam ; Bough Chen
> ; A.s. Dong ; linux-
> m...@vger.kernel.org; linux-kernel@vger.kernel.org; Stefan Agner
>
> Su
On Thu, Jul 12, 2018 at 10:06:23AM +0200, Benjamin Gaignard wrote:
> In some cases the link between between customer and supplier
> already exist. Do not warn about already existing dependencies
> because device_link_add() take care of this case.
Why would a link already exist that is asked to be
On Wed, Jul 11, 2018 at 7:07 PM, Tycho Andersen wrote:
> Anyway, since the lock is not acquired, if uart_shutdown() is called, the
> last chunk of that function may release state->xmit.buf before its assigned
> to null, and cause the race above.
>
> To fix it, let's lock uport->lock when allocati
Hi Matthias,
On 2018년 07월 07일 03:09, Matthias Kaehlcke wrote:
> Hi,
>
> On Wed, Jul 04, 2018 at 02:30:32PM +0900, Chanwoo Choi wrote:
>
>> I didn't see any framework which exporting the class instance.
>> It is very dangerous. Unknown device drivers is able to reset
>> the 'devfreq_class' instan
On Tue, 2018-07-10 at 16:36 +, Yixun Lan wrote:
> The patch will add a MMC clock controller driver which used by MMC or NAND,
> It provide a mux and divider clock, and three phase clocks - core, tx, tx.
>
> Two clocks are provided as the parent of MMC clock controller from
> upper layer clock
On 07/11/2018 02:16 PM, Ulf Hansson wrote:
On 11 July 2018 at 11:41, Ludovic BARRE wrote:
On 07/05/2018 05:17 PM, Ulf Hansson wrote:
On 12 June 2018 at 15:14, Ludovic Barre wrote:
From: Ludovic Barre
Prepare mmci driver to manage dma interface by new property.
This patch defines and
On Thu, 12 Jul 2018, Kamalesh Babulal wrote:
> Support for immediate flag was removed by commit d0807da78e11
> ("livepatch: Remove immediate feature"). We bail out during
> patch registration for architectures, those don't support
> reliable stack trace. Remove the check in klp_try_switch_task(),
On Wed, Jul 11, 2018 at 04:41:10PM +0100, Sudeep Holla wrote:
> On Wed, Jul 11, 2018 at 01:17:38PM +, Wei Yongjun wrote:
> > platform_get_resource() may fail and return NULL, so we should
> > better check it's return value to avoid a NULL pointer dereference
> > a bit later in the code.
> >
>
2018-07-12 10:55 GMT+02:00 Greg KH :
> On Thu, Jul 12, 2018 at 10:06:23AM +0200, Benjamin Gaignard wrote:
>> In some cases the link between between customer and supplier
>> already exist. Do not warn about already existing dependencies
>> because device_link_add() take care of this case.
>
> Why wo
On Wed, Jul 11, 2018 at 10:50:56AM -0700, Daniel Lustig wrote:
> On 7/11/2018 10:00 AM, Peter Zijlstra wrote:
> > On Wed, Jul 11, 2018 at 04:57:51PM +0100, Will Deacon wrote:
> >
> >> It might be simple to model, but I worry this weakens our locking
> >> implementations to a point where they will
Wanpeng Li writes:
> On Thu, 12 Jul 2018 at 08:07, Vitaly Kuznetsov wrote:
>>
>> When we switched from doing rdmsr() to reading FS/GS base values from
>> current->thread we completely forgot about legacy 32-bit userspaces which
>> we still support in KVM (why?). task->thread.{fsbase,gsbase} are
On Wed, Jun 27, 2018 at 10:55 AM Jae Hyun Yoo
wrote:
>
> >> +/* Timeout for bus busy checking */
> >> +#define BUS_BUSY_CHECK_TIMEOUT 25 /* 250ms */
> >> +#define BUS_BUSY_CHECK_INTERVAL1 /*
> >> 10ms */
> >
> > Could you add a com
Hi Jerome
thanks for the review
On 07/12/18 17:09, Jerome Brunet wrote:
> On Tue, 2018-07-10 at 16:36 +, Yixun Lan wrote:
>> The patch will add a MMC clock controller driver which used by MMC or NAND,
>> It provide a mux and divider clock, and three phase clocks - core, tx, tx.
>>
>> Two cloc
This patch set addresses two issues in arch/arm/mach-hisi/hotplug.c
1) The hisi hotplug functions were using a few unchecked
of_iomap() while at the same time the system relied on
those mappings. Checks for !NULL were inserted.
2) Further some mandatory of_node_put() were missing and have
rsion-next is next-20180712)
arch/arm/mach-hisi/hotplug.c | 14 +-
1 file changed, 9 insertions(+), 5 deletions(-)
diff --git a/arch/arm/mach-hisi/hotplug.c b/arch/arm/mach-hisi/hotplug.c
index 3b0d1c6..40857bf 100644
--- a/arch/arm/mach-hisi/hotplug.c
+++ b/arch/arm/mach-hisi
hi3xxx_hotplug_init probably should be bool as that is how
it is being used - the error return is not actually interpreted beyond
detection of failure in its only call site hi3xxx_set_cpu().
Patch was compile tested with: hisi_defconfig (implies CONFIG_SMP=y)
Patch is against 4.18-rc3 (localversion-n
nel - try using WARN_ON"
but here the BUG_ON() seems adequate.
Patch is against 4.18-rc3 (localversion-next is next-20180712)
arch/arm/mach-hisi/hotplug.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/arch/arm/mach-hisi/hotplug.c b/arch/arm/mach-hisi/hotplug.c
in
On Thu, Jul 12, 2018 at 09:40:40AM +0200, Peter Zijlstra wrote:
> And I think if we raise atomic*_acquire() to require TSO (but ideally
> raise it to RCsc) we're there.
To clarify, just the RmW-acquire. Things like atomic_read_acquire() can
stay smp_load_acquire() and be RCpc.
On Thu, Jul 12, 2018 at 11:34:32AM +0200, Peter Zijlstra wrote:
> On Thu, Jul 12, 2018 at 09:40:40AM +0200, Peter Zijlstra wrote:
> > And I think if we raise atomic*_acquire() to require TSO (but ideally
> > raise it to RCsc) we're there.
>
> To clarify, just the RmW-acquire. Things like atomic_re
On Thu, 2018-07-12 at 08:21 +0200, Christian Borntraeger wrote:
>
> Is there a single patch that that I can test or do I have to combine
> all the pieces that are sprinkled in this mail thread?
I believe it should be just these two commits, and the first is
probably optional as the second makes i
On Thu, Jul 12, 2018 at 11:29:38AM +0800, Yandong.Zhao wrote:
> From: Yandong Zhao
>
> It does not matter if the caller of may_use_simd() migrates to
> another cpu after the call, but it is still important that the
> kernel_neon_busy percpu instance that is read matches the cpu the
> task is runn
Print a warning if none of the Signed-off-by lines cover the patch
author.
Non-ASCII quoted printable encoding in From: headers and (lack of)
double quotes are handled.
Split From: headers are not fully handled: only the first part is
compared.
Signed-off-by: Geert Uytterhoeven
---
Tested using
Hi.
2018-07-10 9:45 GMT+09:00 Laura Abbott :
> 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 fil
Hi Joe,
On Wed, Jul 11, 2018 at 7:24 PM Joe Perches wrote:
> On Wed, 2018-07-11 at 19:07 +0200, Geert Uytterhoeven wrote:
> > On Wed, Jul 11, 2018 at 6:20 PM Joe Perches wrote:
> > > On Wed, 2018-07-11 at 17:10 +0200, Geert Uytterhoeven wrote:
> > > > Print a warning if none of the Signed-off-by
On 12/07/18 08:52, Aapo Vienamo wrote:
> On Wed, 11 Jul 2018 16:26:42 +0100
> Jon Hunter wrote:
>
>> On 11/07/18 16:23, Jon Hunter wrote:
>>>
>>> On 11/07/18 15:01, Aapo Vienamo wrote:
Implement a function to query whether a pad is in deep power down mode.
>>> Can you elaborate on why
Hi Yu Chen,
Sorry for my delay...
On Fri, Jul 06, 2018 at 11:28:56PM +0800, Yu Chen wrote:
> Hi Joey Lee,
> On Fri, Jun 29, 2018 at 08:59:43PM +0800, joeyli wrote:
> > On Thu, Jun 28, 2018 at 10:52:07PM +0800, Yu Chen wrote:
> > > Hi,
> > > On Thu, Jun 28, 2018 at 10:28:56PM +0800, joeyli wrote:
On 11/07/18 15:39, Aapo Vienamo wrote:
> Add the missing linux/delay.h include statement for udelay() used by
> fence_udelay() macro.
>
> Signed-off-by: Aapo Vienamo
> Acked-by: Peter De Schrijver
> ---
> drivers/clk/tegra/clk.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/driver
On 11/07/18 15:39, Aapo Vienamo wrote:
> From: Peter De Schrijver
>
> Move this to a separate file so it can be used to calculate the sdmmc
> clock dividers.
>
> Signed-off-by: Peter De-Schrijver
> Signed-off-by: Aapo Vienamo
> Acked-by: Peter De Schrijver
> ---
> drivers/clk/tegra/Makefil
Hello,
Starting with 4.15 I noticed that BTS is sporadically missing the tail
of the trace in the perf_event data buffer. It shows as
[decode error (1): instruction overflow]
in GDB. Chances to see this are higher the longer the debuggee is
running. With this [1] tiny patch to one of GDB'
On Thu, 2018-07-12 at 12:03 +0200, Geert Uytterhoeven wrote:
> Print a warning if none of the Signed-off-by lines cover the patch
> author.
>
> Non-ASCII quoted printable encoding in From: headers and (lack of)
> double quotes are handled.
> Split From: headers are not fully handled: only the firs
> Op 12 jul. 2018, om 05:08 heeft Robert Nelson het
> volgende geschreven:
>
> On Wed, Jul 11, 2018 at 8:31 AM, Tony Lindgren wrote:
>> * Koen Kooi [180711 07:36]:
>>> +&cpu0_opp_table {
>>> + /*
>>> + * All PG 2.0 silicon may not support 1GHz but some of the early
>>> + * Bea
The offset needs to be added after reading the alarm value.
It also needs to be subtracted after the now < alarm test.
Tested-by: Jon Hunter
Signed-off-by: Alexandre Belloni
---
drivers/rtc/interface.c | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/drivers/rtc/inte
The "Beaglebone Enhanced" by Sancloud is based on the Beaglebone Black,
but with the following differences:
* Gigabit capable PHY
* Extra USB hub, optional i2c control
* lps3331ap barometer connected over i2c
* MPU6050 6 axis MEMS accelerometer/gyro connected over i2c
* 1GiB DDR3 RAM
* RTL87
The "Beaglebone Enhanced" by Sancloud is based on the Beaglebone Black,
but with the following differences:
* Gigabit capable PHY
* Extra USB hub, optional i2c control
* lps3331ap barometer connected over i2c
* MPU6050 6 axis MEMS accelerometer/gyro connected over i2c
* 1GiB DDR3 RAM
* RTL87
1 - 100 of 651 matches
Mail list logo
