On 11/13/14 at 11:30am, HATAYAMA Daisuke wrote:
> Currently, VMCOREINFO note information reports the virtual address of
> phys_base that is assigned to symbol phys_base. But this doesn't make
> sense because to refer to phys_base, it's necessary to get the value
> of phys_base itself we are now abo
Dear all,
Is there any issue I need to resolve so that the patch can be merged?
Thanks in advance,
Jisheng
On Wed, 10 Dec 2014 22:26:41 -0800
Jisheng Zhang wrote:
> readl/writel is too expensive especially on Cortex A9 w/ outer L2 cache.
> This introduces i2c read/write errors on Marvell BG2/B
Add 'polling_ms' sysfs node to change charger-manager's monitoring rate
in runtime. It can set only bigger than 2 jiffies (for 200 HZ system it
is 10 msecs.) as it's allowed for minimum poling rate in previous.
It resets poller and re-configure polling rate based on new input if next
polling time i
cm_notify_event() is introduced to get event associated with battery status
externally, but no one had been used. Moreover it makes charger manager
driver more complicated. This patch tries to drop the function and all data
related to simplify the driver.
Signed-off-by: Jonghwa Lee
---
.../bindi
Add additional polling mode for sleep state to define different mode with
normal state. With this change, charger-manager can work differently in
normal state or sleep state. e.g, polling aways for normal and polling
only when charing for sleep. If there is no defined polling mode for
sleep state i
Current charger-manager calls power_suuply_changed() whenever charging
status is changed. This patch removes seperated power_supply_changed()
use and let it be called at end of try_charger_enable() function which
is called to set charging/discharging.
Signed-off-by: Jonghwa Lee
---
drivers/power
This patch prevents direct charging control in cable notification.
It sets only input current limit according to cable type and yields charging
control to be done by cm_monitor() where charging management proceeds.
It may loose few ms to enable charging compared to before, even though it's
more imp
When charger-manager checks whether external power source is available,
it gets information from charger IC driver. However, it's not correct source,
charger IC doesn't have responsibilty to give cable connection status.
The charger-manager already gets cable information from EXTCON susbsystem,
so
After charger manager's initially introduced, it has kept its codes without any
big change. However, the charger manager working operation isn't optimized and
it also has unused codes and non-generic interface. This series tries to make
charger manager more generic and maintainable with some fixes.
The POWER_SUPPLY_CHARGE_NOW/FULL property reflects battery's charges
in uAh unit, but charger-manager has been used it wrongly. This patch
makes it to use those propeties correctly and change to be optional.
Signed-off-by: Jonghwa Lee
---
drivers/power/charger-manager.c | 85 +-
In cm_monitor() where charging management starts, it checks various charging
condition sequentially to decide next charging operation. However, as it
follows sequential process, cascaded IF statements, it does some duplicated
jobs which is already done in previous stage. It results delay in decisio
It drops the way of using power_supply interface to reference battery's
temperature. Then it tries to use thermal subsystem's only. This makes driver
more simple and also can remove ifdeferies.
Signed-off-by: Jonghwa Lee
---
drivers/power/Kconfig |1 +
drivers/power/charger-m
Whenever battery status is changed, charger manager tries to trigger uevent
through private interface. This patch modifies it to use power_supply_changed()
since it belongs to power supply subsystem.
Signed-off-by: Jonghwa Lee
---
drivers/power/charger-manager.c | 91 +-
> -Original Message-
> From: linux-kernel-ow...@vger.kernel.org
> [mailto:linux-kernel-ow...@vger.kernel.org] On Behalf Of Paolo Bonzini
> Sent: Thursday, December 18, 2014 4:37 PM
> To: linux-kernel@vger.kernel.org
> Cc: io...@lists.linux-foundation.org; k...@vger.kernel.org;
> linux-ker
> -Original Message-
> From: iommu-boun...@lists.linux-foundation.org
> [mailto:iommu-boun...@lists.linux-foundation.org] On Behalf Of Zhang, Yang Z
> Sent: Thursday, December 18, 2014 11:10 PM
> To: Paolo Bonzini; k...@vger.kernel.org
> Cc: io...@lists.linux-foundation.org; linux-kernel@
On Fri, Dec 19, 2014 at 4:39 AM, David Miller
wrote:
From: Jason Wang
Date: Thu, 18 Dec 2014 13:57:19 +0800
Fixes cecda693a969816bac5e470e1d9c9c0ef5567bca
Please correct this fixes tag, it should be of the form:
Fixes: $(SHA1) ("header text of commit message")
The SHA1 ID should be re
Commit cecda693a969816bac5e470e1d9c9c0ef5567bca ("net: keep original skb
which only needs header checking during software GSO") keeps the original
skb for packets that only needs header check, but it doesn't drop the
packet if software segmentation or header check were failed.
Fixes cecda693a9 ("n
On 12/19/2014 09:46 AM, Aaron Lu wrote:
> CC Jani, who is working on the patchset to enable 8+ output devices and
> may have some comments on this.
Change Jani's email address, I got a warning from the mailer about his other
email address.
>
> Regards,
> Aaron
>
> On 12/18/2014 09:25 PM, Josh B
Wu, Feng wrote on 2014-12-19:
>
>
> iommu-boun...@lists.linux-foundation.org wrote on
> mailto:iommu-boun...@lists.linux-foundation.org] On Behalf Of:
>> Cc: io...@lists.linux-foundation.org; linux-kernel@vger.kernel.org;
>> k...@vger.kernel.org
>> Subject: RE: [v3 25/26] KVM: Suppress posted-in
(2014/12/19 0:49), Josh Poimboeuf wrote:
> On Thu, Dec 18, 2014 at 08:55:21PM +0900, Masami Hiramatsu wrote:
>> (2014/12/17 2:58), Seth Jennings wrote:
>>> changes in v7:
>>> - TODO: set IPMODIFY (not a blocker to moving forward)
>>
>> Why don't you set this?
>> IPMODIFY series are not completely a
(2014/12/19 0:52), Jiri Kosina wrote:
> On Thu, 18 Dec 2014, Masami Hiramatsu wrote:
>
>>> This adds a new taint flag to indicate when the kernel or a kernel
>>> module has been live patched. This will provide a clean indication in
>>> bug reports that live patching was used.
>>>
>>> Additionally
From: Dan Collins
Date: Fri, 19 Dec 2014 13:32:19 +1300
> + * Dan Collins : Fixed TPACKET_V3 to wake poll when block is closed
> + * rather than for every packet.
Since we now use real version control with commit messages, this
comment at the top of th
I have been trying to move an 8360 based system from a 3.0 kernel to a
3.12 (on the way to 3.14 with ipipe/xenomai) kernel and encountered an
oops in the ucc_geth driver when using RTBI mode on one of the ucc
ports. I haven't managed to find any commits to of_mdio or ucc_geth or
fsl_pq_mdio that w
On Thu, Dec 18, 2014 at 6:45 PM, Dave Jones wrote:
>
> Example of the spew-o-rama below.
Hmm. Not only does it apparently stay up for you now, the traces seem
to be improving in quality.
There's a decided pattern of "copy_page_range()" and "zap_page_range()" here.
Now, what's *also* intriguing
Make TPACKET_V3 signal poll when block is closed rather than for every
packet. Side effect is that poll will be signaled when block retire
timer expires which didn't previously happen. Issue was visible when
sending packets at a very low frequency such that all blocks are retired
before packets are
On Fri, 2014-12-19 at 02:34 +, Chickles, Derek wrote:
> > On Thu, 2014-12-18 at 12:12 -0800, Derek Chickles wrote:
> > > This fixes the check that was supposed to prevent the MAINTAINERS
> > > warning from appearing when you run checkpatch.pl on a patch that
> > > includes new files/directories
On Thu, Dec 18, 2014 at 07:49:41PM -0800, Linus Torvalds wrote:
> And when spinlocks start getting contention, *nested* spinlocks
> really really hurt. And you've got all the spinlock debugging on etc,
> don't you?
Yeah, though remember this seems to have for some reason gotten worse
in more
From: Jason Wang
Date: Fri, 19 Dec 2014 11:09:13 +0800
> Commit cecda693a969816bac5e470e1d9c9c0ef5567bca ("net: keep original skb
> which only needs header checking during software GSO") keeps the original
> skb for packets that only needs header check, but it doesn't drop the
> packet if softwar
On Thu, Dec 18, 2014 at 10:58:59PM -0500, Dave Jones wrote:
> > lock debugging and other overheads (does this still have
> > DEBUG_PAGEALLOC?) you really are getting into a "real" softlockup
> > because things are scaling so horribly badly.
> >
> > If you now disable spinlock debugging a
Eric Paris explains: Since kauditd_send_multicast_skb() gets called in
audit_log_end(), which can come from any context (aka even a sleeping context)
GFP_KERNEL can't be used. Since the audit_buffer knows what context it should
use, pass that down and use that.
See: https://lkml.org/lkml/2014/12/
This sender alert message is generated by PureMessage because it has
encountered the following events.
Event(s): Virus infection detected
Message action: Message quarantined
Message
ID:
Subject: Mail Delivery (failure kullan...@domain.com)
Sender: linux-kernel@vger.kernel.org
Recipient(s): kulla
> -Original Message-
> From: Zhang, Yang Z
> Sent: Friday, December 19, 2014 11:33 AM
> To: Wu, Feng; Paolo Bonzini; k...@vger.kernel.org
> Cc: io...@lists.linux-foundation.org; linux-kernel@vger.kernel.org;
> k...@vger.kernel.org
> Subject: RE: [v3 25/26] KVM: Suppress posted-interrupt w
Wu, Feng wrote on 2014-12-19:
>
>
> Zhang, Yang Z wrote on 2014-12-19:
>> Subject: RE: [v3 25/26] KVM: Suppress posted-interrupt when 'SN' is
>> set
>>
>> Wu, Feng wrote on 2014-12-19:
>>>
>>>
>>> iommu-boun...@lists.linux-foundation.org wrote on
>> mailto:iommu-boun...@lists.linux-foundation.
On 12/19/2014 04:08 AM, Jeremiah Mahler wrote:
Karthik,
On Thu, Dec 18, 2014 at 02:50:11PM +0530, Karthik Nayak wrote:
As per checkpatch warning, removed an unnecessary else statement
proceeding an if statement with a return.
Signed-off-by: Karthik Nayak
---
drivers/staging/rtl8192u/r8192U
On Thu, Dec 18, 2014 at 8:03 PM, Dave Jones wrote:
>
> So the only thing that was on that could cause spinlock overhead
> was DEBUG_SPINLOCK (and LOCK_STAT, though iirc that's not huge either)
So DEBUG_SPINLOCK does have one big downside if I recall correctly -
the debugging spinlocks are very mu
> -Original Message-
> From: Zhang, Yang Z
> Sent: Friday, December 19, 2014 12:44 PM
> To: Wu, Feng; Paolo Bonzini; k...@vger.kernel.org
> Cc: io...@lists.linux-foundation.org; linux-kernel@vger.kernel.org;
> k...@vger.kernel.org
> Subject: RE: [v3 25/26] KVM: Suppress posted-interrupt w
FYI, we noticed the below changes on
commit 7cc36bbddde5cd0c98f0c06e3304ab833d662565 ("vmstat: on-demand vmstat
workers V8")
testbox/testcase/testparams: lkp-sbx04/will-it-scale/performance-pread2
f0d6d1f6ff6f8525 7cc36bbddde5cd0c98f0c06e33
--
On Thu, Dec 18, 2014 at 4:55 PM, Rusty Russell wrote:
>
> The exciting thing here is the getting rid of stop_machine on module
> removal. This is possible by using a simple atomic_t for the counter,
> rather than our fancy per-cpu counter: it turns out that no one is doing
> a module increment pe
On 19 December 2014 at 05:18, Roopa Prabhu wrote:
> On 12/18/14, 3:26 PM, Samudrala, Sridhar wrote:
>>
>>
>> On 12/18/2014 3:07 PM, Roopa Prabhu wrote:
>>>
>>> On 12/18/14, 11:21 AM, John Fastabend wrote:
On 12/18/2014 10:14 AM, Roopa Prabhu wrote:
>
> On 12/18/14, 10:02 AM, Varl
Hi Roger,
On Thursday 18 December 2014 09:22 PM, Roger Quadros wrote:
> Fixing up Paul's email id.
>
> cheers,
> -roger
>
> On 18/12/14 17:49, Roger Quadros wrote:
>> There are quite a few hwmods that don't have sysconfig register and so
>> _find_mpu_rt_port(oh) will return NULL thus preventing r
Wu, Feng wrote on 2014-12-19:
>
>
> Zhang, Yang Z wrote on 2014-12-19:
>> Subject: RE: [v3 25/26] KVM: Suppress posted-interrupt when 'SN' is
>> set
>>
>> Wu, Feng wrote on 2014-12-19:
>>>
>>>
>>> Zhang, Yang Z wrote on 2014-12-19:
Subject: RE: [v3 25/26] KVM: Suppress posted-interrupt wh
On Fri, Dec 19, 2014 at 10:17 AM, Huang Ying wrote:
> FYI, we noticed the below changes on
>
> https://git.linaro.org/people/vireshk/linux cpufreq/stats/cleanups
> commit 2136fa84639adcc0727e968f99ad222c8146810c ("cpufreq: stats: Fix
> locking")
>
>
> +--++
On Thu, 2014-12-18 at 09:05 -0200, Mauro Carvalho Chehab wrote:
> Hi Huang,
>
> Em Thu, 18 Dec 2014 16:13:26 +0800
> Huang Ying escreveu:
>
> > FYI, we noticed the below changes on
> >
> > commit 50d1bb93672fa2f42cec6e06ce799fbe864f57e9 ("sb_edac: add support for
> > Haswell based systems")
>
Current psci's cpu_suspend callback can be used only when common cpu idle
configuration is enabled. However, it's also needed for system which only
uses generic pm suspend not cpu idle. This patch modifies psci driver to
support both of cases.
Signed-off-by: Jonghwa Lee
---
arch/arm64/kernel/psc
The execution flow redirection related implemention in the livepatch
ftrace handler is depended on the specific architecture. This patch
introduces klp_arch_set_pc(like kgdb_arch_set_pc) interface to change
the pt_regs.
Signed-off-by: Li Bin
---
arch/x86/include/asm/livepatch.h |5 +
ker
> -Original Message-
> From: Zhang, Yang Z
> Sent: Friday, December 19, 2014 1:26 PM
> To: Wu, Feng; Paolo Bonzini; k...@vger.kernel.org
> Cc: io...@lists.linux-foundation.org; linux-kernel@vger.kernel.org;
> k...@vger.kernel.org
> Subject: RE: [v3 25/26] KVM: Suppress posted-interrupt wh
%s/ARCH_SUPPORT_FTARCE_OPS/ARCH_SUPPORTS_FTRACE_OPS/
Signed-off-by: Li Bin
---
kernel/trace/ftrace.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/kernel/trace/ftrace.c b/kernel/trace/ftrace.c
index 929a733..9473b24 100644
--- a/kernel/trace/ftrace.c
+++ b/kernel/trac
On 12/18/2014 07:39 PM, Philipp Zabel wrote:
Am Donnerstag, den 18.12.2014, 15:11 +0800 schrieb Liu Ying:
This patch adds i.MX MIPI DSI host controller driver support.
Currently, the driver supports the burst with sync pulses mode only.
Signed-off-by: Liu Ying
---
v1->v2:
* Address almost al
0x6/0x20
> > > [] strcmp+0x6/0x20
> > > [5.354451] RSP
> > > [5.354451] RSP
> > > [5.354451] CR2: 8804e5f0
> > > [5.354451] CR2: 8804e5f0
> > > [5.354451] ---[ end trace 8f9377
On Fri, Dec 19, 2014 at 2:08 AM, Benoit Parrot wrote:
> Alexandre Courbot wrote on Wed [2014-Dec-17 17:41:51
> +0900]:
>> Looks ok to me. I have a few nits below, but otherwise I am happy with
>> how it turned out:
>>
>> Reviewed-by: Alexandre Courbot
> I'll add this to the next version.
>
>>
>
The execution flow redirection related implemention in the livepatch
ftrace handler is depended on the specific architecture. This patch
introduces klp_arch_set_pc(like kgdb_arch_set_pc) interface to change
the pt_regs.
Signed-off-by: Li Bin
---
arch/x86/include/asm/livepatch.h |5 +
ker
Sorry! Bad format, please ignore this patch.
On 2014/12/19 13:37, Li Bin wrote:
> The execution flow redirection related implemention in the livepatch
> ftrace handler is depended on the specific architecture. This patch
> introduces klp_arch_set_pc(like kgdb_arch_set_pc) interface to change
> th
On Wed, Dec 17, 2014 at 10:03:13PM +, Al Viro wrote:
> On Wed, Dec 17, 2014 at 10:52:56AM -0800, Christoph Hellwig wrote:
> > On Wed, Dec 17, 2014 at 06:58:32AM -0800, Omar Sandoval wrote:
> > > See my previous message. If we use O_DIRECT on the original open, then
> > > filesystems that implem
On Thu, Dec 18, 2014 at 10:24:05PM -0800, Omar Sandoval wrote:
> + swap_file = file_open_name(name, O_RDWR | O_LARGEFILE | O_DIRECT, 0);
> + if (IS_ERR(swap_file) && PTR_ERR(swap_file) == -EINVAL)
ITYM if (swap_file == ERR_PTR(-EINVAL)) here...
--
To unsubscribe from this list: send th
Most filesystems prevent truncation of an active swapfile by way of
inode_newsize_ok, called from inode_change_ok. NFS doesn't call either
from nfs_setattr, presumably because most of these checks are expected
to be done server-side. However, the IS_SWAPFILE check can only be done
client-side, and
> From: David Miller [mailto:da...@davemloft.net]
> Sent: Thursday, November 27, 2014 4:34 AM
[...]
> >> > Looks like a candidate for ndo_gso_check(), so that we do not drop, but
> >> > instead segment from netif_needs_gso()/validate_xmit_skb()
> >>
> >> You mean have the bridge implement the ndo
Dear Myungjoo,
On 12/19/2014 11:11 AM, MyungJoo Ham wrote:
>>
>> Dear Myungjoo,
>>
>> Thanks for your review.
>>
>> On 12/18/2014 03:24 PM, MyungJoo Ham wrote:
>>> Hi Chanwoo,
>>>
>>> I love the idea and I now have a little mechanical issues in your code.
>>>
---
drivers/devfreq/Kco
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Thu, Dec 18, 2014 at 10:29:18PM -0800, Omar Sandoval wrote:
> Most filesystems prevent truncation of an active swapfile by way of
> inode_newsize_ok, called from inode_change_ok. NFS doesn't call either
> from nfs_setattr, presumably because most of these checks are expected
> to be done server-
> -Original Message-
> From: Minchan Kim [mailto:minc...@kernel.org]
> Sent: Friday, December 19, 2014 9:05 AM
> To: Wang, Yalin
> Cc: 'Konstantin Khlebnikov'; 'Kirill A. Shutemov'; 'Andrew Morton'; 'linux-
> ker...@vger.kernel.org'; 'linux...@kvack.org'; 'linux-arm-
> ker...@lists.infradea
> There's a simple solution: Call device_set_wakeup_enable() for the device!
> You can do this from the command line by:
>
> echo auto >/sys/bus/usb/devices/.../power/control
>
> where the "..." is the pathname for your device.
>
Yes, this can enable auto-suspend for usb device like a mous
Wu, Feng wrote on 2014-12-19:
>
>
> Zhang, Yang Z wrote on 2014-12-19:
>> Subject: RE: [v3 25/26] KVM: Suppress posted-interrupt when 'SN' is
>> set
>>
>> Wu, Feng wrote on 2014-12-19:
>>>
>>>
>>> Zhang, Yang Z wrote on 2014-12-19:
Subject: RE: [v3 25/26] KVM: Suppress posted-interrupt wh
Karthik,
On Fri, Dec 19, 2014 at 10:16:18AM +0530, karthik nayak wrote:
>
> On 12/19/2014 04:08 AM, Jeremiah Mahler wrote:
> >Karthik,
> >
> >On Thu, Dec 18, 2014 at 02:50:11PM +0530, Karthik Nayak wrote:
> >>As per checkpatch warning, removed an unnecessary else statement
> >>proceeding an if st
On 12/18/2014 09:46 PM, atull wrote:
> On Thu, 18 Dec 2014, Michal Simek wrote:
>
>> Hi Alan,
>>
>> first of all - there are these kernel-doc warnings.
>>
>> Info(drivers/staging/fpga/fpga-mgr.c:37): Scanning doc for
>> fpga_mgr_low_level_state
>> Warning(drivers/staging/fpga/fpga-mgr.c:43): No d
>
> It drops the way of using power_supply interface to reference battery's
> temperature. Then it tries to use thermal subsystem's only. This makes driver
> more simple and also can remove ifdeferies.
>
> Signed-off-by: Jonghwa Lee
Acked-by: MyungJoo Ham
> ---
> drivers/power/Kconfig
I Mark and my wife Cindy Hill of Missouri won a Jackpot we have decided to
donate the sum of 900,000.00 USD to you. Contact us via our personal email.
fill the following. 1.Name 2. Country 3.Sex Note that you have to contact my
private email for more informations.
Goodluck,
Mrs Cindy Hill
---
On 12/18/2014 09:59 PM, atull wrote:
> On Thu, 18 Dec 2014, Michal Simek wrote:
>
> Hi Michal,
>
>>> +
>>> + /* Write out remaining non 32-bit chunks. */
>>> + switch (count) {
>>> + case 3:
>>> + socfpga_fpga_data_writel(priv, buffer_32[i++] & 0x00ff);
>>> + break;
On Fri, 19 Dec 2014, Li Bin wrote:
> The execution flow redirection related implemention in the livepatch
> ftrace handler is depended on the specific architecture. This patch
> introduces klp_arch_set_pc(like kgdb_arch_set_pc) interface to change
> the pt_regs.
>
> Signed-off-by: Li Bin
Good c
On 2014/12/1 18:17, Jason Wang wrote:
On newer hosts that support delayed tx interrupts,
we probably don't have much to gain from orphaning
packets early.
Note: this might degrade performance for
hosts without event idx support.
Should be addressed by the next patch.
Cc: Rusty Russell
Cc: Mich
On Tue, 16 Dec 2014, Seth Jennings wrote:
> This commit introduces code for the live patching core. It implements
> an ftrace-based mechanism and kernel interface for doing live patching
> of kernel and kernel module functions.
>
> It represents the greatest common functionality set between kpat
Hi Andy,
On 12/19/2014 02:33 PM, Andy Yan wrote:
Hi Liu Ying:
I foud Rockchip RK618 (a mfd function device with mipi dsi，lvds
transmitter、HDMI TX、and audio codec，and
controlled by the SOC from i2c ) have the same register layout with your
i.MX MIPI DSI，which means RK618 MIPI
DSI also have the
>
> Whenever battery status is changed, charger manager tries to trigger uevent
> through private interface. This patch modifies it to use
> power_supply_changed()
> since it belongs to power supply subsystem.
>
> Signed-off-by: Jonghwa Lee
The original uevent_notify() has two additional me
On 19 December 2014 at 03:03, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> Having switched over all of the users of CONFIG_PM_RUNTIME to use
> CONFIG_PM directly, turn the latter into a user-selectable option
> and drop the former entirely from the tree.
>
> Signed-off-by: Rafael J. Wys
>
> cm_notify_event() is introduced to get event associated with battery status
> externally, but no one had been used. Moreover it makes charger manager
> driver more complicated. This patch tries to drop the function and all data
> related to simplify the driver.
>
> Signed-off-by: Jonghwa L
There was some discussion to create zero-set pages in background like this:
https://lkml.org/lkml/2004/10/30/73
I'm understand that it is not good for performance.
But I think it can help for a device in my platform.
I'm sorry I can't tell what it is.
But the device needs many zero-set pages, up
On Tue, 25 Nov, at 02:55:09PM, Matt Fleming wrote:
> On Fri, 14 Nov, at 09:15:01PM, Matt Fleming wrote:
> > From: Matt Fleming
> >
> > This patch series adds a new PMU driver for the Intel Cache Monitoring
> > hardware feature available in Intel Xeon processors, which allows
> > monitoring of LLC
At Wed, 17 Dec 2014 16:09:35 -0600,
Chris J Arges wrote:
>
> The num_controls field was incorrectly set to 0 causing 6i6 to not be
> initialized. Set this to 9.
>
> Reported-and-tested-by: Mark Roberts
> Signed-off-by: Chris J Arges
Applied, thanks.
Takashi
> ---
> sound/usb/mixer_scarlett
On 12/17/2014 10:47 PM, Bibek Basu wrote:
Hi Bill,
Though I like your solution, I have a usecase where the driver probe
sequence itself is not right. Both the driver are module_init but one
depends on another during suspend sequence.
In such a situation, my system hangs. What do you suggest to
On Thu, Dec 18, 2014 at 02:29:51PM +0800, Chao Yu wrote:
> Hi Changman,
>
> > -Original Message-
> > From: Changman Lee [mailto:cm224@gmail.com]
> > Sent: Wednesday, December 17, 2014 11:09 PM
> > To: Chao Yu
> > Cc: Jaegeuk Kim; Changman Lee; linux-fsde...@vger.kernel.org;
> > linux-
On Wed, 17 Dec 2014, Arnd Bergmann wrote:
> On Wednesday 17 December 2014 16:45:24 Lee Jones wrote:
> > +- compatible : Must be one of: "st,stih407-lpc" "st,stih416-lpc"
> > + "st,stih415-lpc" "st,stid127-lpc"
> > +- reg : LPC registers base address + siz
Hi Simon,
On Thu, Dec 18, 2014 at 1:33 AM, Simon Horman wrote:
> On Wed, Dec 17, 2014 at 02:20:09PM +, Marc Zyngier wrote:
>> On 17/12/14 13:40, Geert Uytterhoeven wrote:
>> > As of commit 9a1091ef0017c40a ("irqchip: gic: Support hierarchy irq
>> > domain."), armadillo-legacy hangs during boo
FYI, we noticed the below changes on
commit 982792c782ef337381e982fd2047391886f89693 ("x86, mm: probe memory block
size for generic x86 64bit")
I think this is use memory size reduction, so should be a good thing.
testbox/testcase/testparams: brickland3/boot/1
c46a7c817e662a82 982792c782ef337
FYI, we noticed the below changes on
commit e28740ece34d314002b1ddfa14e8fb7c7b909489 ("drm/radeon: Add radeon <-->
amdkfd interface")
+--+++
| | 1c0a46255f | e28740ece3 |
+--
On 12/18/2014 10:17 AM, Huang Ying wrote:
FYI, we noticed the below changes on
commit e28740ece34d314002b1ddfa14e8fb7c7b909489 ("drm/radeon: Add radeon <--> amdkfd
interface")
+--+++
| |
This makes it possible to assign GPIOs at runtime. The
motivation for it is because of need to forward GPIOs from
one device to an other. That feature may be useful for
example with some mfd devices, but initially it is needed
because on some Intel Braswell based ACPI platforms the GPIO
resources c
On Thu, 2014-12-18 at 10:20 +0200, Oded Gabbay wrote:
> On 12/18/2014 10:17 AM, Huang Ying wrote:
> > FYI, we noticed the below changes on
> >
> > commit e28740ece34d314002b1ddfa14e8fb7c7b909489 ("drm/radeon: Add radeon
> > <--> amdkfd interface")
> >
> >
> > +-
From: Zhang Zhuoyu
This implements CPU hotplug for ls1. When cpu is down, it will be put
in boot holdoff state. When cpu is up, it will always soft reset and
boots up the same path as a cold boot.
Signed-off-by: Zhang Zhuoyu
---
arch/arm/mach-imx/common.h | 16 +
arch/arm/mach-imx/hotplu
On Wed, 17 Dec 2014, Guenter Roeck wrote:
> On Wed, Dec 17, 2014 at 04:45:25PM +, Lee Jones wrote:
> > Signed-off-by: David Paris
> > Signed-off-by: Lee Jones
>
> Hi Lee and David,
>
> I still have a couple of comments below. Sorry I didn't catch those earlier.
>
> Thanks,
> Guenter
>
> >
On Wed, Dec 17, 2014 at 09:34:48AM -0800, Greg Kroah-Hartman wrote:
> On Wed, Dec 17, 2014 at 09:30:03AM +0100, Thierry Reding wrote:
> > On Thu, Dec 04, 2014 at 01:06:07PM +0100, Thierry Reding wrote:
> > > From: Thierry Reding
> > >
> > > Commit 1290a958d48e ("usb: phy: propagate __of_usb_find_
On Thu, 18 Dec 2014, gyun...@gmail.com wrote:
> From: Gyungoh Yoo
>
> Signed-off-by: Gyungoh Yoo
> ---
> Changes v10:
> Nothing
>
> Changes v9:
> Nothing
>
> Changes v8:
> Nothing
>
> Changes v7:
> Nothing
>
> Changes v6:
> Nothing
>
> Changes v5:
> Nothing
>
> Changes v4:
> Nothing
>
>
On 12/18/2014 10:26 AM, Huang Ying wrote:
On Thu, 2014-12-18 at 10:20 +0200, Oded Gabbay wrote:
On 12/18/2014 10:17 AM, Huang Ying wrote:
FYI, we noticed the below changes on
commit e28740ece34d314002b1ddfa14e8fb7c7b909489 ("drm/radeon: Add radeon <--> amdkfd
interface")
+
DT Ack please.
> From: Gyungoh Yoo
>
> Signed-off-by: Gyungoh Yoo
> Acked-by: Bryan Wu
> ---
[...]
> Changes v8:
> Renamed property names for backlight with vendor prefix
> Modified gpio-enable property to generic property for GPIO
> Made up the example for backlight DT
[...]
> Changes v2:
On Thu, 18 Dec 2014, gyun...@gmail.com wrote:
> From: Gyungoh Yoo
>
> Signed-off-by: Gyungoh Yoo
> ---
> Changes v10:
> Nothing
>
> Changes v9:
> Nothing
>
> Changes v8:
> Made up the example for backlight DT
>
> Changes v7:
> Nothing
>
> Changes v6:
> Nothing
>
> Changes v5:
> Changed DT
Hi Rafael,
Thanks for your comments!
On Thu, Dec 18, 2014 at 1:57 AM, Rafael J. Wysocki wrote:
> On Wednesday, December 17, 2014 08:33:13 PM Geert Uytterhoeven wrote:
>> On Tue, Dec 16, 2014 at 11:10 PM, Kevin Hilman wrote:
>> > At a deeper level, the problem with this approach is that this is
This series add earlycon support to Mediatek MT8173 SoC. Although 8250 driver
already has earlycon support, but Mediatek UART has highspeed register that
not in 8250_early.c, so I port earlycon in 8250_mtk.c, and add stdout device
tree support.
This patchset is based on 3.18, and my basic support
Add earlycon support to mediatek MT8173 evaluation board dts.
Signed-off-by: Eddie Huang
---
arch/arm64/boot/dts/mt8173-evb.dts | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/arch/arm64/boot/dts/mt8173-evb.dts
b/arch/arm64/boot/dts/mt8173-evb.dts
index b8b2621..b8802fd 1
Mediatek UART has highspeed register, but 8250_early.c doesn't
support this, so add earlycon in 8250_mtk.c
Signed-off-by: Eddie Huang
---
drivers/tty/serial/8250/8250_mtk.c | 33 +
1 file changed, 33 insertions(+)
diff --git a/drivers/tty/serial/8250/8250_mtk.c
On 18/12/2014 04:15, Wu, Feng wrote:
> Thanks for your comments, Paolo!
>
> If we use u64 new_control, we cannot use new.sn any more.
> Maybe we can change the struct pi_desc {} like this:
>
> typedef struct pid_control{
> u64 on : 1,
> sn : 1,
> rsvd_1 :
On 18/12/2014 04:16, Wu, Feng wrote:
>>> pre-block:
>>> - Add the vCPU to the blocked per-CPU list
>>> - Clear 'SN'
>>
>> Should SN be already clear (and NV set to POSTED_INTR_VECTOR)?
>
> I think the SN bit should be clear here, Adding it here is just to make sure
> SN is clear when vCPU is bl
Hi Lee,
On Wed, 17 Dec 2014, Lee Jones wrote:
> Signed-off-by: David Paris
> Signed-off-by: Lee Jones
> ---
> drivers/watchdog/Kconfig | 13 ++
> drivers/watchdog/Makefile | 1 +
> drivers/watchdog/st_wdt.c | 323
> ++
You don't have a patch whi
301 - 400 of 604 matches
Mail list logo
