On Tuesday 15 December 2015 10:33:25 Pali Rohár wrote:
> On Monday 30 November 2015 11:09:42 Nicolas Pitre wrote:
> > On Mon, 30 Nov 2015, Pali Rohár wrote:
> > > On Monday 30 November 2015 07:23:53 Tony Lindgren wrote:
> > > > * Pali Rohár [151129 16:16]:
> > > > > On Monday 30 November 2015
Hi,
I've been experiencing issues with at least 4.4-rc3 (including current
HEAD) on a Calxeda Midway (4*ARM Cortex-A15 (32-bit), 8GB RAM, SATA
spinning disk or SSD).
After some disk I/O load (kernel compile with -j6) I see the kernel
screaming:
[ 103.736982] ata1.00: exception Emask 0x0 SAct
On Tue, Dec 15, 2015 at 12:22:41PM +0900, Kamezawa Hiroyuki wrote:
> On 2015/12/15 4:42, Vladimir Davydov wrote:
> >On Mon, Dec 14, 2015 at 04:30:37PM +0100, Michal Hocko wrote:
> >>On Thu 10-12-15 14:39:14, Vladimir Davydov wrote:
> >>>In the legacy hierarchy we charge memsw, which is dubious,
> -Original Message-
> From: Marc Zyngier [mailto:marc.zyng...@arm.com]
> Sent: Tuesday, December 15, 2015 3:50 PM
> To: Bhushan Bharat-R65777 ;
> kvm...@lists.cs.columbia.edu; k...@vger.kernel.org; linux-arm-
> ker...@lists.infradead.org; linux-kernel@vger.kernel.org
> Subject: Re:
On Tuesday 15 December 2015 14:45:59 Kishon Vijay Abraham I wrote:
> This series is basically to deprecate using phy-omap-control and use
> syscon APIs to program the control module registers.
>
> Changes from v2:
> No changes.
>
> Changes from v1:
> *) cleanup ti_pipe3_probe in multiple steps
>
Hi Mike,
On Friday 20 November 2015 02:52 AM, Heiko Stuebner wrote:
> The USB phys on Rockchip SoCs contain their own internal PLLs to create
> the 480MHz needed. Additionally this PLL output is also fed back into the
> core clock-controller as possible source for clocks like the GPU or others.
>
Hi Mike,
On Friday 20 November 2015 02:52 AM, Heiko Stuebner wrote:
> The otgphy clocks really only drive the phy blocks. These in turn
> contain plls that then generate the 480m clocks the clock controller
> uses to supply some other clocks like uart0, gpu or the video-codec.
>
> So fix this
On 15/12/15 10:37, Andrew Lunn wrote:
On Tue, Dec 15, 2015 at 10:26:47AM +, Srinivas Kandagatla wrote:
+ adding Anatolij
On 15/12/15 10:17, Andrew Lunn wrote:
Is there a reason for this driver to be using the old style?
I can understand the issues with at24/at25 but does this driver
Hi Vinod,
On Fri, Jul 10, 2015 at 10:14 AM, Vinod Koul wrote:
> On Wed, Jul 08, 2015 at 12:12:52PM +0200, Geert Uytterhoeven wrote:
>> On Fri, Apr 26, 2013 at 11:06 AM, Linus Walleij
>> wrote:
>> > The documentation already says these are physical addresses, and
>> > we have concluded that any
> I expect it does matter.
>
> This driver does not implement the in kernel API for accessing the
> EEPROM. That means all users are in user space. And if this file
> moves, it seems very likely these user space users break.
I agree.
signature.asc
Description: Digital signature
On Tue, Dec 15, 2015 at 10:46:53AM +0100, Borislav Petkov wrote:
> I think what is more important is that this should be in the
> x86-specific linker script, not in the generic one.
And related to that, I think all those additions to kernel/extable.c
should be somewhere in arch/x86/ and not in
Em Fri, 11 Dec 2015 16:36:27 -0700
Shuah Khan escreveu:
> On 12/11/2015 03:57 PM, Javier Martinez Canillas wrote:
> > Most media functions that unregister, check if the corresponding register
> > function succeed before. So these functions can safely be called even if a
> > registration was
On Tue, Dec 15, 2015 at 10:26:47AM +, Srinivas Kandagatla wrote:
> + adding Anatolij
>
> On 15/12/15 10:17, Andrew Lunn wrote:
> >>Is there a reason for this driver to be using the old style?
> >>I can understand the issues with at24/at25 but does this driver also
> >>suffer from such issues?
Em Tue, Dec 15, 2015 at 10:03:29AM +0100, Jiri Olsa escreveu:
> On Tue, Dec 15, 2015 at 12:46:13AM +0900, Namhyung Kim wrote:
> > Each tracepoint event has format string for print to improve
> > readability. Try to parse the output and match the field name. If it
> > finds one, use that for the
On Mon, Dec 14, 2015 at 03:17:39PM -0800, Dan Williams wrote:
> commit db0fa0cb0157 "scatterlist: use sg_phys()" did replacements of the
> form:
>
> phys_addr_t phys = page_to_phys(sg_page(s));
> phys_addr_t phys = sg_phys(s) & PAGE_MASK;
>
> However, this breaks platforms where
On 14/12/15 18:02, Steve Muckle wrote:
> Hi Juri,
>
> Thanks for the review.
>
> On 12/11/2015 03:04 AM, Juri Lelli wrote:
> >> +config CPU_FREQ_GOV_SCHED
> >> + bool "'sched' cpufreq governor"
> >> + depends on CPU_FREQ
> >
> > We depend on IRQ_WORK as well, which in turn I think depends on
+ adding Anatolij
On 15/12/15 10:17, Andrew Lunn wrote:
Is there a reason for this driver to be using the old style?
I can understand the issues with at24/at25 but does this driver also
suffer from such issues?
In order to keep backwards compatibility, we need the older file in
/sys. The only
On 14 December 2015 at 01:26, Yuyang Du wrote:
> Hi Vincent,
>
> I don't quite catch what this is doing, maybe I need more time
> to ramp up to the gory detail difficult like this.
>
> Do you scale or not scale? You seem removed the scaling, but added it
> after "Remainder of delta accrued
On 15/12/15 09:53, Bhushan Bharat wrote:
> Hi Mark,
>
>> -Original Message-
>> From: Marc Zyngier [mailto:marc.zyng...@arm.com]
>> Sent: Tuesday, December 15, 2015 3:05 PM
>> To: Bhushan Bharat-R65777 ;
>> kvm...@lists.cs.columbia.edu; k...@vger.kernel.org; linux-arm-
>>
On 14/12/15 17:07, Catalin Marinas wrote:
> If they take the mmdebug.h patch, it's even better. Please let us know
> how that goes.
Andrew Morton's Robot wrote:
> The patch titled
> Subject: include/linux/mmdebug.h: should include linux/bug.h
> has been added to the -mm tree. Its filename
Hi Morten,
Thanks for the review and sorry for the late reply
On 8 December 2015 at 18:04, Morten Rasmussen wrote:
> On Tue, Nov 24, 2015 at 02:49:30PM +0100, Vincent Guittot wrote:
>> The current implementation of load tracking invariance scales the load
>> tracking value with current
> Is there a reason for this driver to be using the old style?
> I can understand the issues with at24/at25 but does this driver also
> suffer from such issues?
In order to keep backwards compatibility, we need the older file in
/sys. The only other option is to remove it and see if anybody
Le 15/12/2015 11:13, Nicolas Ferre a écrit :
> Le 05/11/2015 08:37, Wenyou Yang a écrit :
>> Enabel AT91SAM9X / AT91CAP9 watchdog and SAMA5D4 watchdog.
>>
>> Signed-off-by: Wenyou Yang
>
> Acked-by: Nicolas Ferre
>
> And stacked on top of at91-4.5-dt.
at91-4.5-defconfig I mean ;-)
>
>
Le 05/11/2015 08:39, Wenyou Yang a écrit :
> Add watchdog node to support SAMA5D4 watchdog.
>
> Signed-off-by: Wenyou Yang
Acked-by: Nicolas Ferre
And stacked on top of at91-4.5-dt.
Thanks!
> ---
>
> arch/arm/boot/dts/at91-sama5d2_xplained.dts |4
> arch/arm/boot/dts/sama5d2.dtsi
Le 05/11/2015 08:37, Wenyou Yang a écrit :
> Enabel AT91SAM9X / AT91CAP9 watchdog and SAMA5D4 watchdog.
>
> Signed-off-by: Wenyou Yang
Acked-by: Nicolas Ferre
And stacked on top of at91-4.5-dt.
Thanks!
> ---
>
> arch/arm/configs/sama5_defconfig |3 +++
> 1 file changed, 3
Hi Greg,
Looks like this have not been merged yet. Can you merge it in this
-rc cycle. Let me know if I have to change something.
Bulk of the changes are with respect to adding of_node_put in
the PHY drivers, a fix in PHY core and a patch to fix randconfig error.
Thanks
Kishon
The following
From: Julia Lawall
for_each_child_of_node performs an of_node_get on each iteration,
so a return from the middle of the loop requires an of_node_put.
A simplified version of the semantic patch that finds this problem is as
follows (http://coccinelle.lip6.fr):
//
@@
expression root,e;
local
After the loop we test "if (!retry)" to see if we timedout. The problem
is "retry--" is a post-op so retry will be -1 at the end of the loop. I
have fixed this by changing it to a pre-op instead.
Signed-off-by: Dan Carpenter
diff --git a/drivers/misc/mic/card/mic_virtio.c
On Mon, Dec 14, 2015 at 04:41:14PM -0800, Steve Muckle wrote:
> Hi Yuyang,
>
> On 12/13/2015 11:13 AM, Yuyang Du wrote:
> > Hi Steve,
> >
> > On Fri, Dec 11, 2015 at 06:01:45PM -0800, Steve Muckle wrote:
> >> In init_entity_runnable_average() the last_update_time is initialized to
> >> zero. The
From: Julia Lawall
for_each_available_child_of_node performs an of_node_get on each iteration,
so a return from the middle of the loop requires an of_node_put.
A simplified version of the semantic patch that finds this problem is as
follows (http://coccinelle.lip6.fr):
//
@@
expression
From: Julia Lawall
for_each_available_child_of_node performs an of_node_get on each iteration,
so a return from the middle of the loop requires an of_node_put.
A simplified version of the semantic patch that finds this problem is as
follows (http://coccinelle.lip6.fr):
//
@@
expression
From: Julia Lawall
for_each_child_of_node performs an of_node_get on each iteration,
so a return from the middle of the loop requires an of_node_put.
A simplified version of the semantic patch that finds this problem is as
follows (http://coccinelle.lip6.fr):
//
@@
expression root,e;
local
From: Julia Lawall
for_each_available_child_of_node performs an of_node_get on each iteration,
so a return from the middle of the loop requires an of_node_put.
A simplified version of the semantic patch that finds this problem is as
follows (http://coccinelle.lip6.fr):
//
@@
expression
On 08/12/15 14:05, Andrew Lunn wrote:
The setup() callback is not used by any in kernel code. Remove it.
Any new code which requires access to the eeprom can use the NVMEM
API.
Signed-off-by: Andrew Lunn
---
drivers/misc/eeprom/at25.c | 26 --
On Mon, Dec 14, 2015 at 12:54:53PM +0100, Peter Zijlstra wrote:
> On Mon, Dec 14, 2015 at 06:42:24AM +0800, Yuyang Du wrote:
> > > In most cases 'r' shouldn't exceed 1024 and util_sum not significantly
> > > exceed 1024*47742, but in extreme cases like spawning lots of new tasks
> > > it may
On Tue, Dec 15, 2015 at 03:55:14PM +0800, Jiang Liu wrote:
> Aha, found a possible regression. Could you please help to apply
> the attached bugfix patch ontop of "cc22b9b83f6a x86/irq: Enhance
> __assign_irq_vector() to rollback in case of failure"?
Yap, attached patch seems to work here.
From: Arnd Bergmann
The sun9i usb phy driver calls of_usb_get_phy_mode(), which is not
available if USB is disabled:
drivers/built-in.o: In function `sun9i_usb_phy_probe':
:(.text+0x7fb0): undefined reference to `of_usb_get_phy_mode'
This adds a dependency to avoid the randconfig build errors.
From: Julia Lawall
for_each_child_of_node performs an of_node_get on each iteration,
so a return from the middle of the loop requires an of_node_put.
A simplified version of the semantic patch that finds this problem is as
follows (http://coccinelle.lip6.fr):
//
@@
expression root,e;
local
Thanks Andrew for looking into this.
On 08/12/15 14:05, Andrew Lunn wrote:
This patches converts the old EEPROM drivers in driver/misc/eeprom to
use the NVMEM framework. These drivers export there content in /sys as
read only to root, since the EEPROM may contain sensitive information.
So the
From: Chunfeng Yun
On driver detach, devm_phy_release() will put a refcount to
the phy, so gets a refconut to it before return.
Signed-off-by: Chunfeng Yun
Signed-off-by: Kishon Vijay Abraham I
---
drivers/phy/phy-core.c | 21 +++--
1 file changed, 15 insertions(+), 6
On 08/12/15 14:05, Andrew Lunn wrote:
Add a regmap for accessing the EEPROM, and then use that with the
NVMEM framework. Use it backward compatibility register function, so
that the 'eeprom' file in sys is provided by the framework.
Signed-off-by: Andrew Lunn
---
> -Original Message-
> From: Christoffer Dall [mailto:christoffer.d...@linaro.org]
> Sent: Tuesday, December 15, 2015 2:59 PM
> To: Bhushan Bharat-R65777
> Cc: kvm...@lists.cs.columbia.edu; k...@vger.kernel.org; linux-arm-
> ker...@lists.infradead.org; linux-kernel@vger.kernel.org
>
Below are few comments.
On 08/12/15 14:05, Andrew Lunn wrote:
Older drivers made an 'eeprom' file available in the /sys device
directory. Have the NVMEM core provide this to retain backwards
compatibility.
Signed-off-by: Andrew Lunn
---
drivers/nvmem/Kconfig | 7
From: Julia Lawall
for_each_available_child_of_node performs an of_node_get on each iteration,
so a return from the middle of the loop requires an of_node_put.
A simplified version of the semantic patch that finds this problem is as
follows (http://coccinelle.lip6.fr):
//
@@
expression
On 11/12/15 13:03, Wolfram Sang wrote:
On Tue, Dec 08, 2015 at 03:05:07PM +0100, Andrew Lunn wrote:
Older drivers made an 'eeprom' file available in the /sys device
directory. Have the NVMEM core provide this to retain backwards
compatibility.
Signed-off-by: Andrew Lunn
---
Hi David,
On Tue, Dec 15, 2015 at 7:00 AM, David Gibson
wrote:
>> If the only property needed is the partition table offset, it can be encoded
>> in the unit-address, and the "reg" property:
>>
>> partitions {
>>
>> partition-table@ {
>> reg =
Hi Andrew,
Thanks for this patch.
On 08/12/15 14:05, Andrew Lunn wrote:
Legacy AT24, AT25 EEPROMs are exported in sys so that only root can
read the contents. The EEPROMs may contain sensitive information. Add
a flag so the provide can indicate that NVMEM should also restrict
access to root
Hi all,
Changes since 20151214:
The samsung-krzk tree gained a conflict against the renesas tree.
The net-next tree gained a conflict against the net tree.
The drm-msm tree gained a build failure for which I applied a merge
fix patch.
The akpm-current tree gained a conflict against the
Op 15-12-15 om 02:29 schreef Dmitry Torokhov:
> Userspace can close the sync device while there are still active fence
> points, in which case kernel produces the following warning:
>
> [ 43.853176] [ cut here ]
> [ 43.857834] WARNING: CPU: 0 PID: 892 at
>
On Sat 12-12-15 22:18:55, Vladimir Davydov wrote:
> On Sat, Dec 12, 2015 at 11:45:40AM -0500, Johannes Weiner wrote:
> > On Sat, Dec 12, 2015 at 04:34:02PM +0300, Vladimir Davydov wrote:
> > > Memory cgroup reclaim can be interrupted with mem_cgroup_iter_break()
> > > once enough pages have been
On Thursday 26 November 2015 06:05 AM, Geliang Tang wrote:
> WARN() takes a condition and a format string. The condition was
> omitted. So I added it.
>
> Signed-off-by: Geliang Tang
Applied.
Thanks,
Sekhar
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body
Hi Andrew,
After merging the akpm-current tree, today's linux-next build (powerpc
pseries_le_defconfig) failed like this:
mm/huge_memory.c: In function 'madvise_free_huge_pmd':
mm/huge_memory.c:1592:14: error: implicit declaration of function 'pmd_mkclean'
blk_end_request_all may free request, so we need to save
request_queue pointer before blk_end_request_all call.
The problem was introduced in commit cf8ecc5a8455266f8d51
("null_blk: guarantee device restart in all irq modes")
and causes general protection fault with slab poisoning
enabled.
Hi Mark,
> -Original Message-
> From: Marc Zyngier [mailto:marc.zyng...@arm.com]
> Sent: Tuesday, December 15, 2015 3:05 PM
> To: Bhushan Bharat-R65777 ;
> kvm...@lists.cs.columbia.edu; k...@vger.kernel.org; linux-arm-
> ker...@lists.infradead.org; linux-kernel@vger.kernel.org
> Subject:
On 14/12/15 21:29, Rafael J. Wysocki wrote:
> On Monday, December 14, 2015 03:13:48 PM Marc Zyngier wrote:
>> On 10/12/15 16:55, Suravee Suthikulpanit wrote:
>>> This patch introduces pci_msi_register_fwnode_provider() for irqchip
>>> to register a callback, to provide a way to determine
On Mon, Dec 14, 2015 at 11:22:46AM +0100, Geert Uytterhoeven wrote:
> On Sat, Dec 12, 2015 at 6:51 AM, David Gibson
> wrote:
> > On Thu, Dec 10, 2015 at 12:43:24PM -0800, Brian Norris wrote:
> >> On Mon, Dec 07, 2015 at 12:36:28PM +1100, David Gibson wrote:
> >> > On Sat, Dec 05, 2015 at
On Mon, Dec 14, 2015 at 02:02:18PM -0800, Shi, Yang wrote:
> I tried to enable latencytop for arm64 and came across this discussion, so
> any plan about when this will get merged into mainline? 4.5 merge window?
It's queued in linux-next, so I imagine its heading for 4.5.
Will
--
To unsubscribe
On Mon, Dec 14, 2015 at 05:00:59PM -0800, Luck, Tony wrote:
> Not sure what the "whatnot" would be though. Making it depend on
> X86_MCE should keep it out of the tiny configurations. By the time
> you have MCE support, this seems like a pretty small incremental
> change.
Ok, so it is called
On Tue, Dec 08, 2015 at 07:43:50AM +0100, Anton Bondarenko wrote:
> DMA transfer for SPI was limited to up to 8 bits word size until now.
> Sync in SPI burst size and DMA bus width is necessary to correctly
> support 16 and 32 BPW.
>
> Signed-off-by: Anton Bondarenko
> ---
>
> -Original Message-
> From: Fan Li [mailto:fanofcode...@samsung.com]
> Sent: Tuesday, December 15, 2015 5:03 PM
> To: 'Jaegeuk Kim'
> Cc: linux-kernel@vger.kernel.org; linux-f2fs-de...@lists.sourceforge.net
> Subject: [f2fs-dev] [PATCH] f2fs: fix to reset variable correctlly
>
>
Hi Jaegeuk, Yunlei,
I help do some edits and send it out as my patch's base. :)
But if you want to send patch by yourself, please ignore this patch.
Thanks,
> -Original Message-
> From: Chao Yu [mailto:chao2...@samsung.com]
> Sent: Tuesday, December 15, 2015 5:17 PM
> To: Jaegeuk Kim
Add new device tree node for the control module register space where
PCIe registers are present.
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/boot/dts/dra7.dtsi |5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/dra7.dtsi b/arch/arm/boot/dts/dra7.dtsi
index
Add "syscon-phy-power" property and "syscon-pcs" property which can
be used to perform the control module initializations and remove
the deprecated "ctrl-module" property from PCIe PHY dt nodes.
Phandle to "sysclk" clock node is also added to the PCIe PHY node
since some of the syscon
This series is basically to deprecate using ctrl-module property and use
corresponding syscon properties to program the control module registers.
Changes from v2:
No changes.
Changes from v1:
*) Squashed the patches that replaces "ctrl-module" with
"syscon-phy-power"
*) Added
The USB2 PHY2 has a different register map compared to USB2 PHY1
to power on/off the PHY. In order to handle it, use the new compatible
string "ti,dra7x-usb2-phy2" for the second instance of USB2 PHY.
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/boot/dts/dra7.dtsi |3 ++-
1 file
On Mon 2015-12-14 14:25:10, Andy Lutomirski wrote:
> On Mon, Dec 14, 2015 at 1:24 PM, Arjan van de Ven
> wrote:
> >
> >> That's weird. The only API to do that seems to be manually setting
> >> kmap_prot to _PAGE_KERNEL_EXEC, and nothing does that. (Why is
> >> kmap_prot a variable on x86 at
Add "syscon-phy-power" property and remove the deprecated "ctrl-module"
property from SATA and USB PHY node. Also remove the unused control
module dt nodes.
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/boot/dts/am4372.dtsi | 16 ++--
arch/arm/boot/dts/dra7.dtsi | 34
Hi Peter,
On Friday 04 December 2015 07:23 PM, Peter Ujfalusi wrote:
> Switch to use the ti,edma3-tpcc and ti,edma3-tptc binding for the eDMA3.
> With the new bindings boards can customize and tweak the DMA channel
> priority to match their needs. With the new binding the memcpy is safe
> to be
Stephen Rothwell writes:
> Hi Andrew,
>
> Today's linux-next merge of the akpm-current tree got conflicts in:
>
> arch/powerpc/include/asm/nohash/64/pgtable.h
> arch/powerpc/mm/pgtable_64.c
>
> between various commits from the powerpc tree and commits:
>
> e56ebae0dd4c ("powerpc, thp:
On 12/15/2015 04:47 PM, Kai Huang wrote:
A further thinking is can we move it to mmu_need_write_protect? Passing
can_unsync as parameter to
kvm_unsync_pages sounds a little bit odd.
+
if (s->unsync)
continue;
WARN_ON(s->role.level != PT_PAGE_TABLE_LEVEL);
On 12/15/2015 04:43 PM, Kai Huang wrote:
On 12/01/2015 02:26 AM, Xiao Guangrong wrote:
Now, all non-leaf shadow page are page tracked, if gfn is not tracked
there is no non-leaf shadow page of gfn is existed, we can directly
make the shadow page of gfn to unsync
Signed-off-by: Xiao
On 15/12/15 03:46, Bhushan Bharat wrote:
>
> Hi All,
>
> I am running "iperf" in KVM guest on ARM64 machine and observing below crash.
>
> =
> $iperf -c 3.3.3.3 -P 4 -t 0 -i 5 -w 90k
>
> Client connecting
On Monday 30 November 2015 11:09:42 Nicolas Pitre wrote:
> On Mon, 30 Nov 2015, Pali Rohár wrote:
>
> > On Monday 30 November 2015 07:23:53 Tony Lindgren wrote:
> > > * Pali Rohár [151129 16:16]:
> > > > On Monday 30 November 2015 01:09:17 Nicolas Pitre wrote:
> > > > > On Sun, 29 Nov 2015,
On 2015/12/15 17:30, Vladimir Davydov wrote:
On Tue, Dec 15, 2015 at 12:12:40PM +0900, Kamezawa Hiroyuki wrote:
On 2015/12/15 0:30, Michal Hocko wrote:
On Thu 10-12-15 14:39:14, Vladimir Davydov wrote:
In the legacy hierarchy we charge memsw, which is dubious, because:
- memsw.limit must
On Tue, Dec 15, 2015 at 03:46:03AM +, Bhushan Bharat wrote:
>
> Hi All,
>
> I am running "iperf" in KVM guest on ARM64 machine and observing below crash.
Which host/guest kernel version is this?
Which hardware?
-Christoffer
>
> =
> $iperf -c 3.3.3.3 -P 4 -t 0
On Mon, Dec 14, 2015 at 05:29:55PM -0800, Dmitry Torokhov wrote:
> Userspace can close the sync device while there are still active fence
> points, in which case kernel produces the following warning:
>
> [ 43.853176] [ cut here ]
> [ 43.857834] WARNING: CPU: 0 PID:
Hi Enric,
Am Dienstag, 15. Dezember 2015, 09:25:34 schrieb Enric Balletbo Serra:
> Arght, I'm asleep, I need a coffee this now, there isn't patch 2/2,
> this patch is 1/1.
I do think you can limit the recipients to "a...@kernel.org", the mailing lists
and me (and include
On Mon, Dec 14, 2015 at 04:26:26PM -0800, Eric Anholt wrote:
> VC4 wraps the CMA objects in its own structures, so it needs to do its
> own teardown (waiting for GPU to finish, updating bo_stats tracking).
> The other CMA drivers are using drm_gem_cma_free_object as their
> gem_free_object, so
Stephen,
Do you mind us taking that through the at91 and arm-soc trees?
On 10/12/2015 at 18:06:52 +0100, Boris Brezillon wrote :
> On Fri, 4 Dec 2015 18:03:35 +0100
> Alexandre Belloni wrote:
>
> > Hi,
> >
> > This patch set is a cleanup that properly separate drivers needing to
> > access
No functional change. Introduce local struct device pointer in
probe and replace using >dev/phy->dev with the local
device pointer. This is in preparation to split ti_pipe3_probe
and add separate functions for getting mem resource, getting
sysctrl and getting clocks.
Signed-off-by: Kishon Vijay
No functional change. Moved sysctrl initialization done in probe to a
separate function as part of cleaning up ti_pipe3_probe.
Signed-off-by: Kishon Vijay Abraham I
---
drivers/phy/phy-ti-pipe3.c | 78 +---
1 file changed, 45 insertions(+), 33
Introduce __f2fs_commit_super to include duplicated codes in
f2fs_commit_super for cleanup.
Signed-off-by: Chao Yu
---
fs/f2fs/super.c | 28 +---
1 file changed, 13 insertions(+), 15 deletions(-)
diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c
index 2d4fed8..56a160a
We have already got one copy of valid super block in memory, do not grab
buffer header of super block all the time.
Signed-off-by: Chao Yu
---
fs/f2fs/f2fs.h | 2 +-
fs/f2fs/file.c | 8 ++
fs/f2fs/super.c | 81 +
3 files changed,
No functional change. Previously omap_control_phy_power() was used to power
off the PHY during probe. But once PIPE3 driver is adapted to use syscon,
omap_control_phy_power() cannot be used. Hence used ti_pipe3_power_off
to power off the PHY.
Signed-off-by: Kishon Vijay Abraham I
Acked-by: Roger
Deprecate using phy-omap-control driver to power on/off the PHY and
use *syscon* framework to do the same.
Signed-off-by: Kishon Vijay Abraham I
---
Documentation/devicetree/bindings/phy/ti-phy.txt | 10 ++-
drivers/phy/phy-ti-pipe3.c | 90 ++
2
Deprecate using phy-omap-control driver to set PCS value of the PHY
and start using *syscon* API to do the same.
Signed-off-by: Kishon Vijay Abraham I
Acked-by: Roger Quadros
---
Documentation/devicetree/bindings/phy/ti-phy.txt |2 ++
drivers/phy/phy-ti-pipe3.c | 34
From: Yunlei He
f2fs use fields of f2fs_super_block struct directly in a grabbed buffer.
Once the buffer happen to be destroyed (e.g. through dd), it may bring
in unpredictable effect on f2fs.
This patch fixes to allocate additional buffer to store datas of super
block rather than using
On 12/15/2015 03:52 PM, Kai Huang wrote:
static bool __mmu_gfn_lpage_is_disallowed(gfn_t gfn, int level,
@@ -2140,12 +2150,18 @@ static struct kvm_mmu_page *kvm_mmu_get_page(struct
kvm_vcpu *vcpu,
hlist_add_head(>hash_link,
Deprecate using phy-omap-control driver to power on/off the PHY,
and use *syscon* framework to do the same. This handles
powering on/off the PHY for the USB2 PHYs used in various TI SoCs.
Signed-off-by: Kishon Vijay Abraham I
---
Documentation/devicetree/bindings/phy/ti-phy.txt |8 +-
No functional change. Previously omap_control_phy_power() was used to power
off the PHY during probe. But once phy-omap-usb2 driver is adapted to
use syscon, omap_control_phy_power() cannot be used. Hence used
omap_usb_power_off to power off the PHY.
Signed-off-by: Kishon Vijay Abraham I
This series is basically to deprecate using phy-omap-control and use
syscon APIs to program the control module registers.
Changes from v2:
No changes.
Changes from v1:
*) cleanup ti_pipe3_probe in multiple steps
*) other minor cleanups
Changes from [1] in PHY patches include
*) cleanup
No functional change. Moved clock initialization done in probe to a
separate function as part of cleaning up ti_pipe3_probe.
Signed-off-by: Kishon Vijay Abraham I
---
drivers/phy/phy-ti-pipe3.c | 127 +---
1 file changed, 72 insertions(+), 55
No functional change. Moved mem resource initialization done in
probe to a separate function as part of cleaning up
ti_pipe3_probe.
Signed-off-by: Kishon Vijay Abraham I
---
drivers/phy/phy-ti-pipe3.c | 52
1 file changed, 33 insertions(+), 19
On Mon, 2015-12-14 at 05:01PM +, Marc Zyngier wrote:
> Mark,
>
> On 14/12/15 16:46, Mark Rutland wrote:
> > On Mon, Dec 14, 2015 at 08:31:40AM -0800, Soren Brinkmann wrote:
> >> Signed-off-by: Soren Brinkmann
> >> ---
> >> arch/arm64/boot/dts/xilinx/zynqmp.dtsi | 6 +++---
> >> 1 file
On Tue, Dec 15, 2015 at 08:22:20AM +1100, Dave Chinner wrote:
> $ gdb vmlinux
>
> (gdb) l *(xfs_iflush_cluster+0x9d7)
It's not working. Shame on me, I forgot to set "Compile the kernel with debug
info".
I'm recompiling, to try it again.
Maybe, in the meanwhile, you can do something with my
On 12/15/2015 04:11 PM, Kai Huang wrote:
On 12/01/2015 02:26 AM, Xiao Guangrong wrote:
The page fault caused by write access on the write tracked page can not
be fixed, it always need to be emulated. page_fault_handle_page_track()
is the fast path we introduce here to skip holding mmu-lock
Le 11/12/2015 04:07, Songjun Wu a écrit :
> Add code to unregister codec in probe function,
> when the error occurs after the codec is registered.
>
> Signed-off-by: Songjun Wu
Seems okay:
Acked-by: Nicolas Ferre
Thanks,
> ---
>
> sound/soc/atmel/atmel-classd.c | 14 ++
> 1
Hi,
On Monday 14 December 2015 09:45:48 Rob Herring wrote:
> On Mon, Dec 14, 2015 at 8:28 AM, Linus Walleij
> wrote:
> > On Fri, Dec 11, 2015 at 3:06 PM, Rob Herring wrote:
> >> On Fri, Dec 11, 2015 at 6:39 AM, Linus Walleij
> >> wrote:
> >>> On Fri, Dec 4, 2015 at 6:31 PM, Martyn Welch
>
On 12/14/2015 12:05 PM, Andrzej Hajda wrote:
The function can return negative values, so its result should
be assigned to signed variable.
The problem has been detected using proposed semantic patch
scripts/coccinelle/tests/assign_signed_to_unsigned.cocci [1].
[1]:
On Tue, Dec 15, 2015 at 08:20:50AM +, Wang Nan wrote:
> All hists test cases forget to reset err after using it to hold an
> error code. If error occure in setup_fake_machine() it incorrectly
> return TEST_OK.
>
> This patch fixes it.
>
> Signed-off-by: Wang Nan
> Suggested-by: Namhyung Kim
801 - 900 of 1878 matches
Mail list logo
