On Thu 30-01-14 16:28:27, Greg Thelen wrote:
> On Thu, Jan 30 2014, Michal Hocko wrote:
>
> > On Wed 29-01-14 11:08:46, Greg Thelen wrote:
> > [...]
> >> The series looks useful. We (Google) have been using something similar.
> >> In practice such a low_limit (or memory guarantee), doesn't nest
On Fri, 31 Jan, at 11:29:39AM, Bjorn Helgaas wrote:
> [+cc Matt and Matthew; maybe EFI related?]
(Pulling in Borislav too)
Yeah, looks EFI related.
> On Fri, Jan 31, 2014 at 1:37 AM, Alexandra N. Kossovsky
> wrote:
> > Hello.
> >
> > I've got 3.13.0 kernel creshed on boot. A lot of debug
On 2/3/2014 4:54 AM, Morten Rasmussen wrote:
I'm therefore not convinced that idle state index is the right thing to
give the scheduler. Using a cost metric would be better in my
opinion.
I totally agree with this, and we may need two separate cost metrics
1) A latency driven one
2) A
From: Stephen Gallimore
This patch adds a reset controller platform driver for the STiH416
SoC. This initial version provides a compatible driver for the
"st,stih416-powerdown" device, which registers a system configuration
register based reset controller that controls the powerdown state of
On Sat, 25 Jan 2014 19:04:49 -0800, Florian Fainelli
wrote:
> Le 16/11/2013 04:24, Grant Likely a écrit :
> > On Fri, 15 Nov 2013 06:23:32 +, Florian Fainelli
> > wrote:
> >> Per the ePAPR v1.1 specification, 'phy-connection-type' is the canonical
> >> property name for describing an
From: Stephen Gallimore
This patch adds a reset controller implementation for STMicroelectronics
STi family SoCs; it allows a group of related reset like controls found
in multiple system configuration registers to be represented by a single
controller device. System configuration registers are
From: Stephen Gallimore
This patch selects reset controller support for ARCH_STI and
selects the reset controllers for STiH415 and STiH416 SoCs.
Signed-off-by: Stephen Gallimore
Signed-off-by: Srinivas Kandagatla
---
arch/arm/mach-sti/Kconfig |3 +++
1 file changed, 3 insertions(+)
diff
From: Srinivas Kandagatla
This patch adds softreset controller for STiH416 SOC, soft reset
controller is based on system configuration registers which are mapped
via regmap. This reset controller does not have any feedback or
acknowledgement. With this patch a new device "st,stih416-softreset"
From: Srinivas Kandagatla
This patch adds softreset controller for STiH415 SOC, soft reset
controller is based on system configuration registers which are mapped
via regmap. This reset controller does not have any feedback or
acknowledgement. With this patch a new device "st,stih415-softreset"
From: Stephen Gallimore
This patch adds a reset controller platform driver for the STiH415
SoC. This initial version provides a compatible driver for the
"st,stih415-powerdown" device, which registers a system configuration
register based reset controller that controls the powerdown state of
Hi Mark,
On Mon, 3 Feb 2014 11:02:49 +, Mark Brown wrote:
> On Mon, Feb 03, 2014 at 10:41:41AM +0100, Jean Delvare wrote:
>
> > Can you please review / apply this patch? It fixes a real bug. I also
> > think it should go to the 3.13-stable tree.
>
> Uh, it is applied? I'm the one who
From: Srinivas Kandagatla
Hi All,
This patch series adds reset controller support for STi SOC series STiH415 and
STiH416. It adds support for both power down reset and soft reset controllers.
On STi series SOCs reset lines are wired up to system configuration registers.
Most of the IPs on STi
This patch fixed following warnings on make htmldocs.
Warning(/drivers/scsi/scsi_transport_srp.c:819):
No description found for parameter 'rport'
Signed-off-by: Masanari Iida
---
drivers/scsi/scsi_transport_srp.c | 2 ++
1 file changed, 2 insertions(+)
diff --git
On Thu, 2014-01-23 at 15:05 -0500, David Long wrote:
> From: "David A. Long"
>
> Make the instruction interpreter call back to semantic action functions
> through a function pointer array provided by the invoker. The interpreter
> decodes the instructions into groups and uses the group number
From: Borislav Petkov
... so that one can know what this option is about without opening the
long help text.
Cc: Matthew Garrett
Cc: platform-driver-...@vger.kernel.org
Signed-off-by: Borislav Petkov
---
drivers/platform/x86/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
At Mon, 3 Feb 2014 09:21:16 -0500,
Trond Myklebust wrote:
>
>
> On Feb 3, 2014, at 4:43, Takashi Iwai wrote:
>
> > At Sun, 02 Feb 2014 17:04:38 -0500,
> > Trond Myklebust wrote:
> >>
> >> On Sun, 2014-02-02 at 12:27 +, Russell King - ARM Linux wrote:
> >>> On Sat, Feb 01, 2014 at
On Feb 3, 2014, at 4:43, Takashi Iwai wrote:
> At Sun, 02 Feb 2014 17:04:38 -0500,
> Trond Myklebust wrote:
>>
>> On Sun, 2014-02-02 at 12:27 +, Russell King - ARM Linux wrote:
>>> On Sat, Feb 01, 2014 at 01:03:28AM +, Russell King - ARM Linux wrote:
On Fri, Jan 31, 2014 at
On Feb 3, 2014, at 3:03, Christoph Hellwig wrote:
> On Fri, Jan 31, 2014 at 03:59:30PM -0500, Trond Myklebust wrote:
>> posix_acl_xattr_get requires get_acl() to return EOPNOTSUPP if the
>> filesystem cannot support acls. This is needed for NFS, which can't
>> know whether or not the server
On Wed, Jan 29, 2014 at 03:26:18AM +0100, Jim Lin wrote:
> On Wed, 2014-01-29 at 07:36 +0800, Peter De Schrijver wrote:
> > Implement fuse driver for Tegra20, Tegra30, Tegra114 and Tegra124.
> >
> > Signed-off-by: Peter De Schrijver
> > ---
> > Documentation/ABI/testing/sysfs-driver-tegra-fuse
On Mon, Feb 03, 2014 at 11:12:16AM +0100, Stanislaw Gruszka wrote:
> On Fri, Jan 31, 2014 at 11:01:40AM -0500, Konrad Rzeszutek Wilk wrote:
> > Perhaps by using 'subsys_system_register' and stick it there?
>
> This will not call ->resume callback as it is only called for
> devices, so additional
On Mon, Feb 03, 2014 at 12:30:46AM +0100, Pablo Neira Ayuso wrote:
> On Thu, Jan 16, 2014 at 10:23:01AM +0100, Florian Westphal wrote:
> > Andrew Vagin wrote:
> > > > I think it would be nice if we could keep it that way.
> > > > If everything fails we could proably intoduce a 'larval' dummy list
On Tue, Jan 28, 2014 at 04:14:28PM +, Mark Brown wrote:
> The changes in patch 1431574a1c4c (lib/decompressors: fix "no limit"
> output buffer length) avoid doing decompression a byte at a time when
> decompressing into high physical addresses using a small, well isolated
> change. The patch
On Fri, 31 Jan 2014 14:52:24 -0800
Andrew Morton wrote:
> On Fri, 31 Jan 2014 12:23:43 -0600 Alex Thorlton wrote:
>
> > This reverts commit 8e72033f2a489b6c98c4e3c7cc281b1afd6cb85cm, and adds
>
> 'm' is not a hex digit ;)
>
> > in code to fix up any issues caused by the revert.
> >
> > The
drivers/md/bcache/btree.c: In function ‘insert_u64s_remaining’:
drivers/md/bcache/btree.c:1816: warning: comparison of distinct pointer types
lacks a cast
Signed-off-by: Geert Uytterhoeven
---
Issue has migrated from linux-next to Linus' tree
v2: Drop L-suffix instead of using max_t(ssize_t,
drivers/md/bcache/extents.c: In function ‘btree_ptr_bad_expensive’:
drivers/md/bcache/extents.c:196: warning: format ‘%li’ expects type ‘long int’,
but argument 4 has type ‘size_t’
Signed-off-by: Geert Uytterhoeven
---
Issue has migrated from linux-next to Linus' tree
Add standard ABI entries for pulse capture devices. Also add
a separate ABI entry for the TI ECAP driver polarity option.
Signed-off-by: Matt Porter
---
Documentation/ABI/testing/sysfs-bus-iio | 18 ++
Documentation/ABI/testing/sysfs-bus-iio-pulse-tiecap | 9
On Wed, Jan 15, 2014 at 12:06 PM, Joe Perches wrote:
> On Wed, 2014-01-15 at 10:06 +0100, Geert Uytterhoeven wrote:
>> drivers/md/bcache/btree.c: In function ‘insert_u64s_remaining’:
>> drivers/md/bcache/btree.c:1816: warning: comparison of distinct pointer
>> types lacks a cast
> []
>> diff
Hi Christoffer,
On 02/02/2014 11:56 PM, Christoffer Dall wrote:
> On Thu, Jan 30, 2014 at 11:54:46AM -0500, Christopher Covington wrote:
>> I think it would be informative to provide pointers here to commonly used
>> paravirtualized devices, especially VirtIO PCI/MMIO.
>
> I disagree: that would
Add a channel type to support pulse width capture devices.
These devices capture the timing of a PWM signal based on a
configurable trigger
Signed-off-by: Matt Porter
---
drivers/iio/industrialio-core.c | 1 +
include/linux/iio/types.h | 1 +
2 files changed, 2 insertions(+)
diff --git
Adds support for capturing PWM signals using the TI ECAP peripheral.
This driver supports triggered buffer capture of pulses on multiple
ECAP instances. In addition, the driver supports configurable polarity
of the signal to be captured.
Signed-off-by: Matt Porter
---
drivers/iio/pulse/Kconfig
Add the pulse driver subdirectory when configuring and building
IIO.
Signed-off-by: Matt Porter
---
drivers/iio/Kconfig | 1 +
drivers/iio/Makefile | 1 +
2 files changed, 2 insertions(+)
diff --git a/drivers/iio/Kconfig b/drivers/iio/Kconfig
index 5dd0e12..286acc3 100644
---
The IIO TI ECAP driver depends on the TI PWMSS management
driver in this subsystem. Enable PWMSS when the IIO TI ECAP
driver is selected.
Signed-off-by: Matt Porter
---
drivers/pwm/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pwm/Kconfig
Add missing interrupt properties to the ecap0, ecap1, and ecap2
nodes.
Signed-off-by: Matt Porter
---
arch/arm/boot/dts/am33xx.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
index 6d95d3d..b4139ba 100644
---
Changes since v1:
- Rebased to 3.14-rc1
- Renamed in_pulse_polarity to pulse_polarity
- Added ABI entries for pulse devices and TI ECAP
This series adds support for PWM capture devices within IIO and
adds a TI ECAP IIO driver.
PWM capture devices are supported using a new
Am Sonntag, 2. Februar 2014, 20:24:21 schrieb Jörn Engel:
Hi Jörn,
>On Sun, 2 February 2014 22:25:31 +0100, Stephan Mueller wrote:
>> Am Sonntag, 2. Februar 2014, 15:36:17 schrieb Jörn Engel:
>> > Collects entropy from random behaviour all modern cpus exhibit.
>> > The
>> > scheduler and slab
On Fri, Jan 24, 2014 at 08:39:50PM +0100, Radim Krčmář wrote:
> Hello,
>
> could 3.12.9 and 3.10.28 include
> 0dce7cd kvm: x86: fix apic_base enable check
> ? It fixes a regression applied to 3.10.26 and 3.12.7.
I am also queuing this for the 3.11 kernel. Thanks!
Cheers,
--
Luis
> Stable
On Mon, Feb 03, 2014 at 11:14:05AM +0100, Juri Lelli wrote:
> On 02/03/2014 10:53 AM, Henrik Austad wrote:
> > On Fri, Jan 31, 2014 at 05:43:27PM +0100, Juri Lelli wrote:
> >> Don't compare sysctl_sched_rt_runtime against sysctl_sched_rt_period if
> >> the former is equal to RUNTIME_INF, otherwise
On Thu 30-01-14 12:29:06, Johannes Weiner wrote:
> On Tue, Dec 17, 2013 at 04:45:29PM +0100, Michal Hocko wrote:
> > The current charge path might race with memcg offlining because holding
> > css reference doesn't stop css offline. As a result res counter might be
> > charged after
On 03/02/14 11:57, David Vrabel wrote:
Hi,
That's bad indeed. I think the best solution is to put those parts
behind an #ifdef x86. The ones moved from x86/p2m.c to grant-table.c.
David, Stefano, what do you think?
I don't think we want (more) #ifdef CONFIG_X86 in grant-table.c and the
The grant mapping API does m2p_override unnecessarily: only gntdev needs it,
for blkback and future netback patches it just cause a lock contention, as
those pages never go to userspace. Therefore this series does the following:
- the original functions were renamed to __gnttab_[un]map_refs, with
On Thu 30-01-14 12:18:37, Johannes Weiner wrote:
> On Tue, Dec 17, 2013 at 04:45:26PM +0100, Michal Hocko wrote:
[...]
> > -static int __mem_cgroup_try_charge(struct mm_struct *mm,
> > - gfp_t gfp_mask,
> > +static int __mem_cgroup_try_charge_memcg(gfp_t gfp_mask,
> >
Hi Mark,
On Wed, Jan 29, 2014 at 8:27 PM, Manish Badarkhe
wrote:
> Use devm_* API operations for fixed regulator driver so that
> driver core will manage resources.
>
> Also, introduce a new API "devm_kstrdup" and used it in fixed
> regulator driver to manage resources.
>
> Changes since V3:
>
Theodore Ts'o dixit:
>I really like Jvrn's tests doing repeated boot testing and observing
>on a SMP system, the slab allocation pattern is quite deterministic.
>So even though the numbers might *look* random, an attacker with deep
>knowledge of how the kernel was compiled and what memory
Am Sonntag, 2. Februar 2014, 20:39:22 schrieb Theodore Ts'o:
Hi Theodore,
>On Sun, Feb 02, 2014 at 10:25:31PM +0100, Stephan Mueller wrote:
>> Second, when I offered my initial patch which independently collects
>> some entropy on the CPU execution timing, I got shot down with one
>> concern
On 02/03/2014 02:05 PM, Glauber Costa wrote:
> On Mon, Feb 3, 2014 at 10:57 AM, Vladimir Davydov
> wrote:
>> On 02/03/2014 10:21 AM, David Rientjes wrote:
>>> On Sun, 2 Feb 2014, Vladimir Davydov wrote:
>>>
Per-memcg kmem caches are named as follows:
(:)
where is the
Hi Linus:
This push fixes a number of concurrency issues on s390 where
multiple users of the same crypto transform may clobber each
other's results.
Please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git
or
On 02/03/2014 03:04 PM, David Rientjes wrote:
> On Mon, 3 Feb 2014, Vladimir Davydov wrote:
>
>> AFAIU, cgroup identifiers dumped on oom (cgroup paths, currently) and
>> memcg slab cache names serve for different purposes.
> Sure, you may dump the name for a number of legitimate reasons, but the
This patch makes the hrtimer timeout configurable per PMU
box. Not all counters have necessarily the same width and
rate, thus the default timeout of 60s may need to be adjusted.
This patch adds box->hrtimer_duration. It is set to default
when the box is allocated. It can be overriden when the
On certain processors, the uncore PMU boxes may only be
msr-bsed or PCI-based. But in both cases, the cpumask,
suggesting on which CPUs to monitor to get full coverage
of the particular PMU, must be created.
However with the current code base, the cpumask was only
created on processor which had
With the new template mechanism introduced in IMA since kernel 3.13,
the format of data sent through the binary_runtime_measurements interface
is slightly changed. Now, for a generic measurement, the format of
template data (after the template name) is:
template_len | field1_len | field1 | ... |
This patch is needed because that PMU uses 32-bit free
running counters with no interrupt capabilities.
On SNB/IVB/HSW, we used 20GB/s theoretical peak to calculate
the hrtimer timeout necessary to avoid missing an overflow.
That delay is set to 5s to be on the cautious side.
The SNB IMC uses
Move a couple of functions around to avoid forward declarations
when we add code later on.
Signed-off-by: Stephane Eranian
---
arch/x86/kernel/cpu/perf_event_intel_uncore.c | 73 +
1 file changed, 37 insertions(+), 36 deletions(-)
diff --git
Before this change, to correctly calculate the template digest for the
'ima' template, the event name field (id: 'n') length was set to the fixed
size of 256 bytes.
This patch reduces the length of the event name field to the string
length incremented of one (to make room for the termination
The current code assumes all PCI fixed counters implement more than
32-bit hardware counters. The actual width is then round up to 64 to
enable base + 8 * idx calculations.
Not all PMUs necessarily implement counters with more than 32-bits.
The patch makes the uncore_pci_perf_ctr() function
This patch modifies some of the helper functions to support
more than one fixed counter per uncore PCI PMU box.
Signed-off-by: Stephane Eranian
---
arch/x86/kernel/cpu/perf_event_intel_uncore.c |4 ++--
arch/x86/kernel/cpu/perf_event_intel_uncore.h | 22 +-
2 files
This patch adds a new uncore PMU for Intel SNB/IVB/HSW client
CPUs. It adds the Integrated Memory Controller (IMC) PMU. This
new PMU provides a set of events to measure memory bandwidth utilization.
The IMC on those processor is PCI-space based. This patch
exposes a new uncore PMU on those
This patch makes perf use Mebibytes to display the counts
of uncore_imc/data_reads/ and uncore_imc/data_writes.
1MiB = 1024*1024 bytes.
Signed-off-by: Stephane Eranian
---
arch/x86/kernel/cpu/perf_event_intel_uncore.c |8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git
This patch series adds support for SandyBridge, IvyBridge, Haswell client
(desktop/mobile)
processor PCI-based integrated memory controller PMU. This PMU provides a few
free running
32-bit counters which can be used to determine memory bandwidth utilization.
The code is based on the
This patch enables custom struct pmu callbacks per uncore
PMU types. This feature may be used to simplify counter
setup for certain uncore PMUs which have free running
counters for instance. It becomes possible to bypass
the event scheduling phase of the configuration.
Signed-off-by: Stephane
This patch adds the PCI ids for the Intel SandyBridge,
IvyBridge, Haswell Client memory controller (IMC).
Signed-off-by: Stephane Eranian
---
include/linux/pci_ids.h |3 +++
1 file changed, 3 insertions(+)
diff --git a/include/linux/pci_ids.h b/include/linux/pci_ids.h
index
On Fri, Jan 31, 2014 at 06:19:26PM +, Nicolas Pitre wrote:
> Right now (on ARM at least but I imagine this is pretty universal), the
> biggest impact on information accuracy for a CPU depends on what the
> other CPUs are doing. The most obvious example is cluster power down.
> For a
On Sun, Feb 02, 2014 at 07:06:06PM +0100, Jean-Francois Moine wrote:
> - the .of_match_table is not needed because the i2c client is created by
> the i2c subsystem from the 'reg' in the DT,
It's generally better to have an explict set of OF IDs even if the
default does work - matching purely
[CCing linux-mm]
Does this ring bells? I haven't checked very deeply but it doesn't seem
to be fixed since 3.12.
Hoolger, could you post your config, please?
On Fri 31-01-14 21:12:27, Holger Kiehl wrote:
> Hello,
>
> today one of our system got a kernel bug message. It kept on running
> but
2014-01-29 Akinobu Mita :
> 2014-01-28 Konrad Rzeszutek Wilk :
>> On Mon, Jan 27, 2014 at 02:54:47PM +0100, Marek Szyprowski wrote:
>>> Hello,
>>>
>>> On 2014-01-14 15:13, Akinobu Mita wrote:
>>> >Calling dma_alloc_coherent() with __GFP_ZERO must return zeroed memory.
>>> >
>>> >But when the
On Fri, Jan 31, 2014 at 05:04:02PM +0100, astx wrote:
> Dear Alexey,
>
> seems to help. Thank you for your quick response. Kernel 3.10.28 is
> now stable using h323 / Polycom.
Thanks, if no objection, will pass this patch to David.
>From d98506139d6e192705422ffba13bc2ff476ac513 Mon Sep 17
On 01/31/2014 06:38 PM, Rob Herring wrote:
> On Fri, Jan 31, 2014 at 6:08 AM, Michal Simek wrote:
>> Reserve space from 0x0 - __pa(swapper_pg_dir),
>> if kernel is loaded from 0, which is not DMAable.
>> It is causing problem with MMC driver and others
>> which want to add dma buffers to this
From: Srinivas Kandagatla
This patch adds support to STiH416 SOC, which has two ethernet
snps,dwmac controllers version 3.710. With this patch B2000 and B2020
boards can boot with ethernet in MII and RGMII modes.
Tested on both B2020 and B2000.
Signed-off-by: Srinivas Kandagatla
---
From: Srinivas Kandagatla
This patch adds support to STiH415 SOC, which has two ethernet
snps,dwmac controllers version 3.610. With this patch B2000 and B2020
boards can boot with ethernet in MII and RGMII modes.
Tested on both B2020 and B2000.
Signed-off-by: Srinivas Kandagatla
---
From: Srinivas Kandagatla
STi series SOCs have a glue layer on top of the synopsis gmac IP, this
glue layer needs to be configured before the gmac driver starts using
the IP.
This patch adds a support to this glue layer which is configured via
stmmac setup, init, exit callbacks.
Signed-off-by:
From: Srinivas Kandagatla
Hi All,
This patch series adds Ethernet support to STi series SOCs STiH415 and STiH416.
STi SOC series integrates dwmac IP from synopsis, however there is a hardware
glue on top of this standard IP, this glue needs to configured before the
actual dwmac can be used.
From: James Hogan
> On 03/02/14 10:35, David Laight wrote:
> > From: James Hogan
> >> Combining __packed with __aligned(2) does the trick though (__packed
> >> alone sets __aligned(1) which is obviously going to be suboptimal).
...
>
> Meta is also one of those arches, and according to my quick
On Mon, Feb 03, 2014 at 10:57:28AM +, David Vrabel wrote:
> On 02/02/14 18:52, Zoltan Kiss wrote:
> > On 02/02/14 11:29, Julien Grall wrote:
> >> Hello,
> >>
> >> This patch is breaking Linux compilation on ARM:
> >>
> >> drivers/xen/grant-table.c: In function ‘__gnttab_map_refs’:
> >>
Adding call-graph option support into .perfconfig file,
so it's now possible use call-graph option like:
[top]
call-graph = fp
[record]
call-graph = dwarf,8192
Above options ONLY setup the unwind method. To enable
perf record/top to actually use it the command line
option
On Wed, Jan 29, 2014 at 04:15:18PM -0800, Mukesh Rathor wrote:
> We need to set cr4 flags for APs that are already set for BSP.
The title is missing the 'xen' part.
I rewrote it a bit and I think this should go in 3.14.
David, Boris: It is not the full fix as there are other parts to
make an
On 02/02/2014 10:40 AM, Masami Hiramatsu wrote:
> (2014/02/01 21:17), Chen Gang wrote:
>> When CONFIG_KRETPROBES disabled, cleanup_rp_inst() is useless too. It
>> is only called by unregister_kretprobes() which is in CONFIG_KRETPROBES
>> enabled area.
>>
>> The related warning (allmodconfig under
We use PERF_SAMPLE_PERIOD sample type only for frequency
setup -F (default) option. The -c does not need store period,
because it's always the same.
In -c case the report code uses '1' as period. Fixing
it to perf_event_attr::sample_period.
Signed-off-by: Jiri Olsa
Cc: Corey Ashford
Cc: David
Adding people readable output for callchain debug,
to get following '-v' output:
$ perf record -v -g ls
callchain: type DWARF
callchain: stack dump size 4096
...
Signed-off-by: Jiri Olsa
Cc: Corey Ashford
Cc: David Ahern
Cc: Ingo Molnar
Cc: Namhyung Kim
Cc: Paul Mackerras
Cc: Peter
On Fri, Jan 31, 2014 at 02:24:33PM -0500, Waiman Long wrote:
>
> Light contention is the only case where the qspinlock may not perform as
> good as the ticket spinlock. I know this is the most common case. However, I
> would argue that the slowdown, if any, will not be really noticeable. This
>
On Sun, Feb 02, 2014 at 10:03:57AM +0100, Ingo Molnar wrote:
>
> * Waiman Long wrote:
>
> > How about making the selection of MCS or ticket queuing either user
> > configurable or depending on the setting of NR_CPUS, NUMA, etc?
>
> No!
>
> There are lots of disadvantages to adding such
We have few fedora bug reports about list corruption on pinctrl,
for example:
https://bugzilla.redhat.com/show_bug.cgi?id=1051918
Most likely corruption happen due lack of protection of pinctrl_list
when adding new nodes to it. Patch corrects that.
Fixes: 57b676f9c1b ("pinctrl: fix and simplify
System clks are just gates, and thus do not provide any rate operations.
Authorize clk rate change to be propagated to system clk parents.
Signed-off-by: Boris BREZILLON
---
drivers/clk/at91/clk-system.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
On 02/03/2014 06:03 PM, Chen Gang wrote:
> On 02/03/2014 04:58 PM, Dan Carpenter wrote:
>> On Sat, Feb 01, 2014 at 09:57:39PM +0800, Chen Gang wrote:
>>> It seems, our kernel still stick to treate 'pack' region have effect
>>> with both 'align' and 'sizeof'.
>>>
>>
>> It's not about packed
On Tue, Jan 28, 2014 at 01:18:40PM +0100, Krzysztof Kozlowski wrote:
> - /* Battery-Charger Constant Voltage (CV) Mode, from SM-V700: 4.35V */
> + /* Battery-Charger Constant Voltage (CV) Mode, set to: 4.35V */
Does this charger chip support only 4.35V batteries? If the CV is hard coded
Hi Thomas,
On Thursday 16 January 2014 03:52 PM, Sricharan R wrote:
> Hi Thomas,
>
> On Tuesday 03 December 2013 03:57 PM, Sricharan R wrote:
>> Some socs have a large number of interrupts requests to service
>> the needs of its many peripherals and subsystems. All of the
>> interrupt lines from
Hello Mike,
This series fixes a bug in the prog clk prepare function (the platform hangs
when preparing a prog clk).
It also implements the determine_rate callback for these prog clks and allow
system clk to propagate the rate change to its parent.
These modifications are needed to get the
The prog irq is a level irq reflecting the prog clk status. As a result the
irq line will stay high when the prog clk is ready and the system will
hang.
Disable the irq when it is handled to avoid this problem.
Signed-off-by: Boris BREZILLON
---
drivers/clk/at91/clk-programmable.c |5 -
Implement the determine_rate callback to choose the best parent clk that
fulfills the requested rate.
Signed-off-by: Boris BREZILLON
---
drivers/clk/at91/clk-programmable.c | 56 +--
1 file changed, 28 insertions(+), 28 deletions(-)
diff --git
Hi
[..snip..]
> Finally, support for probing GK20A is added in the last 2 patches. It should
> be
> noted that contrary to what Nouveau currently expects, GK20A does not embed
> any
> display hardware (that part being handled by tegradrm). So this driver should
> really be only used through DRM
Guten Tag,
Mein Name ist Mr.SUN Zhijun, ich mit der Bank of China zu arbeiten. Ich brauche
Ihre Unterstützung in Durchführung einer Transaktion bei $ 18,5 Millionen
Dollar geschätzt, möchte ich Ihnen 30% der gesamten Mittel als Ausgleich für
Ihre Unterstützung in dieser Transaktion. Ich werde
On Sun, 2 Feb 2014, Josh Boyer wrote:
> Hi All,
>
> With v3.13-11147-gb399c46 I'm seeing the following build errors for
> Xen on ARM. I haven't been able to test Linus' recent tree yet, but I
> was wondering if anyone had seen this yet.
>
> josh
Thanks for the report, we'll fix as soon as
On Mon, Feb 03, 2014 at 02:29:43AM -0800, Christoph Hellwig wrote:
> On Thu, Jan 30, 2014 at 02:01:38PM -0800, Linus Torvalds wrote:
> > In the end, all the original call-sites should have a dentry, and none
> > of this is "fundamental". But you're right, it looks like an absolute
> > nightmare to
On Sun, 2014-02-02 at 20:56 -0800, Christoffer Dall wrote:
> On Thu, Jan 30, 2014 at 11:54:46AM -0500, Christopher Covington wrote:
> > Hi Ian,
> >
> > On 01/30/2014 11:11 AM, Ian Campbell wrote:
> > > mach-virt has existed for a while but it is not written down what it
> > > actually
> > >
On Mon, 3 Feb 2014, David Vrabel wrote:
> On 02/02/14 18:52, Zoltan Kiss wrote:
> > On 02/02/14 11:29, Julien Grall wrote:
> >> Hello,
> >>
> >> This patch is breaking Linux compilation on ARM:
> >>
> >> drivers/xen/grant-table.c: In function ‘__gnttab_map_refs’:
> >>
On Sat, 01 Feb 2014 10:09:03 -0500
Peter Hurley wrote:
> On 01/14/2014 11:24 AM, Pavel Roskin wrote:
> > Hi Alan,
> >
> > Quoting One Thousand Gnomes :
> >
> >>> Maybe we should unset the low_latency flag as soon as DMA fails? There
> >>> are two flags, one is state->uart_port->flags and the
On Mon, 3 Feb 2014, Vladimir Davydov wrote:
> AFAIU, cgroup identifiers dumped on oom (cgroup paths, currently) and
> memcg slab cache names serve for different purposes.
Sure, you may dump the name for a number of legitimate reasons, but the
problem still exists that it's difficult to
On Mon, Feb 03, 2014 at 10:41:41AM +0100, Jean Delvare wrote:
> Can you please review / apply this patch? It fixes a real bug. I also
> think it should go to the 3.13-stable tree.
Uh, it is applied? I'm the one who maintains the regulator tree
generally...
signature.asc
Description: Digital
On 03/02/14 10:35, David Laight wrote:
> From: James Hogan
>> On 03/02/14 10:05, David Laight wrote:
>>> Architectures that define such alignment rules are a right PITA.
>>> You either need to get the size to 2 without using 'packed', or
>>> just not define such structures.
>>> It is worth seeing
> >> > Patch looks good to me. Is there any reason why we should rush this in
> >> > for v3.14, or is it okay to go to -next?
> >>
> >> No rush, but it's been on review like forever so unless there is
> >> some noise from the DT people at -rc1 I'd be very happy if you
> >> could apply patches 1 &
> This changes the following mechanisms in the TC3589x device tree
> probing path:
>
> - Use the .of_match_table in struct device_driver to match the
> device in the device tree.
> - Add matches for the proper compatible strings "toshiba,..."
> and all sub-variants, just as is done for the
Hi Kalle,
Could you please review the three updated patches?
Thanks!
--
Regards,
Alexander Gordeev
agord...@redhat.com
--
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
501 - 600 of 1358 matches
Mail list logo
