From: Anton Vorontsov anton.voront...@linaro.org
The actual values of KDB_REPEAT_* enum values and overall logic stayed
the same, but we now treat the values as flags.
This makes it possible to add other flags and combine them, plus makes
the code a lot simpler and shorter. But
From: Anton Vorontsov anton.voront...@linaro.org
We're about to add more options for command behaviour, so let's expand
the meaning of kdb_repeat_t.
So far we just do various renames, there should be no functional changes.
Signed-off-by: Anton Vorontsov anton.voront...@linaro.org
Signed-off-by:
From: Anton Vorontsov anton.voront...@linaro.org
We're about to add more options for commands behaviour, so let's give
a more generic name to the low-level kdb command registration function.
There are just various renames, no functional changes.
Signed-off-by: Anton Vorontsov
From: Anton Vorontsov anton.voront...@linaro.org
The struct member is never used in the code, so we can remove it.
We will introduce real flags soon by renaming cmd_repeat to cmd_flags.
Signed-off-by: Anton Vorontsov anton.voront...@linaro.org
Signed-off-by: John Stultz john.stu...@linaro.org
On 06/19/2014 04:00 PM, Kishon Vijay Abraham I wrote:
Hi Tero,
On Thursday 19 June 2014 04:42 PM, Tero Kristo wrote:
On 05/29/2014 09:38 AM, Kishon Vijay Abraham I wrote:
From: Keerthy j-keer...@ti.com
Change the parent of apll_pcie_in_clk_mux to dpll_pcie_ref_m2ldo_ck
from dpll_pcie_ref_ck.
Hi Tero,
On Thursday 19 June 2014 04:46 PM, Tero Kristo wrote:
On 05/29/2014 09:38 AM, Kishon Vijay Abraham I wrote:
Added missing 32khz clock used by PCIe PHY.
The documention for this node can be found @ ../bindings/clock/ti/gate.txt.
You can drop the node documentation ref, and rather
Currently the Tamonten DTS define a fixed regulator for the 5V supply.
However this regulator is in fact on the base board. Fix this by
properly defining the regulators found on the base boards.
Signed-off-by: Alban Bedel alban.be...@avionic-design.de
---
v2: * Put the board regualtors in the
Hi,
On Thursday 19 June 2014 04:50 PM, Tero Kristo wrote:
On 05/29/2014 09:38 AM, Kishon Vijay Abraham I wrote:
Added missing clocks used by second instance of PCIe PHY.
The documention for this nodes can be found @ ../bindings/clock/ti/gate.txt.
Drop the ref to the binding doc and rather
On Thu, Jun 19, 2014 at 12:02:29PM +0200, Rasmus Villemoes wrote:
This change shaves a few bytes off the generated code.
Signed-off-by: Rasmus Villemoes li...@rasmusvillemoes.dk
---
mm/percpu.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/mm/percpu.c
Enable the RGB output and add the panel definition to the Medcom Wide
DTS. Also add a label to the backlight defintion to reference it in
the panel definition.
Signed-off-by: Alban Bedel alban.be...@avionic-design.de
---
v2: * no changes since v1
---
arch/arm/boot/dts/tegra20-medcom-wide.dts |
On 06/19/2014 04:23 PM, Kishon Vijay Abraham I wrote:
Hi Tero,
On Thursday 19 June 2014 04:46 PM, Tero Kristo wrote:
On 05/29/2014 09:38 AM, Kishon Vijay Abraham I wrote:
Added missing 32khz clock used by PCIe PHY.
The documention for this node can be found @ ../bindings/clock/ti/gate.txt.
On Thu, Jun 19, 2014 at 09:25:36AM -0400, Tejun Heo wrote:
On Thu, Jun 19, 2014 at 12:02:29PM +0200, Rasmus Villemoes wrote:
This change shaves a few bytes off the generated code.
Signed-off-by: Rasmus Villemoes li...@rasmusvillemoes.dk
---
mm/percpu.c | 3 +--
1 file changed, 1
On 06/19/2014 03:45 PM, Kishon Vijay Abraham I wrote:
Hi Tero,
On Thursday 19 June 2014 04:40 PM, Tero Kristo wrote:
On 05/29/2014 09:38 AM, Kishon Vijay Abraham I wrote:
From: Keerthy j-keer...@ti.com
Add divider table to optfclk_pciephy_div clock. The Documentation
for divider clock can be
Patch bug: Make BUG() always stop the machine changed the
behavior of BUG() with CONFIG_BUG=n from a no-op into an infinite
loop. Modify the definition of BUG_ON() accordingly such that the
behavior of BUG_ON(1) is identical to that of BUG().
Signed-off-by: Bart Van Assche bvanass...@acm.org
Cc:
Hi Lee,
Purely for testing purposes, as it's the only board I have. If
anyone has the other revisions and would be happy to test the driver
for me then great.
Ok that's what I suspected.
If you tell me how, I can test on a Rev C board. But as there are several
other
On Thu, Jun 19, 2014 at 11:01:26AM +0800, Lai Jiangshan wrote:
+ /*
+* Restore per-cpu operation. smp_store_release() is paired with
+* smp_load_acquire() in __pcpu_ref_alive() and guarantees that the
s/smp_load_acquire()/smp_read_barrier_depends()/
Will update.
On Wed, 18 Jun 2014 15:10:48 +0100
Lee Jones lee.jo...@linaro.org wrote:
So I guess you should either a) take the whole patch-set through your mfd
tree
or b) merge the mfd patches and create an immutable branch that can be
pulled by
Mark, Mike and Alessandro.
I don't know what's
Hey, Paul.
On Wed, Jun 18, 2014 at 07:27:08PM -0700, Paul E. McKenney wrote:
Yep, smp_load_acquire() orders its load against later loads and stores,
so it really does need a memory barrier on weakly ordered systems.
Yeap.
This is the publish operation for dynamically allocated per-CPU
On Thursday, June 19, 2014 04:23:29 PM Allen Yu wrote:
On Thursday, June 19, 2014, Rafael J. Wysocki wrote:
On Wednesday, June 18, 2014 11:30:51 AM Alan Stern wrote:
On Tue, 17 Jun 2014, Rafael J. Wysocki wrote:
On Tuesday, June 17, 2014 10:37:03 PM Rafael J. Wysocki wrote:
On
From: Matt Fleming matt.flem...@intel.com
It appears that the BayTrail-T class of hardware requires EFI in order
to powerdown and reboot and no other reliable method exists.
This quirk is generally applicable to all hardware that has the ACPI
Hardware Reduced bit set, since usually ACPI would be
From: Matt Fleming matt.flem...@intel.com
Both x86 and ARM need a way to reboot/poweroff machines using the EFI
runtime services.
For x86, we want to really, really restrict this support to those
platforms that absolultely have no other method because EfiResetSystem()
doesn't generally work very
From: Matt Fleming matt.flem...@intel.com
Implement efi_reboot(), which is really just a wrapper around the
EfiResetSystem() EFI runtime service, but it does at least allow us to
funnel all callers through a single location.
It also simplifies the callsites since users no longer need to check to
From: Matt Fleming matt.flem...@intel.com
Not only can EfiResetSystem() be used to reboot, it can also be used to
power down machines.
By and large, this functionality doesn't work very well across the range
of EFI machines in the wild, so it should definitely only be used as a
last resort. In
On Thu, Jun 05, 2014 at 03:52:58PM +0300, Heikki Krogerus wrote:
On some platforms a PHY may need to be handled also in the
host controller driver. Exynos5420 SoC requires some PHY
tuning based on the USB speed. This patch delivers dwc3's
PHYs to the xhci platform device when it's created.
On Thu, 19 Jun 2014 05:46:43 +0200
Mike Galbraith umgwanakikb...@gmail.com wrote:
On Wed, 2014-06-18 at 20:12 -0400, Steven Rostedt wrote:
Dear RT Folks,
I'm pleased to announce the 3.12.22-rt33 stable release.
Didn't we have this issue before?
git@marge:~/linux-2.6 git diff
On Fri, Jun 06, 2014 at 04:32:03PM +0530, Vivek Gautam wrote:
Hi,
On Fri, Jun 6, 2014 at 12:41 PM, Antoine Ténart
antoine.ten...@free-electrons.com wrote:
Hi,
On Fri, Jun 06, 2014 at 12:09:06PM +0530, Vivek Gautam wrote:
On Thu, Jun 5, 2014 at 9:18 PM, Antoine Ténart
Hi Linus,
Please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
pm+acpi-3.16-rc2
to receive ACPI and power management updates for v3.16-rc2
with top-most commit 2ba87ea132a7364dbeb71126f3d7b8ec8e59d0e9
Merge branches 'pm-cpufreq' and 'pm-cpuidle'
on top of
On Fri, Jun 13, 2014 at 11:36:24AM +, David Laight wrote:
From: Robert Baldyga
usb_gadget_disconnect() shouldn't be called under spinlock to avoid
spinlock recursion. Function usb_gadget_disconnect() calls pullup(),
which is callback from UDC driver, usually calling
linux-kernel@vger.kernel.org
DKK 6874,49
http://aryacharge.com/nemlog-in.dk/login.aspx/noeglekort/
--
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
On Thu, Jun 19, 2014 at 12:04 AM, Laura Abbott lau...@codeaurora.org wrote:
The common early_init_dt_add_memory_arch takes the base and size
of a memory region as u64 types. The function never checks if
the base and size can actually fit in a phys_addr_t which may
be smaller than 64-bits. This
Linus,
This includes three patches from Oleg Nesterov. The first is a fix to a
race condition that happens between enabling/disabling syscall tracepoints
and new process creations (the check to go into the ptrace path for a process
can be set when it shouldn't, or not set when it should). Not a
This reverts commit 87c00572ba05aa8c9db118da75c608f47eb10b9e.
OS X = 10.7.* are the only known guests which realistically required
this functionality. As it turns out, OS X can be told to forego using
monitor/mwait by passing it idlehalt=0 as a kernel argument, so we're
better off removing this
On Wed, Jun 18, 2014 at 9:13 PM, Greg KH gre...@linuxfoundation.org wrote:
On Wed, Jun 18, 2014 at 12:36:54PM +0200, Maarten Lankhorst wrote:
+#define CREATE_TRACE_POINTS
+#include trace/events/fence.h
+
+EXPORT_TRACEPOINT_SYMBOL(fence_annotate_wait_on);
v1: introduced feature as a framework within power supply class driver with
separate files for battid framework and charging framework
v2: fixed review comments, moved macros and inline functions to power_supply.h
v3: moved the feature as a separate driver, combined battid framework and
As per Product Safety Engineering (PSE) specification for battery charging, the
battery characteristics and thereby the charging rates can vary on different
temperature zones. This patch introduces a PSE compliant charging algorithm with
maintenance charging support. The algorithm can be selected
Add new power supply properties for input current, charge termination
current, min and max temperature
POWER_SUPPLY_PROP_TEMP_MIN - minimum operatable temperature
POWER_SUPPLY_PROP_TEMP_MAX - maximum operatable temperature
POWER_SUPPLY_PROP_INLMT - input current limit programmed by charger.
Hi,
Overall I like the idea, I've some comments on the implementation inline.
On 06/19/2014 03:04 PM, Ulf Hansson wrote:
The pwrseq subsystem handles complex power sequences, typically useful
for subsystems that makes use of discoverable buses, like for example
MMC and I2C.
I2C is not
This patch introduces BQ24261 charger driver. The driver makes use of power
supply charging driver to setup charging. So the driver does hardware
abstraction and handles h/w specific corner cases. The charging logic resides
with power supply charging driver
Signed-off-by: Jenny TC
For the Armada 380 and Armada 385 SoCs, the common bindings for those
2 SoCs, was forgotten. This patch add the documentation for the
marvell,aramda38x property.
Signed-off-by: Gregory CLEMENT gregory.clem...@free-electrons.com
---
Hi,
This fix should be merged in 3.16. For 3.15 I am not sure as
On Thu, 19 Jun, at 08:22:32PM, Kefeng Wang wrote:
commit 9d0c4dfed(of/fdt: update of_get_flat_dt_prop in prep for libfdt)
change the of_get_flat_dt_prop, so update related variable to fix build
warning. Btw, remove unused variable 'name'.
Signed-off-by: Kefeng Wang wangkefeng.w...@huawei.com
On Wed, 18 Jun 2014 21:15:59 -0400
Steven Rostedt rost...@goodmis.org wrote:
On Thu, 19 Jun 2014 03:25:46 +0800
kbuild test robot fengguang...@intel.com wrote:
tree:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
ftrace/core
head:
Linus,
Please do not pull this. I just found out that it can break other archs
as it uses TIF_SYSCALL_TRACEPOINT in generic code and not all archs
define it.
I'll work on a fix for this and send an update.
-- Steve
On Thu, 19 Jun 2014 09:59:08 -0400
Steven Rostedt rost...@goodmis.org wrote:
Hi all,
I'm currently adding VFIO support for kvmtool, so I'm interested in this
patch series (although actually from a PCI perspective).
Eric: can you CC me on future versions of this series please? Once things
start to stabilise, I can help with testing.
On Thu, Jun 05, 2014 at 03:39:50PM
On Fri, Jun 13, 2014 at 01:02:56PM +0200, Tomasz Nowicki wrote:
This commit abstracts MCE calls and provides weak corresponding default
implementation for those architectures which do not need arch specific
actions. Each platform willing to do additional architectural actions
should provides
On Thu, Jun 19, 2014 at 02:03:31PM +0900, Masami Hiramatsu wrote:
(2014/06/19 11:08), Josh Poimboeuf wrote:
On Tue, Jun 17, 2014 at 11:04:36AM +, Masami Hiramatsu wrote:
Hi,
Here is the version 2 of the series of patches which introduces
IPMODIFY flag for ftrace_ops to detect
Hi,
On 06/19/2014 04:03 PM, Hans de Goede wrote:
Hi,
snip
Also I'm not sold on how you're making this a devm only thing, and
are using devres_alloc to not only allocate memory for resource tracking,
but also the actual backing struct, that is not how devres_alloc is
intended to be used
On Fri, Jun 13, 2014 at 01:02:57PM +0200, Tomasz Nowicki wrote:
Currently APEI depends on x86 architecture. It is because of NMI hardware
error notification of GHES which is currently supported by x86 only.
However, many other APEI features can be still used perfectly by other
architectures.
Hi Thierry,
Thanks for your review. Please see my replies inline.
Regards
Ajitpal Singh
On Thursday 19 June 2014 02:14 PM, Lee Jones wrote:
I'll comment on some of the more fluffy topics, I'll let Ajit reply to
the more technical details of the patch.
On Thu, 19 Jun 2014, Thierry Reding
On Fri, Jun 13, 2014 at 03:10:51PM +0200, Robert Richter wrote:
On 13.06.14 13:02:58, Tomasz Nowicki wrote:
@@ -811,6 +819,8 @@ static int ghes_notify_nmi(unsigned int cmd, struct
pt_regs *regs)
int sev, sev_global = -1;
int ret = NMI_DONE;
+
On Thu, 2014-06-19 at 08:10 +0200, Daniel Vetter wrote:
On Thu, Jun 19, 2014 at 3:47 AM, Alex Williamson
alex.william...@redhat.com wrote:
Finding some more specs... the MGGC0 register (50h) seems to indicate
the GTT stolen memory size is 2M, which sounds suspiciously like the 2M
that the
On Thu, 19 Jun 2014, Tejun Heo wrote:
On Thu, Jun 19, 2014 at 12:02:29PM +0200, Rasmus Villemoes wrote:
This change shaves a few bytes off the generated code.
Signed-off-by: Rasmus Villemoes li...@rasmusvillemoes.dk
---
mm/percpu.c | 3 +--
1 file changed, 1 insertion(+), 2
Hi all,
While fuzzing with trinity inside a KVM tools guest running the latest -next
kernel I've stumbled on the following spew. It seems to cause an actual lockup
as hung task messages followed soon after.
[ 690.762537] =
[ 690.764196] [ INFO:
On Thu, 19 Jun 2014, Rafael J. Wysocki wrote:
Well, we used to have the notion that runtime_status is not meaningful for
devices with dev-power.disable_depth greater than 0 (except for the special
case in the suspend code path where we know why it is greater than 0). I
think
it was useful.
On Thursday, June 19, 2014, Rafael J. Wysocki wrote:
On Thursday, June 19, 2014 04:23:29 PM Allen Yu wrote:
On Thursday, June 19, 2014, Rafael J. Wysocki wrote:
On Wednesday, June 18, 2014 11:30:51 AM Alan Stern wrote:
On Tue, 17 Jun 2014, Rafael J. Wysocki wrote:
On Tuesday,
On Thu, Jun 19, 2014 at 09:29:52AM -0500, Christoph Lameter wrote:
- if (unlikely(size 1))
- size++;
+ size += size 1;
I'm not gonna apply this. This isn't that hot a path. It's not
worthwhile to micro optimize code like this.
Dont we have an ALIGN() macro for this?
Hm, that's a bit unexpected. You are on a gen4 device, which means
we'll return the right error in the same function after a few more
register writes. But those are harmless.
On gen5+ we do more (call the pipe_control setup code), which could
potentially clobber the error code. So your patch
On Thu, Jun 19, 2014 at 4:35 PM, Daniel Vetter daniel.vet...@ffwll.ch wrote:
The actual bug we seem to have is blowing up on the ggtt_unpin in
context_fini. Which is doubly-impossible: Gen4 doesn't have hw
contexts, so should have dctx-obj == NULL. And ring init failures
fail earlier so
On 06/19/2014 04:13 PM, Will Deacon wrote:
Hi all,
I'm currently adding VFIO support for kvmtool, so I'm interested in this
patch series (although actually from a PCI perspective).
Eric: can you CC me on future versions of this series please? Once things
start to stabilise, I can help
On Wed, 18 Jun, at 06:48:35PM, Daniel Kiper wrote:
Why don't you want to export efi.fw_vendor, etc? Rationale please.
I am exporting real addresses (machine addresses) of things which
I am able to get. Stuff which was created artificially and lives
in dom0 address space or does not exist
On Thu, Jun 19, 2014 at 4:29 PM, Alex Williamson
alex.william...@redhat.com wrote:
But is there a way for software to discover its location from the
device? If so, then I think we can recreate all the identity maps we'd
need for a guest from the device. If not, then we'd need to figure out
On 06/19, Daniel Vetter wrote:
On Thu, Jun 19, 2014 at 4:35 PM, Daniel Vetter daniel.vet...@ffwll.ch wrote:
The actual bug we seem to have is blowing up on the ggtt_unpin in
context_fini. Which is doubly-impossible: Gen4 doesn't have hw
contexts, so should have dctx-obj == NULL. And ring
On Wed, 18 Jun 2014, Andi Kleen wrote:
I still think it's totally the wrong direction to pollute so
many fast paths with this obscure debugging check workaround
unconditionally.
cond_resched() is in EVERY sleeping lock and in EVERY memory allocation!
And these are really critical paths for
Il 10/06/2014 23:06, Marcelo Tosatti ha scritto:
BTW how about general PMU migration? As far as I can tell there
is no code to save/restore the state for that currently, right?
Paolo wrote support for it, recently. Paolo?
Yes, on the KVM side all that is needed is to special case MSR reads
Adds new macro KERNEL_EXTRAVERSION(a,b,c,d) and value
LINUX_EXTRAVERSION_CODE to version.h, allowing ranged version checks of
extended-stable versions that use a numeric EXTRAVERSION value.
The new KERNEL_EXTRAVERSION(a,b,c,d) works like KERNEL_VERSION(a,b,c)...
If EXTRAVERSION is set to
On Thu, 19 Jun 2014, David Rientjes wrote:
On Thu, 19 Jun 2014, Andrey Ryabinin wrote:
I had to do some modifications in this file for some reasons, and for me it
was hard to not
notice lack of endif in the end.
Ok, cool, I don't think there's any need for a stable backport in that
Il 02/06/2014 21:57, Andi Kleen ha scritto:
It would be a bigger concern if we expected virtual PMU migration to
work, but I think it would be nice to update kvm_pmu_cpuid_update() to
notice the presence/absence of the new CPUID bits, and then store that
into per-VM kvm_pmu-pebs_allowed
This updated patch also fixes out of bound access to b[].
In dib9000_risc_apb_access_write() an out of bound access to mb[].
The current test to avoid out of bound access to mb[] is insufficient.
For len = 19 non-existent mb[10] will be accessed.
For odd values of len b[] is accessed out of
The commit 9da0763bdd82572be243fcf5161734f11568960f
kbuild: Use relative path when building in a subdir of the source tree
When doing make O=subdir, use '..' to refer to the source tree. This
allows for more readable compiler messages, and, more importantly, it
On Thu, Jun 19, 2014 at 9:07 AM, Gregory CLEMENT
gregory.clem...@free-electrons.com wrote:
For the Armada 380 and Armada 385 SoCs, the common bindings for those
2 SoCs, was forgotten. This patch add the documentation for the
marvell,aramda38x property.
Signed-off-by: Gregory CLEMENT
On Thu, 19 Jun 2014, Tejun Heo wrote:
Indeed, a patch?
Subject: percpu: Use ALIGN macro instead of hand coding alignment calculation
Signed-off-by: Christoph Lameter c...@linux.com
Index: linux/mm/percpu.c
===
---
On 06/19/2014 05:52 PM, Boaz Harrosh wrote:
The commit 9da0763bdd82572be243fcf5161734f11568960f
kbuild: Use relative path when building in a subdir of the source tree
When doing make O=subdir, use '..' to refer to the source tree. This
allows for more readable compiler
On Thu, Jun 19, 2014 at 09:59:18AM -0500, Christoph Lameter wrote:
On Thu, 19 Jun 2014, Tejun Heo wrote:
Indeed, a patch?
Subject: percpu: Use ALIGN macro instead of hand coding alignment calculation
Signed-off-by: Christoph Lameter c...@linux.com
Applied to percpu/for-3.17. Thanks.
Please pull bugfixes for 3.16 from
git://linux-nfs.org/~bfields/linux.git for-3.16
Fixes for a new regression from the xdr encoding rewrite, and a
delegation problem we've had for a while (made somewhat more annoying by
the vfs delegation support added in 3.13.)
--b.
From: Anil Belur ask...@gmail.com
- this change fixes the warning WARNING: simple_strtoul is obsolete, use
kstrtoul instead
- removed the unused var 'end' as this is no longer required for
kstrtoul()
Signed-off-by: Anil Belur ask...@gmail.com
---
On Thu, 19 Jun 2014, Allen Yu wrote:
So what's the exact state of device if dev-power.is_suspended flag
is set and runtime_status is RPM_ACTIVE? Is it a state like
suspended but still can be accessed?
I'm just afraid the existing code would cause a device hang if we
allow it to be accessed
On Thu, 19 Jun 2014, Jörg Otte wrote:
on resume with 3.16-rc1 I get the following error messages in dmesg
which are alltogether not present in 3.15:
[ 43.518116] dpm_run_callback(): 0xa53c4120 returns -13
[ 43.518119] PM: Device 1-1 failed to resume async: error -13
[
On Thu, 19 Jun 2014, Sasha Levin wrote:
[ 690.770137] ? __this_cpu_preempt_check (lib/smp_processor_id.c:63)
[ 690.770137] __slab_alloc (mm/slub.c:1732 mm/slub.c:2205 mm/slub.c:2369)
[ 690.770137] ? __lock_acquire (kernel/locking/lockdep.c:3189)
[ 690.770137] ? __debug_object_init
On 06/18, Steven Rostedt wrote:
On Wed, 18 Jun 2014 21:17:37 -0400
Steven Rostedt rost...@goodmis.org wrote:
On Wed, 18 Jun 2014 21:15:59 -0400
Steven Rostedt rost...@goodmis.org wrote:
On Thu, 19 Jun 2014 03:25:46 +0800
kbuild test robot fengguang...@intel.com wrote:
tree:
drivers/gpio/gpio-crystalcove.c: In function 'crystalcove_gpio_dbg_show':
drivers/gpio/gpio-crystalcove.c:286:3: error: implicit declaration of function
'seq_printf'
seq_printf(s, gpio-%-2d %s %s %s %s ctlo=%2x,%s %s %s\n,
Reported-by: Stephen Rothwell s...@canb.auug.org.au
Signed-off-by:
Dear RT Folks,
I'm pleased to announce the 3.12.22-rt34 stable release.
Usually for non stable merged releases I post an -rc iteration. But as
this is a small simple fix, I'm posting this next version directly.
-- Steve
You can get this release via the git tree at:
On Fri, Jun 20, 2014 at 12:03 AM, Lee Jones lee.jo...@linaro.org wrote:
drivers/gpio/gpio-crystalcove.c: In function 'crystalcove_gpio_dbg_show':
drivers/gpio/gpio-crystalcove.c:286:3: error: implicit declaration of
function 'seq_printf'
seq_printf(s, gpio-%-2d %s %s %s %s ctlo=%2x,%s %s
Hi Paul,
On Wed, 18 Jun 2014 14:26:27 -0400 Paul Moore p...@paul-moore.com wrote:
On Wednesday, June 18, 2014 08:40:46 AM Stephen Rothwell wrote:
The selinux tree (git://git.infradead.org/users/pcmoore/selinux#next)
contains some commits going back to January and also has merges of
On 06/19, Steven Rostedt wrote:
On Wed, 18 Jun 2014 21:15:59 -0400
Steven Rostedt rost...@goodmis.org wrote:
On Thu, 19 Jun 2014 03:25:46 +0800
kbuild test robot fengguang...@intel.com wrote:
tree:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
On Mon, Jun 16, 2014 at 10:20:36AM +0200, Robert Baldyga wrote:
This field allows to mark ep as claimed in more clear way. Claiming
endpoint by setting driver_data to non-null value is leaky solution
and makes code unreadable.
how come ? How can it be unreadable ? how can it be leaky ?
--
I'm relatively new to Linux and working on getting a real-time kernel up and
running for robot applications. I'm on Ubuntu 14.04, using kernel 3.14.3 and
the 3.14.3-rt5 real-time patch. Also using x86-64.
There's a known error where the whole system crashes under some load when
lazy preempt is
On Thu, May 22, 2014 at 04:57:31PM +0200, Jean-Jacques Hiblot wrote:
With CONFIG_PREEMPT_RT_FULL the tty_flip_buffer_push(..) actions are executed
immeditely (same behaviour as if low_latency flag was set). We thus have to
release port_lock before callng tty_flip_buffer_push().
This issue
To avoid someone attempting to change this regulator_get back into a
devm_regulator_get put a comment in explaining that devres can't be used
here as the regulator will be destroyed before devres calls
regulator_put.
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
On Fri, 20 Jun 2014, Alexandre Courbot wrote:
On Fri, Jun 20, 2014 at 12:03 AM, Lee Jones lee.jo...@linaro.org wrote:
drivers/gpio/gpio-crystalcove.c: In function 'crystalcove_gpio_dbg_show':
drivers/gpio/gpio-crystalcove.c:286:3: error: implicit declaration of
function 'seq_printf'
Am Donnerstag, 19. Juni 2014, 08:11:21 schrieb tdjames:
I'm relatively new to Linux and working on getting a real-time kernel up and
running for robot applications. I'm on Ubuntu 14.04, using kernel 3.14.3
and the 3.14.3-rt5 real-time patch. Also using x86-64.
I don´t know about lazy preempt,
Asynchronous hash API allows initiate hash calculation and perform
other tasks while hash is calculated.
This patch introduces usage of double buffering for simultenous
hashing and reading of the next chunk of data from the storage.
Signed-off-by: Dmitry Kasatkin d.kasat...@samsung.com
---
Depending on the IMA policy, it might require to measure huge amount of files.
It may be very important to speedup hash calculation or to reduce (bettery)
energy required to do it. Currently IMA uses synchronous hash API (shash)
which is CPU based. CPU based hash calculation is very CPU intensive
Async hash API allows to use HW acceleration for hash calculation.
It may give significant performance gain or/and reduce power consumption,
which might be very beneficial for battery powered devices.
This patch introduces hash calculation using ahash API.
ahash peformance depends on data size
Use of multiple-page collect buffers reduces:
1) the number of block IO requests
2) the number of asynchronous hash update requests
Second is important for HW accelerated hashing, because significant
amount of time is spent for preparation of hash update operation,
which includes configuring
On Thu, Jun 19, 2014 at 03:28:19PM +0200, Bart Van Assche wrote:
Patch bug: Make BUG() always stop the machine changed the
behavior of BUG() with CONFIG_BUG=n from a no-op into an infinite
loop. Modify the definition of BUG_ON() accordingly such that the
behavior of BUG_ON(1) is identical to
On Wed, Jun 18, 2014 at 11:37 PM, Daniel Vetter dan...@ffwll.ch wrote:
On Wed, Jun 18, 2014 at 06:15:56PM -0700, Greg KH wrote:
On Wed, Jun 18, 2014 at 12:37:11PM +0200, Maarten Lankhorst wrote:
Just to show it's easy.
Android syncpoints can be mapped to a timeline. This removes the need
On Thu, 19 Jun 2014 17:03:00 +0200
Oleg Nesterov o...@redhat.com wrote:
On 06/18, Steven Rostedt wrote:
On Wed, 18 Jun 2014 21:17:37 -0400
Steven Rostedt rost...@goodmis.org wrote:
On Wed, 18 Jun 2014 21:15:59 -0400
Steven Rostedt rost...@goodmis.org wrote:
On Thu, 19 Jun
Hi Mimi,
If there is no objections, should we queue this patch for next release?
- Dmitry
On 16/05/14 15:03, Dmitry Kasatkin wrote:
Before IMA appraisal was introduced, IMA was using own integrity cache
lock along with i_mutex. process_measurement and ima_file_free took
the iint-mutex first
Em Thu, Jun 19, 2014 at 09:56:44PM +0900, Namhyung Kim escreveu:
2014-06-19 (목), 13:41 +0200, Jiri Olsa:
Adding report.show-headers config file option to setup
the appearance of the columns headers.
Currently columns headers are displayed by default, following
lines in ~/.perfconfig
On 06/02/2014 12:30 PM, Paul Gortmaker wrote:
On 14-06-02 07:51 AM, Prarit Bhargava wrote:
I have a system on which I have disabled threading in the BIOS, and I am
booting
the kernel with the option idle=poll.
The kernel displays
process: WARNING: polling idle and HT enabled,
On Thu, Jun 19, 2014 at 5:28 AM, Daniel Vetter dan...@ffwll.ch wrote:
On Thu, Jun 19, 2014 at 1:48 PM, Thierry Reding
thierry.red...@gmail.com wrote:
With these changes, can we pull the android sync logic out of
drivers/staging/ now?
Afaik the google guys never really looked at this and
201 - 300 of 1522 matches
Mail list logo
