Same as bpf_program__fd() and bpf_program__nth_fd(), add methods for
fetching the nth ubpf entry.
Signed-off-by: He Kuang
Signed-off-by: Wang Nan
---
tools/lib/bpf/libbpf.c | 14 ++
tools/lib/bpf/libbpf.h | 1 +
2 files changed, 15 insertions(+)
diff --git a/tools/lib/bpf/libbpf.c
Hi,
2016-06-26 20:20 GMT+09:00 Chanwoo Choi :
> Hi,
>
> This patch looks good to me.
> But, there is some comment.
>
> 2016-06-26 14:56 GMT+09:00 Stephen Boyd :
>> Some Qualcomm PMICs have a misc device that performs USB id pin
>> detection via an interrupt. When the interrupt triggers, we
>> shou
Userspace bpf program has the ability to invoke helper functions
provided externally, this patch stores the helper functions in array
and adds methods for set/get functions in it. Theoretically the
function index can be up to UINT32_MAX, here we simply use an array
contains 64 function pointer slot
Different from bpf for kernel which is loaded into kernel and
represented by the fd handle returned, userspace bpf prgrams should be
loaded each time we run it. The field 'insns' is stored in ubpf entry
since the vm execute interface __bpf_prog_run() needs that to run the
bpf prog.
Signed-off-by:
Make sure that ubpf load/store instructions only access the context
and stack region.
Signed-off-by: He Kuang
---
tools/perf/util/bpf-vm.c | 35 +++
tools/perf/util/bpf-vm.h | 3 ++-
2 files changed, 37 insertions(+), 1 deletion(-)
diff --git a/tools/perf/util/b
From: Wang Nan
UBPF are not built by default, unless user explicitly build perf with
UBPF defined.
Signed-off-by: Wang Nan
Signed-off-by: He Kuang
---
tools/lib/bpf/Makefile | 4
tools/perf/Makefile.perf | 2 ++
tools/perf/config/Makefile | 4
3 files changed, 10 insertions(+)
From: Wang Nan
Reigster basic extern functions for uBPF programs.
Signed-off-by: Wang Nan
Cc: Arnaldo Carvalho de Melo
Cc: Alexei Starovoitov
Cc: Brendan Gregg
Cc: Jiri Olsa
Cc: Li Zefan
Signed-off-by: He Kuang
---
tools/perf/perf.c | 3 ++
tools/perf/util/Build
Let ubpf invoke function calls. The function index is stored in
insns->imm, use it to fetch the corresponding functions in libbpf and
make the function call.
Signed-off-by: He Kuang
---
tools/perf/util/bpf-vm.c | 24 ++--
1 file changed, 22 insertions(+), 2 deletions(-)
diff
A boundary check is added before each store/load instruction, since we
don't have a verifier in userspace bpf. There's no functionality
change without UBPF_BUILD flag.
Signed-off-by: He Kuang
---
kernel/bpf/vm.c | 11 +--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/kern
Fill up the run_ubpf_program slot by fetching the ubpf entry and call
__bpf_prog_run().
Signed-off-by: He Kuang
Signed-off-by: Wang Nan
---
tools/perf/util/ubpf-hooks.c | 19 ---
1 file changed, 16 insertions(+), 3 deletions(-)
diff --git a/tools/perf/util/ubpf-hooks.c b/tools/
Supporting different bpf program types loaded into kernel and
userspace, this patch abstracts the operations to related to bpf
program into bpf_engine. The methods set for bpf loaded into kernel
are included in engine-kbpf.c, which is used as the default value.
Signed-off-by: He Kuang
Signed-off-
Add methods to set ubpf engine for a bpf program and to check whether
a program's engine is ubpf.
Signed-off-by: He Kuang
Signed-off-by: Wang Nan
---
tools/lib/bpf/engine-ubpf.c | 12
tools/lib/bpf/libbpf.h | 17 +
2 files changed, 29 insertions(+)
diff --git
Split part of codes in libbpf.c out for internal usage, debug print
functions are changed to non-static for other files to use.
Signed-off-by: He Kuang
---
tools/lib/bpf/libbpf-internal.h | 65 +++
tools/lib/bpf/libbpf.c | 68 +
On Sat, Jun 25, 2016 at 05:45:01AM +0200, meg...@megous.com wrote:
> From: Ondrej Jirman
>
> SY8106A is I2C attached single output voltage regulator
> made by Silergy.
I'm missing almost all of this series, I've just got this and another
patch which look like a standalone driver so it's hard to
Clean up unnecessary assignments to local variable 'result.pfd', and
remove 'pfd' field in 'struct bpf_prog_prep_result' since no one else
uses it.
Signed-off-by: He Kuang
---
tools/lib/bpf/libbpf.c | 4
tools/lib/bpf/libbpf.h | 3 ---
tools/perf/util/bpf-loader.c | 1 -
3 files
From: Wang Nan
This patch copies "include/linux/math64.h" into
"tools/include/linux/math64.h" and copies
"include/asm-generic/div64.h" into
"tools/include/asm-generic/div64.h", to enable other libraries use
arithmetic operation defined in them.
tools/perf/MANIFEST is also updated for 'make perf-
This patchset is based on Wang Nan's v1:
http://thread.gmane.org/gmane.linux.kernel/2203717/focus=2203707
"""
This patch set allows to perf invoke some user space BPF scripts on
some point. uBPF scripts and kernel BPF scripts reside in one BPF
object. They communicate with each other
On Sat, Jun 25, 2016 at 05:45:02AM +0200, meg...@megous.com wrote:
> From: Ondrej Jirman
>
> This patch adds the binding documentation for the
> sy8106a regulator driver.
Please submit patches using subject lines reflecting the style for the
subsystem. This makes it easier for people to identif
From: Wang Nan
Split out function __bpf_prog_run() and related macros from bpf/core.c
into bpf/vm.c.
Signed-off-by: Wang Nan
Signed-off-by: He Kuang
---
include/linux/filter.h | 1 +
kernel/bpf/Makefile| 2 +-
kernel/bpf/core.c | 487 --
From: Wang Nan
The cpu_to_le* macros in kernel.h are defined without considering
endianese. This patch includes "byteoder/generic.h" instead to fix the
bug, and removes redundant definitions of those macros in intel-bts.c
and intel-pt-pkt-decoder.c.
Signed-off-by: Wang Nan
Signed-off-by: He Kua
This patch is a preparation for compiling bpf vm into external
libraries. Parts of the instruction handlers are wrapped into macros
or functions so that userspace libraries can override them. There's no
functionality change without UBPF_BUILD flag.
Signed-off-by: He Kuang
Signed-off-by: Wang Nan
From: Wang Nan
This patch adopts the macros for byte order conversion from
"include/linux/byteorder/generic.h" to
"tools/include/linux/byteorder/generic.h"
tools/perf/MANIFEST is also updated for 'make perf-*-src-pkg'.
Signed-off-by: Wang Nan
Signed-off-by: He Kuang
---
tools/include/linux/b
On Fri, Jun 24, 2016 at 01:00:48PM +1000, Aleksa Sarai wrote:
This allows users to dynamically adjust their limits based on how many
failed forks happened since they last reset their limits, otherwise they
would have to track (in a racy way) how many limit failures there were
since the last limit
On 26 June 2016 at 13:21, Mark Brown wrote:
> On Sun, Jun 26, 2016 at 04:23:41AM +0200, Michal Suchanek wrote:
>> On 26 June 2016 at 03:15, Mark Brown wrote:
>
>> > I can't relate this hunk to the changelog and there's a coding style
>> > problem, if there's { } on one side of an if statement it
On Thu, Jun 23, 2016 at 02:57:35PM +0200, Rafael J. Wysocki wrote:
> On Thu, Jun 23, 2016 at 12:01 PM, Mark Brown wrote:
> > That works too, if I do that I'll make a tag in case it needs to get
> > pulled elsewhere.
> Sounds good, thanks!
The following changes since commit 1a695a905c18548062509
On Sun, Jun 26, 2016 at 01:35:46PM +0200, Michal Suchanek wrote:
> On 26 June 2016 at 13:21, Mark Brown wrote:
> > You can just add the entire slave node in the overlay, it's not clear
> > that this buys us anything useful
> You have to target the master node and specify the CS in the overlay
>
The patch
ASoC: samsung: fix spelling mistake: "unknwon" -> "unknown"
has been applied to the asoc tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours)
The patch
spi: ti-qspi: spelling mistake: "trasnfers" -> "transfers"
has been applied to the spi tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and
The patch
regulator: qcom_spmi: Add support for S4 supply on pm8941
has been applied to the regulator tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24
The patch
ASoC: tpa6130a2: Remove goto err_gpio
has been applied to the asoc tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus dur
The patch
regulator: qcom_spmi: Add support for get_mode/set_mode on switches
has been applied to the regulator tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in t
The patch
ASoC: wm8753: Remove unneeded header file
has been applied to the asoc tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus
The patch
ASoC: tpa6130a2: Add DAPM support
has been applied to the asoc tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
The patch
regulator: qcom_spmi: Update mvs1/mvs2 switches on pm8941
has been applied to the regulator tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24
The patch
SoC: dwc: trivial fix of spelling mistake "unsuppted" -> "unsupported"
has been applied to the asoc tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the nex
On 02.06.2016 15:29, Daniel Wagner wrote:
>> Hmmm, Ok. I've been running the lockperf test and kernel builds all
>> day on a filesystem that is identical in shape and size to yours
>> (i.e. xfs_info output is the same) but I haven't reproduced it yet.
> I don't know if that is important: I run the
Hi Mike,
On Fri, Jun 24, 2016 at 05:28:37PM -0700, Michael Turquette wrote:
> Hi Maxime,
>
> Nice series! Looks really great to me. :-)
Great :)
> Quoting Maxime Ripard (2016-06-07 13:41:53)
> > +static SUNXI_CCU_NKMP_WITH_GATE_LOCK(pll_cpux_clk, "pll-cpux",
> > +
On 26 June 2016 at 13:58, Mark Brown wrote:
> On Sun, Jun 26, 2016 at 01:35:46PM +0200, Michal Suchanek wrote:
>> On 26 June 2016 at 13:21, Mark Brown wrote:
>
>> > You can just add the entire slave node in the overlay, it's not clear
>> > that this buys us anything useful
>
>> You have to target
On Sun, Jun 19, 2016 at 03:09:02PM +0900, Andi Shyti wrote:
> > > This is true, but there are cases where the CS is not connected
> > > and this case needs to be treated separately to allow the device
> > > to work.
> > In what way? It is just as easy for a device with no physical chip
> > selec
On Sun, Jun 26, 2016 at 02:39:20PM +0200, Michal Suchanek wrote:
> On 26 June 2016 at 13:58, Mark Brown wrote:
> > No, there's a lot more to having overlays to board-neutral connectors...
> If you are fine with using only the SPI pins then this is all it takes.
No, there's other things like fig
On 24.06.2016 16:19, George Spelvin wrote:
> Here's a regression you might add.
Thx, added.
> I only reported it to dri-devel,
> since it's DRI-specific, but since there's been thunderous silence
> for a few weeks, I'm trying to be a squeakier wheel.
Added the nouveau developers to CC, maybe i
On 26 June 2016 at 14:45, Mark Brown wrote:
> On Sun, Jun 26, 2016 at 02:39:20PM +0200, Michal Suchanek wrote:
>> On 26 June 2016 at 13:58, Mark Brown wrote:
>
>> > No, there's a lot more to having overlays to board-neutral connectors...
>
>> If you are fine with using only the SPI pins then this
On Sun, Jun 26, 2016 at 02:53:31PM +0200, Michal Suchanek wrote:
> On 26 June 2016 at 14:45, Mark Brown wrote:
> > No, there's other things like figuring out which controller to bind to
> > that need to be taken into consideration.
> Why do you care? So long as you name the CS that is available
Hello. I wanted to unsubscribe from this list, sent a line "subscribe
linux-kernel" to majord...@vger.kernel.org, but it does not reply at
all. what is/may be the problem?
I wanted to switch to more specific lists to track things I am
specifically interested in
On 06/25/2016 05:53 PM, Dmitry Torokhov wrote:
> On Sat, Jun 25, 2016 at 10:34:04AM +0200, Neil Armstrong wrote:
>> On 06/25/2016 12:07 AM, Dmitry Torokhov wrote:
>>> On Fri, Jun 24, 2016 at 11:18:04AM +0200, Neil Armstrong wrote:
In order to support pwrkey for Qualcomm MDM9615 SoC, add suppor
Hi,
It's probably a bug fix that unveils the link errors.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: da2f6aba4a21f8da3331e5251a117c52764da579
commit: c60f169202c7643991a8b4bfeea60e06843d5b5a
arch/mn10300/kernel/fpu-nofpu.c: needs asm/elf.h
date:
Hi,
I think the idea looks good. A couple of comments below though...
On 24/06/16 20:50, Bob Peterson wrote:
This patch adds a new prune_icache_sb function for the VFS slab
shrinker to call. Trying to directly free the inodes from memory
might deadlock because it evicts inodes, which calls into
On 06/25/2016 09:40 PM, Guenter Roeck wrote:
> By concerting the driver to regmap, we can use regmap to cache non-volatile
> registers. Stop caching the temperature register; while potentially reading
> it more often can result in reading it more often than necessary, this is
> offset by the gain d
On 21/06/2016 at 23:32:19 +0200, Alexandre Belloni wrote :
> > RTC: rtctest: Change alarm IRQ support detection
> > RTC: rtctest: Change no IRQ detection for RTC_IRQP_READ
> > RTC: rtctest: Change no IRQ detection for RTC_IRQP_SET
>
> I already had patches for that issue in a development tre
On 06/25/2016 09:40 PM, Guenter Roeck wrote:
[...]
> /* convert left adjusted 13-bit TMP102 register value to milliCelsius */
> @@ -78,8 +82,16 @@ static struct tmp102 *tmp102_update_device(struct device
> *dev)
> struct tmp102 *tmp102 = dev_get_drvdata(dev);
> struct i2c_client *clie
On 06/25/2016 09:40 PM, Guenter Roeck wrote:
> By registering a cleanup function with devm_add_action(), we can
> simplify the error path in the probe function and drop the remove
> function entirely.
>
> Signed-off-by: Guenter Roeck
Acked-by: Nishanth Menon
--
Regards,
Nishanth Menon
On 06/25/2016 09:40 PM, Guenter Roeck wrote:
> The FSF address can change, so drop it from the driver.
>
> Signed-off-by: Guenter Roeck
Acked-by: Nishanth Menon
--
Regards,
Nishanth Menon
From: Markus Elfring
Date: Sun, 26 Jun 2016 15:25:43 +0200
Several update suggestions were taken into account
from static source code analysis.
Markus Elfring (6):
twl-core: Return directly after a failed platform_device_alloc()
in add_numbered_child()
twl-core: Refactoring for add_numbe
On Tue 2016-05-31 06:33:32, David Niklas wrote:
> Hello,
> My laptop will, after a short while, wake right up after issuing the command
> pm-suspend.
> The computer does not need to be connected to the internet.
> I Get no errors and pm-suspend returns 0.
> This tells me that the kernel must have s
From: Markus Elfring
Date: Sun, 26 Jun 2016 12:25:36 +0200
The platform_device_put() function was called in one case by the
add_numbered_child() function during error handling even if the passed
variable "pdev" contained a null pointer.
Return directly in this case.
This issue was detected by us
From: Markus Elfring
Date: Sun, 26 Jun 2016 13:03:59 +0200
Adjust jump targets according to the Linux coding style convention.
Another check for the variable "status" can be omitted then at the end.
Signed-off-by: Markus Elfring
Acked-by: Lee Jones
---
drivers/mfd/twl-core.c | 21 +++-
From: Markus Elfring
Date: Sun, 26 Jun 2016 13:40:35 +0200
The platform_device_put() function was called in one case by the
add_child() function during error handling even if the passed
variable "pdev" contained a null pointer.
Return directly in this case.
This issue was detected by using the C
From: Markus Elfring
Date: Sun, 26 Jun 2016 13:56:58 +0200
Adjust jump targets according to the Linux coding style convention.
Another check for the variable "status" can be omitted then at the end.
Signed-off-by: Markus Elfring
---
drivers/mfd/dm355evm_msp.c | 18 ++
1 file ch
From: Markus Elfring
Date: Sun, 26 Jun 2016 14:14:54 +0200
The variable "ret" will be set to an appropriate value a bit later.
Thus omit the explicit initialisation at the beginning.
Signed-off-by: Markus Elfring
---
drivers/mfd/smsc-ece1099.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion
From: Markus Elfring
Date: Sun, 26 Jun 2016 14:30:46 +0200
This issue was detected by using the Coccinelle software.
Return directly if a call of the function "devm_regmap_init_i2c"
or "regmap_write" failed.
Delete the jump label "err" then.
Signed-off-by: Markus Elfring
---
drivers/mfd/smsc
On 24/06/16 12:16, Bijosh Thykkoottathil wrote:
> Added macros for sensing range as the corresponding magic numbers
> were used at multiple places.
>- SENSING_RANGE_0 for 375 lux full range
>- SENSING_RANGE_1 for 10k lux full range
>
> Signed-off-by: Bijosh Thykkoottathil
Hi Bijosh,
Macr
On 06/26/2016 06:31 AM, Nishanth Menon wrote:
On 06/25/2016 09:40 PM, Guenter Roeck wrote:
[...]
/* convert left adjusted 13-bit TMP102 register value to milliCelsius */
@@ -78,8 +82,16 @@ static struct tmp102 *tmp102_update_device(struct device
*dev)
struct tmp102 *tmp102 = dev_get_d
Hi! Here is my third regression report for Linux 4.7. It has
24 entries; 9 of them are new; 4 regressions (not included here)
were fixed since the last report(¹).
Please let me know if a regression is missing in the list; or if
there is something on the list which shouldn't be there.
HTH, CU, T
On Sun, Jun 26, 2016 at 02:58:00PM +0800, panxinhui wrote:
[snip]
> >>
> >
> > Unfortunately, on PPC, we compile pseries code along with powernv code
> > in a kernel binary, therefore we need to wire the proper primitives at
> > runtime.
> >
> no, we can use same vcpu preempted check ops actuall
Hi Nishanth,
On 06/26/2016 06:27 AM, Nishanth Menon wrote:
Note, at this point:
We have set CR0=0, CR1=1 (4HZ conversion rate). we do indeed have a
26typical (worst case 35ms) conversion time, but if we read register
before 250 ms, we are not getting a new data, instead, we are just
reading the
On Sun, Jun 26, 2016 at 03:08:20PM +0800, panxinhui wrote:
[snip]
> > @@ -106,6 +109,9 @@ bool osq_lock(struct optimistic_spin_queue *lock)
> > node->prev = prev;
> > WRITE_ONCE(prev->next, node);
> >
> > + old = old - 1;
> > + vpc = vcpu_preempt_count();
> > +
> > /*
> > * No
On Sat, Jun 25, 2016 at 11:00:36PM +0100, Luis de Bethencourt wrote:
> When sending an email regarding a patch to wilc1000, you get the following
> automatic replies:
> "Sung_hoon Cho is no longer with Atmel Corporation."
> "Kang_hee Park is no longer with Atmel Corporation."
> "Dong_ho Shin is no
On Sat, Jun 25, 2016 at 02:37:39PM -0700, Deepa Dinamani wrote:
> CURRENT_TIME macro is not appropriate for filesystems as it
> doesn't use the right granularity for filesystem timestamps.
> Use current_time() instead.
>
> This is also in preparation for the patch that transitions
> vfs timestamps
On Sat, Jun 25, 2016 at 10:43:33PM +0100, Luis de Bethencourt wrote:
> On 25/06/16 22:36, Greg KH wrote:
> > On Thu, Jun 23, 2016 at 01:36:17PM +0100, Luis de Bethencourt wrote:
> >> The common format to check if a function returned an error pointer is to
> >> use PTR_ERR(). Instead of ERR_PTR() wh
On Sat, Jun 25, 2016 at 06:45:20PM -0300, Pedro Nieto wrote:
> Hello this was my first attempt of a patch and as you can see i have made a
> few
> mistakes. About the name PedroNieto is my github's account user, i am not sure
> if that is the name that i should use, or just an alias is fine.
We n
On 23/06/16 09:50, Florian Vaussard wrote:
> Hello Peter,
>
> On 06/22/2016 09:06 AM, Peter Rosin wrote:
>> On 2016-06-22 08:22, Florian Vaussard wrote:
>>> Hello Peter,
>>>
>>> Le 21. 06. 16 à 09:51, Peter Rosin a écrit :
That is, if you need this patch at all, see my reply to 2/3...
>>
On 21/06/16 07:55, Florian Vaussard wrote:
> Hello,
>
> This series first adds support for parts missing from mcp4531 driver
> (MCP454x, MCP456x, MCP464x and MCP466x). It then introduces the necessary
> device tree binding to perform DT boot.
>
> Tested with MCP4561-103 and MCP4561-503 (DT boot).
On Sun, Jun 26, 2016 at 8:30 AM, Alexandre Belloni
wrote:
> Hi,
>
> A few comments, mostly about style.
>
> On 20/06/2016 at 10:52:14 +0800, Chen-Yu Tsai wrote :
>> +struct ac100_rtc_dev {
>> + struct rtc_device *rtc;
>> + struct device *dev;
>> + struct regmap *regmap;
>> + struct
On 22/06/16 20:43, Luis de Bethencourt wrote:
> sca3000_read_ctrl_reg() returns a negative number on failure, check for
> this instead of zero.
>
> Signed-off-by: Luis de Bethencourt
> Reviewed-by: Andrew F. Davis
> Reviewed-by: Jonathan Cameron
Note that, like any tag, reviewed-by tags must b
On Sun, Jun 26, 2016 at 8:45 AM, Alexandre Belloni
wrote:
> On 20/06/2016 at 10:52:15 +0800, Chen-Yu Tsai wrote :
>> +struct ac100_clk32k {
>> + struct clk_hw hw;
>> + struct regmap *regmap;
>> + u8 offset;
>> +};
>> +
>> +#define to_ac100_clk32k(_hw) container_of(_hw, struct ac100_clk
On 22/06/16 20:43, Luis de Bethencourt wrote:
> Go to error_ret if sca3000_read_ctrl_reg() failed.
>
> Signed-off-by: Luis de Bethencourt
Applied to the togreg branch of iio.git - will be initially
pushed out as testing for the autobuilders to play with it.
Thanks,
Jonathan
> ---
> drivers/sta
On 26.6.2016 13:26, Mark Brown wrote:
> On Sat, Jun 25, 2016 at 05:45:01AM +0200, meg...@megous.com wrote:
>> From: Ondrej Jirman
>>
>> SY8106A is I2C attached single output voltage regulator
>> made by Silergy.
>
> I'm missing almost all of this series, I've just got this and another
> patch whi
On 26.6.2016 13:27, Mark Brown wrote:
> On Sat, Jun 25, 2016 at 05:45:02AM +0200, meg...@megous.com wrote:
>> From: Ondrej Jirman
>>
>> This patch adds the binding documentation for the
>> sy8106a regulator driver.
>
> Please submit patches using subject lines reflecting the style for the
> subsy
> 在 2016年6月26日，22:29，Boqun Feng 写道：
>
> On Sun, Jun 26, 2016 at 03:08:20PM +0800, panxinhui wrote:
> [snip]
>>> @@ -106,6 +109,9 @@ bool osq_lock(struct optimistic_spin_queue *lock)
>>> node->prev = prev;
>>> WRITE_ONCE(prev->next, node);
>>>
>>> + old = old - 1;
>>> + vpc = vcpu_pr
On 06/26/2016 02:16 PM, Thorsten Leemhuis wrote:
> On 02.06.2016 15:29, Daniel Wagner wrote:
>>> Hmmm, Ok. I've been running the lockperf test and kernel builds all
>>> day on a filesystem that is identical in shape and size to yours
>>> (i.e. xfs_info output is the same) but I haven't reproduced i
On Sat, Jun 25, 2016 at 06:15:15PM -0700, Stefan Agner wrote:
> Use the PMIC's repower capability for reboots. Register a restart
> handler and use a slightly elevated priority of 192 since the PMIC
> has suprior reset capability (causing a system wide reset).
>
> Signed-off-by: Stefan Agner
> Re
On 21/06/16 15:37, Crestez Dan Leonard wrote:
> On 06/19/2016 02:57 PM, Jonathan Cameron wrote:
>> On 17/06/16 12:10, Crestez Dan Leonard wrote:
>>> From: Peter Meerwald
>>>
>>> The si114x supports x=1,2,3 IR LEDs for proximity sensing together with
>>> visible and IR ambient light sensing (ALS).
On 26 June 2016 at 14:57, Mark Brown wrote:
> On Sun, Jun 26, 2016 at 02:53:31PM +0200, Michal Suchanek wrote:
>> On 26 June 2016 at 14:45, Mark Brown wrote:
>
>> > No, there's other things like figuring out which controller to bind to
>> > that need to be taken into consideration.
>
>> Why do yo
Am Sonntag, den 26.06.2016, 14:52 +0200 schrieb Thorsten Leemhuis:
> On 24.06.2016 16:19, George Spelvin wrote:
> >
> > Here's a regression you might add.
> Thx, added.
>
Probably the same bug as
https://bugzilla.kernel.org/show_bug.cgi?id=119861 and already fixed in
the last -rc.
Regards,
Lu
> 在 2016年6月26日，22:11，Boqun Feng 写道：
>
> On Sun, Jun 26, 2016 at 02:58:00PM +0800, panxinhui wrote:
> [snip]
>>>
>>> Unfortunately, on PPC, we compile pseries code along with powernv code
>>> in a kernel binary, therefore we need to wire the proper primitives at
>>> runtime.
>>>
>> no, we
Hi,
I've just spend most of my Sunday debugging a problem
where Allwinner ARM SoC based boards will not shutdown when
using a Fedora 24 userland, where as the exact same
kernel works fine with Fedora 22.
It turns out that irq-balanced is to blame. In Fedora 24
it pins the i2c controller, which t
On 12/06/16 07:55, Matt Ranostay wrote:
>
> Also important to note these warnings are environment related (e.g. room with
> lot of EMI noise) and unlikely a chip misconfiguration. Unless the tuning
> capacitor setting is wrong of course
Applied to the togreg branch of iio.git. Initially pushed o
On 14/06/16 07:53, Linus Walleij wrote:
> On Mon, Jun 13, 2016 at 3:06 PM, William Breathitt Gray
> wrote:
>
>> The Apex Embedded Systems STX104 device features eight lines of digital
>> I/O (four digital inputs and four digital outputs). This patch adds GPIO
>> support for these eight lines of d
Hi Stephen,
On Mon, Jun 20, 2016 at 06:48:16PM -0700, Stephen Boyd wrote:
> On 06/07, Maxime Ripard wrote:
> >
> > The current code has been tested on the H3 and an Orange Pi PC,
> > including making sure that MMC still works, so the general approach
> > seems ok.
> >
> > Let me know what you th
On Mon, Jun 20, 2016 at 6:46 PM, Leo Yan wrote:
> Hi Amit,
>
> On Mon, Jun 20, 2016 at 05:46:36PM +0530, Amit Kucheria wrote:
>> The Hisilicon clock stub driver is needed to allow the thermal drivers to
>> actually scale the frequency. Make it an automatic dependency.
>>
>> Signed-off-by: Amit Kuc
On 20/06/16 00:28, Azael Avalos wrote:
> This patch adds the accelerometer axis data to the IIO subsystem.
>
> Currently reporting the X, Y and Z values, as no other data can be
> queried given the fact that the accelerometer chip itself is hidden
> behind the Toshiba proprietary interface.
>
> S
Hello Krzysztof,
just wanted to ask on which kernel branch the patchset is based on. At
least for me the set doesn't apply cleanly to 4.7-rc4.
With best wishes,
Tobias
Krzysztof Kozlowski wrote:
> Hi,
>
>
> Some time ago, Robert tried to add VBUS detection to extcon-usb-gpio
> driver [1]. Th
On Sun, Jun 26, 2016 at 02:45:44AM +0200, Rafael J. Wysocki wrote:
> The (hopefully) final one is https://patchwork.kernel.org/patch/9189139/
> and it still is pending a test on the Boris' machine where the previous one
> didn't work. If that doesn't pass, we'll need to defer it until we know
> th
On Fri, Jun 24, 2016 at 8:35 AM, Josh Poimboeuf wrote:
> On Thu, Jun 23, 2016 at 09:23:08PM -0700, Andy Lutomirski wrote:
>> If we overflow the stack, print_context_stack will abort. Detect
>> this case and rewind back into the valid part of the stack so that
>> we can trace it.
>>
>> Signed-off-
On 21/06/16 12:44, kbuild test robot wrote:
> Hi,
>
Hi Florian,
Usual way around this is to make the devicetree pointers true pointers by
providing the address of the array member instead of it's index.
Only requires a slight rework of what you have.
Jonathan
> [auto build test WARNING on iio/t
On 21/06/16 08:09, Florian Vaussard wrote:
> The driver supports MAX11644, MAX11645, MAX11646 and MAX11647 parts. But
> the corresponding i2c_device_id are missing. Add them!
>
> Signed-off-by: Florian Vaussard
Applied. oops.
Thanks ;)
Jonathan
> ---
> drivers/iio/adc/max1363.c | 4
> 1
On 22/06/16 07:18, Florian Vaussard wrote:
> Hi Rob,
>
> Le 21. 06. 16 à 23:49, Rob Herring a écrit :
>> On Tue, Jun 21, 2016 at 09:09:28AM +0200, Florian Vaussard wrote:
>>> Add the device tree documentation for all the supported parts. Mandatory
>>> binding is the compatible string and the slave
Em Sat, Jun 25, 2016 at 09:29:04AM +0800, Wangnan (F) escreveu:
> You can add:
>
> Fixes: 41840d211c51 ("perf config: Move config declarations from
> util/cache.h to util/config.h")
Yeah, I'll do that, thanks for pointing it out!
- Arnaldo
> Thank you.
>
> On 2016/6/24 20:40, Jiri Olsa wrote:
On Sun, Jun 26, 2016 at 2:50 AM, Thorsten Leemhuis
wrote:
>
> Al, what's the status here? This made it on my 4.7 regressions report
> due to the "regression" keyword in the subject.
I don't think the tmpfs locking is going to get changed for 4.7. This
issue will likely only show up for some very
On Sun, Jun 26, 2016 at 2:24 AM, Vegard Nossum wrote:
>
> This is the best I could come up with: assuming gcc is not allowed to
> reason about what's inside the asm(), this is the only way I could
> think of to lose the array information without incurring unnecessary
> overheads. It should also be
101 - 200 of 424 matches
Mail list logo
