Use [ ! -z "$VAR" ] instead of [ "$VAR" ] to check
whether the given string variable is not zero-length
since it obviously shows what it means.
Signed-off-by: Masami Hiramatsu
---
tools/testing/selftests/ftrace/ftracetest |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff
On Thu 2017-07-06 10:01:32, Thierry Reding wrote:
> On Fri, Jun 30, 2017 at 01:21:07PM +0200, Enric Balletbo i Serra wrote:
> > From: huang lin
> >
> > Some panels (i.e. N116BGE-L41), in their power sequence specifications,
> > request a delay between set the PWM signal and enable the backlight
iov_iter/uaccess/hardening pile. For one thing, it trims the
inline part of copy_to_user/copy_from_user to the minimum that *does*
need to be inlined - object size checks, basically. For another,
it sanitizes the checks for iov_iter primitives. There are 4 groups
of checks: access_ok(),
On Thu, Jul 06, 2017 at 08:31:07AM +, Naoya Horiguchi wrote:
>Hi Baoquan, everyone,
>
>I'm also interested in KASLR/EFI related issue (but not the same issue
>with yours, so I separated the thread.)
>
>This patch is based on Baoquan's recent patches[1], adding more code
>on the new function
On Tue, Jun 27, 2017 at 12:05:22PM +0200, Alvaro Gamez Machado wrote:
> This patch adds support for the IP core provided by Xilinx.
> This IP core can function as a two independent timers, but can also use
> both counters as values for period and duty cycle of a PWM output.
>
> Signed-off-by:
Hi Andy,
On 四, 7月 06, 2017 at 12:00:29下午 +0300, Andy Shevchenko wrote:
> On Thu, Jul 6, 2017 at 11:47 AM, Baolin Wang
> wrote:
> > This patch adds the I2C controller driver for Spreadtrum SC9860 platform.
> >
>
> Reviewed-by: Andy Shevchenko
>
> P.S. There is still room for improvement,
If CONFIG_CORESIGHT is disable, it'll through compilation error.
drivers/hwtracing/coresight/coresight-etm-perf.c:462:5: error: redefinition of
‘etm_perf_symlink’
int etm_perf_symlink(struct coresight_device *csdev, bool link)
^
In file included from
On Thu, 2017-07-06 at 17:01 +0800, Lin Zhang wrote:
> In the pull_pages code block, if the first frags size > eat,
> we can end the loop in advance to avoid extra copy.
>
> Signed-off-by: Lin Zhang
> ---
> net/core/skbuff.c | 4
> 1 file changed, 4 insertions(+)
>
> diff --git
On 06/07/17 10:12, Pavel Machek wrote:
On Thu 2017-07-06 10:01:32, Thierry Reding wrote:
On Fri, Jun 30, 2017 at 01:21:07PM +0200, Enric Balletbo i Serra wrote:
From: huang lin
Some panels (i.e. N116BGE-L41), in their power sequence specifications,
request a delay between set the PWM signal
On Thu, Jul 06, 2017 at 11:02:20AM +0200, Jerome Brunet wrote:
> On Thu, 2017-07-06 at 08:59 +0200, Thierry Reding wrote:
> > On Thu, Jun 08, 2017 at 02:24:13PM +0200, Jerome Brunet wrote:
> > > The pwms found in the AO domain of the meson gx family have different
> > > clock sources than the ones
Hi Naoya Horiguchi,
Thanks for making this!
On 07/06/17 at 08:31am, Naoya Horiguchi wrote:
> Hi Baoquan, everyone,
>
> I'm also interested in KASLR/EFI related issue (but not the same issue
> with yours, so I separated the thread.)
>
> This patch is based on Baoquan's recent patches[1], adding
Hi Jassi,
On 06/07/17 07:28, Jassi Brar wrote:
> On Wed, Jul 5, 2017 at 11:32 PM, Sudeep Holla wrote:
>
>>
>> I have posted the SCMI patches now[1],
>>
> I wish I was CC'ed on that. Now LKML seems too busy to forward it.
>
Yes, my mistake, I should have cc-ed you.
>> please let me know how
From: Jun-Ru Chang
Commit b87281e7f205 ("irqchip/mips-gic: Remove device IRQ domain")
removes the device IRQ domain and uses gic_irq_domain_alloc() to
allocate the shared/local domain. However, the shared interrupt handler
is not set after allocating. It causes that the system hangs with
On Thu, Jul 06, 2017 at 07:29:32AM +0530, yash007 wrote:
> From: Yash Omer
>
Send your patch to yourself until you figure out the right format then
send it to the list.
regards,
dan carpenter
On Thu, 2017-07-06 at 02:16 -0700, Eric Dumazet wrote:
> On Thu, 2017-07-06 at 17:01 +0800, Lin Zhang wrote:
> > In the pull_pages code block, if the first frags size > eat,
> > we can end the loop in advance to avoid extra copy.
> >
> > Signed-off-by: Lin Zhang
> > ---
> > net/core/skbuff.c |
On Thu, Jul 06, 2017 at 05:13:32PM +0800, Chao Fan wrote:
> On Thu, Jul 06, 2017 at 08:31:07AM +, Naoya Horiguchi wrote:
> >Hi Baoquan, everyone,
> >
> >I'm also interested in KASLR/EFI related issue (but not the same issue
> >with yours, so I separated the thread.)
> >
> >This patch is based
On Thu, Jul 06, 2017 at 10:17:18AM +0100, Daniel Thompson wrote:
> On 06/07/17 10:12, Pavel Machek wrote:
> > On Thu 2017-07-06 10:01:32, Thierry Reding wrote:
> > > On Fri, Jun 30, 2017 at 01:21:07PM +0200, Enric Balletbo i Serra wrote:
> > > > From: huang lin
> > > >
> > > > Some panels (i.e.
On Thu, Jul 6, 2017 at 2:48 PM, Sudeep Holla wrote:
> Hi Jassi,
>
> On 06/07/17 07:28, Jassi Brar wrote:
>> On Wed, Jul 5, 2017 at 11:32 PM, Sudeep Holla wrote:
>>
>>>
>>> I have posted the SCMI patches now[1],
>>>
>> I wish I was CC'ed on that. Now LKML seems too busy to forward it.
>>
>
> Yes,
On Wed, Jul 6, 2017 at 10:49 AM, Sergey Senozhatsky wrote:
> On (07/02/17 20:28), Seth Jennings wrote:
>> On Sun, Jul 2, 2017 at 9:19 AM, Srividya Desireddy
>> > Zswap is a cache which compresses the pages that are being swapped out
>> > and stores them into a dynamically allocated RAM-based
Hello,
On Thu, Jul 06, 2017 at 09:45:13AM +0200, Christoffer Dall wrote:
> Let's look at the callers to stage2_get_pmd, which is the only caller of
> stage2_get_pud, where the problem was observed:
>
> user_mem_abort
>-> stage2_set_pmd_huge
> -> stage2_get_pmd
>
> user_mem_abort
On 06/07/17 10:27, Jassi Brar wrote:
> On Thu, Jul 6, 2017 at 2:48 PM, Sudeep Holla wrote:
>> Hi Jassi,
>>
>> On 06/07/17 07:28, Jassi Brar wrote:
>>> On Wed, Jul 5, 2017 at 11:32 PM, Sudeep Holla wrote:
>>>
I have posted the SCMI patches now[1],
>>> I wish I was CC'ed on that.
On Wed, Jul 05, 2017 at 11:55:09PM +0800, Lynn Lei wrote:
> Fixed a of_device_id structure normally be const warning issue which
> checked by scripts/checkpatch.pl:
> WARNING: struct of_device_id should normally be const
>
> Signed-off-by: Lynn Lei
> ---
> drivers/video/backlight/pwm_bl.c | 2
On 06/07/17 08:45, Christoffer Dall wrote:
On Thu, Jul 06, 2017 at 09:07:49AM +0200, Alexander Graf wrote:
On 05.07.17 10:57, Suzuki K Poulose wrote:
Hi Alex,
On Wed, Jul 05, 2017 at 08:20:31AM +0200, Alexander Graf wrote:
The kvm_age_hva callback may be called all the way concurrently
2017-07-06 17:23 GMT+08:00 Eric Dumazet :
> On Thu, 2017-07-06 at 02:16 -0700, Eric Dumazet wrote:
>> On Thu, 2017-07-06 at 17:01 +0800, Lin Zhang wrote:
>> > In the pull_pages code block, if the first frags size > eat,
>> > we can end the loop in advance to avoid extra copy.
>> >
>> >
On Thu, Jul 06, 2017 at 05:18:09PM +0800, Baoquan He wrote:
> Hi Naoya Horiguchi,
>
> Thanks for making this!
>
> On 07/06/17 at 08:31am, Naoya Horiguchi wrote:
> > Hi Baoquan, everyone,
> >
> > I'm also interested in KASLR/EFI related issue (but not the same issue
> > with yours, so I
From: Sricharan R
Finally add the device link between the master device and
smmu, so that the smmu gets runtime enabled/disabled only when the
master needs it. This is done from add_device callback which gets
called once when the master is added to the smmu.
Signed-off-by: Sricharan R
---
fwspec->iommu_priv is available only after arm_smmu_master_cfg
instance has been allocated. We shouldn't free it before that.
Also it's logical to free the master cfg itself without
checking for fwspec.
Signed-off-by: Vivek Gautam
---
drivers/iommu/arm-smmu.c | 6 +++---
1 file changed, 3
From: Sricharan R
The smmu device probe/remove and add/remove master device callbacks
gets called when the smmu is not linked to its master, that is without
the context of the master device. So calling runtime apis in those places
separately.
Signed-off-by: Sricharan R
[stanimir: added runtime
This series provides the support for turning on the arm-smmu's
clocks/power domains using runtime pm. This is done using the
recently introduced device links patches, which lets the symmu's
runtime to follow the master's runtime pm, so the smmu remains
powered only when the masters use it.
Took
From: Sricharan R
The smmu needs to be functional only when the respective
master's using it are active. The device_link feature
helps to track such functional dependencies, so that the
iommu gets powered when the master device enables itself
using pm_runtime. So by adapting the smmu driver for
qcom,msm8996-smmu-v2 is an arm,smmu-v2 implementation with
specific clock and power requirements. This smmu core is used
with multiple masters on msm8996, viz. mdss, video, etc.
Add bindings for the same.
Signed-off-by: Vivek Gautam
---
Documentation/devicetree/bindings/iommu/arm,smmu.txt | 18
From: Sricharan R
The MMU400x/500 is the implementation of the SMMUv2
arch specification. It is split in to two blocks
TBU, TCU. TBU caches the page table, instantiated
for each master locally, clocked by the TBUn_clk.
TCU manages the address translation with PTW and has
the programming
On Thu, Jul 06, 2017 at 09:22:38AM +, Naoya Horiguchi wrote:
>On Thu, Jul 06, 2017 at 05:13:32PM +0800, Chao Fan wrote:
>> On Thu, Jul 06, 2017 at 08:31:07AM +, Naoya Horiguchi wrote:
>> >Hi Baoquan, everyone,
>> >
>> >I'm also interested in KASLR/EFI related issue (but not the same issue
On Thu, Jul 06, 2017 at 10:34:58AM +0100, Suzuki K Poulose wrote:
> On 06/07/17 08:45, Christoffer Dall wrote:
> >On Thu, Jul 06, 2017 at 09:07:49AM +0200, Alexander Graf wrote:
> >>
> >>
> >>On 05.07.17 10:57, Suzuki K Poulose wrote:
> >>>Hi Alex,
> >>>
> >>>On Wed, Jul 05, 2017 at 08:20:31AM
Instead of adding a binary sysfs attribute from the driver (which suffers
from a race condition as the attribute appears after the device), use the
core to register an nvmem device.
Signed-off-by: Alexandre Belloni
---
drivers/rtc/rtc-ds1307.c | 88
This removes a possible race condition and crash and allows for further
improvement of the driver.
Signed-off-by: Alexandre Belloni
---
drivers/rtc/rtc-ds1307.c | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/drivers/rtc/rtc-ds1307.c b/drivers/rtc/rtc-ds1307.c
index
Create rtc_allocate_device to allocate memory for a struct rtc_device and
initialize it.
Signed-off-by: Alexandre Belloni
---
drivers/rtc/class.c | 63 +++--
1 file changed, 37 insertions(+), 26 deletions(-)
diff --git a/drivers/rtc/class.c
Many RTCs have an on board non volatile storage. It can be battery backed
RAM or an EEPROM. Use the nvmem subsystem to export it to both userspace
and in-kernel consumers.
This stays compatible with the previous (non documented) ABI that was using
/sys/class/rtc/rtcx/device/nvram to export that
ds1307_remove() is now empty, remove it
Signed-off-by: Alexandre Belloni
---
drivers/rtc/rtc-ds1307.c | 6 --
1 file changed, 6 deletions(-)
diff --git a/drivers/rtc/rtc-ds1307.c b/drivers/rtc/rtc-ds1307.c
index 6f91c11a5f03..ea83ddc5a513 100644
--- a/drivers/rtc/rtc-ds1307.c
+++
rv8803_remove() is now empty, remove it.
Signed-off-by: Alexandre Belloni
---
drivers/rtc/rtc-rv8803.c | 6 --
1 file changed, 6 deletions(-)
diff --git a/drivers/rtc/rtc-rv8803.c b/drivers/rtc/rtc-rv8803.c
index 10474ab7887d..aae2576741a6 100644
--- a/drivers/rtc/rtc-rv8803.c
+++
Sorry for noise. Please ignore this patch.
On Thursday 06 July 2017 02:45 PM, Arvind Yadav wrote:
If CONFIG_CORESIGHT is disable, it'll through compilation error.
drivers/hwtracing/coresight/coresight-etm-perf.c:462:5: error: redefinition of
‘etm_perf_symlink’
int etm_perf_symlink(struct
There are multiple race condition issues in the RTC drivers. It is
especially apparent in the IRQ handling and additionnal sysfs attributes
registration.
To solve most of those and allow to extend the framework more easily,
introduce a new registration method that allows to first allocate an
Hi Andrea,
On Thu, Jul 06, 2017 at 11:31:26AM +0200, Andrea Arcangeli wrote:
> Hello,
>
> On Thu, Jul 06, 2017 at 09:45:13AM +0200, Christoffer Dall wrote:
> > Let's look at the callers to stage2_get_pmd, which is the only caller of
> > stage2_get_pud, where the problem was observed:
> >
> >
Instead of adding a binary sysfs attribute from the driver (which suffers
from a race condition as the attribute appears after the device), use the
core to register an nvmem device.
Signed-off-by: Alexandre Belloni
---
drivers/rtc/rtc-rv8803.c | 51
This removes a possible race condition and allows for further improvement
of the driver.
Signed-off-by: Alexandre Belloni
---
drivers/rtc/rtc-rv8803.c | 15 +--
1 file changed, 9 insertions(+), 6 deletions(-)
diff --git a/drivers/rtc/rtc-rv8803.c b/drivers/rtc/rtc-rv8803.c
index
Sorry for noise. Please ignore this patch
Thanks
~arvind
On Thursday 06 July 2017 02:35 PM, Arvind Yadav wrote:
If CONFIG_RMI4_F34 is disable, it'll through compilation error.
drivers/input/rmi4/rmi_f34.c:594:5: error: redefinition of
‘rmi_f34_create_sysfs’
int rmi_f34_create_sysfs(struct
Create rtc_device_get_id to allocate the id for an RTC.
Signed-off-by: Alexandre Belloni
---
drivers/rtc/class.c | 44 +---
1 file changed, 25 insertions(+), 19 deletions(-)
diff --git a/drivers/rtc/class.c b/drivers/rtc/class.c
index
While highly unlikely, it is possible to get an interrupt as soon as it is
requested. In that case, at91_rtc_interrupt() will be called with rtc ==
NULL.
Solve that by using devm_rtc_allocate_device/rtc_register_device.
Signed-off-by: Alexandre Belloni
---
drivers/rtc/rtc-at91rm9200.c | 14
From: Corentin Labbe
Date: Thu, 6 Jul 2017 10:51:47 +0200
> On Sun, Jul 02, 2017 at 02:31:59PM +0200, Corentin Labbe wrote:
>> Since internal phy-mode is reserved for non-xMII protocol we cannot use
>> it with dwmac-sun8i
>> This reverts commit 1c2fa5f84683 ("net: stmmac: support future possible
Introduce rtc_register_device() to register an already allocated and
initialized struct rtc_device. It automatically sets up the owner and the
two steps allocation/registration will allow to remove race conditions in
the IRQ handling of some driver. It also allows to properly extend the core
On 06.07.2017 11:04, Peter Zijlstra wrote:
> On Mon, Jun 19, 2017 at 09:02:26PM +0300, Kirill Tkhai wrote:
>
>> Subject: [PATCH 2/7] rwsem-spinlock: Add killable versions of
>> rwsem_down_read_failed()
>
>> kernel/locking/rwsem-xadd.c | 33 ++---
>
> Fixed that
On Thu, 2017-07-06 at 17:35 +0800, lin zhang wrote:
> thanks, i am a newer, "net-next is closed" it means i need repost it
> after net-next reopened?
Yes, please read Documentation/networking/netdev-FAQ.txt for details.
If NO_DMA=y:
ERROR: "usb_gadget_map_request" [drivers/usb/gadget/udc/renesas_usb3.ko]
undefined!
ERROR: "usb_gadget_unmap_request" [drivers/usb/gadget/udc/renesas_usb3.ko]
undefined!
ERROR: "bad_dma_ops" [drivers/usb/gadget/udc/renesas_usb3.ko] undefined!
Add a dependency on
If NO_DMA=y:
ERROR: "usb_gadget_map_request" [drivers/usb/gadget/udc/snps_udc_core.ko]
undefined!
ERROR: "dma_pool_destroy" [drivers/usb/gadget/udc/snps_udc_core.ko]
undefined!
ERROR: "usb_gadget_unmap_request" [drivers/usb/gadget/udc/snps_udc_core.ko]
undefined!
ERROR:
A frequency-invariant load-tracking solution based on cpufreq transition
notifier will not work for future fast frequency switching policies.
That is why a different solution is presented with this patch.
Let cpufreq call the function arch_set_freq_scale() to pass the current
frequency, the max
Free cpumask cpus_to_visit in case registering
init_cpu_capacity_notifier has failed or the parsing of the cpu
capacity-dmips-mhz property is done. The cpumask cpus_to_visit is
only used inside the notifier call init_cpu_capacity_callback.
Cc: Greg Kroah-Hartman
Cc: Juri Lelli
Reported-by:
Define arch_set_freq_scale to be the arch_topology "driver" function
topology_set_freq_scale() to let FIE work correctly.
Cc: Russell King
Cc: Juri Lelli
Signed-off-by: Dietmar Eggemann
---
arch/arm/include/asm/topology.h | 5 +
arch/arm/kernel/topology.c | 1 -
2 files changed, 5
Commit dfbca41f3479 ("sched: Optimize freq invariant accounting")
changed the wiring which now has to be done by associating
arch_scale_freq_capacity with the actual implementation provided
by the architecture.
Define arch_scale_freq_capacity to use the arch_topology "driver"
function
To speed up the cpu- and frequency-invariant accounting of the task
scheduler make sure that the CIE (topology_get_cpu_scale()) and FIE
(topology_get_freq_scale() get completely inlined into the task
scheduler consumer functions (e.g. __update_load_avg_se()).
This patch-set changes the interface
Commit 8cd5601c5060 ("sched/fair: Convert arch_scale_cpu_capacity() from
weak function to #define") changed the wiring which now has to be done
by associating arch_scale_cpu_capacity with the actual implementation
provided by the architecture.
Define arch_scale_cpu_capacity to use the
Commit 8cd5601c5060 ("sched/fair: Convert arch_scale_cpu_capacity() from
weak function to #define") changed the wiring which now has to be done
by associating arch_scale_cpu_capacity with the actual implementation
provided by the architecture.
Define arch_scale_cpu_capacity to use the
Commit dfbca41f3479 ("sched: Optimize freq invariant accounting")
changed the wiring which now has to be done by associating
arch_scale_freq_capacity with the actual implementation provided
by the architecture.
Define arch_scale_freq_capacity to use the arch_topology "driver"
function
Define arch_set_freq_scale to be the arch_topology "driver" function
topology_set_freq_scale() to let FIE work correctly.
Cc: Catalin Marinas
Cc: Will Deacon
Cc: Juri Lelli
Signed-off-by: Dietmar Eggemann
---
arch/arm64/include/asm/topology.h | 5 +
arch/arm64/kernel/topology.c | 1
For a more accurate (i.e. frequency- and cpu-invariant) load-tracking
the task scheduler needs a frequency-scaling and on a heterogeneous
system a cpu-scaling correction factor.
This patch-set implements a Frequency Invariance Engine (FIE)
(topology_get_freq_scale()) in
Implements an arch-specific frequency-scaling function
topology_get_freq_scale() which provides the following frequency
scaling factor:
current_freq(cpu) << SCHED_CAPACITY_SHIFT / max_supported_freq(cpu)
One possible consumer of this is the Per-Entity Load Tracking (PELT)
mechanism of the task
On 07/04/2017 06:04 PM, Georgi Djakov wrote:
As there is no way to actually query the hardware for the current clock
rate, now racalc_rate() just returns the last rate that was previously
set. But if the rate was not set yet, we return the bogus rate of 1KHz.
Knowing what the rate of XO is
Em Wed, 5 Jul 2017 14:22:35 -0700
Jim Davis escreveu:
> On Mon, Jul 3, 2017 at 5:44 AM, Jonathan Corbet wrote:
> > On Mon, 3 Jul 2017 10:25:38 +0200
> > Daniel Vetter wrote:
> >
> >> Only now stumbled over the full thread, but the drm patch is already
> >> queued up for at least 4.13 (Dave
> Hi Meelis,
>
> can you try the patch below?
Yes, the OOPS is gone and everything seems to be working.
> Also we're trying to move people away from the cciss driver, can you
> check if the hpsa SCSI driver works for you as well?
I have older adapter:
Compaq Computer Corporation Smart Array
Hi!
On Thu 2017-07-06 11:24:48, Thierry Reding wrote:
> On Thu, Jul 06, 2017 at 10:17:18AM +0100, Daniel Thompson wrote:
> > On 06/07/17 10:12, Pavel Machek wrote:
> > > On Thu 2017-07-06 10:01:32, Thierry Reding wrote:
> > > > On Fri, Jun 30, 2017 at 01:21:07PM +0200, Enric Balletbo i Serra
From: Stephen Rothwell
Date: Thu, 6 Jul 2017 10:27:12 +1000
> Hi,
>
> Not sure why you sent this to me ... it fixes a commit in the net-next
> tree (now in Linus' tree) ...
>
> On Thu, 6 Jul 2017 07:58:53 +0800 kbuild test robot
> wrote:
>>
>> Fixes: 0c5f0311f690 ("Add linux-next specific
On 06/07/17 10:24, Thierry Reding wrote:
On Thu, Jul 06, 2017 at 10:17:18AM +0100, Daniel Thompson wrote:
On 06/07/17 10:12, Pavel Machek wrote:
On Thu 2017-07-06 10:01:32, Thierry Reding wrote:
On Fri, Jun 30, 2017 at 01:21:07PM +0200, Enric Balletbo i Serra wrote:
From: huang lin
Some
From: Colin Ian King
The arrays pctl0_data and pctl1_data do not need to be in global scope,
so them both static.
Cleans up sparse warnings:
symbol 'pctl0_data' was not declared. Should it be static?
symbol 'pctl1_data' was not declared. Should it be static?
Signed-off-by: Colin Ian King
---
This patch adds support to the FPGA manager for programming
MachXO2 device’s internal flash memory, via slave SPI.
Signed-off-by: Paolo Pisati
---
drivers/fpga/Kconfig | 7 ++
drivers/fpga/Makefile | 1 +
drivers/fpga/machxo2-spi.c | 298
Hi all,
Hi Elaine,
Am Donnerstag, 6. Juli 2017, 16:28:34 CEST schrieb Elaine Zhang:
> fractional divider must set that denominator is 20 times larger than
> numerator to generate precise clock frequency.
> Otherwise the CLK jitter is very big, poor quality of the clock signal.
>
> RK document
Add dt binding documentation details for Lattice MachXO2 FPGA configuration
over Slave SPI interface.
Signed-off-by: Paolo Pisati
Acked-by: Rob Herring
---
.../bindings/fpga/lattice-machxo2-spi.txt | 29 ++
1 file changed, 29 insertions(+)
create mode 100644
On Thu, Jul 06, 2017 at 10:31:38AM +0200, Romain Perier wrote:
> Hello,
>
>
> Le 05/07/2017 à 15:29, Uwe Kleine-König a écrit :
> > Hello,
> >
> > On Wed, Jul 05, 2017 at 03:07:01PM +0200, Romain Perier wrote:
> >> From: Nandor Han
> >>
> >> Avoid the situation when `dma_is_rxing` could
On Thu, Jul 6, 2017 at 5:29 AM, Srividya Desireddy
wrote:
> On Wed, Jul 6, 2017 at 10:49 AM, Sergey Senozhatsky wrote:
>> On (07/02/17 20:28), Seth Jennings wrote:
>>> On Sun, Jul 2, 2017 at 9:19 AM, Srividya Desireddy
>>> > Zswap is a cache which compresses the pages that are being swapped out
On Wed, 5 Jul 2017 12:42:16 +0200
Ingo Molnar wrote:
>
> * Naveen N. Rao wrote:
>
> > Similar to commit 90ec5e89e393c ("kretprobes: Ensure probe location is
> > at function entry"), ensure that the jprobe probepoint is at function
> > entry.
Sorry I missed it.
> >
> > Signed-off-by: Naveen
On Thu, Jul 06, 2017 at 08:31:07AM +, Naoya Horiguchi wrote:
>Hi Baoquan, everyone,
>
>I'm also interested in KASLR/EFI related issue (but not the same issue
>with yours, so I separated the thread.)
>
>This patch is based on Baoquan's recent patches[1], adding more code
>on the new function
From: Colin Ian King
When us->extra is null the driver is not initialized, however, a
later call to osd200_scsi_to_ata is made that dereferences
us->extra, causing a null pointer dereference. The code
currently detects and reports that the driver is not initialized;
add a return to avoid the
On Thu, Jul 06, 2017 at 10:24:06AM +0200, Willy Tarreau wrote:
> On Wed, Jul 05, 2017 at 04:51:06PM -0700, Linus Torvalds wrote:
> > On Wed, Jul 5, 2017 at 4:35 PM, Ben Hutchings wrote:
> > >>
> > >> And I think your second patch breaks that "use a really large value to
> > >> approximate
On 07/06/17 11:53, Archit Taneja wrote:
>
>
> On 07/04/2017 06:04 PM, Georgi Djakov wrote:
>> As there is no way to actually query the hardware for the current clock
>> rate, now racalc_rate() just returns the last rate that was previously
>> set. But if the rate was not set yet, we return the
On Thu, Jul 06, 2017 at 09:53:13AM +0200, Daniel Vetter wrote:
> On Wed, Jul 05, 2017 at 03:10:13PM -0700, Keith Packard wrote:
> > These provide crtc-id based functions instead of pipe-number, while
> > also offering higher resolution time (ns) and wider frame count (64)
> > as required by the
Document "mac-offset" binding that will be used by at24 EEPROM driver.
Signed-off-by: Claudiu Beznea
---
Documentation/devicetree/bindings/eeprom/eeprom.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings/eeprom/eeprom.txt
Add support for reading MAC address from different offsets of EEPROM. The
offset is initialized via device tree. If nothing is given as input the
old value, 0x90, is used. In this way the driver could be used as generic
driver for different vendor memories by only changing the reading offset
via
Hi all,
Please give feedback on the following approach to extends at24 EEPROM
driver to support reading MAC from different addresses in EEPROM. This
will allow the at24 driver to be used as a generic driver by different
hardwares.
Thank you,
Claudiu Beznea
Claudiu Beznea (3):
dt-bindings:
Document all at24 memories specific bindings.
Signed-off-by: Claudiu Beznea
---
Documentation/devicetree/bindings/eeprom/eeprom.txt | 17 ++---
1 file changed, 10 insertions(+), 7 deletions(-)
diff --git a/Documentation/devicetree/bindings/eeprom/eeprom.txt
On Thu, Jul 06, 2017 at 06:04:46PM +0800, Chao Fan wrote:
>On Thu, Jul 06, 2017 at 08:31:07AM +, Naoya Horiguchi wrote:
>>Hi Baoquan, everyone,
>>
>>I'm also interested in KASLR/EFI related issue (but not the same issue
>>with yours, so I separated the thread.)
>>
>>This patch is based on
On 2017-07-06 12:23, Stephen Boyd wrote:
On 07/03, Kiran Gunda wrote:
From: Fenglin Wu
The opc parameter in pmic_arb_write_cmd() function is defined with
type
u8 and it's always greater than or equal to 0. Checking that it's not
less than 0 is redundant and it can cause a forbidden warning
On 06-07-17, 10:49, Dietmar Eggemann wrote:
> Free cpumask cpus_to_visit in case registering
> init_cpu_capacity_notifier has failed or the parsing of the cpu
> capacity-dmips-mhz property is done. The cpumask cpus_to_visit is
> only used inside the notifier call init_cpu_capacity_callback.
>
>
On the first revision of the bindings, only the gates + resets were known
in the AO Clock HW, but more registers used to configures AO clock are known
to be spread among the AO register space.
This patch adds these registers to the Ao Clock bindings with direct access
and shared extcon access.
This patch adds the clock binding entry for the CEC 32K AO Clock.
Signed-off-by: Neil Armstrong
---
include/dt-bindings/clock/gxbb-aoclkc.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/dt-bindings/clock/gxbb-aoclkc.h
b/include/dt-bindings/clock/gxbb-aoclkc.h
index
Hi Sylwester,
On 05-07-2017 21:52, Sylwester Nawrocki wrote:
> On 07/04/2017 04:11 PM, Jose Abreu wrote:
>> Document the bindings for the Synopsys Designware HDMI RX.
>>
>> Signed-off-by: Jose Abreu
>> ---
>> .../devicetree/bindings/media/snps,dw-hdmi-rx.txt | 70
>> ++
The CEC 32K AO Clock is a dual divider with dual counter to provide a more
precise 32768Hz clock for the CEC subsystem from the external xtal.
The AO clocks management registers are spread among the AO register space,
so this patch also adds management of these registers mappings then uses them
In order to support the standalone CEC Controller on the Amlogic SoCs,
a specific CEC 32K clock must be handled in the AO domain.
The CEC 32K AO Clock is a dual divider with dual counter to provide a more
precise 32768Hz clock for the CEC subsystem from the external xtal.
The AO clocks
The Amlogic SoC embeds a standalone CEC controller, this patch adds a driver
for such controller.
The controller does not need HPD to be active, and could support up to max
5 logical addresses, but only 1 is handled since the Suspend firmware can
make use of this unique logical address to wake up
The Amlogic SoCs embeds a standalone CEC Controller, this patch adds this
device bindings.
Signed-off-by: Neil Armstrong
---
.../devicetree/bindings/media/meson-ao-cec.txt | 28 ++
1 file changed, 28 insertions(+)
create mode 100644
The Amlogic SoC embeds a standalone CEC controller, this patch adds a driver
for such controller.
The controller does not need HPD to be active, and could support up to max
5 logical addresses, but only 1 is handled since the Suspend firmware can
make use of this unique logical address to wake up
On Wed, Jul 05, 2017 at 01:02:21PM -0700, Joe Perches wrote:
> Make the code like the rest of the kernel.
>
> Signed-off-by: Joe Perches
> ---
> drivers/s390/net/ctcm_main.c| 2 +-
> drivers/s390/net/qeth_l3_main.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
> diff --git
1101 - 1200 of 1854 matches
Mail list logo
