On Wed, Mar 15, 2017 at 05:28:43PM +0100, Michal Hocko wrote:
> On Wed 15-03-17 23:44:07, Aaron Lu wrote:
> > On Wed, Mar 15, 2017 at 03:18:14PM +0100, Michal Hocko wrote:
> > > On Wed 15-03-17 16:59:59, Aaron Lu wrote:
> > > [...]
> > > > The proposed parallel free did this: if the process has man
> From: Shawn Starr [mailto:shawn.st...@rogers.com]
> Sent: Tuesday, March 14, 2017 1:43 PM
> To: linux-kernel@vger.kernel.org
> Cc: Brown, Aaron F
> Subject: Re: [4.10][regression][PM] Oops pci_restore_msi_state() e1000e?
> (Re: [BUG] 4.11.0-rc1 panic on shutdown X61s)
>
> This isn't just Lenovo
On Thu, Mar 16, 2017 at 11:14:09AM +0900, Greg Kroah-Hartman wrote:
> On Tue, Mar 14, 2017 at 01:41:55PM +, Okash Khawaja wrote:
> > This moves spk_synth_immediate and spk_serial_synth_probe functions into
> > serialio.c. These functions do outgoing serial comms. The move is a step
> > towards
On 02.03.2017 08:17, Minchan Kim wrote:
Hi Michal,
On Tue, Feb 28, 2017 at 09:12:24AM +0100, Michal Hocko wrote:
On Tue 28-02-17 14:17:23, Minchan Kim wrote:
On Mon, Feb 27, 2017 at 10:44:49AM +0100, Michal Hocko wrote:
On Mon 27-02-17 18:02:36, Minchan Kim wrote:
[...]
>From 9779a1c5d32e2ed
From: Andrew Lunn
Add properties to the gpio nodes to allow them to be also used as pwm
lines.
Signed-off-by: Andrew Lunn
URL: https://patchwork.ozlabs.org/patch/427294/
Signed-off-by: Ralph Sennhauser
---
arch/arm/boot/dts/armada-370.dtsi| 10 --
arch/arm/boot/dts/armada-xp-m
From: Andrew Lunn
Armada 370/XP devices can 'blink' gpio lines with a configurable on
and off period. This can be modelled as a PWM.
However, there are only two sets of PWM configuration registers for
all the gpio lines. This driver simply allows a single gpio line per
gpio chip of 32 lines to b
* Arnaldo Carvalho de Melo wrote:
> Added more people to the CC list.
>
> Em Wed, Mar 15, 2017 at 05:58:19PM -0700, Alexei Starovoitov escreveu:
> > On Thu, Feb 16, 2017 at 05:00:50PM +1100, Anton Blanchard wrote:
> > > We have uses of CONFIG_UPROBE_EVENT and CONFIG_KPROBE_EVENT as
> > > well a
* Mark Rutland wrote:
> The counters in struct lockdep_stats are all (signed) ints. For some
> counters (e.g. hardirqs_on_events, hardirqs_off_events), it's easy to
> trigger an overflow in a short period of time, rendering the information
> exposed under /proc/lockdep_stats erroneous, and causi
From: Andrew Lunn
The mvebu gpio driver can also perform PWM on some pins. Us the pwm-fan
driver to control the fan of the WRT1900AC, giving us finer grained
control over its speed and hence noise.
Signed-off-by: Andrew Lunn
URL: https://patchwork.ozlabs.org/patch/427291/
Signed-off-by: Ralph S
From: Andrew Lunn
Now that the gpio driver also supports PWM operation, enable the PWM
framework and fan driver in mvebu_v7_defconfig.
Signed-off-by: Andrew Lunn
URL: https://patchwork.ozlabs.org/patch/427297/
[Ralph Sennhauser: add fan driver to defconfig]
Signed-off-by: Ralph Sennhauser
---
Hi everyone
this patch series was originally submitted by Andrew Lunn but got stalled.
I picked up the series and addressed what was disscussed for the earlier
submission with some helpful input from Andrew. Hopefully this time support
for the PWM fan as found on Linksys WRT1900AC (Mamba) will mak
On Thu, Mar 16, 2017 at 11:01:38AM +0530, Pushkar Jambhlekar wrote:
> Any comment?
>
> On Wed, Mar 15, 2017 at 12:01 PM, Pushkar Jambhlekar
One day's response? Hah, give me a few weeks at best for trivial stuff
like this please.
Actually, I totally missed this in my last sweep of staging patche
Hi everyone
I did pick up a patch series by Andrew Lunn adding PWM upport to mvebu's
gpio controller. Checkpach complained quite a bit and there are extra
inconsitencies which make it worth to clean drivers/gpio/gpio-mvebu.c a bit
before adding the desired pwm fan support for armada 370 / xp.
Thi
While this isn't an issue according to checkpatch two styles are used.
Add a blank line to the block comments missing a blank line at the start
so multiline block comments look the same across the file.
Signed-off-by: Ralph Sennhauser
---
drivers/gpio/gpio-mvebu.c | 6 --
1 file changed, 4 i
A modern compiler should know better when to inline, so drop the inline
keywords.
Signed-off-by: Ralph Sennhauser
---
drivers/gpio/gpio-mvebu.c | 18 +++---
1 file changed, 7 insertions(+), 11 deletions(-)
diff --git a/drivers/gpio/gpio-mvebu.c b/drivers/gpio/gpio-mvebu.c
index d9aa
Fix whitespace errors reported by checkpatch.
Signed-off-by: Ralph Sennhauser
---
drivers/gpio/gpio-mvebu.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpio/gpio-mvebu.c b/drivers/gpio/gpio-mvebu.c
index a9522f4..1933e63 100644
--- a/drivers/gpio/gpio-mvebu.c
+++ b/drivers/gpio/g
Fix whitespace errors missed by checkpatch.
Signed-off-by: Ralph Sennhauser
---
drivers/gpio/gpio-mvebu.c | 13 ++---
1 file changed, 6 insertions(+), 7 deletions(-)
diff --git a/drivers/gpio/gpio-mvebu.c b/drivers/gpio/gpio-mvebu.c
index 1933e63..d9aa77b 100644
--- a/drivers/gpio/gpio-
Fix issues in block comments reported by checkpatch.
Signed-off-by: Ralph Sennhauser
---
drivers/gpio/gpio-mvebu.c | 24
1 file changed, 16 insertions(+), 8 deletions(-)
diff --git a/drivers/gpio/gpio-mvebu.c b/drivers/gpio/gpio-mvebu.c
index a649556..a2351f3 100644
---
Use unsigned int instead of plain unsigned as reported by checkpatch.
Signed-off-by: Ralph Sennhauser
---
drivers/gpio/gpio-mvebu.c | 13 +++--
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/drivers/gpio/gpio-mvebu.c b/drivers/gpio/gpio-mvebu.c
index 80b1d52..a9522f4 10064
Replace &tp->napi with napi and tp->netdev with netdev.
Signed-off-by: Hayes Wang
---
drivers/net/usb/r8152.c | 43 ++-
1 file changed, 26 insertions(+), 17 deletions(-)
diff --git a/drivers/net/usb/r8152.c b/drivers/net/usb/r8152.c
index 227e1fd..4b85e95
Tim Chen writes:
> On Wed, 2017-03-15 at 09:19 +0800, Huang, Ying wrote:
>> Tim Chen writes:
>>
>> >
>> > On Wed, 2017-03-08 at 15:26 +0800, Huang, Ying wrote:
>> > >
>> > > From: Huang Ying
>> > >
>> > > The swap cluster allocation/free functions are added based on the
>> > > existing swap
On 15/03/17 20:23, Stefano Stabellini wrote:
> Implement functions to handle the xenbus handshake. Upon connection,
> allocate the rings according to the protocol specification.
>
> Initialize a work_struct and a wait_queue. The work_struct will be used
> to schedule work upon receiving an event c
Replace &tp->napi with napi and tp->netdev with netdev.
Signed-off-by: Hayes Wang
---
drivers/net/usb/r8152.c | 44 +++-
1 file changed, 27 insertions(+), 17 deletions(-)
diff --git a/drivers/net/usb/r8152.c b/drivers/net/usb/r8152.c
index 227e1fd..e480e9
On Thu, Mar 16, 2017 at 02:44:30PM +0900, Sergey Senozhatsky wrote:
> On (03/16/17 14:33), Minchan Kim wrote:
> [..]
> > "There is no user for it"
> >
> > I was liar so need to be a honest guy.
>
> ha-ha-ha. I didn't say that :)
>
> [..]
> > @@ -1414,7 +1414,7 @@ static bool try_to_unmap_one(str
On 15/03/17 20:23, Stefano Stabellini wrote:
> Hi all,
>
> This patch series implements a new transport for 9pfs, aimed at Xen
> systems.
>
> The transport is based on a traditional Xen frontend and backend drivers
> pair. This patch series implements the frontend, which typically runs in
> a reg
Now that the mm core supports section-unaligned hotplug of ZONE_DEVICE
memory, we no longer need to add padding at pfn/dax device creation
time. The kernel will still honor padding established by older kernels.
Cc: Toshi Kani
Signed-off-by: Dan Williams
---
drivers/nvdimm/pfn_devs.c | 42
Historically kasan has not been careful about whether vmemmap_populate()
internally allocates a section worth of memmap even if the parameters
call for less. For example, a request to shadow map a single page
results in a full section (128MB) that contains that page being mapped.
Also, kasan has n
The initial motivation for this change is persistent memory platforms
that, unfortunately, align the pmem range on a boundary less than a full
section (64M vs 128M), and may change the alignment from one boot to the
next. A secondary motivation is the arrival of prospective ZONE_DEVICE
users that w
Prepare the memory hot-{add,remove} paths for handling sub-section
ranges by plumbing the starting page frame and number of pages being
handled through arch_{add,remove}_memory() to
sparse_{add,remove}_one_section().
This is simply plumbing, small cleanups, and some identifier renames. No
intended
In preparation for sub-section memory hotplug support, remove a
dependency on ->section_mem_map being populated. In SPARSEMEM_VMEMMAP=y
configurations pfn_to_page() does not use ->section_mem_map. The
sub-section hotplug support relies on this fact and skips initializing
it. Without ->section_mem_m
Teach devm_memremap_pages() about the new sub-section capabilities of
arch_{add,remove}_memory().
Cc: Michal Hocko
Cc: Toshi Kani
Cc: Andrew Morton
Cc: Logan Gunthorpe
Cc: Stephen Bates
Signed-off-by: Dan Williams
---
kernel/memremap.c | 24 +++-
1 file changed, 7 inse
Allow sub-section sized ranges to be added to the memmap.
populate_section_memmap() takes an explict pfn range rather than
assuming a full section, and those parameters are plumbed all the way
through to vmmemap_populate(). There should be no sub-section in
current code. New warnings are added to c
We mark and check that the section is present under a spin_lock() in
sparse_add_one_section(), so the lock ensures it will not change between
those 2 events. Also, we do not check the -EBUSY return value in
sparse_init(). Just make sparse_init_one_section() return void and clean
up the error handli
Prepare for hot{plug,remove} of sub-ranges of a section by tracking a
section active bitmask, each bit representing 2MB (SECTION_SIZE (128M) /
map_active bitmask length (64)).
Cc: Michal Hocko
Cc: Vlastimil Babka
Cc: Johannes Weiner
Cc: Logan Gunthorpe
Cc: Mel Gorman
Cc: Andrew Morton
Cc: St
Up-level the local section size and mask from kernel/memremap.c to
global definitions. These will be used by the new sub-section hotplug
support.
Cc: Michal Hocko
Cc: Vlastimil Babka
Cc: Johannes Weiner
Cc: Logan Gunthorpe
Cc: Mel Gorman
Cc: Andrew Morton
Cc: Stephen Bates
Signed-off-by: D
devm_memremap_pages() records mapped ranges in pgmap_radix with an entry
per section's worth of memory (128MB). The key for each of those
entries is a section number.
This leads to false positives when devm_memremap_pages() is passed a
section-unaligned range as lookups in the misalignment fail t
section_nr_to_pfn() will silently accept an argument that is too small
to contain a pfn. Cast the argument to an unsigned long, similar to
PFN_PHYS(). Fix up pfn_to_section_nr() in the same way.
This was discovered in __add_pages() when converting it to use an
signed integer for the loop variable.
'struct mem_section_usage' combines the existing 'pageblock_flags' bitmap
with a new 'map_active' bitmap. The new bitmap enables the memory
hot{plug,remove} implementation to act on incremental sub-divisions of
a section. The primary impetus for this functionality is to support
platforms that mix
Changes since v3 [1]:
1/ Rebased on v4.11-rc2
2/ Worked around kasan regression ("x86, kasan: clarify kasan's
dependency on vmemmap_populate_hugepages()") (Nicolai)
[1]: https://lwn.net/Articles/712099/
---
The initial motivation for this change is persistent memory platforms
that, unfortun
Add appropriate properties to devices in the Linksys WRT AC Series for the
mvneta driver to use hardware buffer management.
Also update "soc" ranges property and set the status of bm and bm-bppi
to "okay" (SRAM).
Signed-off-by: Ralph Sennhauser
---
v1 -> v2:
Use independent pools for sh
On (03/16/17 14:51), Minchan Kim wrote:
[..]
> > > @@ -1414,7 +1414,7 @@ static bool try_to_unmap_one(struct page *page,
> > > struct vm_area_struct *vma,
> > >*/
> > > if (unlikely(PageSwapBacked(page) !=
> > > PageSwapCache(page))) {
> > >
Hello,
We run CRIU tests for linux-next and here is a new bug in the kernel log
[2.431229] Freeing unused kernel memory: 1356K
[2.436371] Freeing unused kernel memory: 168K
[2.522236] BUG: spinlock bad magic on CPU#0, init/1
[2.527487] lock: 0x94915477fd88, .magic: ,
On Wednesday 15 March 2017 05:53 PM, Peter Zijlstra wrote:
On Wed, Mar 15, 2017 at 05:20:15PM +1100, Michael Ellerman wrote:
I see no implementation; so why are you poking at it.
Maddy has posted an implementation of the kernel part for powerpc in
patch 2 of this series, but maybe you're not
On 15/03/17 19:44, Stefano Stabellini wrote:
> On Wed, 15 Mar 2017, Juergen Gross wrote:
>> On 14/03/17 22:22, Stefano Stabellini wrote:
>>> Hi Juergen,
>>>
>>> thank you for the review!
>>>
>>> On Tue, 14 Mar 2017, Juergen Gross wrote:
On 14/03/17 00:50, Stefano Stabellini wrote:
> Implem
On 2017/3/16 9:06, Arnaldo Carvalho de Melo wrote:
Added more people to the CC list.
Em Wed, Mar 15, 2017 at 05:58:19PM -0700, Alexei Starovoitov escreveu:
On Thu, Feb 16, 2017 at 05:00:50PM +1100, Anton Blanchard wrote:
We have uses of CONFIG_UPROBE_EVENT and CONFIG_KPROBE_EVENT as
well as
On Wed, 15 Mar 2017 20:17:35 +0100
Gregory CLEMENT wrote:
> Hi Ralph,
>
> On mer., mars 08 2017, Ralph Sennhauser
> wrote:
>
>
>
> > @@ -88,6 +89,9 @@
> > ethernet@7 {
> > status = "okay";
> > phy-mode = "rgmii-
On Wednesday 15 March 2017 11:50 AM, Michael Ellerman wrote:
Hi Peter,
Peter Zijlstra writes:
On Tue, Mar 14, 2017 at 02:31:51PM +0530, Madhavan Srinivasan wrote:
Huh? PPC hasn't yet implemented this? Then why are you fixing it?
yes, PPC hasn't implemented this (until now).
until now whe
On (03/16/17 14:33), Minchan Kim wrote:
[..]
> "There is no user for it"
>
> I was liar so need to be a honest guy.
ha-ha-ha. I didn't say that :)
[..]
> @@ -1414,7 +1414,7 @@ static bool try_to_unmap_one(struct page *page, struct
> vm_area_struct *vma,
>*/
>
On Wed, 15 Mar 2017, Andy Lutomirski wrote:
> Can you give this a try:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git/commit/?h=x86/fixes&id=9edb8154863ba1a7f6f1f15ffe6aecf3cf32bf21
>
> (The link doesn't work yet but it should in a minute or two.)
I've tested it and I am una
Hi,
On 03/15/2017 04:15 PM, Philipp Zabel wrote:
On Wed, 2017-02-22 at 10:54 +0530, Vivek Gautam wrote:
Add support to get a list of resets available for the device.
These resets must be kept de-asserted until the device is
in use.
Cc: Felipe Balbi
Signed-off-by: Vivek Gautam
---
Based on
> Added more people to the CC list.
>
> Em Wed, Mar 15, 2017 at 05:58:19PM -0700, Alexei Starovoitov escreveu:
> > On Thu, Feb 16, 2017 at 05:00:50PM +1100, Anton Blanchard wrote:
> > > We have uses of CONFIG_UPROBE_EVENT and CONFIG_KPROBE_EVENT as
> > > well as CONFIG_UPROBE_EVENTS and CONFIG_KPR
Objects of "struct cpufreq_cooling_device" are named a bit
inconsistently. Lets use cpufreq_dev everywhere.
Signed-off-by: Viresh Kumar
---
drivers/thermal/cpu_cooling.c | 133 +-
1 file changed, 66 insertions(+), 67 deletions(-)
diff --git a/drivers/ther
The CPU cooling driver uses the cpufreq policy, to get clip_cpus, the
frequency table, etc. Most of the callers of CPU cooling driver's
registration routines have the cpufreq policy with them, but they only
pass the policy->related_cpus cpumask. The __cpufreq_cooling_register()
routine then gets th
The OPPs are registered for all CPUs of a cpufreq policy now and we
don't need to run the loop in build_dyn_power_table(). Just check for
the policy->cpu and we should be fine.
Signed-off-by: Viresh Kumar
---
drivers/thermal/cpu_cooling.c | 26 +++---
1 file changed, 11 inser
On Wed, Mar 15, 2017 at 05:37:29PM +0100, Andrea Arcangeli wrote:
> On Wed, Mar 15, 2017 at 02:11:40PM +0100, Michal Hocko wrote:
> > OK, I see now. I am afraid there is quite a lot of code which expects
> > that zones do not overlap. We can have holes in zones but not different
> > zones interleav
Hey, Sergey,
On Thu, Mar 16, 2017 at 01:40:23PM +0900, Sergey Senozhatsky wrote:
> Hello,
>
>
> On (03/15/17 14:24), Minchan Kim wrote:
> > There is no user for it. Remove it.
> >
>
> there is one.
>
> mm/rmap.c
>
> try_to_unmap_one()
> ...
> if (unlikely(PageSwapBacked(page) != PageSw
We need such a routine at two places already, lets create one.
Signed-off-by: Viresh Kumar
---
drivers/cpufreq/cpufreq_stats.c | 13 -
drivers/thermal/cpu_cooling.c | 22 +-
include/linux/cpufreq.h | 14 ++
3 files changed, 27 insertions(+),
The frequency passed to get_level() is returned by cpu_power_to_freq()
and it is guaranteed that get_level() can't fail.
Get rid of error code.
Signed-off-by: Viresh Kumar
---
drivers/thermal/cpu_cooling.c | 20 +---
1 file changed, 5 insertions(+), 15 deletions(-)
diff --git a
Any comment?
On Wed, Mar 15, 2017 at 12:01 PM, Pushkar Jambhlekar
wrote:
> Fixing 'if' block coding style. '{' should follow 'if' for multiline block
>
> Signed-off-by: Pushkar Jambhlekar
> ---
> drivers/staging/vc04_services/interface/vchiq_arm/vchiq_shim.c | 3 +--
> 1 file changed, 1 inserti
'cpu_dev' is used by only one function, get_static_power(), and it
wouldn't be time consuming to get the cpu device structure within it.
This would help removing cpu_dev from struct cpufreq_cooling_device.
Signed-off-by: Viresh Kumar
---
drivers/thermal/cpu_cooling.c | 22 ++
We keep two arrays for idle time stats and allocate memory for them
separately. It would be much easier to follow if we create an array of
idle stats structure instead and allocate it once.
Signed-off-by: Viresh Kumar
---
drivers/thermal/cpu_cooling.c | 53 ---
The frequency table shouldn't have any zero frequency entries and so
such a check isn't required. Though it would be better to make sure
'state' is within limits.
Signed-off-by: Viresh Kumar
---
drivers/thermal/cpu_cooling.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --gi
This shrinks the size of the structure on arm64 by 8 bytes by avoiding
padding of 4 bytes at two places.
Also add missing doc comment for freq_table
Signed-off-by: Viresh Kumar
---
drivers/thermal/cpu_cooling.c | 15 ---
1 file changed, 8 insertions(+), 7 deletions(-)
diff --git a/
'cpu' is used at only one place and there is no need to keep a separate
variable for it.
Signed-off-by: Viresh Kumar
---
drivers/thermal/cpu_cooling.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/thermal/cpu_cooling.c b/drivers/thermal/cpu_cooling.c
index 99dc683
The cpu_cooling driver keeps two tables:
- freq_table: table of frequencies in descending order, built from
policy->freq_table.
- power_table: table of frequencies and power in ascending order, built
from OPP table.
If the OPPs are used for the CPU device then both these tables are
actually
There is only one user of cpufreq_cooling_get_level() and that already
has pointer to the cpufreq_dev structure. It can directly call
get_level() instead and we can get rid of cpufreq_cooling_get_level().
Signed-off-by: Viresh Kumar
---
drivers/thermal/cpu_cooling.c | 33 +---
The cpufreq policy can be used by the cpu_cooling driver, lets store it
in the cpufreq_cooling_device structure.
Signed-off-by: Viresh Kumar
---
drivers/thermal/cpu_cooling.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/thermal/cpu_cooling.c b/drivers/thermal/cpu_cooling.c
inde
Just to make it look better.
Signed-off-by: Viresh Kumar
---
drivers/thermal/cpu_cooling.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/thermal/cpu_cooling.c b/drivers/thermal/cpu_cooling.c
index 6fd258d62e47..7ce73eee866f 100644
--- a/drivers/thermal/cpu_cooling
'allowed_cpus' is a copy of policy->related_cpus and can be replaced by
it directly. At some places we are only concerned about online CPUs and
policy->cpus can be used there.
Signed-off-by: Viresh Kumar
---
drivers/thermal/cpu_cooling.c | 77 ---
1 file c
Objects of "struct thermal_cooling_device" are named a bit
inconsistently. Lets use cdev everywhere.
Signed-off-by: Viresh Kumar
---
drivers/thermal/cpu_cooling.c | 36 ++--
1 file changed, 18 insertions(+), 18 deletions(-)
diff --git a/drivers/thermal/cpu_coolin
After the lock is dropped, it is possible that the cpufreq_dev gets
freed before we call get_level() and that can cause kernel to crash.
Drop the lock after we are done using the structure.
Cc: 4.2+
Fixes: 02373d7c69b4 ("thermal: cpu_cooling: fix lockdep problems in
cpu_cooling")
Signed-off-by:
Hi Guys,
The cpu_cooling driver is designed to use CPU frequency scaling to avoid
high thermal states for a platform. But it wasn't glued really well with
cpufreq core.
This series tries to improve interactions between cpufreq core and
cpu_cooling driver and does some fixes/cleanups to the cpu_co
This introduces a basic driver for communicating over "native glink"
with the RPM found in Qualcomm platforms.
Signed-off-by: Bjorn Andersson
---
drivers/rpmsg/Kconfig |8 +
drivers/rpmsg/Makefile |1 +
drivers/rpmsg/qcom_glink_rpm.c | 1249 ++
Add device tree binding documentation for the Qualcomm GLINK RPM, used
for communication with the Resource Power Management subsystem in
various Qualcomm SoCs.
Signed-off-by: Bjorn Andersson
---
.../devicetree/bindings/soc/qcom/qcom,glink.txt| 73 ++
1 file changed, 73 in
On 2017/3/16 8:07, Martin K. Petersen wrote:
> Kefeng Wang writes:
>
> Kefeng,
>
>> 'n = header_length + block_descriptor_length' could be greater than 512,
>> and will lead to oob access, so enlarge transfer buffer to fix it.
>
> Can you share the output of sg_modes -p 0x2a /dev/srN for the
The rpmsg devices are allocated in the backends and as such must be
freed there as well.
Signed-off-by: Bjorn Andersson
---
drivers/rpmsg/qcom_smd.c | 11 +++
drivers/rpmsg/virtio_rpmsg_bus.c | 9 +
2 files changed, 20 insertions(+)
diff --git a/drivers/rpmsg/qcom_smd.c
Hello,
commit 4f86a82ff7df ("x86/atomic: move __arch_atomic_add_unless out of line")
moved __arch_atomic_add_unless() out atomic.h and new KASAN atomic
instrumentation [1] can't see it anymore
In file included from ./arch/x86/include/asm/atomic.h:257:0,
from ./include/linux/atom
Hello,
On (03/15/17 14:24), Minchan Kim wrote:
> There is no user for it. Remove it.
>
there is one.
mm/rmap.c
try_to_unmap_one()
...
if (unlikely(PageSwapBacked(page) != PageSwapCache(page))) {
WARN_ON_ONCE(1);
ret = SWAP_FAIL;
page_vma
"Andrew F. Davis" writes:
> When CONFIG_MACINTOSH_DRIVERS is not set make will still descend into the
> macintosh directory but nothing will be built. This produces unneeded
> build artifacts and messages in addition to slowing the build.
> Fix this here.
>
> Signed-off-by: Andrew F. Davis
> ---
Add basic support for handling suspend and resume.
Signed-off-by: Jane Li
---
Since v1:
- add mvneta_conf_mbus_windows() and mvneta_bm_port_init() in mvneta_resume()
drivers/net/ethernet/marvell/mvneta.c | 62 ---
1 file changed, 58 insertions(+), 4 deletions(-)
Embedded function names are less appropriate to use when
refactoring, can cause function renaming. Prefer the use
of "%s", __func__ to embedded function names
Signed-off-by: Mohsin Shan
---
drivers/staging/goldfish/goldfish_nand.c | 16
1 file changed, 8 insertions(+), 8 deleti
Hi Philipp,
On Wed, Mar 15, 2017 at 4:10 PM, Philipp Zabel wrote:
> Hi Vivek,
>
> On Fri, 2017-03-10 at 20:10 +0530, Vivek Gautam wrote:
>> Hi Philipp,
>>
>>
>> On Wed, Feb 22, 2017 at 10:54 AM, Vivek Gautam
>> wrote:
>> > Count number of reset phandles available with the device node
>> > to kn
On Thu, 16 Mar 2017 11:19:10 +0800 Jane Li wrote:
> Add basic support for handling suspend and resume.
>
> Signed-off-by: Jane Li
> ---
> Since v1:
> - add mvneta_conf_mbus_windows() and mvneta_bm_port_init() in mvneta_resume()
>
> drivers/net/ethernet/marvell/mvneta.c | 62
>
On Tue, Mar 14, 2017 at 08:05:39AM -0700, Andrey Smirnov wrote:
> Add code allowing for control of various power domains managed by GPCv2
> IP block found in i.MX7 series of SoCs. Power domains covered by this
> patch are:
>
> - PCIE PHY
> - MIPI PHY
> - USB HSIC PHY
> - USB OTG1/2
On Wed, 15 Mar 2017 23:20:30 -0400
Steven Rostedt wrote:
> > It is used in lots of places outside trace_handle_return, so that would
> > give far less savings.
Actually, I think you'll probably have *more* savings inlining
trace_handle_return() than trace_seq_has_overflowed(). Why?
Think abou
Mapping entire GCR mem region in this driver creates
mem region request conflict in sub devices that depend
on PMC. This creates driver probe failure in devices like
iTC0_wdt and telemetry device.
Currently this driver only need memory mapping for
s0ix counter registers. So this patch fixes this i
For RK3399, the grf clk should be enabled before writing grf registers,
otherwise the register value can not be changed.
Signed-off-by: Chris Zhong
---
Changes in v2:
- check the grf_clk only for RK3399
drivers/gpu/drm/rockchip/dw-mipi-dsi.c | 21 +
1 file changed, 21 inser
For the RK3399, the grf_switch_reg name should be RK3399_GRF_SOC_CON20,
not RK3399_GRF_SOC_CON19.
Signed-off-by: Chris Zhong
---
Changes in v2: None
drivers/gpu/drm/rockchip/dw-mipi-dsi.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/rockchip/dw-mipi-d
Hi all
This series set the phy_cfg_clk to be a required clock for RK3399, and
add a grf clock control in dw-mipi-dsi driver. And then correct a
register name.
Changes in v2:
- check the grf_clk only for RK3399
Chris Zhong (4):
drm/rockchip/dsi: check phy_cfg_clk only for RK3399
dt-bindings:
For RK3399, the phy_cfg_clk is a required clock, if phy_cfg_clk is
disabled, MIPI phy can not work. Let's return a error if there is no
phy_cfg_clk in dts property, when the pdata match RK3399.
Signed-off-by: Chris Zhong
---
Changes in v2: None
drivers/gpu/drm/rockchip/dw-mipi-dsi.c | 10 -
For RK3399, the grf clock should be controlled by dw-mipi-dsi driver,
add the description for this clock.
Signed-off-by: Chris Zhong
---
Changes in v2: None
.../devicetree/bindings/display/rockchip/dw_mipi_dsi_rockchip.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Tue, Mar 14, 2017 at 08:05:38AM -0700, Andrey Smirnov wrote:
> Add DT bindings for power domain driver for GPCv2 IP block found in
> i.MX7 SoCs.
>
> Cc: yurov...@gmail.com
> Cc: Lucas Stach
> Cc: Rob Herring
> Cc: Mark Rutland
> Cc: Fabio Estevam
> Cc: devicet...@vger.kernel.org
> Cc: linux
Jerry Snitselaar @ 2017-03-16 02:38 GMT:
> Jarkko Sakkinen @ 2017-03-15 05:57 GMT:
>
>> From: Jarkko Sakkinen
>>
>> This commit adds support for requesting and relinquishing locality 0 in
>> tpm_crb for the course of command transmission.
>>
>> In order to achieve this, two new callbacks are add
Hi Jisheng,
On 2017年03月15日 15:18, Jisheng Zhang wrote:
Hi Jane,
On Wed, 15 Mar 2017 15:08:34 +0800 Jane Li wrote:
Add basic support for handling suspend and resume.
Signed-off-by: Jane Li
---
drivers/net/ethernet/marvell/mvneta.c | 44 +++
1 file changed
On Wed, 15 Mar 2017 19:27:57 -0700
Andi Kleen wrote:
> On Wed, Mar 15, 2017 at 08:54:20PM -0400, Steven Rostedt wrote:
> > On Tue, 14 Mar 2017 19:14:25 -0700
> > Andi Kleen wrote:
> >
> > > From: Andi Kleen
> > >
> > > Inlining trace_seq_overflowed takes ~17k in text size in my kernel.
> >
Removing mixed spaces/hard-tabs used to create a "column alignment" of
macro names and macro values.
Signed-off-by: Matthew Giassa
---
drivers/staging/ks7010/ks_wlan_ioctl.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/ks7010/ks_wlan_ioctl.h
b/drivers/
Re-aligning function parameters in function prototypes by inserting
additional hard-tabs to resolve a checkpatch warning.
Signed-off-by: Matthew Giassa
---
drivers/staging/ks7010/ks_wlan_ioctl.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/ks7010/ks_wlan_io
Wrapping all complex macros with parentheses to resolve checkpatch
errors. This change, along with the preceding changes in this change
set, resolves all checkpatch warnings and errors for the file.
Signed-off-by: Matthew Giassa
---
drivers/staging/ks7010/ks_wlan_ioctl.h | 64 +--
Removing trailing white space characters in comments to resolve
a checkpatch warning.
Signed-off-by: Matthew Giassa
---
drivers/staging/ks7010/ks_wlan_ioctl.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/ks7010/ks_wlan_ioctl.h
b/drivers/staging/ks7010/ks_w
The following patches address all outstanding checkpatch warnings/errors
present in drivers/staging/ks7010/ks_wlan_ioctl.h.
This change set has been rebased off of the current master
(69eea5a4ab9c705496e912b55a9d312325de19e6) as per an earlier request,
and the change log formatting has been slight
1 - 100 of 928 matches
Mail list logo