This patch modify devfreq_remove_device() to improve the sequence of resource
free. If executing existing devfreq_remove_device(), this function always
executes _remove_devfreq() twice. In result, second _remove_devfreq() always
return error value. So, This patch resolves complicated function
Hi Jens,
On Wed, Apr 23, 2014 at 9:25 AM, Jens Axboe wrote:
> On 2014-04-22 18:53, Ming Lei wrote:
>
>
>> In my null_blk test on a quad core SMP VM:
>>
>> - 4 hw queue
>> - timer mode
>>
>> With the above approach, tag allocation from local CPU can be
>> improved from:
>>
>>
This patchset fix devfreq_remove_device() to remove duplicate function call
of _remove_devfreq() and add following functions for the resource management
of devfreq device and simpify the control of resource on exynos4_bus/exynos5_bus
driver.
- devm_devfreq_add_device
- devm_devfreq_remove_device
-
On Fri, Apr 11, 2014 at 01:00:29PM -0400, r...@redhat.com wrote:
> From: Rik van Riel
>
> Setting the numa_preferred_node for a task in task_numa_migrate
> does nothing on a 2-node system. Either we migrate to the node
> that already was our preferred node, or we stay where we were.
>
> On a
This patch add resource-managed function for devfreq device as following
functions. The devm_devfreq_add_device() manages automatically the memory
of devfreq device using device resource management.
- devm_devfreq_add_device()
- devm_devfreq_remove_device()
Signed-off-by: Chanwoo Choi
---
This patch uses devm_devfreq_add_device()/devm_devfreq_register_opp_notifier()
to control automatically the resource of devfreq.
Signed-off-by: Chanwoo Choi
Cc: Kukjin Kim
Cc: Sachin Kamat
Cc: Bartlomiej Zolnierkiewicz
Cc: Manish Badarkhe
Cc: Abhilash Kesavan
Cc:
This patch uses devm_devfreq_add_device()/devm_devfreq_register_opp_notifier()
to control automatically the resource of devfreq.
Signed-off-by: Chanwoo Choi
Cc: Kukjin Kim
Cc: Bartlomiej Zolnierkiewicz
Cc: Wei Yongjun
Cc: linux-arm-ker...@lists.infradead.org
Cc:
On 2014-4-24 20:28, Tejun Heo wrote:
> On Wed, Apr 23, 2014 at 10:27:26AM -0400, Tejun Heo wrote:
>> Applied to libata/for-3.16.
>
> Reverted due to build failure. I was apparently too dependent on
> build-bot but what the hell? This isn't acceptable.
>
Sorry, apologize for this, send new
On Fri, Apr 11, 2014 at 01:00:28PM -0400, r...@redhat.com wrote:
> From: Rik van Riel
>
> When tasks have not converged on their preferred nodes yet, we want
> to retry fairly often, to make sure we do not migrate a task's memory
> to an undesirable location, only to have to move it again later.
change in v6:
1) type of host_flags changed from unsigned int to unsigned long,
fix the building warning and error.
channge in v5:
1) drop AHCI_HFLAGS(...) from ahci_xgene.c and do use host_flags
in ahci_platform_init_host, it's my carelessness.
changes in v4:
1) add a dynamic host_flags
On Fri, Apr 11, 2014 at 01:00:27PM -0400, r...@redhat.com wrote:
> From: Rik van Riel
>
> The NUMA code is smart enough to distribute the memory of workloads
> that span multiple NUMA nodes across those NUMA nodes.
>
> However, it still has a pretty high scan rate for such workloads,
> because
Append AHCI_HFLAG_NO_FBS to force turning off FBS flag.
Signed-off-by: Haojian Zhuang
Signed-off-by: Kefeng Wang
---
drivers/ata/ahci.h|1 +
drivers/ata/libahci.c |5 +
2 files changed, 6 insertions(+)
diff --git a/drivers/ata/ahci.h b/drivers/ata/ahci.h
index b5eb886..48073ef
On Thursday, April 24, 2014 9:28 PM, Peter Griffin wrote:
>
> From: Arnd Bergmann
>
> The LP855X driver cannot be successfully built if we don't
> enable the PWM subsystem. This patch makes that dependency
> explicit in Kconfig and prevents broken randconfig builds.
>
> Signed-off-by: Arnd
> -Original Message-
> From: Alexander Gordeev [mailto:agord...@redhat.com]
> Sent: Friday, April 25, 2014 2:31 PM
> To: Shahed Shaikh
> Cc: linux-kernel; Dept-HSG Linux NIC Dev; netdev; linux-pci
> Subject: Re: [PATCH net-next 2/2] qlcnic: Use pci_enable_msix_exact()
> instead of
On initialization failure, an error message is already printed with
level KERN_ERR, no need to print another one with level KERN_INFO.
Signed-off-by: Jean Delvare
Cc: Greg Kroah-Hartman
Cc: Jiri Slaby
---
drivers/tty/n_hdlc.c |4
1 file changed, 4 deletions(-)
---
On Thursday, April 24, 2014 9:28 PM, Peter Griffin wrote:
>
> The LM3630A driver cannot be successfully built if we don't
> enable the PWM subsystem. This patch makes that dependency
> explicit in Kconfig and prevents broken randconfig builds.
>
> Based on Arnd Bergmann patch but split out into
The hip04 SoC of hisilicon has an AHCI compliant SATA controller,
and it is compliant with the ahci 1.3 and sata 3.0 specification.
There is a wrong bit in HOST_CAP of hip04 sata controller, which
enable unsupported feature of FBS, use AHCI_HFLAG_NO_FBS hflag to
disable it.
Signed-off-by: Kefeng
Add a dynamic host_flags argument to make ahci_platform_init_host more flexible,
then remove the AHCI_HFLAGS(...) argument from some driver's ata_port_info,
and pass that in as the new argument.
Cc: Hans de Geode
Signed-off-by: Kefeng Wang
---
drivers/ata/ahci_da850.c |3 ++-
On Fri, Apr 25, 2014 at 08:48:14AM +, Shahed Shaikh wrote:
> > diff --git a/drivers/net/ethernet/qlogic/qlcnic/qlcnic_main.c
> > b/drivers/net/ethernet/qlogic/qlcnic/qlcnic_main.c
> > index dbf7539..26f022b 100644
> > --- a/drivers/net/ethernet/qlogic/qlcnic/qlcnic_main.c
> > +++
On Thursday, April 24, 2014 9:28 PM, Peter Griffin wrote:
>
> From: Arnd Bergmann
>
> This fixes a randconfig build error when BACKLIGHT_CLASS_DEVICE
> is disabled, by describing the dependency in Kconfig,
> as we do for the other drivers in this directory.
>
> Signed-off-by: Arnd Bergmann
>
On Thursday, April 24, 2014 9:28 PM, Peter Griffin wrote:
>
> The LP8788 driver cannot be successfully built if we don't
> enable the PWM subsystem. This patch makes that dependency
> explicit in Kconfig and prevents broken randconfig builds.
>
> Based on Arnd Bergmann patch but split out into
Estimado E-mail del usuario;
Se ha superado 23.432 Repositorio para el conjunto buzón
Servicios Web / Administrador, y habrás problemas al enviar y
recepción de correo, mientras que volver a verificar. Debe actualizar
haciendo clic en enlace de abajo y complete la información para
verificar
Hi Greg,
Thank you for your review.
(2014/04/25 8:11), Greg Kroah-Hartman wrote:
On Thu, Apr 17, 2014 at 03:06:44PM +0900, Yoshihiro YUNOMAE wrote:
[snip]
+static DEVICE_ATTR(rx_int_trig, S_IRUSR | S_IWUSR | S_IRGRP,
+ serial8250_get_attr_rx_int_trig,
+
On Fri, Apr 25, 2014 at 8:06 AM, Chung-Lin Tang wrote:
> I'll try to explain a probable situation for Nios II. I'm not sure about
> other soft-cores, but nios2 is sort of uncommon in that the maximum
> alignment is 4-bytes (32-bits), even for doubles/long-longs.
FWIW, that's the same as on m32r.
On Thu, Apr 24, 2014 at 01:52:00PM -0400, Dan Streetman wrote:
> On Wed, Apr 23, 2014 at 9:14 AM, Mel Gorman wrote:
> > On Sat, Apr 12, 2014 at 05:00:54PM -0400, Dan Streetman wrote:
> >> Originally get_swap_page() started iterating through the singly-linked
> >> list of swap_info_structs using
> -Original Message-
> From: Alexander Gordeev [mailto:agord...@redhat.com]
> Sent: Friday, April 25, 2014 1:36 PM
> To: linux-kernel
> Cc: Alexander Gordeev; Shahed Shaikh; Dept-HSG Linux NIC Dev; netdev;
> linux-pci
> Subject: [PATCH net-next 2/2] qlcnic: Use pci_enable_msix_exact()
commit 813b3b5db83 (ipv4: Use caller's on-stack flowi as-is
in output route lookups.) introduces another regression which
is very similar to the problem of commit e6b45241c (ipv4: reset
flowi parameters on route connect) wants to fix:
Before we call ip_route_output_key() in sctp_v4_get_dst() to
We lacked of convenient method of getting the pid inside containers.
If some issues occurred inside container guest, host user
could not know which process is in trouble just by guest pid:
the users of container guest only knew the pid inside containers.
This will bring obstacle for trouble
On 04/25/2014 01:58 PM, Viresh Kumar wrote:
> On 25 April 2014 13:48, Srivatsa S. Bhat
> wrote:
>> During frequency transitions, the cpufreq core takes the responsibility of
>> invoking cpufreq_freq_transition_begin() and cpufreq_freq_transition_end()
>> for those cpufreq drivers that define the
On 04/25/2014 02:07 PM, Viresh Kumar wrote:
> On 25 April 2014 13:48, Srivatsa S. Bhat
> wrote:
>
>> diff --git a/drivers/cpufreq/longhaul.c b/drivers/cpufreq/longhaul.c
>
>> @@ -269,8 +269,6 @@ static void longhaul_setstate(struct cpufreq_policy
>> *policy,
>
> This routine has this code as
On 04/25/2014 03:57 PM, Julian Anastasov wrote:
Hello,
On Fri, 25 Apr 2014, Xufeng Zhang wrote:
diff --git a/net/sctp/protocol.c b/net/sctp/protocol.c
index c09757f..f8a5968 100644
--- a/net/sctp/protocol.c
+++ b/net/sctp/protocol.c
@@ -493,6 +493,10 @@ static void
On 25 April 2014 13:48, Srivatsa S. Bhat
wrote:
> diff --git a/drivers/cpufreq/longhaul.c b/drivers/cpufreq/longhaul.c
> @@ -269,8 +269,6 @@ static void longhaul_setstate(struct cpufreq_policy
> *policy,
This routine has this code as well:
mult = mults[mults_index & 0x1f];
if (mult == -1)
On Thu, Apr 24, 2014 at 02:48:43PM -0400, Dan Streetman wrote:
> >>
> >> - }
> >> -
> >> + list_for_each(tmp, _list_head) {
> >> + si = list_entry(tmp, typeof(*si), list);
> >> spin_lock(>lock);
> >> - if (!si->highest_bit) {
> >> -
> On Apr 24, 2014, at 11:06 PM, "Chung-Lin Tang"
> wrote:
>
>> On 2014/4/25 02:42 AM, Pinski, Andrew wrote:
>>
>>
On Apr 24, 2014, at 11:37 AM, "Chung-Lin Tang"
wrote:
> On 2014/4/24 11:28 PM, Catalin Marinas wrote:
>> On Thu, Apr 24, 2014 at 09:55:25AM +0100,
On Wed, Apr 23, 2014 at 04:31:14PM +0200, Vlastimil Babka wrote:
> >>>
> >>> Hello,
> >>>
> >>> How about doing more clean-up at this time?
> >>>
> >>> What I did is that taking end_pfn out of the loop and consider zone
> >>> boundary once. After then, we just subtract pageblock_nr_pages on
> >>>
On 25 April 2014 13:48, Srivatsa S. Bhat
wrote:
> During frequency transitions, the cpufreq core takes the responsibility of
> invoking cpufreq_freq_transition_begin() and cpufreq_freq_transition_end()
> for those cpufreq drivers that define the ->target_index callback but don't
> set the
During frequency transitions, the cpufreq core takes the responsibility of
invoking cpufreq_freq_transition_begin() and cpufreq_freq_transition_end()
for those cpufreq drivers that define the ->target_index callback but don't
set the ASYNC_NOTIFICATION flag.
The powernow-k7 cpufreq driver falls
During frequency transitions, the cpufreq core takes the responsibility of
invoking cpufreq_freq_transition_begin() and cpufreq_freq_transition_end()
for those cpufreq drivers that define the ->target_index callback but don't
set the ASYNC_NOTIFICATION flag.
The longhaul cpufreq driver falls
On 25 April 2014 13:48, Srivatsa S. Bhat
wrote:
> During frequency transitions, the cpufreq core takes the responsibility of
> invoking cpufreq_freq_transition_begin() and cpufreq_freq_transition_end()
> for those cpufreq drivers that define the ->target_index callback but don't
> set the
* Masami Hiramatsu wrote:
> > So I don't think this should be a Kconfig entry, just enable it
> > unconditionally. That will further simplify the code.
>
> Hmm, it consumes some amount of memory (36KB/core) just for the case
> of several thousand of kprobes. On enterprise servers and desktop
On 04/25/2014 01:22 PM, Viresh Kumar wrote:
> CPUFREQ_ASYNC_NOTIFICATION was initially designed for drivers which don't want
> core to send notifications for them as they wouldn't finish frequency
> transitions in ->target_index().
>
And let's keep it that way. Overloading ASYNC_NOTIFICATION with
Tracking dirty status on 2 level pages requires very ugly macros
and taking into account how old the machines who can operate
without PAE mode only are, lets drop soft dirty tracker from
them for code simplicity (note I can't drop all the macros
from 2 level pages by now since _PAGE_BIT_PROTNONE
_PAGE_BIT_FILE (bit 6) is always less than _PAGE_BIT_PROTNONE (bit 8),
so drop redundant #ifdef.
CC: Linus Torvalds
CC: Mel Gorman
CC: Peter Anvin
CC: Ingo Molnar
CC: Steven Noonan
CC: Rik van Riel
CC: David Vrabel
CC: Andrew Morton
CC: Peter Zijlstra
CC: Pavel Emelyanov
Signed-off-by:
Hi, here are a few simplifications for softdirty memory tracker code, in
particular we dropped off x86-32 support since it seems noone needed it
here on x86 platform.
As Andrew requested I've rebased patches on top of current linux-next repo.
Also at first I wanted to rip off _PAGE_PSE bit which
* Masami Hiramatsu wrote:
> (2014/04/24 17:56), Ingo Molnar wrote:
> >> diff --git a/include/linux/module.h b/include/linux/module.h
> >> index f520a76..2fdb673 100644
> >> --- a/include/linux/module.h
> >> +++ b/include/linux/module.h
> >> @@ -16,6 +16,7 @@
> >> #include
> >> #include
> >>
During frequency transitions, the cpufreq core takes the responsibility of
invoking cpufreq_freq_transition_begin() and cpufreq_freq_transition_end()
for those cpufreq drivers that define the ->target_index callback but don't
set the ASYNC_NOTIFICATION flag.
The powernow-k6 cpufreq driver falls
Hi,
Meelis Roos reported hangs during boot in the longhaul cpufreq driver, after
commit 12478cf0c55 (cpufreq: Make sure frequency transitions are serialized).
The root-cause of this issue is the extra invocation of the
cpufreq_freq_transition_begin() and cpufreq_freq_transition_end() APIs in the
The board supported by this driver does not have analog outputs. Remove
the subdevice init for it.
Signed-off-by: Chase Southwood
Cc: Ian Abbott
Cc: H Hartley Sweeten
---
Compile tested only.
drivers/staging/comedi/drivers/addi_apci_1564.c | 13 ++---
1 file changed, 2
This board does not have analog inputs. Remove the subdevice init for
them.
Signed-off-by: Chase Southwood
Cc: Ian Abbott
Cc: H Hartley Sweeten
---
Compile tested only. To be applied on top of
[PATCH] staging: comedi: addi_apci_1564: separate from addi_common.c
On 04/25/2014 10:11 AM, Viresh Kumar wrote:
> On 25 April 2014 00:33, Meelis Roos wrote:
>
>> [ 240.140176] INFO: task kworker/0:1:116 blocked for more than 120 seconds.
>> [ 240.140353] Not tainted 3.15.0-rc2-dirty #37
>> [ 240.140485] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
On 24 April 2014 23:44, Tim Kryger wrote:
> The eMMC signalling voltage is determined by VCCQ which is provided to
> the card by the host. Signalling is not required to begin at 3.3v and,
> if the host and card both support a particular VCC/VCCQ combination, it
> can be used immediately.
>
> In
On 25 April 2014 00:36, Tim Kryger wrote:
> Switch the common SDHCI code over to use mmc_host's regulator pointers
> and remove the ones in the sdhci_host structure. Additionally, use the
> common mmc_regulator_get_supply function to get the regulators and set
> the ocr_avail mask.
>
> This
* Jiri Olsa wrote:
> SNIP
>
> >
> > Okay, so the problem is that we don't have a simple binary-state
> > feature in this case, but three possible states: 'libunwind', or
> > 'libdw-dwarf-unwind', or 'OFF', right?
> >
> > If so then the solution would be to replace those 3 last lines with
Unpaired quotes really confuse mutt when copy & pasting it into the To:
form.
Signed-off-by: Christoph Hellwig
diff --git a/MAINTAINERS b/MAINTAINERS
index 6dc67b1..11a1966 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -7293,7 +7293,7 @@ F:Documentation/blockdev/ramdisk.txt
F:
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() or pci_enable_msi_exact()
and pci_enable_msix_range() or pci_enable_msix_exact()
interfaces.
On 04/24/2014 01:24 PM, Willy Tarreau wrote:
On Thu, Apr 24, 2014 at 10:10:08AM +0800, zhuyj wrote:
On 04/23/2014 07:41 PM, Ben Hutchings wrote:
On Wed, 2014-04-23 at 15:48 +0800, zhuyj wrote:
On 04/23/2014 01:53 AM, Ben Hutchings wrote:
[...]
For what it's worth, I would recommend against
Hi,
On Fri, Apr 25, 2014 at 1:27 PM, Tushar Behera wrote:
> On 04/14/2014 08:07 PM, Sylwester Nawrocki wrote:
>> On 08/04/14 16:36, Vivek Gautam wrote:
>>> diff --git a/Documentation/devicetree/bindings/phy/samsung-phy.txt
>>> b/Documentation/devicetree/bindings/phy/samsung-phy.txt
>>> index
Hello,
The series completes converison of network drivers to the new
MSI initialization API.
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() or
Hello,
On Fri, 25 Apr 2014, Xufeng Zhang wrote:
> commit 813b3b5db83 (ipv4: Use caller's on-stack flowi as-is
> in output route lookups.) introduces another regression which
> is very similar to the problem of commit e6b45241c (ipv4: reset
> flowi parameters on route connect) wants to
* Jiri Olsa wrote:
> hi Ingo,
> please consider pulling
>
> thanks,
> jirka
>
>
> The following changes since commit a81fef347b32dea2b31275826afe1c93fa0d2d54:
>
> Merge tag 'perf-core-for-mingo' of
> git://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf into perf/core
> (2014-04-22
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() or pci_enable_msi_exact()
and pci_enable_msix_range() or pci_enable_msix_exact()
interfaces.
Cc:
This adds ability for the arc_emac to really handle its supplying clock.
To get the needed clock-frequency either a real clock or the previous
clock-frequency property must be provided.
Signed-off-by: Heiko Stuebner
Tested-by: Max Schwarz
---
changes since v1:
- fix wrong clk error check found
* Oren Twaig wrote:
> vSMP Foundation provides locality based interrupt routing which needed
> vector_allocation_domain to allow all online cpus can handle all possible
> vectors.
>
> Enforcing Interrupt Routing Comply (IRC) mode requires us to unplug this hook
> as
> otherwise the IOAPIC,
The probe function at the moment only frees the netdev but does not disconnect
the phy or removes the mdio bus it registered.
Signed-off-by: Heiko Stuebner
---
changes since v1:
- fix duplicate netif_api_del found by Max Schwarz
drivers/net/ethernet/arc/emac_main.c | 23 ++-
On 04/24/2014 10:50 PM, Greg KH wrote:
On Tue, Apr 22, 2014 at 03:22:57PM +0300, Mathias Nyman wrote:
Hi Greg
Here are the xhci fixes for 3.15-rc usb-linus.
Most of them are very small fixes that didn't make
it to 3.14, sitting and waiting for 3.15-rc1 to come out.
Only the "Prefer endpoint
On 24 April 2014 21:30, Yuyang Du wrote:
> Hi Ingo, PeterZ, and others,
>
> The current scheduler's load balancing is completely work-conserving. In some
> workload, generally low CPU utilization but immersed with CPU bursts of
> transient tasks, migrating task to engage all available CPUs for
>
On 25/04/2014 09:50, Boris BREZILLON wrote:
> Hi Maxime,
>
> On 24/04/2014 15:29, Maxime Ripard wrote:
>> On Thu, Apr 24, 2014 at 01:55:16PM +0200, Boris BREZILLON wrote:
>>> The P2WI looks like an SMBus controller which only supports byte data
>>> transfers. But, it differs from standard SMBus
On Fri, 2014-04-25 at 00:13 -0700, Jason Low wrote:
> On Fri, 2014-04-25 at 10:42 +0530, Preeti U Murthy wrote:
> > I agree with this. However I am concerned with an additional point that
> > I have mentioned in my reply to Peter's mail on this thread.
> >
> > Should we verify if
Hi Don,
On Thu, 24 Apr 2014 17:00:15 -0400, Don Zickus wrote:
> On Thu, Apr 24, 2014 at 10:41:39PM +0900, Namhyung Kim wrote:
>> Hmm.. it seems that it's exactly sorted by the data symbol addresses, so
>> I don't see any problem here. What did you expect? If you want to see
>> those
On 04/14/2014 08:07 PM, Sylwester Nawrocki wrote:
> On 08/04/14 16:36, Vivek Gautam wrote:
>> diff --git a/Documentation/devicetree/bindings/phy/samsung-phy.txt
>> b/Documentation/devicetree/bindings/phy/samsung-phy.txt
>> index 28f9edb..6d99ba9 100644
>> ---
Hi Ingo,
On Wed, 23 Apr 2014 08:09:38 +0200, Ingo Molnar wrote:
> * Namhyung Kim wrote:
>> Well, I'm okay to add the extra decimal, but it seems that it only makes
>> sense when the unit is 'K'..
>>
>> And I think it might be worth adding filtered sample count as well if
>> filtering is enabled
CPUFREQ_ASYNC_NOTIFICATION was initially designed for drivers which don't want
core to send notifications for them as they wouldn't finish frequency
transitions in ->target_index().
But there were other kinds of drivers as well who don't have straight forward
implementations of ->target_index()
On Wed, Apr 23, 2014 at 5:28 PM, Thierry Reding
wrote:
> From: Thierry Reding
>
> Many bindings use the -gpio suffix in property names. Support this in
> addition to the -gpios suffix when requesting GPIOs using the new
> descriptor-based API.
>
> Signed-off-by: Thierry Reding
It appears this
Hi Maxime,
On 24/04/2014 15:29, Maxime Ripard wrote:
> On Thu, Apr 24, 2014 at 01:55:16PM +0200, Boris BREZILLON wrote:
>> The P2WI looks like an SMBus controller which only supports byte data
>> transfers. But, it differs from standard SMBus protocol on several
>> aspects:
>> - it supports only
Patches need to be sent inline. Perhaps use git send-email.
On Fri, Apr 25, 2014 at 01:06:44AM -0300, Nicolas Del Piano wrote:
>
> >From 38e0d5778bd97062115e7d8a8ca40d18f3d71707 Mon Sep 17 00:00:00 2001
> From: Nicolas Del Piano
> Date: Thu, 24 Apr 2014 18:46:49 -0300
> Subject: [PATCH]
On 24 April 2014 14:48, Dietmar Eggemann wrote:
> On 24/04/14 08:30, Vincent Guittot wrote:
>> On 23 April 2014 17:26, Dietmar Eggemann wrote:
>>> On 23/04/14 15:46, Vincent Guittot wrote:
On 23 April 2014 13:46, Dietmar Eggemann wrote:
> Hi,
>
> [...]
>
>>
>> More than the flag that
On Sat, 2014-04-19 at 16:46 +0200, Mike Galbraith wrote:
> Hi Sebastian,
>
> On Fri, 2014-04-11 at 20:57 +0200, Sebastian Andrzej Siewior wrote:
> > Dear RT folks!
> >
> > I'm pleased to announce the v3.14-rt1 patch set.
>
> This hunk in hotplug-light-get-online-cpus.patch looks like a bug.
>
On Thu, Apr 24, 2014 at 12:46:36PM -0400, Trond Myklebust wrote:
> On Thu, Apr 24, 2014 at 12:34 PM, J. Bruce Fields
> wrote:
> > On Thu, Apr 24, 2014 at 11:31:16AM -0400, J. Bruce Fields wrote:
> >> On Thu, Apr 24, 2014 at 06:51:03AM -0400, Trond Myklebust wrote:
> >> > Hi Bruce,
> >> >
> >> >
On Thu, Apr 24, 2014 at 11:06 PM, Rob Herring wrote:
> On Thu, Apr 24, 2014 at 7:47 AM, Linus Walleij
> wrote:
>> On Wed, Apr 23, 2014 at 5:28 PM, Thierry Reding
>> wrote:
>>
>>> From: Thierry Reding
>>>
>>> Many bindings use the -gpio suffix in property names. Support this in
>>> addition to
A tester found out that we need add_disk_randomness for my scsi-mq
branch. The patch applied exports add_disk_randomness so that modular
scsi still works with a driver that either uses the low-level I/O
completion routines for the old block layer, or blk-mq, and I'd love
to get this in through
This will be needed for pending changes to the scsi midlayer that now calls
lower level block APIs, as well as any blk-mq driver that wants to contribute
to the random pool.
Signed-off-by: Christoph Hellwig
---
drivers/char/random.c |1 +
1 file changed, 1 insertion(+)
diff --git
On Thu, Apr 24, 2014 at 10:25:56AM -0500, Timur Tabi wrote:
> On 04/24/2014 06:58 AM, Westerberg, Mika wrote:
> >>>No, that's my point. I was expecting the pinmux functions of the
> >>>pinctrl driver are used by ACPI, but apparently they aren't, and
> >>>that's why I'm asking.
>
> >Which
On Fri, Apr 25, 2014 at 03:05:52PM +0800, Alex Shi wrote:
> [ 18.624755]CPU0
>
> [ 18.627349]
>
> [ 18.629943] lock(_stats->syncp.seq);
>
> [ 18.634735]
>
> [ 18.637512] lock(_stats->syncp.seq);
>
Stable kernel should already carry a fix for this,
On 24 April 2014 15:26, Meelis Roos wrote:
> This is VIA EPIA board with 533 MHz VIA Samuel 2 CPU. Normally, longhaul
> is not enabled automatically but with longhaul.enable=1. It used to work
> up to 3.14 but in 3.15-rc, different cpufreq-related codepaths block for
> long times and cause
On 2014/4/25 5:33, Adam Williamson wrote:
> On Thu, 2014-04-24 at 21:30 +0800, Jin, Yao wrote:
>
>>> Jin, do you have any idea what is going on?
>>>
>>
>> Maybe neither the patch (http://dougvj.net/baytrail_gpio_quirk_v3.patch)
>> nor my patch breaks the touch screen.
>>
>> I have tried the
On 04/24/2014 03:38 PM, Guenter Roeck wrote:
> On 04/23/2014 11:16 PM, Michal Simek wrote:
>> On 04/23/2014 05:45 PM, Guenter Roeck wrote:
>>> On Wed, Apr 23, 2014 at 04:12:59PM +0200, Michal Simek wrote:
On 04/23/2014 03:38 PM, Guenter Roeck wrote:
> On 04/22/2014 10:32 PM, Michal Simek
Adapt the NVC0 BAR driver to make it able to support chips that do not
expose a BAR3. When this happens, BAR1 is then used for USERD mapping
and the BAR alloc() functions is disabled, making GPU objects unable
to rely on BAR for data access and falling back to PRAMIN.
Signed-off-by: Alexandre
Some chips that use system memory exclusively (e.g. GK20A) do not
expose 2 BAR regions. For them only BAR1 exists, and it should be used
for USERD mapping. Do not map BAR3 if its resource does not exist.
Signed-off-by: Alexandre Courbot
Reviewed-by: Thierry Reding
---
Add support for initializing the priv ring of GK20A. This is done by the
BIOS on desktop GPUs, but needs to be done by hand on Tegra.
Signed-off-by: Alexandre Courbot
---
drivers/gpu/drm/nouveau/Makefile | 1 +
drivers/gpu/drm/nouveau/core/include/subdev/ibus.h | 1 +
Add a simple FB device for GK20A, as well as a RAM implementation based
on contiguous DMA memory allocations suitable for chips that use system
memory as video RAM.
Signed-off-by: Alexandre Courbot
---
drivers/gpu/drm/nouveau/Makefile | 2 +
nvc0_graph_ctor() would only let the graphics engine be enabled if its
oclass has a proper microcode linked to it. This prevents GR from being
enabled at all on chips that rely exclusively on external firmware, even
though such a use-case is valid.
Relax the conditions enabling the GR engine to
Add a GR device for GK20A based on NVE4, with the correct classes
definitions (GK20A's 3D class is 0xa297).
Most of the NVE4 code can be used on GK20A, so make relevant bits of
NVE4 available to other chips as well.
Signed-off-by: Alexandre Courbot
---
drivers/gpu/drm/nouveau/Makefile
GK20A's FIFO is compatible with NVE0, but only features 128 channels and
1 runlist.
Signed-off-by: Alexandre Courbot
Reviewed-by: Thierry Reding
---
drivers/gpu/drm/nouveau/Makefile | 1 +
drivers/gpu/drm/nouveau/core/engine/fifo/gk20a.c | 35 ++
Set the correct subdev/engine classes when GK20A (0xea) is probed.
Signed-off-by: Alexandre Courbot
---
drivers/gpu/drm/nouveau/core/engine/device/nve0.c | 17 +
1 file changed, 17 insertions(+)
diff --git a/drivers/gpu/drm/nouveau/core/engine/device/nve0.c
Pad the microcode to a multiple of 0x40 words, otherwise firmware will
fail to run from non-prepadded firmware files.
Signed-off-by: Alexandre Courbot
Reviewed-by: Thierry Reding
---
drivers/gpu/drm/nouveau/core/engine/graph/nvc0.c | 4
1 file changed, 4 insertions(+)
diff --git
Changes since v2:
- Enabled software class
- Removed unneeded changes to nouveau_accel_init()
- Replaced use of architecture-private pfn_to_dma() and dma_to_pfn() with
the portable page_to_phys()/phys_to_page()
- Fixed incorrect comment/commit log talking about bytes instead of words
Hope this
commit 813b3b5db83 (ipv4: Use caller's on-stack flowi as-is
in output route lookups.) introduces another regression which
is very similar to the problem of commit e6b45241c (ipv4: reset
flowi parameters on route connect) wants to fix:
Before we call ip_route_output_key() in sctp_v4_get_dst() to
On Fri, 2014-04-25 at 10:42 +0530, Preeti U Murthy wrote:
> I agree with this. However I am concerned with an additional point that
> I have mentioned in my reply to Peter's mail on this thread.
>
> Should we verify if rq->next_balance update is independent of
> pulled_tasks? sd->balance_interval
On 04/16/2014 04:13 PM, Lee Jones wrote:
Hi Andrew,
From: Roger Tseng
Realtek USB memstick host driver provides memstick host support based on the
Realtek USB card reader MFD driver.
Signed-off-by: Roger Tseng
---
drivers/memstick/host/Kconfig | 10 +
I caught a deadlock bug in 3.14 kernel occasionally on my panda board. It looks
like a real issue. Any one like take a look on this?
* Starting configure virtual network devices[74G[ OK ]
* Stopping configure virtual network devices[74G[ OK ]
* Stopping OpenSSH server[74G[ OK ]
*
701 - 800 of 1628 matches
Mail list logo
