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
---
drivers/thermal/qcom/tsens-v2.c | 6 +-
On Mon, Jul 2, 2018 at 11:23 PM, Eduardo Valentin wrote:
> On Mon, Jul 02, 2018 at 06:14:03PM +0530, Amit Kucheria wrote:
>> This series is a mixed bag:
>> - Some code moves to allow code sharing between various v2.x.y versions of
>> the TSENS IP,
>> - new qcom,tsens-v2.4.0 DT property for
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 something wrong.
On 5 July 2018 at 16:22, Stefan Agner wrote:
> On 05.07.2018 15:10, Ulf Hansson wrote:
>> On 4 July 2018 at 17:07, Stefan Agner wrote:
>>> If pinctrl nodes for 100/200MHz are missing, the controller should
>>> not select any mode which need signal frequencies 100MHz or higher.
>>> To prevent
Hi Andrew,
On Fri, Jul 06, 2018 at 05:30:49PM -0700, Andrew Morton wrote:
> On Tue, 19 Jun 2018 13:53:08 +0100 Will Deacon wrote:
>
> > In preparation for implementing the asm-generic atomic bitops in terms
> > of atomic_long_*, we need to prevent asm/atomic.h implementations from
> > pulling
On Mon, Jul 09, 2018 at 12:12:15PM +0100, David Woodhouse wrote:
> On Mon, 2018-07-09 at 13:06 +0200, Peter Zijlstra wrote:
> > On Mon, Jul 09, 2018 at 11:56:41AM +0100, David Woodhouse wrote:
> > > > But either proposal is exactly the same in this respect. The whole
> > > > rcu_urgent_qs thing
On 6 July 2018 at 09:19, Jisheng Zhang wrote:
> Add support for Synopsys SDHCI compatible DesignWare Cores Mobile
> Storage Host Controller which can support eMMC/SD/SDIO.
>
> Since v1:
> - move the dt bindings into a separate patch
>
> Jisheng Zhang (2):
> dt: bindings: Add bindings for
On 09/07/2018 11:05, Peter Zijlstra wrote:
> On Fri, Jul 06, 2018 at 06:13:11PM +0200, Thomas Gleixner wrote:
>> -native_write_msr(msr_kvm_wall_clock, low, high);
>> +wrmsrl(msr_kvm_wall_clock, slow_virt_to_phys(_clock));
> Does it matter that you went from an explicit native WRMSR
On 06-07-18, 06:47, Gustavo A. R. Silva wrote:
> Hi Vinod,
>
> On 07/06/2018 12:56 AM, Vinod wrote:
> > On 02-07-18, 13:06, Gustavo A. R. Silva wrote:
> >> In preparation to enabling -Wimplicit-fallthrough, mark switch cases
> >> where we are expecting to fall through.
> >>
> >> Signed-off-by:
Hello,
syzbot found the following crash on:
HEAD commit:d00d6d9a339d Add linux-next specific files for 20180709
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=10ad496840
kernel config: https://syzkaller.appspot.com/x/.config?x=94fe2b586beccacd
>
> On Wed, Jul 04, 2018 at 12:34:49PM +0300, Dan Carpenter wrote:
> > We accidentally removed the check for negative returns without
> > considering the issue of type promotion. The "if_version_length"
> > variable is type size_t so if __mei_cl_recv() returns a negative then
> > "bytes_recv" is
On Mon, Jul 9, 2018 at 4:57 PM, Amit Kucheria wrote:
> 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
> ---
>
On 3 July 2018 at 09:54, Rafael J. Wysocki wrote:
> On Tue, Jul 3, 2018 at 7:44 AM, Ulf Hansson wrote:
>> Rafael,
>>
>> On 20 June 2018 at 19:22, Ulf Hansson wrote:
>>> Changes in v8:
>>> - Added some tags for reviews and acks.
>>> - Cleanup timer patch (patch6) according to comments from
Also, you really should be sending this as a [PATCH v3] with a note
under the --- cut off that says "V3: fix From header, and indenting"
Google for how to send a v2 patch.
regards,
dan carpenter
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
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
---
drivers/thermal/qcom/tsens.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/thermal/qcom/tsens.h
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.
Fixing old DTs to split the address space into allows us to
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
---
drivers/thermal/qcom/Makefile
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
---
arch/arm64/boot/dts/qcom/sdm845.dtsi | 16
1 file changed, 16 insertions(+)
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
We also split up the regmap address space into two, one for the TM
registers, the other for the SROT registers. This was required to deal with
different address offsets for the TM and SROT registers across different
SoC families.
Since tsens-common.c/init_common() currently only registers one
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
---
drivers/thermal/qcom/tsens-v2.c | 6 +-
On Wed 2018-06-27 17:06:41, Petr Mladek wrote:
> On Tue 2018-06-26 10:39:59, Steven Rostedt wrote:
> > This looks fine. For proper history though, what I do in this case,
> > would be to make this into two patches. One with Namit's original
> > patch, and then a second that removes the code
Dirk Gouders writes:
> Dirk Gouders writes:
>
>> Masahiro Yamada writes:
>>
>>> syncconfig updates the .config only when sym_change_count > 0, i.e.
>>> any change in config symbols has been detected.
>>>
>>> Not only symbols but also comments are contained in the .config file.
>>> If only
On Monday, 9 July 2018 03:00:17 MSK Stephen Boyd wrote:
> Quoting Dmitry Osipenko (2018-06-17 07:55:37)
>
> > Kernel should never gate the EMC clock as it causes immediate lockup, so
> > removing clk-gate functionality doesn't affect anything. Turning EMC clk
> > gate into divider allows to
Hi Bo,
On 06/07/18 17:27, Bo Yan wrote:
Hi Robin, Luke,
Recently I bumped into an error when running GCC undefined behavior
sanitizer:
UBSAN: Undefined behaviour in
kernel-4.9/arch/arm64/include/asm/checksum.h:34:6
load of misaligned address ffc198c8b254 for type 'const
Hello,
syzbot found the following crash on:
HEAD commit:7f93d1295131 Merge git://git.kernel.org/pub/scm/linux/kern..
git tree: bpf
console output: https://syzkaller.appspot.com/x/log.txt?x=11bc56d040
kernel config: https://syzkaller.appspot.com/x/.config?x=2ca6c7a31d407f86
On 07/09/2018 04:25 AM, joakim.mis...@gmail.com wrote:
> From: Joakim Misund
>
> Issue:
> Currently TCP stack does not check for a destination specific CC before
> responding to a syn with a syn/ack.
> The system wide default CC is used. If the default CC does not need ECN, but
> the
On Mon, Jul 09, 2018 at 04:27:58PM +0530, Jaya Durga wrote:
> From: root
Again, wrong address :(
On Wed, Jun 27, 2018 at 1:49 PM Paul Cercueil wrote:
> The .gpio_set_direction() callback was setting inverted direction
> for SoCs older than the JZ4770, this restores the correct behaviour.
>
> Signed-off-by: Paul Cercueil
As you pointed out that this was an important fix I picked it
out and
On Fri, Jul 06, 2018 at 06:04:44PM +0100, Quentin Perret wrote:
> 'max_util' is basically the util we use to request an OPP. 'sum_util' is
> how long the CPUs will be running.
A indeed. But yes bit of a mess, but it wants doing I think.
Perhaps a little something like the below... The alternative
On Mon, Jul 09, 2018 at 05:31:04PM +0530, Rohit Kumar wrote:
> On 7/9/2018 4:44 PM, Mark Brown wrote:
> > On Fri, Jul 06, 2018 at 03:13:13PM +0530, Rohit kumar wrote:
> > > +static const struct component_master_ops sdm845_ops = {
> > > + .bind = sdm845_bind,
> > > + .unbind = sdm845_unbind,
> > >
On Mon, Jul 09, 2018 at 11:36:21AM +, Winkler, Tomas wrote:
> >
> > On Wed, Jul 04, 2018 at 12:34:49PM +0300, Dan Carpenter wrote:
> > > We accidentally removed the check for negative returns without
> > > considering the issue of type promotion. The "if_version_length"
> > > variable is
Hi Alexandre,
On 26/06/18 22:31, Alexandre Belloni wrote:
> On 26/06/2018 17:54:57+0100, Jon Hunter wrote:
>>
>> On 26/06/18 17:15, Alexandre Belloni wrote:
>>> Hi,
>>>
>>> On 26/06/2018 16:51:40+0100, Jon Hunter wrote:
> rtc: tps6586x: let the core handle rtc range
Sorry I am
Every time I tried to upgrade my laptop from 3.10.x to 4.x I faced an
issue by which the fan would run at full speed upon resume. Bisecting
it showed me the issue was introduced in 3.17 by commit 821d6f0359b0
(ACPI / sleep: Do not save NVS for new machines to accelerate S3). This
code only affects
On Mon, Jul 09, 2018 at 10:29:54AM +0100, John Whitmore wrote:
> On Sun, Jul 08, 2018 at 05:38:11PM +0200, Greg KH wrote:
> > On Sat, Jul 07, 2018 at 03:55:04PM +0100, John Whitmore wrote:
> > > Coding style change to simply remove the unrequired spaces before a
> > > closing
> > > brace or
Commit e501ce957a78 ("x86: Force asm-goto") bumped the minimum GCC
version to 4.5 for building the x86 kernel.
arch/x86/Makefile no longer needs to take care of older GCC versions.
Signed-off-by: Masahiro Yamada
---
arch/x86/Makefile | 5 -
1 file changed, 5 deletions(-)
diff --git
Hi folks,
On Wed, Jun 27, 2018 at 7:18 PM Andy Shevchenko
wrote:
> Even if GPIO and pin muxing has only one set of buffers to indicate
> input or output (same registers in use) it's a GPIO driver business to
> get direction from GPIO part of IP.
>
> Looking into the existing code I would rather
On 29/06/2018 23:11, Tony Krowiak wrote:
Provides the sysfs interfaces for assigning AP adapters to
and unassigning AP adapters from a mediated matrix device.
The IDs of the AP adapters assigned to the mediated matrix
device are stored in an AP mask (APM). The bits in the APM,
from most
+ Rafael
2018-07-09 13:17 GMT+02:00 Marek Szyprowski :
> Dear All,
>
> On 2018-07-05 19:55, Mark Brown wrote:
>> The patch
>>
>> regulator: core: Link consumer with regulator driver
>>
>> has been applied to the regulator tree at
>>
>>
On 29/06/2018 23:11, Tony Krowiak wrote:
Provides the sysfs interfaces for assigning AP domains to
and unassigning AP domains from a mediated matrix device.
An AP domain ID corresponds to an AP queue index (APQI). For
each domain assigned to the mediated matrix device, its
corresponging APQI is
Ping?
The logging here is very excessive. If not this change, then some
other change is needed to cut down on the sheer quantity of messages.
Thanks,
Jason
On Fri, Jun 22, 2018 at 12:25 PM, Jason Andryuk wrote:
> Commit ac75a041048b ("HID: i2c-hid: fix size check and type usage")
> started
On 09/07/2018 13:04:36+0100, Jon Hunter wrote:
> > Ok, I probably found the issue but the fix is not immediate. I'll try to
> > post something tomorrow.
>
> Sorry if I missed it, but did you send a fix for this?
>
Not yet, I'll keep you copied. I was missing the serial cable of my T20
board
On Thu, Jun 28, 2018 at 9:11 PM Paul Cercueil wrote:
> Sure, it'd be pretty straightforward to do it from the GPIO driver, but
> I'd still like to hear Linus' point of view about this.
I'm not sure about it, I guess it would be my second choice.
> As for merging pinctrl-ingenic.c and
From: Peter De-Schrijver
These clocks have low jitter paths to certain parents. To model these
correctly, use the sdmmc mux divider clock type.
Signed-off-by: Peter De-Schrijver
Signed-off-by: Aapo Vienamo
Acked-by: Peter De Schrijver
---
drivers/clk/tegra/clk-id.h | 2 --
Add the missing linux/delay.h include statement for udelay() used by
fence_udelay() macro.
Signed-off-by: Aapo Vienamo
---
drivers/clk/tegra/clk.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/clk/tegra/clk.h b/drivers/clk/tegra/clk.h
index e1f8846..e3b9c22 100644
---
From: Peter De-Schrijver
Add a clock type to model the sdmmc switch divider clocks which have paths
to source clocks bypassing the divider (Low Jitter paths). These
are handled by selecting the lj path when the divider is 1 (ie the
rate is the parent rate), otherwise the normal path with divider
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/Makefile | 1 +
drivers/clk/tegra/clk-divider.c | 30
Hi Sudeep,
On 2.5.2018 12:30, Sudeep Holla wrote:
> PSCI v1.1 introduced SYSTEM_RESET2 to allow both architectural resets
> where the semantics are described by the PSCI specification itself as
> well as vendor-specific resets. Currently only system warm reset
> semantics is defined as part of
From: Yandong Zhao
Dear Dave,
The scenario for this bug is:
The A process is sched out when the CPU0 executes the function
raw_cpu_read(kernel_neon_busy) and just gets the address of
kernel_neon_busy without reading.
The B process starts running kernel_neon_begin() on CPU0, and the variable
On 07/03/2018 01:05 PM, Eric Anholt wrote:
> Hi Florian,
>
> The following changes since commit ce397d215ccd07b8ae3f71db689aedb85d56ab40:
>
> Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)
>
> are available in the Git repository at:
>
> git://github.com/anholt/linux
cma_alloc() function doesn't really support gfp flags other than
__GFP_NOWARN, so convert gfp_mask parameter to boolean no_warn parameter.
This will help to avoid giving false feeling that this function supports
standard gfp flags and callers can pass __GFP_ZERO to get zeroed buffer,
what has
Dear All,
The CMA related functions cma_alloc() and dma_alloc_from_contiguous()
have gfp mask parameter, but sadly they only support __GFP_NOWARN flag.
This gave their users a misleading feeling that any standard memory
allocation flags are supported, what resulted in the security issue when
On 29/06/2018 23:11, Tony Krowiak wrote:
Provides a sysfs interface to view the AP matrix configured for the
mediated matrix device.
The relevant sysfs structures are:
/sys/devices/vfio_ap
... [matrix]
.. [mdev_supported_types]
. [vfio_ap-passthrough]
[devices]
On Sun, Jul 8, 2018 at 8:56 AM Leon Romanovsky wrote:
>
> On Fri, Jul 06, 2018 at 10:48:03PM +0200, Jann Horn wrote:
> > In general, accessing userspace memory beyond the length of the supplied
> > buffer in VFS read/write handlers can lead to both kernel memory corruption
> > (via
With old bindings imx_gpc_onecell_data always sets num_domains to 2 so
the DISPMIX domain can't actually be referenced. The pd is still defined
and pm core shuts it down as "unused" so display can't work.
Fix this by converting to new gpc bindings by adding pgc nodes and
referencing the
Right now the imx6sl display power domain is automatically shut down
during boot so lcd doesn't work at all. This has been broken for a while
with old gpc bindings, since nobody noticed fix by converting to new
bindings.
Link to v1: https://lkml.org/lkml/2018/6/5/689
There is also a nasty errata
The imx6sl chip errata document describes ERR006287 like this:
"""
Upon resuming from power gating, the modules in the display power domain
(eLCDIF, EPDC, PXP and SPDC) might fail to perform register reads
correctly.
When the modules listed above are used, do not use power gating on the
display
Hi,
On Mon, Jul 09, 2018 at 02:46:28PM +0530, Bhushan Shah wrote:
> The kernel would not boot on the hammerhead hardware due to the
> following error:
>
> mmc0: Timeout waiting for hardware interrupt.
> mmc0: sdhci: SDHCI REGISTER DUMP ===
> mmc0: sdhci: Sys addr:
On 07/03/2018 01:05 PM, Eric Anholt wrote:
> The following changes since commit ce397d215ccd07b8ae3f71db689aedb85d56ab40:
>
> Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)
>
> are available in the Git repository at:
>
> git://github.com/anholt/linux tags/bcm2835-defconfig-64-next-2018-07-03
On 07/03/2018 01:05 PM, Eric Anholt wrote:
> The following changes since commit ce397d215ccd07b8ae3f71db689aedb85d56ab40:
>
> Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)
>
> are available in the Git repository at:
>
> git://github.com/anholt/linux tags/bcm2835-defconfig-next-2018-07-03
>
On Mon, Jul 09, 2018 at 10:31:18AM +0200, Peter Zijlstra wrote:
> On Mon, Jul 09, 2018 at 02:57:25AM +0200, Eugeniu Rosca wrote:
> > diff --git a/include/linux/lockdep.h b/include/linux/lockdep.h
> > index 6fc77d4dbdcd..eeed7ea2e198 100644
> > --- a/include/linux/lockdep.h
> > +++
On 07/03/2018 01:05 PM, Eric Anholt wrote:
> The following changes since commit ce397d215ccd07b8ae3f71db689aedb85d56ab40:
>
> Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)
>
> are available in the Git repository at:
>
> git://github.com/anholt/linux tags/bcm2835-drivers-next-2018-07-03
>
>
On Mon, Jul 09, 2018 at 02:13:35PM +0200, Benjamin Gaignard wrote:
> 2018-07-09 13:17 GMT+02:00 Marek Szyprowski :
> > [ cut here ]
> > WARNING: CPU: 1 PID: 1 at drivers/base/core.c:108
> > device_is_dependent+0xa4/0xb4
> > Modules linked in:
> > CPU: 1 PID: 1 Comm:
On Fri, 22 Jun 2018, Jason Andryuk wrote:
> Commit ac75a041048b ("HID: i2c-hid: fix size check and type usage")
> started writing messages when the ret_size is <= 2 from i2c_master_recv.
> However, my device i2c-DLL07D1 returns 2 for a short period of time
> (~0.5s) after I stop moving the
On 09/07/18 12:23, Dave Martin wrote:
> On Fri, Jul 06, 2018 at 05:39:00PM +0100, Suzuki K Poulose wrote:
>> On 07/06/2018 04:09 PM, Marc Zyngier wrote:
>>> On 06/07/18 14:49, Suzuki K Poulose wrote:
On 04/07/18 23:03, Suzuki K Poulose wrote:
> On 07/04/2018 04:51 PM, Will Deacon 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; otherwise
> there's a double free of
On Mon, Jul 09, 2018 at 01:06:57PM +0200, Peter Zijlstra wrote:
> On Mon, Jul 09, 2018 at 11:56:41AM +0100, David Woodhouse wrote:
>
> > > But either proposal is exactly the same in this respect. The whole
> > > rcu_urgent_qs thing won't be set any earlier either.
> >
> > Er Marius, our
On 09/07/18 12:14, Mark Brown wrote:
+static const struct component_master_ops sdm845_ops = {
+ .bind = sdm845_bind,
+ .unbind = sdm845_unbind,
+};
Why is this using the component stuff rather than the normal support for
finding the components of audio cards?
Could you elaborate
On Fri 06-07-18 17:05:39, David Rientjes wrote:
[...]
> Blockable mmu notifiers and mlocked memory is not the extent of the
> problem, if a process has a lot of virtual memory we must wait until
> free_pgtables() completes in exit_mmap() to prevent unnecessary oom
> killing. For
On 09/07/18 13:17, Michal Simek wrote:
> Hi Sudeep,
>
> On 2.5.2018 12:30, Sudeep Holla wrote:
>> PSCI v1.1 introduced SYSTEM_RESET2 to allow both architectural resets
>> where the semantics are described by the PSCI specification itself as
>> well as vendor-specific resets. Currently only
On Mon, Jul 09, 2018 at 01:34:42PM +0100, Srinivas Kandagatla wrote:
> On 09/07/18 12:14, Mark Brown wrote:
> > > +static const struct component_master_ops sdm845_ops = {
> > > + .bind = sdm845_bind,
> > > + .unbind = sdm845_unbind,
> > > +};
> > Why is this using the component stuff rather than
On Mon, 2018-07-09 at 05:34 -0700, Paul E. McKenney wrote:
> The reason that David's latencies went from 100ms to one second is
> because I made this code less aggressive about invoking resched_cpu().
Ten seconds. We saw synchronize_sched() take ten seconds in 4.15. We
wouldn't have been happy
On 09/07/18 13:41, Mark Brown wrote:
This is not the case, the card will be unbound at the ASoC level when
any of the components are removed and then probed again when they
reappear.
I will give that a try now!
--srini
From: root
CHECK: Macro argument reuse 'gdm' - possible side-effects?
convert GDM_TTY_READY to gdm_tty_ready static function
to fix checkpath check
Signed-off-by: Jaya Durga
---
drivers/staging/gdm724x/gdm_tty.c | 14 +-
1 file changed, 9 insertions(+), 5 deletions(-)
diff --git
Linus,
please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git for-linus
to receive HID subsystem fixes:
=
- spectrev1 pattern fix in hiddev from Gustavo A. R. Silva
- Bounds check fix for hid-debug from Daniel Rosenberg
- Regression fix for HID autobinding from
In some cases a device may end up supplying itself, for example when a
DCDC is used to improve the efficiency of LDOs or when a LDO is provided
to clean up sensitive supplies. In these cases the driver core will
warn loudly about attempts to add links so suppress them here.
Reported-by: Marek
Hello Matthew,
It seems to me that there are other locations which do not check xas_store()
failure. Is that really OK? If they are OK, I think we want a comment like
/* This never fails. */ or /* Failure is OK because ... */
for each call without failure check.
>From
On Mon, Jul 09, 2018 at 05:34:57AM -0700, Paul E. McKenney wrote:
> But KVM defeats this by checking need_resched() before invoking
> cond_resched().
That's not wrong or even uncommon I think.
On Wed, 2018-07-04 at 18:54 +0200, Jerome Brunet wrote:
> Jerome Brunet (3):
> clk: meson: gxbb: remove HHI_GEN_CLK_CTNL duplicate definition
> clk: meson: expose GEN_CLK clkid
> clk: meson: add gen_clk
Applied
I don't understand why you have sent this patch four times.
Are you a script which has a bug? Please answer us so that we know you
are a human being.
regards,
dan carpenter
On Mon, 2018-07-09 at 14:55 +0200, Peter Zijlstra wrote:
> On Mon, Jul 09, 2018 at 05:34:57AM -0700, Paul E. McKenney wrote:
> > But KVM defeats this by checking need_resched() before invoking
> > cond_resched().
>
> That's not wrong or even uncommon I think.
Right. Which is precisely why I
On Thu, Jul 5, 2018 at 11:10 AM Tony Lindgren wrote:
> Here is a resend of fixes for a race issues for generic group and
> functions reported by H. Nikolaus Schaller .
I applied these 5 for fixes (no choice I guess) will push them to the
zeroday build for testing and then to next. Added the
On Mon, Jul 09, 2018 at 02:55:16PM +0200, Peter Zijlstra wrote:
> On Mon, Jul 09, 2018 at 05:34:57AM -0700, Paul E. McKenney wrote:
> > But KVM defeats this by checking need_resched() before invoking
> > cond_resched().
>
> That's not wrong or even uncommon I think.
In fact, I think we recently
Hi ,
I have updated the patch --subject-prefix="PATCH v3" and made the
commit as per your suggestion ,
i don't know why does the script doesn't update my changes,will try to
sort out the issue ,
sorry for the inconvenience.
Regards,
Jaya Durga
On Mon, Jul 9, 2018 at 6:26 PM, Dan Carpenter
On Tue, Jul 3, 2018 at 3:22 AM Anson Huang wrote:
> Some i.MX SoCs have GPIO clock gate in CCM, accessing
> GPIO registers needs to enable GPIO clock gate first,
> i.MX GPIO driver will enable clock gate if there is
> clock property in GPIO node of dtb, add optional property
> to i.MX GPIO
* Linus Walleij [180709 13:02]:
> On Thu, Jul 5, 2018 at 11:10 AM Tony Lindgren wrote:
>
> > Here is a resend of fixes for a race issues for generic group and
> > functions reported by H. Nikolaus Schaller .
>
> I applied these 5 for fixes (no choice I guess) will push them to the
> zeroday
On 9.7.2018 14:36, Sudeep Holla wrote:
>
>
> On 09/07/18 13:17, Michal Simek wrote:
>> Hi Sudeep,
>>
>> On 2.5.2018 12:30, Sudeep Holla wrote:
>>> PSCI v1.1 introduced SYSTEM_RESET2 to allow both architectural resets
>>> where the semantics are described by the PSCI specification itself as
>>>
On Wed, Jul 4, 2018 at 12:18 AM Janusz Krzysztofik wrote:
> Avoid replication of error code conversion in non-DT GPIO consumers'
> code by returning -EPROBE_DEFER from gpiod_find() in case a chip
> identified by its label in a registered lookup table is not ready.
>
> See
From: Peter Zijlstra
> Sent: 09 July 2018 09:50
> On Sat, Jul 07, 2018 at 10:54:28PM +0900, Tetsuo Handa wrote:
> > >> Since syzbot is confused by concurrent printk() messages [1],
> > >> this patch changes show_opcodes() to use snprintf().
snprintf() is probably the wrong function.
You want the
On Tue, Jul 3, 2018 at 7:35 AM Ulf Hansson wrote:
> On 3 July 2018 at 04:25, Fabio Estevam wrote:
> > On Mon, Jul 2, 2018 at 11:13 PM, Anson Huang wrote:
> >
> >> I think either way is OK, since flexible array is used in kernel code
> >> quite commonly,
> >> so I prefer to make code change as
Make use of the swap macro and remove unnecessary variable *tmp*.
This makes the code easier to read and maintain. Also, reduces the
stack usage.
This code was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
fs/ext4/move_extent.c | 4 +---
1 file changed, 1
On 09/07/18 14:13, Michal Simek wrote:
> On 9.7.2018 14:36, Sudeep Holla wrote:
>>
>>
>> On 09/07/18 13:17, Michal Simek wrote:
>>> Hi Sudeep,
>>>
>>> On 2.5.2018 12:30, Sudeep Holla wrote:
PSCI v1.1 introduced SYSTEM_RESET2 to allow both architectural resets
where the semantics are
Hello,
syzbot found the following crash on:
HEAD commit:d00d6d9a339d Add linux-next specific files for 20180709
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1414611c40
kernel config: https://syzkaller.appspot.com/x/.config?x=94fe2b586beccacd
On Wed 2018-06-27 16:08:14, Petr Mladek wrote:
> The commit 719f6a7040f1bdaf96 ("printk: Use the main logbuf in NMI
> when logbuf_lock is available") brought back the possible deadlocks
> in printk() and NMI.
>
> This is rework of the proposed fix, see
>
On Sun, Jul 08, 2018 at 03:29:00PM +0200, Greg Kroah-Hartman wrote:
> On Sat, Jul 07, 2018 at 02:39:38PM -0700, Guenter Roeck wrote:
> > On Fri, Jul 06, 2018 at 07:46:24AM +0200, Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 4.14.54 release.
> > > There are
On 06.07.2018 22:39, Alexandre Belloni wrote:
Hi Codrin,
On 18/06/2018 17:12:38+0300, Codrin Ciubotariu wrote:
From: Cyrille Pitchen
This patch adds DT nodes for I2S0 and I2S1. It also adds an alias for
each I2S node.
Signed-off-by: Cyrille Pitchen
[codrin.ciubota...@microchip.com: added
On Mon, Jul 9, 2018 at 3:25 PM, syzbot
wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:d00d6d9a339d Add linux-next specific files for 20180709
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=1414611c4
On Mon, Jul 09, 2018 at 09:55:17PM +0900, Tetsuo Handa wrote:
> Hello Matthew,
>
> It seems to me that there are other locations which do not check xas_store()
> failure. Is that really OK? If they are OK, I think we want a comment like
> /* This never fails. */ or /* Failure is OK because ... */
Hi Mark,
On 2018-07-09 14:54, Mark Brown wrote:
> In some cases a device may end up supplying itself, for example when a
> DCDC is used to improve the efficiency of LDOs or when a LDO is provided
> to clean up sensitive supplies. In these cases the driver core will
> warn loudly about attempts
1001 - 1100 of 1608 matches
Mail list logo
