Re: [PATCH 3/3] KVM: x86: correct mwait and monitor emulation

On Thu, Jun 19, 2014 at 02:52:20PM +0300, Nadav Amit wrote: > On 6/19/14, 2:23 PM, Gleb Natapov wrote: > >On Thu, Jun 19, 2014 at 01:53:36PM +0300, Nadav Amit wrote: > >> > >>On Jun 19, 2014, at 1:18 PM, Michael S. Tsirkin wrote: > >> > >>>On Wed, Jun 18, 2014 at 02:46:01PM -0400, Gabriel L.

Re: kbuild: support of new KBUILD_FULL_PATH

On 06/19/2014 01:41 PM, Michal Marek wrote: <> >> Is there a document I need to edit for this new parameter? > > That would be Documentation/kbuild/kbuild.txt > Will send a VER2 thanks > >> Signed-off-by: Boaz Harrosh >> --- >> Makefile | 8 +++- >> 1 file changed, 7 insertions(+), 1

Re: [PATCH 1/2] selinux: simple cleanup for cond_read_node()

On 06/18/2014 03:36 PM, Paul Moore wrote: > On Sunday, June 15, 2014 01:19:01 AM Namhyung Kim wrote: >> The node->cur_state and len can be read in a single call of next_entry(). >> And setting len before reading is a dead write so can be eliminated. >> >> Signed-off-by: Namhyung Kim >> --- >>

Re: [PATCH net-next v5 1/3] ieee802154: cc2520: adds driver for TI CC2520 radio

Hi Alex, Thanks for the comments On 06/19/2014 04:14 PM, Alexander Aring wrote: Hi Varka, why do you add new features while you trying to get the first version mainline? This h/w address filtering feature is required for me to get CC2520 Hardware ACK, which enable TinyOS nodes to

Re: [PATCH 1/5] perf trace: add support for pagefault tracing

> So make it default to the most common case :-) Ok, agreed, will make --pf=all|maj|min and will default it to maj. > That is my expectation, yes, if I ask for the map where address N is, it > should return just that, where have you found this bug? > > The thread__find_addr_map will end up

Re: [PATCH 3/3] KVM: x86: correct mwait and monitor emulation

On Thu, Jun 19, 2014 at 02:52:20PM +0300, Nadav Amit wrote: > On 6/19/14, 2:23 PM, Gleb Natapov wrote: > >On Thu, Jun 19, 2014 at 01:53:36PM +0300, Nadav Amit wrote: > >> > >>On Jun 19, 2014, at 1:18 PM, Michael S. Tsirkin wrote: > >> > >>>On Wed, Jun 18, 2014 at 02:46:01PM -0400, Gabriel L.

Re: [PATCH 3/3] KVM: x86: correct mwait and monitor emulation

On 6/19/14, 3:07 PM, Gleb Natapov wrote: On Thu, Jun 19, 2014 at 02:52:20PM +0300, Nadav Amit wrote: On 6/19/14, 2:23 PM, Gleb Natapov wrote: On Thu, Jun 19, 2014 at 01:53:36PM +0300, Nadav Amit wrote: On Jun 19, 2014, at 1:18 PM, Michael S. Tsirkin wrote: On Wed, Jun 18, 2014 at

Re: [PATCHv7 2/5] mailbox: Introduce framework for mailbox

Hello, On 18 June 2014 22:55, Jassi Brar wrote: >> >> I sure would like to see some more Reviewed-by tags from those folks to >> confirm that those starting to use it think it's on the right track. >> > The upstreaming attempts have been going on for months now, and via > non-public interactions

Re: [PATCH 3/3] KVM: x86: correct mwait and monitor emulation

On Thu, Jun 19, 2014 at 03:10:21PM +0300, Nadav Amit wrote: > On 6/19/14, 3:07 PM, Gleb Natapov wrote: > >On Thu, Jun 19, 2014 at 02:52:20PM +0300, Nadav Amit wrote: > >>On 6/19/14, 2:23 PM, Gleb Natapov wrote: > >>>On Thu, Jun 19, 2014 at 01:53:36PM +0300, Nadav Amit wrote: > > On Jun

Re: [PATCH 3/3] KVM: x86: correct mwait and monitor emulation

On Thu, Jun 19, 2014 at 03:10:21PM +0300, Nadav Amit wrote: > On 6/19/14, 3:07 PM, Gleb Natapov wrote: > >On Thu, Jun 19, 2014 at 02:52:20PM +0300, Nadav Amit wrote: > >>On 6/19/14, 2:23 PM, Gleb Natapov wrote: > >>>On Thu, Jun 19, 2014 at 01:53:36PM +0300, Nadav Amit wrote: > > On Jun

Re: [PATCH 1/3] perf timechart: implement IO mode

> > Hmm.. it looks like an unrelated issue. I can see the bars in inkscape, > > but still see empty grey bars in firefox. > I'll try to have a look; maybe I'm writing some non-standard svg > instructions which fail on (probably) standard-compliant firefox and > work on more robust inkscape.

Re: Should Pstore(ramoops) records customized information?

On 2014/6/19 1:50, Luck, Tony wrote: Hi Tony, Thanks for you reply. >> (1) The backend (ramoops) provides servel memory regions staticly. Each >> region >> is a ring buffer, which does not connect with certain PSTORE_TYPE_ID. So no >> one >> can modify or use it before allocation. >> >> (2)

[PATCH] efi: fix build warning about of_get_flat_dt_prop

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 --- drivers/firmware/efi/efi.c |5 ++--- drivers/firmware/efi/fdt.c |2

[PATCH 3/3] perf timechart: add more options to IO mode

--io-skip-eagain - don't show EAGAIN errors --io-min-time- make small io bursts visible --io-merge-dist - merge adjacent events Signed-off-by: Stanislav Fomichev --- tools/perf/Documentation/perf-timechart.txt | 13 + tools/perf/builtin-timechart.c | 75

[PATCH v3 0/3] perf timechart io mode

This patchset adds IO mode: instead of process time we record io syscalls and then draw timechart of writes/reads/tx/rx/polls. v3: - fixed segfault when skipping invalid tracepoints - added ms/us units support for --io-xyz time options - fixed missing boxes on Firefox v2: - separated

[PATCH 2/3] perf timechart: conditionally update start_time on fork

We don't need to overwrite current task start_time on fork, so update it only if it's zero. Signed-off-by: Stanislav Fomichev --- tools/perf/builtin-timechart.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/perf/builtin-timechart.c b/tools/perf/builtin-timechart.c

[PATCH 1/3] perf timechart: implement IO mode

In IO mode timechart shows any disk/network activity. Signed-off-by: Stanislav Fomichev --- tools/perf/Documentation/perf-timechart.txt | 25 +- tools/perf/builtin-timechart.c | 613 +++- tools/perf/util/svghelper.c | 98 -

Re: [REPOST PATCH 4/8] android: convert sync to fence api, v5

On Thu, Jun 19, 2014 at 1:48 PM, Thierry Reding 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 acked it. So I'm not >> sure whether they'll follow along. The other issue I have as the

Re: [PATCH 3/3] KVM: x86: correct mwait and monitor emulation

On 6/19/14, 3:17 PM, Michael S. Tsirkin wrote: On Thu, Jun 19, 2014 at 03:10:21PM +0300, Nadav Amit wrote: On 6/19/14, 3:07 PM, Gleb Natapov wrote: On Thu, Jun 19, 2014 at 02:52:20PM +0300, Nadav Amit wrote: On 6/19/14, 2:23 PM, Gleb Natapov wrote: On Thu, Jun 19, 2014 at 01:53:36PM +0300,

Re: [PATCH net-next v5 1/3] ieee802154: cc2520: adds driver for TI CC2520 radio

On Thu, Jun 19, 2014 at 05:34:30PM +0530, Varka Bhadram wrote: > Hi Alex, > > Thanks for the comments > > On 06/19/2014 04:14 PM, Alexander Aring wrote: > >Hi Varka, > > > >why do you add new features while you trying to get the first version > >mainline? > Yes, address filtering is needed for

[PATCH] drivers/sbus/char: Micro-optimization in display7seg.c

Flipping a bit doesn't need four lines of code; and gcc seems to actually generate two branches. Signed-off-by: Rasmus Villemoes --- drivers/sbus/char/display7seg.c | 5 + 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/drivers/sbus/char/display7seg.c

[Question] is it a race condition in acking PMIC sub-interrupt?

Hi, Mark: Sorry to trouble you, I met a question related the interrupt ack sequence in regmap framework; could you please share your advice on this? thank you very much; 1) the following is the connection related to PMIC on my development board: PMIC ---> GPIO --> GIC the GPIO is

Re: [PATCH -tip v2 3/3] kprobes: Set IPMODIFY flag only if the probe can change regs->ip

Hi Masami, 2014-06-17 (화), 11:04 +, Masami Hiramatsu: > +static int __ftrace_add_filter_ip(struct ftrace_ops *ops, unsigned long ip, > + int *ref) > +{ > + int ret; > + > + /* Try to set given ip to filter */ > + ret = ftrace_set_filter_ip(ops, ip, 0,

Re: [PATCHv7 2/5] mailbox: Introduce framework for mailbox

Hi Jassi, On 19/06/14 03:55, Jassi Brar wrote: On 18 June 2014 22:33, Kevin Hilman wrote: [...] That's great. I sure would like to see some more Reviewed-by tags from those folks to confirm that those starting to use it think it's on the right track. The upstreaming attempts have been

new mailing list for union/overlay filesystems?

Hi Dave, There's interest in having a mailing list specifically for "union filesystem" like solutions (currently active projects are aufs, union-mounts and overlayfs). Would it be possible to create one on vger for this purpose? Thanks, Miklos -- To unsubscribe from this list: send the line

[tip:sched/core] sched: Fix CACHE_HOT_BUDY condition

Commit-ID: 5d5e2b1bcbdc996e72815c03fdc5ea82c4642397 Gitweb: http://git.kernel.org/tip/5d5e2b1bcbdc996e72815c03fdc5ea82c4642397 Author: Hillf Danton AuthorDate: Tue, 10 Jun 2014 10:58:43 +0200 Committer: Ingo Molnar CommitDate: Wed, 18 Jun 2014 18:29:59 +0200 sched: Fix CACHE_HOT_BUDY

[tip:sched/core] sched/numa: Always try to migrate to preferred node at task_numa_placement() time

Commit-ID: bb97fc31647539f1f102eed646a95e200160a150 Gitweb: http://git.kernel.org/tip/bb97fc31647539f1f102eed646a95e200160a150 Author: Rik van Riel AuthorDate: Wed, 4 Jun 2014 16:33:15 -0400 Committer: Ingo Molnar CommitDate: Wed, 18 Jun 2014 18:29:58 +0200 sched/numa: Always try to

[tip:sched/core] sched/numa: Ensure task_numa_migrate() checks the preferred node

Commit-ID: a43455a1d572daf7b730fe12eb747d1e17411365 Gitweb: http://git.kernel.org/tip/a43455a1d572daf7b730fe12eb747d1e17411365 Author: Rik van Riel AuthorDate: Wed, 4 Jun 2014 16:09:42 -0400 Committer: Ingo Molnar CommitDate: Wed, 18 Jun 2014 18:29:57 +0200 sched/numa: Ensure

[tip:locking/core] lockdep: Revert lockdep check in raw_seqcount_begin()

Commit-ID: 22fdcf02f6e80d64a927f702dd9d631a927d87d4 Gitweb: http://git.kernel.org/tip/22fdcf02f6e80d64a927f702dd9d631a927d87d4 Author: Trond Myklebust AuthorDate: Thu, 5 Jun 2014 11:31:01 -0400 Committer: Ingo Molnar CommitDate: Wed, 18 Jun 2014 18:41:23 +0200 lockdep: Revert lockdep

[tip:locking/core] x86, locking: Use no more OOSTORE nonsense

Commit-ID: 4f3aaf2c2ba35bc2cd823a240f9969ebfb3c7549 Gitweb: http://git.kernel.org/tip/4f3aaf2c2ba35bc2cd823a240f9969ebfb3c7549 Author: Peter Zijlstra AuthorDate: Wed, 11 Jun 2014 11:01:45 +0200 Committer: Ingo Molnar CommitDate: Wed, 18 Jun 2014 18:41:22 +0200 x86, locking: Use no

[tip:perf/core] blackfin, perf: Use common PMU interrupt disabled code

Commit-ID: 6e316f9c19a088586fd9ae058f9ea35b271571f3 Gitweb: http://git.kernel.org/tip/6e316f9c19a088586fd9ae058f9ea35b271571f3 Author: Vince Weaver AuthorDate: Sun, 15 Jun 2014 02:01:58 -0400 Committer: Ingo Molnar CommitDate: Wed, 18 Jun 2014 18:43:45 +0200 blackfin, perf: Use common

[tip:perf/core] arc, perf: Use common PMU interrupt disabled code

Commit-ID: 2cc9e588b0ff80c209c59a3e369c73e591535ba8 Gitweb: http://git.kernel.org/tip/2cc9e588b0ff80c209c59a3e369c73e591535ba8 Author: Vince Weaver AuthorDate: Sun, 15 Jun 2014 02:00:18 -0400 Committer: Ingo Molnar CommitDate: Wed, 18 Jun 2014 18:43:44 +0200 arc, perf: Use common PMU

[tip:perf/core] metag, perf: Use common PMU interrupt disabled code

Commit-ID: 1b92722fafe2003e49ec904f33c0020ade36bd16 Gitweb: http://git.kernel.org/tip/1b92722fafe2003e49ec904f33c0020ade36bd16 Author: Vince Weaver AuthorDate: Sun, 15 Jun 2014 02:03:13 -0400 Committer: Ingo Molnar CommitDate: Wed, 18 Jun 2014 18:43:45 +0200 metag, perf: Use common

[tip:perf/core] powerpc, perf: Use common PMU interrupt disabled code

Commit-ID: 703daddffe550121e607c8294176ad2b12661147 Gitweb: http://git.kernel.org/tip/703daddffe550121e607c8294176ad2b12661147 Author: Vince Weaver AuthorDate: Sun, 15 Jun 2014 02:04:25 -0400 Committer: Ingo Molnar CommitDate: Wed, 18 Jun 2014 18:43:46 +0200 powerpc, perf: Use common

[tip:perf/core] sh, perf: Use common PMU interrupt disabled code

Commit-ID: ba553c9e167971c21b0158d89737bc385c326447 Gitweb: http://git.kernel.org/tip/ba553c9e167971c21b0158d89737bc385c326447 Author: Vince Weaver AuthorDate: Sun, 15 Jun 2014 02:06:15 -0400 Committer: Ingo Molnar CommitDate: Wed, 18 Jun 2014 18:43:47 +0200 sh, perf: Use common PMU

Re: [PATCH 1/3] perf timechart: implement IO mode

Hi Stanislav, 2014-06-19 (목), 16:18 +0400, Stanislav Fomichev: > > > Hmm.. it looks like an unrelated issue. I can see the bars in inkscape, > > > but still see empty grey bars in firefox. > > I'll try to have a look; maybe I'm writing some non-standard svg > > instructions which fail on

[tip:perf/core] s390, perf: Use common PMU interrupt disabled code

Commit-ID: d7302ac28ba24eeac512c8f45107c962c701eb38 Gitweb: http://git.kernel.org/tip/d7302ac28ba24eeac512c8f45107c962c701eb38 Author: Vince Weaver AuthorDate: Sun, 15 Jun 2014 02:05:23 -0400 Committer: Ingo Molnar CommitDate: Wed, 18 Jun 2014 18:43:47 +0200 s390, perf: Use common PMU

Re: [PATCH] drivers/i915: Fix unnoticed failure of init_ring_common()

On 06/19, Daniel Vetter wrote: > On Thu, Jun 19, 2014 at 12:38 AM, Konrad Zapalowicz > wrote: > > This commit add check for return value of init_ring_common() in the > > init_render_ring(). Now, when failure is detected the error code is > > propagated to the caller layer instead of being

Re: [PATCH v2 0/5] Add glob pattern matching support on trigger and kprobe-event

On Thu, 19 Jun 2014 15:36:53 +0900 Masami Hiramatsu wrote: > These are separated enhancement. Feel free to apply the 1st bugfix patch. That first bugfix patch is already in mainline. > I'll update the series :) Thanks! -- Steve -- To unsubscribe from this list: send the line "unsubscribe

Re: [PATCH v2 06/18] ARM: dts: DRA7: Add divider table to optfclk_pciephy_div clock

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 >> >> Add divider table to optfclk_pciephy_div clock. The Documentation >> for divider clock can be found at ../clock/ti/divider.txt > > This patch requires a

URGENT.......

Bonjour. I am Michael B. Curtis from France. I have been advised to contact you regarding business investment in your country. I will love to discuss this investment proposition with you. For more details please reply me via this email: michaelcurtis...@qq.com Michael Curtis +33-753-194-496

[GIT PULL] sound fixes for 3.16-rc2

Linus, please pull sound fixes for v3.16-rc2 from: git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git tags/sound-3.16-rc2 The topmost commit is 8d42fda9ea9820d271a40f0bf7ed436647f2ddb9 sound fixes for 3.16-rc2 The

Re: [PATCH 12/24] ARM64: Add is_ilp32_compat_task and is_ilp32_compat_thread and TIF_32BIT_AARCH64.

On Sat, May 24, 2014 at 12:02:07AM -0700, Andrew Pinski wrote: > diff --git a/arch/arm64/include/asm/compat.h b/arch/arm64/include/asm/compat.h > index fad7612..85f945c 100644 > --- a/arch/arm64/include/asm/compat.h > +++ b/arch/arm64/include/asm/compat.h > @@ -313,6 +313,26 @@ static inline int

Re: [PATCH 13/24] Drivers:input: Use is_compat_task for ARM64 also.

On Sat, May 24, 2014 at 12:02:08AM -0700, Andrew Pinski wrote: > diff --git a/drivers/input/input-compat.h b/drivers/input/input-compat.h > index 148f66f..6656957 100644 > --- a/drivers/input/input-compat.h > +++ b/drivers/input/input-compat.h > @@ -19,7 +19,7 @@ > > /* Note to the author of

Re: [PATCH 14/24] ARM64:ILP32: COMPAT_USE_64BIT_TIME is true for ILP32 tasks.

On Sat, May 24, 2014 at 12:02:09AM -0700, Andrew Pinski wrote: > Since __kernel_long_t (time_t) is long long, we need to tell the rest > of kernel that we use 64bit time_t for compat when the task is not an > AARCH32 task. The reason why we check AARCH32 rather than ILP32 here > is because if we

Re: [PATCH 15/24] ARM64:ILP32: Use the non compat HWCAP for ILP32.

On Sat, May 24, 2014 at 12:02:10AM -0700, Andrew Pinski wrote: > Signed-off-by: Andrew Pinski Please add some commit log, even if minimal. > --- > arch/arm64/include/asm/hwcap.h | 12 ++-- > 1 files changed, 10 insertions(+), 2 deletions(-) > > diff --git

Re: [PATCH 5/5] perf tools: Add report.show-headers config file option

Hi Jiri, 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 file will disable that: > > [report] >

Re: [PATCH v2 07/18] ARM: dts: DRA7: Change the parent of apll_pcie_in_clk_mux to dpll_pcie_ref_m2ldo_ck

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 >> >> Change the parent of apll_pcie_in_clk_mux to dpll_pcie_ref_m2ldo_ck >> from dpll_pcie_ref_ck. > > Why? Needs a better changelog also. Figure 26-22.

Re: [PATCH 5/5] perf tools: Add report.show-headers config file option

On Thu, Jun 19, 2014 at 09:56:44PM +0900, Namhyung Kim wrote: > Hi Jiri, > > 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 > >

[RFC 2/2] mmc: core: Add support for power sequences

The MMC subsystem uses a discoverable bus which sometimes means the power sequences to enable power to the card, is far too complex to be handled through the regular ->set_ios() callback. To adress these scenarios, we try to fetch a pwrseq method while parsing the common MMC DT bindings. If a

[RFC 0/2] pwrseq: Add subsystem for power sequences

Some background: Subsystems using discoverable buses, sometimes requires to handle a complex power sequence, to be able to initialize their devices. Historically, there have been several attempts and posted patches to address this problem. Here are a some links to a subset of discussions:

[RFC 1/2] pwrseq: Add subsystem to handle complex power sequences

The pwrseq subsystem handles complex power sequences, typically useful for subsystems that makes use of discoverable buses, like for example MMC and I2C. The pwrseq subsystem is dependant on CONFIG_OF to be able to parse a DT childnode to find out what power sequence method to bind for a device.

Re: [PATCH 5/5] perf tools: Add report.show-headers config file option

2014-06-19 (목), 15:02 +0200, Jiri Olsa: > On Thu, Jun 19, 2014 at 09:56:44PM +0900, Namhyung Kim wrote: > > [SNIP] > > > @@ -35,6 +35,7 @@ struct symbol_conf symbol_conf = { > > > .demangle = true, > > > .cumulate_callchain = true, > > > .symfs = "", > > >

Re: [PATCH 1/6] blk-mq: make blk_mq_stop_hw_queue() reliably block queue processing

Hello, Ming. On Thu, Jun 19, 2014 at 06:10:28PM +0800, Ming Lei wrote: > > void blk_mq_stop_hw_queue(struct blk_mq_hw_ctx *hctx) > > { > > - cancel_delayed_work(>run_work); > > - cancel_delayed_work(>delay_work); > > set_bit(BLK_MQ_S_STOPPED, >state); > > +

Re: kbuild: support of new KBUILD_FULL_PATH

Dne 19.6.2014 14:01, Boaz Harrosh napsal(a): > On 06/19/2014 01:41 PM, Michal Marek wrote: >>> Signed-off-by: Boaz Harrosh >>> -ifeq ($(KBUILD_SRC)/,$(dir $(CURDIR))) >>> +# if KBUILD_FULL_PATH is not empty then condition will fail >>> +ifeq

[PATCH] x86: Micro-optimization in nhmex_rbox_get_constraint

Flipping the LSB doesn't require four lines of code. This shaves a few bytes of the generated code, including a branch. Signed-off-by: Rasmus Villemoes --- arch/x86/kernel/cpu/perf_event_intel_uncore.c | 5 + 1 file changed, 1 insertion(+), 4 deletions(-) diff --git

[PATCH v5 8/8] kdb: Allow access to sensitive commands to be restricted by default

Currently kiosk mode must be explicitly requested by the bootloader or userspace. It is convenient to be able to change the default value in a similar manner to CONFIG_MAGIC_SYSRQ_DEFAULT_MASK. Signed-off-by: Daniel Thompson Cc: Jason Wessel Cc: kgdb-bugrep...@lists.sourceforge.net ---

[PATCH v5 5/8] kdb: Remove KDB_REPEAT_NONE flag

From: Anton Vorontsov Since we now treat KDB_REPEAT_* as flags, there is no need to pass KDB_REPEAT_NONE. It's just the default behaviour when no flags are specified. Signed-off-by: Anton Vorontsov Signed-off-by: John Stultz Signed-off-by: Daniel Thompson Cc: Jason Wessel Cc: Steven Rostedt

[PATCH v5 6/8] kdb: Categorize kdb commands (similar to SysRq categorization)

This patch introduces several new flags to collect kdb commands into groups (later allowing them to be optionally disabled). This follows similar prior art to enable/disable magic sysrq commands. The commands have been categorized as follows: Always on: go (w/o args), env, set, help, ?, cpu

[PATCH v5 7/8] kdb: Add enable mask for groups of commands

From: Anton Vorontsov Currently all kdb commands are enabled whenever kdb is deployed. This makes it difficult to deploy kdb to help debug certain types of systems. Android phones provide one example; the FIQ debugger found on some Android devices has a deliberately weak set of commands to

[PATCH v5 0/8] kdb: Allow selective reduction in capabilities (was "kiosk mode")

This patchset implements restricted modes for the KDB debugger. It is a continuation of previous kiosk mode work of Anton Vorontsov. There are no outstanding review comments for this patchset. It provides a means for the root user to choose the set of kdb commands that are available on the kdb

[PATCH v5 4/8] kdb: Use KDB_REPEAT_* values as flags

From: Anton Vorontsov 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 functionality-wise, there should be no

[PATCH v5 2/8] kdb: Rename kdb_repeat_t to kdb_cmdflags_t, cmd_repeat to cmd_flags

From: Anton Vorontsov 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 Signed-off-by: John Stultz Signed-off-by: Daniel Thompson Cc:

[PATCH v5 3/8] kdb: Rename kdb_register_repeat() to kdb_register_flags()

From: Anton Vorontsov 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 Signed-off-by: John Stultz Signed-off-by:

[PATCH v5 1/8] kdb: Remove currently unused kdbtab_t->cmd_flags

From: Anton Vorontsov 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 Signed-off-by: John Stultz Signed-off-by: Daniel Thompson Cc: Jason Wessel Cc: Ingo Molnar Cc:

Re: [PATCH v2 07/18] ARM: dts: DRA7: Change the parent of apll_pcie_in_clk_mux to dpll_pcie_ref_m2ldo_ck

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 Change the parent of apll_pcie_in_clk_mux to dpll_pcie_ref_m2ldo_ck from dpll_pcie_ref_ck. Why? Needs a

Re: [PATCH v2 10/18] ARM: dts: dra7xx-clocks: Add missing 32khz clocks used for PHY

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

[PATCHv2 1/2] ARM: tegra: tamonten: add the base board regulators

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 --- v2: * Put the board regualtors in the 'regulator' group with IDs

Re: [PATCH v2 13/18] ARM: dts: dra7xx-clocks: Add missing clocks for second PCIe PHY instance

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

Re: [PATCH] mm: percpu: micro-optimize round-to-even

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 > --- > mm/percpu.c | 3 +-- > 1 file changed, 1 insertion(+), 2 deletions(-) > > diff --git a/mm/percpu.c b/mm/percpu.c > index

[PATCHv2 2/2] ARM: tegra: tamonten: add the display to the Medcom Wide

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 --- v2: * no changes since v1 --- arch/arm/boot/dts/tegra20-medcom-wide.dts | 20 +++- 1

Re: [PATCH v2 10/18] ARM: dts: dra7xx-clocks: Add missing 32khz clocks used for PHY

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.

Re: [PATCH] mm: percpu: micro-optimize round-to-even

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 > > --- > > mm/percpu.c | 3 +-- > > 1 file changed, 1 insertion(+),

Re: [PATCH v2 06/18] ARM: dts: DRA7: Add divider table to optfclk_pciephy_div clock

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 Add divider table to optfclk_pciephy_div clock. The Documentation for divider clock can be found at

[PATCH] bug: Fix CONFIG_BUG=n BUG_ON()

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 Cc: Arnd Bergmann

Re: [STLinux Kernel] [PATCH 4/7] ARM: stih416-b2020e: Enable PWM on the B2020 Rev-E

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

Re: [PATCH v2 6/6] percpu-refcount: implement percpu_ref_reinit() and percpu_ref_is_zero()

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. >

Re: [PATCH v2 07/10] regulator: Add driver for Maxim 77802 PMIC regulators

On Wed, 18 Jun 2014 15:10:48 +0100 Lee Jones 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 the

Re: [PATCH 6/6] percpu-refcount: implement percpu_ref_reinit() and percpu_ref_is_zero()

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 >

Re: [PATCH 1/1] PM / Runtime: let rpm_resume fail if rpm disabled and device suspended.

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

[PATCH 3/3] x86/reboot: Add EFI reboot quirk for ACPI Hardware Reduced flag

From: Matt Fleming 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 the preferred method.

[PATCH 0/3] EFI reboot/poweroff support

From: Matt Fleming 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 well in the wild. The

[PATCH 1/3] efi/reboot: Add generic wrapper around EfiResetSystem()

From: Matt Fleming 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 see whether

[PATCH 2/3] efi/reboot: Allow powering off machines using EFI

From: Matt Fleming 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 an ideal world, this

Re: [PATCHv2 6/6] usb: dwc3: host: convey the PHYs to xhci

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

Re: [ANNOUNCE] 3.12.22-rt33

On Thu, 19 Jun 2014 05:46:43 +0200 Mike Galbraith 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 v3.12... >

Re: [PATCH 4/9] usb: phy: add the Berlin USB PHY driver

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 > 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 > >> wrote: > >> > Add the driver

[GIT PULL] ACPI and power management updates for v3.16-rc2

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

Re: [PATCH] usb: gadget: composite: unlock spinlock before usb_gadget_disconnect()

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

Tilbagebetaling af skat 2013 - 808384233

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

Re: [PATCH] of: Check for phys_addr_t overflows in early_init_dt_add_memory_arch

On Thu, Jun 19, 2014 at 12:04 AM, Laura Abbott 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 may result in

[GIT PULL] tracing: Cleanups and fixes to syscall tracepoints

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

[PATCH] Revert "kvm: x86: emulate monitor and mwait instructions as nop"

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

Re: [REPOST PATCH 1/8] fence: dma-buf cross-device synchronization (v17)

On Wed, Jun 18, 2014 at 9:13 PM, Greg KH wrote: > On Wed, Jun 18, 2014 at 12:36:54PM +0200, Maarten Lankhorst wrote: >> +#define CREATE_TRACE_POINTS >> +#include >> + >> +EXPORT_TRACEPOINT_SYMBOL(fence_annotate_wait_on); >> +EXPORT_TRACEPOINT_SYMBOL(fence_emit); > > Are you really willing to

[PATCHv9 0/4] power_supply: Introduce power supply charging driver

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

[PATCH 3/4] power_supply: Introduce PSE compliant algorithm

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

[PATCH 1/4] power_supply: Add inlmt,iterm, min/max temp props

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.

Re: [RFC 1/2] pwrseq: Add subsystem to handle complex power sequences

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

[PATCH 4/4] power_supply: bq24261 charger driver

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 ---

[PATCH] ARM: mvebu: Fix missing binding documentation for Armada 38x

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 --- Hi, This fix should be merged in 3.16. For 3.15 I am not sure as it is not a regression. Thanks,

<    5   6   7   8   9   10   11   12   13   14   >