On Tue, Dec 3, 2013 at 11:05 PM, Qiao Zhou wrote:
> sram driver can be used by many chips besides CPU_MMP2, and so build
> it alone.
>
> Reported-by: Dan Williams
> Signed-off-by: Qiao Zhou
> ---
> arch/arm/mach-mmp/Kconfig |5 +
> arch/arm/mach-mmp/Makefile |3 ++-
> 2 files
On Tue, Dec 03, 2013 at 06:01:50PM +0100, Borislav Petkov wrote:
> Date: Tue, 3 Dec 2013 18:01:50 +0100
> From: Borislav Petkov
> To: "Chen, Gong"
> Cc: Levente Kurusa , Ingo Molnar ,
> Thomas Gleixner , Tony Luck , "H.
> Peter Anvin" , x...@kernel.org, EDAC
> , LKML
> Subject: Re: [PATCH]
hi,
i have few changes in my mtd partitions, i want to change the erasesize of a
partition. can any one tell me where i should look to change erasesize of
mtd3...
Thanks
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Wed, 2013-12-04 at 10:38 +0300, Dan Carpenter wrote:
> On Wed, Dec 04, 2013 at 06:35:15AM +0200, Aldo Iljazi wrote:
> > Samuel Thibault wrote:
> >
> > > Err, I'd rather make it really visible that the for loop doesn't have
> > > its first statement?
> >
> > Wouldn't it be better if you add a
On Mon, 25 Nov 2013 14:49:37 +0100
Hiroshi Doyu wrote:
> Hi Joerg,
>
> Do you have some time to review this patch along with the following ones?
>
> [PATCHv6 02/13] iommu/of: introduce a global iommu device list
> http://lists.linuxfoundation.org/pipermail/iommu/2013-November/007050.html
>
(2013/12/04 10:44), David Ahern wrote:
> On 12/3/13, 6:22 PM, Masami Hiramatsu wrote:
>
>>> I figured out what you meant by uprobe_events interface yesterday. If I
>>> have to go to that interface for even 1 function I would do it for all
>>> -- from a user perspective it is just simpler to have
On Wed, Dec 04, 2013 at 06:35:15AM +0200, Aldo Iljazi wrote:
> Samuel Thibault wrote:
>
> > Err, I'd rather make it really visible that the for loop doesn't have
> > its first statement?
>
> Wouldn't it be better if you add a comment there? So it would follow the
> coding style?
No. Adding
(2013/12/04 11:54), Sandeepa Prabhu wrote:
> On 4 December 2013 06:58, Masami Hiramatsu
> wrote:
>> Hi,
>> Here is the version 4 of NOKPORBE_SYMBOL series.
>>
>> In this version, I removed the cleanup patches and
>> add bugfixes I've found, since those bugs will be
>> critical.
>> Rest of the
Hi Keerthy,
> + rdev = regulator_register([id], );
Can you make use of "devm_regulator_register" instead?
> + if (IS_ERR(rdev)) {
> + dev_err(tps->dev, "failed to register %s regulator\n",
> + pdev->name);
> + return PTR_ERR(rdev);
>
On 12/04/2013 02:38 AM, Glauber Costa wrote:
>> In memcg_update_kmem_limit() we do the whole process of limit
>> initialization under a mutex so the situation we need protection from in
>> tcp_update_limit() is impossible. BTW once set, the 'activated' flag is
>> never cleared and never checked
> usb: chipidea: Reallocate regmap only if lpm is detected
>
> The regmap only needs to reallocate if the hw_read on the CAP register
> shows
> lpm is used. Therefore the if() statement check the change.
>
> Signed-off-by: Chris Ruehl
> Acked-by: Peter Chen
> ---
>
On Mon, Nov 25, 2013 at 02:53:37PM +1100, dt.ta...@gmail.com wrote:
> From: Daniel Tang
>
> The USB controller in TI-NSPIRE calculators are based off either Freescale's
> USB OTG controller or the USB controller found in the IMX233, both of which
> are Chipidea compatible.
>
> This patch adds a
That thing should be del_timer_sync(); consider what happens
if ext4_put_super() call of del_timer() happens to come just as it's
getting run on another CPU. Since that timer reschedules itself
to run next day, you are pretty much guaranteed that you'll end up
with kfree'd scheduled
Oh, another member has already fixed it (found earlier than me), and
integrated it into next-20131203 tree, so this patch is obsoleted.
The related git commit is "8aced95 staging: ft1000: fix use of
potentially uninitialized variable"
Thanks.
On 11/27/2013 05:27 PM, Chen Gang wrote:
On Tuesday, December 03, 2013 04:15 PM, Heikki Krogerus wrote:
On Mon, Dec 02, 2013 at 03:05:19PM +0800, Chris Ruehl wrote:
@@ -154,6 +164,27 @@ int usb_phy_gen_create_phy(struct device *dev, struct
usb_phy_gen_xceiv *nop,
{
int err;
+ if (nop->ulpi_vbus> 0) {
+
On 12/03/2013 10:32 PM, Christophe Leroy wrote:
Convert mpc8xxx_wdt.c to the new watchdog API.
Signed-off-by: Christophe Leroy
Reviewed-by: Guenter Roeck
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More
Hi Stephen,
On Fri, Nov 22, 2013 at 10:35 AM, Alex Courbot wrote:
> On 11/22/2013 05:30 AM, Stephen Warren wrote:
>>
>> On 11/20/2013 07:40 PM, Alexandre Courbot wrote:
>>>
>>> FUSE clock is enabled by most bootloaders, but we cannot expect it to be
>>> on in all contexts (e.g. kexec).
>>>
>>>
On Wed, Dec 04, 2013 at 02:44:14PM +0800, Axel Lin wrote:
> 2013/12/4 Rob Landley :
> > On 11/16/2013 02:15:23 AM, Axel Lin wrote:
> >>
> >> The deleted variable is always 1 in current code.
> >> Initialize deleted variable to be 0, so delete_path() will be called only
> >> when
> >> necessary.
>
sram driver can be used by many chips besides CPU_MMP2, and so build
it alone.
Reported-by: Dan Williams
Signed-off-by: Qiao Zhou
---
arch/arm/mach-mmp/Kconfig |5 +
arch/arm/mach-mmp/Makefile |3 ++-
2 files changed, 7 insertions(+), 1 deletions(-)
diff --git
Reported-by: Dan Williams
Signed-off-by: Qiao Zhou
---
drivers/dma/Kconfig |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/dma/Kconfig b/drivers/dma/Kconfig
index dd2874e..4e41b69 100644
--- a/drivers/dma/Kconfig
+++ b/drivers/dma/Kconfig
@@ -288,6 +288,7 @@
On Tue, Dec 03, 2013 at 11:39:21PM -0500, Adrien Vergé wrote:
> Usage of ETM tracing facility is currently very limited: user can
> only start/stop tracing. This set of patches enables management of
> address combinations and PIDs that trigger tracing.
>
> ETM management was done via sysfs
Hi Rafael,
> This patch series introduces support for CPU overclocking technique
> called Boost.
>
> It is a follow up of a LAB governor proposal. Boost is a LAB
> component:
> http://thread.gmane.org/gmane.linux.kernel/1484746/match=cpufreq
>
> Boost unifies hardware based solution (e.g. Intel
2013/12/4 Rob Landley :
> On 11/16/2013 02:15:23 AM, Axel Lin wrote:
>>
>> The deleted variable is always 1 in current code.
>> Initialize deleted variable to be 0, so delete_path() will be called only
>> when
>> necessary.
>>
>> Signed-off-by: Axel Lin
>
>
> I'm not seeing this in linux-next, or
"David E. Box" writes:
>
> +config X86_IOSF_MBI
> + tristate "IOSF-SB MailBox Interface access support for Intel
> SOCs"
This is only implicitly used by other drivers, right?
Please make it not user visible (drop the string after tristate), as users
will not know when to enable it.
The
Convert mpc8xxx_wdt.c to the new watchdog API.
Signed-off-by: Christophe Leroy
diff -ur a/drivers/watchdog/mpc8xxx_wdt.c b/drivers/watchdog/mpc8xxx_wdt.c
--- a/drivers/watchdog/mpc8xxx_wdt.c2013-05-11 22:57:46.0 +0200
+++ b/drivers/watchdog/mpc8xxx_wdt.c2013-11-30
On 12/04/2013 08:51 AM, Dave Chinner wrote:
> On Tue, Dec 03, 2013 at 04:15:57PM +0400, Vladimir Davydov wrote:
>> On 12/03/2013 02:48 PM, Dave Chinner wrote:
@@ -236,11 +236,17 @@ shrink_slab_node(struct shrink_control *shrinkctl,
struct shrinker *shrinker,
return 0;
On Tue, Dec 3, 2013 at 7:20 PM, Will Deacon wrote:
> On Mon, Dec 02, 2013 at 09:34:03AM +, Vinayak Kale wrote:
>> static void
>> +armpmu_disable_percpu_irq(void *data)
>> +{
>> + struct arm_pmu *armpmu = data;
>> + struct platform_device *pmu_device = armpmu->plat_device;
>> +
(2013/12/04 12:08), HATAYAMA Daisuke wrote:
(2013/12/04 0:25), Vivek Goyal wrote:
On Tue, Dec 03, 2013 at 10:32:26AM +0900, HATAYAMA Daisuke wrote:
[..]
diff --git a/Documentation/kernel-parameters.txt
b/Documentation/kernel-parameters.txt
index 50680a5..dd77bec 100644
---
On Tue, 2013-12-03 at 22:17 -0600, Rob Herring wrote:
> From: Rob Herring
>
> This adds a simple check that any compatible strings in DeviceTree dts
> files are present in Documentation/devicetree/bindings. Vendor prefixes
> are also checked for existing in vendor-prefixes.txt These should be
>
On Tue, Dec 3, 2013 at 7:35 PM, Elena Ufimtseva wrote:
> On Tue, Nov 19, 2013 at 1:29 PM, Dario Faggioli
> wrote:
>> On mar, 2013-11-19 at 10:38 -0500, Konrad Rzeszutek Wilk wrote:
>>> On Mon, Nov 18, 2013 at 03:25:48PM -0500, Elena Ufimtseva wrote:
>>> > The patchset introduces vnuma to
Thanks for your quick response.
Please find my comments below.
On Tue, Dec 3, 2013 at 11:09 PM, Bjorn Helgaas wrote:
> On Tue, Dec 3, 2013 at 4:24 AM, Jagan Teki wrote:
>> Hi,
>>
>> I have few question on Linux PCIe subsystem, I am trying to understand
>> the PCIe on ARM platform.
>> 1.
On 12/03/2013 08:35 PM, Alex Shi wrote:
> We are not always 0 when update nohz cpu load, after nohz_full enabled.
> But current code still treat the cpu as idle. that is incorrect.
> Fix it to use correct cpu_load.
Frederic, Could you like to give some comments?
>
> Signed-off-by: Alex Shi
>
On Mon, Nov 11, 2013 at 03:35:36PM +0200, Ivan T. Ivanov wrote:
> From: "Ivan T. Ivanov"
>
The commit log is needed.
> Signed-off-by: Ivan T. Ivanov
> ---
> drivers/usb/chipidea/ci_hdrc_msm.c |1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/usb/chipidea/ci_hdrc_msm.c
>
On 2013/12/03 18:06:13, kexec wrote:
> >> This is a suggestion from different point of view...
> >>
> >> In general, data on crash dump can be corrupted. Thus, order contained in
> >> a page
> >> descriptor can also be corrupted. For example, if the corrupted value were
> >> a huge
> >> number,
On Wed, 4 Dec 2013, Johannes Weiner wrote:
> However, the GFP_NOFS | __GFP_NOFAIL task stuck in the page allocator
> may hold filesystem locks that could prevent a third party from
> freeing memory and/or exiting, so we can not guarantee that only the
> __GFP_NOFAIL task is getting stuck, it
On Mon, Nov 11, 2013 at 03:35:34PM +0200, Ivan T. Ivanov wrote:
> From: "Ivan T. Ivanov"
>
Please add something in commit log
> Signed-off-by: Ivan T. Ivanov
> Cc: devicet...@vger.kernel.org
> ---
> .../devicetree/bindings/usb/msm-hsusb.txt | 16
> 1 file changed,
Hi Stephen,
Initially Chris sent this patch to Linux-USB alias alone & there I Acked it.
Plz check http://marc.info/?l=linux-usb=138475663023376=1
Then he resent the patch to linux-kernel alias with my ACK added.
Thanks,
Venu
> -Original Message-
> From: Stephen Warren
On Mon, Nov 11, 2013 at 04:36:09PM +0200, Ivan T. Ivanov wrote:
>
> Hi Peter,
>
> On Mon, 2013-11-11 at 21:59 +0800, Peter Chen wrote:
> > On Mon, Nov 11, 2013 at 03:35:37PM +0200, Ivan T. Ivanov wrote:
> > > From: "Ivan T. Ivanov"
> > >
> > > PHY drivers keep track of the current state of
Hi,
Comment as following.
> -Original Message-
> From: Jaegeuk Kim [mailto:jaegeuk@samsung.com]
> Sent: Monday, December 02, 2013 4:27 PM
> To: linux-fsde...@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org; linux-f2fs-de...@lists.sourceforge.net
> Subject: Re: [f2fs-dev] [PATCH
> > > > +static int fsl_pwm_parse_clk_ps(struct fsl_pwm_chip *fpc)
> > > > +{
> > > > + int ret;
> > > > + struct of_phandle_args clkspec;
> > > > + struct device_node *np = fpc->chip.dev->of_node;
> > > > +
> > > > + fpc->sys_clk = devm_clk_get(fpc->chip.dev, "ftm0");
> >
Thanks for the review Mark.
On Tuesday 03 December 2013 08:46 PM, Mark Brown wrote:
On Tue, Dec 03, 2013 at 12:13:24PM +0530, Keerthy wrote:
+static int tps65218_ldo1_dcdc3_vsel_to_uv(unsigned int vsel)
+{
+ int uV = 0;
+
+ if (vsel <= 26)
+ uV = vsel * 25000 +
Hi Abhilash,
On 3 December 2013 20:16, Abhilash Kesavan wrote:
> Hi Yadwinder and Sachin,
> CC'ing Doug and Andrew who have also worked on ASV.
>
> I tested these patches on a 5250 Chromebook after modifying the
> cpufreq code and a few other changes for booting the board. The driver
> is
Hi Linus,
The following changes since commit a31ab44ef5d07c6707df4a9ad2c8affd2d62ff4b:
ARM: bcm2835: add missing #xxx-cells to I2C nodes (2013-11-25 21:56:00 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git
tags/fixes-for-linus
When enabling mutex debugging, in case the imbalanced mutex_unlock()
is called, we still get the warning like below:
[ 364.208284] DEBUG_LOCKS_WARN_ON(lock->owner != current)
But in that case, it is due to imbalanced mutex_unlock calling, and
the lock->owner is NULL.
Here we can enhance the
On Wednesday 04 December 2013 01:39 AM, Stephen Warren wrote:
On 12/02/2013 06:55 AM, Laxman Dewangan wrote:
Signed-off-by: Laxman Dewangan
Patch description?
BTW, did you compile all the Tegra DT files before and after this
change, and make sure that there's zero difference between them
On Wednesday 04 December 2013 01:38 AM, Stephen Warren wrote:
On 12/02/2013 11:04 PM, Laxman Dewangan wrote:
On Monday 02 December 2013 07:55 PM, Thierry Reding wrote:
* PGP Signed by an unknown key
On Mon, Dec 02, 2013 at 07:25:01PM +0530, Laxman Dewangan wrote:
+
+/* Schmitt enable/disable
AArch64 Single Steping and Breakpoint debug exceptions will be
used by multiple debug framworks like kprobes & kgdb.
This patch implements the hooks for those frameworks to register
their own handlers for handling breakpoint and single step events.
Reworked the debug exception handler in
This patch adds support for breakpoint and single-step exception hooks.
v3 version of this patch is published and reviewed with arm64 kdgb and kprobes
patch series [1] and [2]
[1] http://lwn.net/Articles/570648/
[2] https://lwn.net/Articles/571063/
Changes v3 -> v4:
-Incorporated review
On Wednesday 04 December 2013 01:34 AM, Stephen Warren wrote:
On 12/02/2013 06:09 AM, Laxman Dewangan wrote:
Use key code macros for all key code refernced for keys.
For tegra20-seaboard.dts and tegra20-harmony.dts:
The key comment for key (16th row and 1st column) is KEY_KPSLASH but
> From: linux-acpi-ow...@vger.kernel.org
> [mailto:linux-acpi-ow...@vger.kernel.org] On Behalf Of Hanjun Guo
> Sent: Wednesday, December 04, 2013 12:37 AM
>
> introduce arm_core.c and its related head file, after this patch,
> we can get ACPI tables from BIOS on ARM64 now.
>
> Signed-off-by: Al
(2013/12/03 22:15), Rafael J. Wysocki wrote:
On Tuesday, December 03, 2013 11:46:24 AM Yasuaki Ishimatsu wrote:
(2013/11/29 22:08), Rafael J. Wysocki wrote:
On Friday, November 29, 2013 11:36:55 AM Yasuaki Ishimatsu wrote:
Hi Rafael,
Hi,
Replying to this mail may be wrong.
OK, so this
On Tue, Dec 03, 2013 at 09:20:17PM -0800, David Rientjes wrote:
> Now that a per-process flag is available, define it for processes that
> handle userspace oom notifications. This is an optimization to avoid
> mantaining a list of such processes attached to a memcg at any given time
> and
On Wed, Dec 04, 2013 at 03:34:17PM +1100, Dave Chinner wrote:
> On Tue, Dec 03, 2013 at 10:01:01PM -0500, Johannes Weiner wrote:
> > On Tue, Dec 03, 2013 at 03:40:13PM -0800, David Rientjes wrote:
> > > On Tue, 3 Dec 2013, Johannes Weiner wrote:
> > > I believe the page allocator would be
The res_counter_{charge,uncharge}_locked() variants are not used in the
kernel outside of the resource counter code itself, so remove the
interface.
Signed-off-by: David Rientjes
---
Documentation/cgroups/resource_counter.txt | 14 ++
include/linux/res_counter.h| 6
Add documentation on memcg oom reserves to
Documentation/cgroups/memory.txt and give an example of its usage and
recommended best practices.
Signed-off-by: David Rientjes
---
Documentation/cgroups/memory.txt | 26 ++
1 file changed, 26 insertions(+)
diff --git
Now that a per-process flag is available, define it for processes that
handle userspace oom notifications. This is an optimization to avoid
mantaining a list of such processes attached to a memcg at any given time
and iterating it at charge time.
This flag gets set whenever a process has
For memcg oom reserves, we'll need a resource counter interface that will
not fail when exceeding the memcg limit like res_counter_charge_nofail,
but only to a ceiling.
This patch adds res_counter_charge_nofail_max() that will exceed the
resource counter but only to a maximum defined value. If
PF_MEMPOLICY is an unnecessary optimization for CONFIG_SLAB users.
There's no significant performance degradation to checking
current->mempolicy rather than current->flags & PF_MEMPOLICY in the
allocation path, especially since this is considered unlikely().
Per-process flags are a scarce
slab_node() is actually a mempolicy function, so rename it to
mempolicy_slab_node() to make it clearer that it used for processes with
mempolicies.
At the same time, cleanup its code by saving numa_mem_id() in a local
variable (since we require a node with memory, not just any node) and
remove an
Userspace needs a way to define the amount of memory reserves that
processes handling oom conditions may utilize. This patch adds a per-
memcg oom reserve field and file, memory.oom_reserve_in_bytes, to
manipulate its value.
If currently utilized memory reserves are attempted to be reduced by
copy_flags() does not use the clone_flags formal and can be collapsed
into copy_process() for cleaner code.
Signed-off-by: David Rientjes
---
kernel/fork.c | 12 ++--
1 file changed, 2 insertions(+), 10 deletions(-)
diff --git a/kernel/fork.c b/kernel/fork.c
--- a/kernel/fork.c
+++
On 12/03/2013 09:49 PM, Heikki Krogerus wrote:
This makes it possible to request the gpio descriptors in
rfkill_gpio driver regardless of the platform.
Signed-off-by: Heikki Krogerus
---
arch/arm/mach-tegra/board-paz00.c | 11 +++
1 file changed, 11 insertions(+)
Changes since v3:
On 12/03/2013 05:31 AM, Christophe Leroy wrote:
Convert mpc8xxx_wdt.c to the new watchdog API.
Signed-off-by: Christophe Leroy
diff -ur a/drivers/watchdog/mpc8xxx_wdt.c b/drivers/watchdog/mpc8xxx_wdt.c
--- a/drivers/watchdog/mpc8xxx_wdt.c2013-05-11 22:57:46.0 +0200
+++
Change x86_msi.restore_msi_irqs(struct pci_dev *dev, int irq) to
x86_msi.restore_msi_irqs(struct pci_dev *dev)
From its naming, restore_msi_irqs is used to restore multiple msix irqs,
param 'int irq' is unneeded. This could make code looks consistent in vm
and bare metal.
Dom0 msix restore
Konrad Rzeszutek Wilk wrote:
On Fri, Nov 08, 2013 at 09:44:09AM +0800, Zhenzhong Duan wrote:
On 2013-11-07 07:51, Bjorn Helgaas wrote:
[+cc Thomas, Ingo, Peter, x86 list]
On Wed, Nov 6, 2013 at 2:16 PM, Konrad Rzeszutek Wilk
wrote:
Certain platforms do not allow writes in the
On Tue, Dec 03, 2013 at 04:15:57PM +0400, Vladimir Davydov wrote:
> On 12/03/2013 02:48 PM, Dave Chinner wrote:
> >> @@ -236,11 +236,17 @@ shrink_slab_node(struct shrink_control *shrinkctl,
> >> struct shrinker *shrinker,
> >>return 0;
> >>
> >>/*
> >> - * copy the current
On Tue, Dec 03, 2013 at 05:15:43PM -0500, Tejun Heo wrote:
> Hello,
>
> Can you please test whether this patch makes the lockdep warning go
> away?
>
> Thanks a lot!
been running a few hours now, looks good.
Tested-by: Dave Jones
Dave
--
To unsubscribe from this list: send
Ping!
On Thu, Nov 28, 2013 at 5:26 PM, Peter Crosthwaite
wrote:
> When searching the interrupt map, if a matched parent is disabled, just
> ignore it and move on with the search.
>
> This allows for specifying connection of a single device IRQ to
> multiple interrupt controllers via the
In the same manner as for enabling tracing, an entry is created in
sysfs to set the PID that triggers tracing. This change requires
CONFIG_PID_IN_CONTEXTIDR to be set when using on-chip ETM.
Signed-off-by: Adrien Vergé
Cc: Russell King
Cc: Ben Dooks
Cc: Will Deacon
Cc: Dietmar Eggemann
Cc:
In the same manner as for enabling tracing, an entry is created
in sysfs to set the address range that triggers tracing.
Signed-off-by: Adrien Vergé
Cc: Russell King
Cc: Ben Dooks
Cc: Will Deacon
Cc: Dietmar Eggemann
Cc: Andrew Morton
Cc: "zhangwei(Jovi)"
Cc: Greg Kroah-Hartman
Cc: Randy
Since there are different types of comparators, and other kinds will
be used (such as Context ID comparators), rename them properly.
Signed-off-by: Adrien Vergé
Cc: Russell King
Cc: Ben Dooks
Cc: Will Deacon
Cc: Dietmar Eggemann
Cc: Andrew Morton
Cc: "zhangwei(Jovi)"
Cc: Greg Kroah-Hartman
Usage of ETM tracing facility is currently very limited: user can
only start/stop tracing. This set of patches enables management of
address combinations and PIDs that trigger tracing.
ETM management was done via sysfs entries (trace_info,
trace_running...), this code adds trace_addrrange and
Usage of ETM tracing facility is currently very limited: user can
only start/stop tracing. This set of patches enables management of
address combinations and PIDs that trigger tracing.
ETM management was done via sysfs entries (trace_info,
trace_running...), this code adds trace_addrrange and
Samuel Thibault wrote:
> Err, I'd rather make it really visible that the for loop doesn't have
> its first statement?
Wouldn't it be better if you add a comment there? So it would follow the
coding style?
--
Aldo Iljazi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
On Tue, Dec 03, 2013 at 10:01:01PM -0500, Johannes Weiner wrote:
> On Tue, Dec 03, 2013 at 03:40:13PM -0800, David Rientjes wrote:
> > On Tue, 3 Dec 2013, Johannes Weiner wrote:
> > I believe the page allocator would be susceptible to the same deadlock if
> > nothing else on the system can
On Tue, Dec 03, 2013 at 08:47:12PM -0700, Jens Axboe wrote:
> On Wed, Dec 04 2013, Dave Chinner wrote:
> > On Wed, Dec 04, 2013 at 12:58:38PM +1100, Dave Chinner wrote:
> > > On Wed, Dec 04, 2013 at 08:59:40AM +1100, Dave Chinner wrote:
> > > > Hi Jens,
> > > >
> > > > Not sure who to direct this
From: Rob Herring
This adds a simple check that any compatible strings in DeviceTree dts
files are present in Documentation/devicetree/bindings. Vendor prefixes
are also checked for existing in vendor-prefixes.txt These should be
temporary checks until we have more sophisticated binding schema
On 11/28/13, 6:58 PM, David Ahern wrote:
On 11/28/13, 5:48 PM, Namhyung Kim wrote:
Do we really need to look up the callchain to find out an idle thread?
---8<---
It seems every idle/swapper thread for each cpu has a pid of 0.
I knew I had this code in there for a reason
Older
On 12/03/2013 07:02 PM, Chris Ruehl wrote:
> usb: phy-tegra-usb.c: wrong pointer check for remap UTMI
>
> A wrong pointer was used to test the result of devm_ioremap()
>
> Signed-off-by: Chris Ruehl
> Acked-by: Venu Byravarasu
Out of curiosity, when did that ack happen? I didn't see it. But
Replace the "fake" clocks defined in the "bcm11351.dtsi" device tree
file with real definitions backed by the new BCM281xx clock driver..
Signed-off-by: Alex Elder
Reviewed-by: Matt Porter
Reviewed-by: Tim Kryger
---
arch/arm/boot/dts/bcm11351.dtsi | 222
Document the device tree binding for Broadcom Kona architecture
clock control units and clocks. Kona device nodes are represented
with compatible strings having "bcm11351" in their name.
Kona clocks are managed by "clock control units" (CCUs). Each CCU
has a device tree node, and within that
This series adds support for Kona clock control units (CCUs) and
clocks, used by Broadcom BCM281xx family SoCs. Kona CCUs are
represented by nodes in the device tree, and the names of the clocks
provided by a CCU are included in its node. Implementation details
of those clocks are defined in a C
On Wed, Dec 04 2013, Dave Chinner wrote:
> On Wed, Dec 04, 2013 at 12:58:38PM +1100, Dave Chinner wrote:
> > On Wed, Dec 04, 2013 at 08:59:40AM +1100, Dave Chinner wrote:
> > > Hi Jens,
> > >
> > > Not sure who to direct this to or CC, so I figured you are the
> > > person to do that. I just had
On Wed, Dec 04, 2013 at 12:58:38PM +1100, Dave Chinner wrote:
> On Wed, Dec 04, 2013 at 08:59:40AM +1100, Dave Chinner wrote:
> > Hi Jens,
> >
> > Not sure who to direct this to or CC, so I figured you are the
> > person to do that. I just had xfstests generic/299 (an AIO/DIO test)
> > oops in
On Tue, Dec 03, 2013 at 03:50:41PM -0800, David Rientjes wrote:
> On Tue, 3 Dec 2013, Michal Hocko wrote:
>
> > OK, as it seems that the notification part is too controversial, how
> > would you like the following? It reverts the notification part and still
> > solves the fault on exit path. I
Resending adding Mauro's new Email address...
On 1/17/13, Lance Ortiz wrote:
> This header file will define a new trace event that will be triggered when
> a AER event occurs. The following data will be provided to the trace
> event.
>
> char * dev_name - The name of the slot where the device
On Tue, Dec 3, 2013 at 4:01 PM, Andi Kleen wrote:
> Alexei Starovoitov writes:
>
> Can you do some performance comparison compared to e.g. ktap?
> How much faster is it?
imo the most interesting ktap scripts (like kmalloc-top.kp) need
tables and timers.
tables are almost ready for prime time,
(2013/12/04 0:25), Vivek Goyal wrote:
On Tue, Dec 03, 2013 at 10:32:26AM +0900, HATAYAMA Daisuke wrote:
[..]
diff --git a/Documentation/kernel-parameters.txt
b/Documentation/kernel-parameters.txt
index 50680a5..dd77bec 100644
--- a/Documentation/kernel-parameters.txt
+++
Hi Thierry,
On 12/03/2013 05:43 PM, Thierry Reding wrote:
On Tue, Dec 03, 2013 at 11:09:12AM +0800, Bo Shen wrote:
On 12/02/2013 06:59 PM, Thierry Reding wrote:
On Mon, Nov 18, 2013 at 05:13:21PM +0800, Bo Shen wrote:
[...]
diff --git a/drivers/pwm/pwm-atmel.c b/drivers/pwm/pwm-atmel.c
On Tue, Dec 03, 2013 at 03:40:13PM -0800, David Rientjes wrote:
> On Tue, 3 Dec 2013, Johannes Weiner wrote:
>
> > > > Spin on which level? The whole point of this change was to not spin for
> > > > ever because the caller might sit on top of other locks which might
> > > > prevent somebody else
Hi all,
Changes since 20131203:
The staging tree gained a conflict against the staging.current tree.
Non-merge commits (relative to Linus' tree): 2328
2507 files changed, 92621 insertions(+), 65164 deletions(-)
I
On 11/16/2013 02:15:23 AM, Axel Lin wrote:
The deleted variable is always 1 in current code.
Initialize deleted variable to be 0, so delete_path() will be called
only when
necessary.
Signed-off-by: Axel Lin
I'm not seeing this in linux-next, or a reply on the web archive.
Assuming
On 4 December 2013 06:58, Masami Hiramatsu
wrote:
> Hi,
> Here is the version 4 of NOKPORBE_SYMBOL series.
>
> In this version, I removed the cleanup patches and
> add bugfixes I've found, since those bugs will be
> critical.
> Rest of the cleanup and visible blacklists will be
> proposed later
On Tue, Dec 03, 2013 at 06:44:52PM -0800, David E. Box wrote:
> On Wed, Dec 04, 2013 at 02:21:30AM +, Matthew Garrett wrote:
> > Well sure, but why do you need to be a platform device at all? This
> > functionality was intended for cases where we already have a driver for
> > the part that
On Wed, 2013-10-16 at 12:26 +0530, Anshuman Khandual wrote:
> This patchset is the re-spin of the original branch stack
> sampling
> patchset which introduced new PERF_SAMPLE_BRANCH_COND branch filter. This
> patchset
> also enables SW based branch filtering support for book3s
On 11/20/13, Prarit Bhargava wrote:
> Second try at this ...
>
> Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=64791
>
> When a cpu is downed on a system, the irqs on the cpu are assigned to other
> cpus. It is possible, however, that when a cpu is downed there aren't
> enough free
Hi, Toshi
> Oh, I think I now understand what the issue was. The z420 firmware
> updates the SMBIOS table address in the EFI system table to a virtual
> address after calling EFI SetVirtualAddressMap. So, you are passing the
> original physical address of the SMBIOS table from the 1st kernel to
On Wed, Dec 04, 2013 at 02:21:30AM +, Matthew Garrett wrote:
> On Tue, Dec 03, 2013 at 06:17:03PM -0800, David E. Box wrote:
> > This is per the requirement in Documentation/acpi/enumeration.txt:
> >
> > "Currently the kernel is not able to automatically determine from which ACPI
> > device
Hi Linus,
Please consider pulling the following Squashfs bug fix.
Thanks
Phillip
The following changes since commit ed4f381ec15e5f11724cdbc68cffd2c22d1eaebd:
Squashfs: Check stream is not NULL in decompressor_multi.c (2013-11-20
03:59:20 +)
are available in the git repository at:
Dear RT Folks,
I'm pleased to announce the 3.2.53-rt75 stable release.
This release is just an update to the new stable 3.2.53 version
and no RT specific changes have been made.
You can get this release via the git tree at:
1 - 100 of 1844 matches
Mail list logo
