On Wed, Jul 10, 2013 at 11:39:50AM -0400, Vince Weaver wrote:
> On Wed, 10 Jul 2013, Dave Jones wrote:
>
> > Something is really fucked up in the kernel side of perf.
> > I get this right after booting..
> >
> > [ 114.516619] perf samples too long (4262 > 2500), lowering
> >
If the WAKEUP_INT is asserted at wakeup and not cleared, we'll end up
looping around forever. This has been seen to happen on exynos5420
silicon despite the fact that we haven't enabled any wakeup events.
Signed-off-by: Doug Anderson
---
Changes in v3: None
Changes in v2:
- Use suspend_noirq as
The TMOUT register is initted to 0x at probe time but isn't
initted after suspend/resume. Add an init of this value.
No problems were observed without this (it will also get initted in
__dw_mci_start_request if there is data to send), but it makes the
register dump before and after
On some devices (like exynos5420) the dw_mmc controller may be in a
strange state after we wake up from sleep. Add callbacks to allow for
dealing with these quirks. We use the "_noirq" versions of the
callbacks since in the case of exynos5420 the strange state caused
interrupts to fire so we
After suspend/resume all of the dw_mmc registers are reset to
defaults. We restore most of them, but specifically don't setup the
clock registers after resume unless we've got a powered card. Things
still work because the core will eventually call set_ios() and we'll
set things up.
There
The dw_mmc driver keeps a cache of the current slot->clock in order to
avoid doing a whole lot of work every time set_ios() is called.
However, after suspend/resume the register values are bogus so we need
to ensure that the cached value is invalidated.
In many cases we got by without this since
On Wed, Jul 10, 2013 at 05:20:15PM +0200, Markus Trippelsdorf wrote:
> On 2013.07.10 at 11:13 -0400, Dave Jones wrote:
> > I get this right after booting..
> >
> > [ 114.516619] perf samples too long (4262 > 2500), lowering
> > kernel.perf_event_max_sample_rate to 5
>
> You can
On Wed, 10 Jul 2013, Dave Jones wrote:
> Something is really fucked up in the kernel side of perf.
> I get this right after booting..
>
> [ 114.516619] perf samples too long (4262 > 2500), lowering
> kernel.perf_event_max_sample_rate to 5
>
> That's before I even get a chance to log in,
On 07/10/13 16:38, Roland Dreier wrote:
On Wed, Jul 10, 2013 at 7:35 AM, Sebastian Riemer
wrote:
I've checked the commits on that tag and the following commit is not
what we've agreed on:
Sorry about that. The discussion was long and complex and I probably
made a mistake in aplying the
I had this on my mind for a bit of time now... Never liked INIT_COMPLETION
because of inconsistencies. See patch 1 to see why I think a replacement is
proper. I wonder what to do about the old INIT_COMPLETION, though. We could
a) remove it right away (bad luck for out-of-tree users, still my
For the casual device driver writer, it is hard to remember when to use
init_completion (to init a completion structure) or INIT_COMPLETION (to
*reinit* a completion structure). Furthermore, while all other completion
functions exepct a pointer as a parameter, INIT_COMPLETION does not. To make it
Use this new function to make code more comprehensible, since we are
reinitialzing the completion, not initializing.
Signed-off-by: Wolfram Sang
Acked-by: Linus Walleij (personally at LCE13)
---
This is now a tree-wide patch for easier review. I can easily split it up later.
With the lists this time
On Wed, Jul 10, 2013 at 6:17 PM, Ohad Ben-Cohen wrote:
> The following changes since commit 9e895ace5d82df8929b16f58e9f515f6d54ab82d:
>
> Linux 3.10-rc7 (2013-06-22 09:47:31 -1000)
>
> are available in the git repository at:
>
>
The following changes since commit 4d3797d7e1861ac1af150a6189315786c5e1c820:
Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net (2013-06-05
19:19:04 +0900)
are available in the git repository at:
git://github.com/kleikamp/linux-shaggy.git tags/jfs-3.11
for you to fetch changes
On Wed, Jul 10, 2013 at 11:03:15AM -0400, Konrad Rzeszutek Wilk wrote:
> On Wed, Jul 10, 2013 at 01:47:17PM +0300, Gleb Natapov wrote:
> > On Wed, Jul 10, 2013 at 12:40:47PM +0200, Peter Zijlstra wrote:
> > > On Wed, Jul 10, 2013 at 01:33:25PM +0300, Gleb Natapov wrote:
> > >
> > > Here's an
Hi,
There was no intention to prevent auto loading. Did you get chance to
test these changes?
Thanks,
Srinivas
On 07/10/2013 01:31 AM, Alexander Holler wrote:
Hello,
I'm not sure if it was by intention that none of the hid-sensor drivers
were loaded automatically. But I assume it was not
On 2013.07.10 at 11:13 -0400, Dave Jones wrote:
> On Sat, Jul 06, 2013 at 09:24:08AM +0200, Ingo Molnar wrote:
> >
> > * Dave Jones wrote:
> >
> > > On Fri, Jul 05, 2013 at 05:15:07PM +0200, Thomas Gleixner wrote:
> > > > On Fri, 5 Jul 2013, Dave Jones wrote:
> > > >
> > > > > BUG:
Hi,
After Michal's (somewhat positive) response to the first iteration,
here's the second iteration fixing the reserved-letters problem.
I also find hitting to return to the previous page quite
annoying, and I hope to tackle this in the future depending on how the
community responds to [3/3].
Like in Vim.
Cc: Michal Marek
Signed-off-by: Ramkumar Ramachandra
---
scripts/kconfig/lxdialog/menubox.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/scripts/kconfig/lxdialog/menubox.c
b/scripts/kconfig/lxdialog/menubox.c
index 698d7c3..151394a 100644
---
first_alpha() checks only against lowercase characters anyway.
Cc: Michal Marek
Signed-off-by: Ramkumar Ramachandra
---
scripts/kconfig/lxdialog/menubox.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/kconfig/lxdialog/menubox.c
These letters that should not be used in menu selection.
Cc: Michal Marek
Signed-off-by: Ramkumar Ramachandra
---
scripts/kconfig/lxdialog/menubox.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/scripts/kconfig/lxdialog/menubox.c
> > suspend complete.
> >
> > I can start bi-sect of this problem on intel-display scope if you
> > would like me to. Please let me know if the bisect scope should be larger.
> >
> > -- Shuah
>
> I got finally an older system where this reproduces consistently, I'm trying
> to
> root cause that
On 07/10/2013 12:48 AM, Wei Ni wrote:
> On 07/09/2013 10:00 PM, Eduardo Valentin wrote:
>> In order to be able to build thermal policies
>> based on generic sensors, like I2C device, that
>> can be places in different points on different boards,
>> there is a need to have a way to feed board
On Sat, Jul 06, 2013 at 09:24:08AM +0200, Ingo Molnar wrote:
>
> * Dave Jones wrote:
>
> > On Fri, Jul 05, 2013 at 05:15:07PM +0200, Thomas Gleixner wrote:
> > > On Fri, 5 Jul 2013, Dave Jones wrote:
> > >
> > > > BUG: soft lockup - CPU#3 stuck for 23s! [trinity-child1:14565]
> > >
James,
On Wed, Jul 10, 2013 at 1:37 AM, James Hogan wrote:
>> -SIMPLE_DEV_PM_OPS(dw_mci_pltfm_pmops, dw_mci_pltfm_suspend,
>> dw_mci_pltfm_resume);
>> +const struct dev_pm_ops dw_mci_pltfm_pmops = {
>> + SET_SYSTEM_SLEEP_PM_OPS(dw_mci_pltfm_suspend, dw_mci_pltfm_resume)
>> +
On Wed, Jul 10, 2013 at 01:47:17PM +0300, Gleb Natapov wrote:
> On Wed, Jul 10, 2013 at 12:40:47PM +0200, Peter Zijlstra wrote:
> > On Wed, Jul 10, 2013 at 01:33:25PM +0300, Gleb Natapov wrote:
> >
> > Here's an idea, trim the damn email ;-) -- not only directed at gleb.
> >
> Good idea.
>
> >
Seungwon,
On Wed, Jul 10, 2013 at 7:54 AM, Seungwon Jeon wrote:
> On Wed, July 10, 2013, Doug Anderson wrote:
>> If the WAKEUP_INT is asserted at wakeup and not cleared, we'll end up
>> looping around forever. This has been seen to happen on exynos5420
>> silicon despite the fact that we
On 10.07.2013, at 16:17, Alexey Kardashevskiy wrote:
> On 07/10/2013 08:27 PM, Alexander Graf wrote:
>>
>> On 10.07.2013, at 01:35, Alexey Kardashevskiy wrote:
>>
>>> On 07/10/2013 01:35 AM, Alexander Graf wrote:
On 06/27/2013 07:02 AM, Alexey Kardashevskiy wrote:
> Signed-off-by:
On Wed, 2013-07-10 at 14:28 +0200, Jean Delvare wrote:
> Hi Joe,
hi Jean.
> Le Tuesday 09 July 2013 à 09:19 -0700, Joe Perches a écrit :
> > On Tue, 2013-07-09 at 17:42 +0200, Jean Delvare wrote:
[]
> > If the function name is used in every printk, it might
> > be better to add
> > #define
Stephen Mell writes:
> Currently, the proc mount options hidepid and pidgid are stored on the
> pid_namespace struct that serves as proc's superblock info. As a
> result, mounting proc from the same pid namespace with different mount
> options will change the behaviour of any existing mounts.
>
On Wed, 10 Jul 2013, Roger Quadros wrote:
> On 07/09/2013 05:16 PM, Alan Stern wrote:
> > On Tue, 9 Jul 2013, Roger Quadros wrote:
> >
> >> Most HCD drivers are doing the same thing in their ".shutdown" callback
> >> so it makes sense to use the generic usb_hcd_platform_shutdown()
> >> handler
Dne 9.7.2013 01:08, Sören Brinkmann napsal(a):
> On Sat, Jul 06, 2013 at 06:00:05PM -0500, Rob Landley wrote:
>> On 07/05/2013 06:32:59 AM, Ramkumar Ramachandra wrote:
>>> Like in Vim.
>>>
>>> Cc: Michal Marek
>>> Signed-off-by: Ramkumar Ramachandra
>>> ---
>>> Unsure why nobody has done this
On Wed, July 10, 2013, Doug Anderson wrote:
> In (1fb5f68 mmc: dw_mmc: Don't loop when handling an interrupt), the
> code for handling DW_MCI_QUIRK_IDMAC_DTO became dead code. Move it to
> where it ought to live.
>
> Found by code inspection and compile-tested only--I don't know of any
> boards
On 17:51 Wed 10 Jul , Bo Shen wrote:
> add pinctrl of TWI for at91sam9n12 SoC
>
> Signed-off-by: Bo Shen
> ---
> arch/arm/boot/dts/at91sam9n12.dtsi | 20
> 1 file changed, 20 insertions(+)
>
> diff --git a/arch/arm/boot/dts/at91sam9n12.dtsi
>
On Wed, July 10, 2013, Doug Anderson wrote:
> If the WAKEUP_INT is asserted at wakeup and not cleared, we'll end up
> looping around forever. This has been seen to happen on exynos5420
> silicon despite the fact that we haven't enabled any wakeup events.
>
> Signed-off-by: Doug Anderson
> ---
>
On Wed, July 10, 2013, Doug Anderson wrote:
> The TMOUT register is initted to 0x at probe time but isn't
> initted after suspend/resume. Add an init of this value.
>
> No problems were observed without this (it will also get initted in
> __dw_mci_start_request if there is data to send),
On Wed, Jul 10, 2013 at 04:39:02PM +0200, Ingo Molnar wrote:
>
> * Peter Zijlstra wrote:
>
> > Hi,
> >
> > I just stumbled over commit 582b336ec2 and had a massive WTF moment.
> >
> > The Changelog -- empty!
> > The Implementation -- complete crap!
> >
> > fail^2.
> >
> > A git grep later I
On Wed, Jul 10, 2013 at 11:19:23AM +0200, Roger Pau Monné wrote:
> On 08/07/13 21:41, Konrad Rzeszutek Wilk wrote:
> > On Mon, Jul 08, 2013 at 03:03:27PM +0200, Roger Pau Monne wrote:
> >> Right now blkfront has no way to unmap grant refs, if using persistent
> >> grants once a grant is used
even more trivial...
On Wed, 2013-07-10 at 14:47 +0200, Jean Delvare wrote:
> +++ linux-3.11-rc0/drivers/firmware/dmi_scan.c2013-07-10
> 14:11:56.544792703 +0200
> @@ -62,8 +62,6 @@ static const char * __init dmi_string(co
> str = dmi_alloc(len);
> if (str != NULL)
[]
> @@
> So it would be nice to have at least some time to address this with upstream
> grub and the main distributions to patch their grub.
Sounds quite sensible. Michael would you be OK doing this?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On 07/10/2013 05:54 AM, Peter Zijlstra wrote:
On Tue, Jul 09, 2013 at 06:35:27PM -0400, Sasha Levin wrote:
While going through the NMI dump, I noticed that it's very incomplete, and full
of:
[ 2536.500130] INFO: NMI handler (arch_trigger_all_cpu_backtrace_handler)
took too long to run:
On 10/07/13 15:54, Egger, Christoph wrote:
> On 10.07.13 11:19, Roger Pau Monné wrote:
>> On 08/07/13 21:41, Konrad Rzeszutek Wilk wrote:
>>> On Mon, Jul 08, 2013 at 03:03:27PM +0200, Roger Pau Monne wrote:
Right now blkfront has no way to unmap grant refs, if using persistent
grants
Attention.
Your fund $7.6m released via ATM card contact our bank for your ATM to
processing the delivery. email: (davidnam...@wss-id.org) Phone +229 98078483
Dr.Olunna.Ike.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Wed, Jun 26, 2013 at 04:14:14PM +0900, Namhyung Kim wrote:
SNIP
>
> +static int
> +__cmd_ftrace_report(struct perf_ftrace *ftrace, int argc, const char **argv)
> +{
> + int ret = -1;
> + const char * const report_usage[] = {
> + "perf ftrace report []",
> +
On 17:51 Wed 10 Jul , Bo Shen wrote:
> add qt1070 support on at91sam9n12ek board
>
> Signed-off-by: Bo Shen
> ---
> arch/arm/boot/dts/at91sam9n12ek.dts | 16
> 1 file changed, 16 insertions(+)
>
> diff --git a/arch/arm/boot/dts/at91sam9n12ek.dts
>
On Wed, Jun 26, 2013 at 04:14:13PM +0900, Namhyung Kim wrote:
> From: Namhyung Kim
>
> The ftrace show subcommand is for viewing recorded ftrace files. It
> enters perf.data.dir directory and open perf.header file to find out
> necessary information. And then read out per-cpu trace records
On Wed, Jul 10, 2013 at 6:20 AM, Jason Cooper wrote:
> Please keep in mind that the DT is supposed to be tied to the hardware,
> *not* the kernel. iow, a dtb comes with a board, and the user/OS
> upgrades the kernel as needed w/o upgrading or changing the dtb.
Thank you for making this position
* Peter Zijlstra wrote:
> Hi,
>
> I just stumbled over commit 582b336ec2 and had a massive WTF moment.
>
> The Changelog -- empty!
> The Implementation -- complete crap!
>
> fail^2.
>
> A git grep later I find its x86_64 paravirt only.. for this we add
> unconditional crap to the
Simon Horman writes:
> From: Stephen Warren
>
> Prior to commit 3ab8352 "kexec jump", if machine_kexec() returned,
> sys_reboot() would return -EINVAL. This patch restores this behaviour
> for the non-KEXEC_JUMP case, where machine_kexec() is not expected to
> return.
>
> This situation can
On Wed, Jul 10, 2013 at 7:35 AM, Sebastian Riemer
wrote:
>
> I've checked the commits on that tag and the following commit is not
> what we've agreed on:
Sorry about that. The discussion was long and complex and I probably
made a mistake in aplying the patches. Please me send a patch to fix
Hi Roland,
I've checked the commits on that tag and the following commit is not
what we've agreed on:
commit 086f44f58855ae18bab19fb794cce6c6d2c6143b
Author: Bart Van Assche
IB/srp: Avoid skipping srp_reset_host() after a transport error
Together with the following commit this results in
On Wed, Jul 10, 2013 at 06:50:18PM +0900, HATAYAMA Daisuke wrote:
[..]
> If you want to avoid looking up vmcore_list that takes linear time w.r.t. the
> number
> of the elements, you can still calculate the range of offsets in /proc/vmcore
> corresponding to HSA during /proc/vmcore
On Wed, 2013-07-10 at 13:34 +0200, Maarten Lankhorst wrote:
> Hey,
>
> It seems that in the merge window my macbook pro stopped working at some
> point. I looked for suspicious
> efi related commits, and found that reverting commit
> 1acba98f810a14b1255e34bc620594f83de37e36 worked,
> letting my
Linus,
Please pull the latest x86-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-urgent-for-linus
HEAD: 4787c368a9bca39e173d702389ee2eaf0520abc1 x86/tracing: Add
irq_enter/exit() in smp_trace_reschedule_interrupt()
irq-tracing fixlet.
My previous refactoring in commit 79bae42d51a5 resulted in slightly
tricky code (though I think it's more elegant). Explain what it's
doing.
Signed-off-by: Ben Hutchings
---
drivers/firmware/dmi_scan.c | 14 ++
1 file changed, 14 insertions(+)
diff --git
23: warning: ‘imx_init_l2cache’ defined but
> not used [-Wunused-function]
>
> Signed-off-by: Vincent Stehlé
> Cc: Shawn Guo
> Cc: Sascha Hauer
> Cc: Russell King
> Cc: triv...@kernel.org
> ---
>
>
> Hi,
>
> Linux next-20130710 breaks compilation of ARM m
On Wed, Jun 26, 2013 at 04:14:12PM +0900, Namhyung Kim wrote:
> From: Namhyung Kim
SNIP
> +
> +static int create_perf_directory(struct perf_ftrace *ftrace)
> +{
> + int err;
> + char buf[PATH_MAX];
> + struct stat statbuf;
> +
> + scnprintf(buf, sizeof(buf), "%s.dir",
On Wed, Jun 26, 2013 at 04:14:18PM +0900, Namhyung Kim wrote:
> From: Namhyung Kim
>
> Cc: Steven Rostedt
> Cc: Frederic Weisbecker
> Signed-off-by: Namhyung Kim
> ---
SNIP
> +OPTIONS
> +---
> +...::
> + Any command you can specify in a shell.
> +
> +-t::
> +--tracer=::
> +
This patch removes the forward declaration of qfq_update_agg_ts, by moving
the definition of the function above its first call. This patch also
removes a useless forward declaration of qfq_schedule_agg.
Reported-by: David S. Miller
Signed-off-by: Paolo Valente
---
net/sched/sch_qfq.c | 118
In make_eligible, a mask is used to decide which groups must become eligible:
the i-th group becomes eligible only if the i-th bit of the mask (from the
right) is set. The mask is computed by left-shifting a 1 by a given number of
places, and decrementing the result. The shift is performed on a
Hi,
this patchset tries to address the two issues raised by Dave in
http://marc.info/?l=linux-kernel=136254542019113=2
The first of these issues has been also raised by
David Laight:
http://marc.info/?l=linux-kernel=136256446624557=2
> Although two topics for possibly resolving later:
>
> 1)
Rename LL_SO to BUSY_POLL_SO
Rename sysctl_net_ll_{read,poll} to sysctl_busy_{read,poll}
Fix up users of these variables.
Fix documentation for sysctl.
a patch for the socket.7 man page will follow separately,
because of limitations of my mail setup.
Signed-off-by: Eliezer Tamir
---
Add description for the SO_BUSY_POLL socket option to the socket(7) manpage.
v2
fixed typos reported by Rasmus Villemoes
Signed-off-by: Eliezer Tamir
---
man7/socket.7 | 25 +
1 files changed, 25 insertions(+), 0 deletions(-)
diff --git a/man7/socket.7
On Wed, Jun 26, 2013 at 04:14:09PM +0900, Namhyung Kim wrote:
> From: Namhyung Kim
>
> The -p (--pid) option enables to trace existing process by its pid.
hi,
I can't get any output from -p for live subcommand:
[jolsa@krava perf]$ pgrep yes
6443
[jolsa@krava perf]$ sudo ./perf ftrace live -p
On 07/10/2013 08:27 PM, Alexander Graf wrote:
>
> On 10.07.2013, at 01:35, Alexey Kardashevskiy wrote:
>
>> On 07/10/2013 01:35 AM, Alexander Graf wrote:
>>> On 06/27/2013 07:02 AM, Alexey Kardashevskiy wrote:
Signed-off-by: Alexey Kardashevskiy
---
include/uapi/linux/kvm.h |
Rename the file and correct all the places where it is included.
Signed-off-by: Eliezer Tamir
---
drivers/net/ethernet/broadcom/bnx2x/bnx2x_cmn.c |2
drivers/net/ethernet/intel/ixgbe/ixgbe.h|2
drivers/net/ethernet/mellanox/mlx4/en_netdev.c |2
On Wed, Jul 03, 2013 at 12:52:40PM +0300, Mika Westerberg wrote:
> Some Intel LPSS I2C devices make the SDA hold time parameter available via
> SSCN (standard mode) and FMCN (fast mode) ACPI methods. If we find that
> such method exist, we evaluate it and pass the returned SDA hold value to
> the
Rename ndo_ll_poll to ndo_busy_poll.
Rename sk_mark_ll to sk_mark_napi_id.
Rename skb_mark_ll to skb_mark_napi_id.
Correct all useres of these functions.
Update comments and defines in include/net/busy_poll.h
Signed-off-by: Eliezer Tamir
---
drivers/net/ethernet/broadcom/bnx2x/bnx2x_cmn.c |
David,
Here are three patches that complete the rename of lls to busy-poll
1. rename include/net/ll_poll.h to include/net/busy_poll.h
2. Rename ndo_ll_poll to ndo_busy_poll.
Rename sk_mark_ll to sk_mark_napi_id.
Rename skb_mark_ll to skb_mark_napi_id.
Correct all useres of these
On Wed, Jul 10, 2013 at 8:24 PM, Jason Cooper wrote:
> On Wed, Jul 10, 2013 at 04:19:46PM +0800, Haojian Zhuang wrote:
>> On Tue, Jul 9, 2013 at 8:49 PM, Jason Cooper wrote:
>> > Neil,
>> >
>> > On Tue, Jul 09, 2013 at 02:42:44PM +0800, Neil Zhang wrote:
>> >> The documented vendor prefix for
Hi Linus,
the misc branch is reserved for Coccinelle this time:
- 'report' is the default mode
- MAINTAINERS update for Coccinelle
- documentation udate
- use new option format for spatch(1)
- J= variable to mimic make -j for coccicheck
- check for missing pci_free_consistent() calls
There are
Gerhard Sittig wrote:
>+ * Author is Alexander Popov.
nit pick: is 1337 speak usual and appropriate here?
Um, that's his actual email address.
shouldn't headers get sorted alphabetically?
Is that a new policy? I've never heard that requirement.
+MODULE_AUTHOR("Alexander Popov ");
Hi,
On Friday 05 July 2013 01:59 PM, Jingoo Han wrote:
> Exynos PCIe IP consists of Synopsys specific part and Exynos
> specific part. Only core block is a Synopsys designware part;
> other parts are Exynos specific.
> Also, the Synopsys designware part can be shared with other
> platforms; thus,
Add RTC driver for MOXA ART SoCs.
Signed-off-by: Jonas Jensen
---
Notes:
Applies to next-20130703
drivers/rtc/Kconfig | 9 ++
drivers/rtc/Makefile | 1 +
drivers/rtc/rtc-moxart.c | 335 +++
3 files changed, 345 insertions(+)
create
On 10/07/2013 16:17, Arend van Spriel wrote:
> On 07/10/2013 02:13 PM, Eliezer Tamir wrote:
>> Rename the file and correct all the places where it is included.
>> Signed-off-by: Eliezer Tamir
>> ---
>> include/net/busy_poll.h | 183
>> +++
>>
On 07/10/2013 08:46 AM, Gerhard Sittig wrote:
> On Wed, Jul 10, 2013 at 14:21 +0400, Alexander Popov wrote:
>>
>> This is SCLPC device driver for the Freescale MPC512x.
>> It is needed for Direct Memory Access to the devices on LocalPlus Bus.
>>
>> Signed-off-by: Alexander Popov
>> ---
>>
Hi Linus,
please pull the kbuild bits for v3.11-rc1:
- fix for make headers_install argv explosion with too long path
- scripts/setlocalversion does not call git update-index needlessly
- fix for the src.rpm produced by make rpm-pkg. The new make image_name
can be useful also for other
On 10.07.13 11:19, Roger Pau Monné wrote:
> On 08/07/13 21:41, Konrad Rzeszutek Wilk wrote:
>> On Mon, Jul 08, 2013 at 03:03:27PM +0200, Roger Pau Monne wrote:
>>> Right now blkfront has no way to unmap grant refs, if using persistent
>>> grants once a grant is used blkfront cannot assure if
Hi Linus,
please pull these kconfig commit for v3.11-rc1:
- dependency solver fix for make defconfig
- randconfig fixes, one of which had to be reverted again
- more user-friendly sorting of search results
- hex and range keywords support longs
- fix for [mn]conf not to rely on particular
On Wed, 10 Jul 2013 11:24:39 +0300
"Michael S. Tsirkin" wrote:
> On x86, kvm_arch_create_memslot assumes that rmap/lpage_info for the
> slot are zeroed out: if they weren't, error handling code after out_free
> label will free memory which wasn't allocated here.
> This always happens to be the
Add GPIO driver for MOXA ART SoCs.
Signed-off-by: Jonas Jensen
---
Notes:
Applies to next-20130703
drivers/gpio/Kconfig | 7 ++
drivers/gpio/Makefile | 1 +
drivers/gpio/gpio-moxart.c | 168 +
3 files changed, 176 insertions(+)
On Wed, Jul 10, 2013 at 14:21 +0400, Alexander Popov wrote:
>
> This is SCLPC device driver for the Freescale MPC512x.
> It is needed for Direct Memory Access to the devices on LocalPlus Bus.
>
> Signed-off-by: Alexander Popov
> ---
> arch/powerpc/boot/dts/mpc5121.dtsi| 8 +-
>
Additionally remove trailing whitespace when print triggering type.
Signed-off-by: Andy Shevchenko
---
drivers/pinctrl/pinctrl-baytrail.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/pinctrl/pinctrl-baytrail.c
b/drivers/pinctrl/pinctrl-baytrail.c
index
Eliezer Tamir writes:
> +While busy polling my improve latency of some application, care must be
> +taken when using it since this will increase both CPU utilization power
> usage.
s/my/may/; missing 'and' before 'power usage'. [And should
'application' be plural?]
Rasmus
--
To unsubscribe
Hi!
> >> But:
> >> 1) it should not list unavailable options
> >>
> >> 2) operation not permitted seems like wrong error code for
> >> operation not supported.
> >
> > So I forcibly enabled ASPM, and now ping latencies are in normal
> > range... no matter how I set
> >
On Wed, Jul 10, 2013 at 06:52:09PM +0530, Ramkumar Ramachandra wrote:
> Michael S. Tsirkin wrote:
> > This is usespace code so it needs the cleaned-up version from
> > usr/include, not the internal kernel one.
>
> Right, thanks for clearing that up. However, it does seem to depend
> on some code
On Wed, Jul 10, 2013 at 7:16 AM, Geert Uytterhoeven
wrote:
> drivers/gpu/drm/drm_edid_load.c: In function ‘drm_load_edid_firmware’:
> drivers/gpu/drm/drm_edid_load.c:245: warning: initialization discards
> qualifiers from pointer target type
>
> drm_get_connector_name() returns a "const char *",
Michael S. Tsirkin wrote:
> This is usespace code so it needs the cleaned-up version from
> usr/include, not the internal kernel one.
Right, thanks for clearing that up. However, it does seem to depend
on some code in /include in the linux tree. From
tools/virtio/linux/virtio_ring.h:
On 07/10/2013 02:13 PM, Eliezer Tamir wrote:
Rename the file and correct all the places where it is included.
Signed-off-by: Eliezer Tamir
---
drivers/net/ethernet/broadcom/bnx2x/bnx2x_cmn.c |2
drivers/net/ethernet/intel/ixgbe/ixgbe.h|2
Hi Linus,
this Microblaze merge window is quite minimal.
I have also added to my branch one xilinx systemace sparse fix
because haven't got any reply from block maintainer.
Thanks,
Michal
The following changes since commit 9e895ace5d82df8929b16f58e9f515f6d54ab82d:
Linux 3.10-rc7 (2013-06-22
On 7/9/2013 8:55 AM, Morten Rasmussen wrote:
Extends the power scheduler capacity management algorithm to handle
frequency scaling and provide basic frequency/P-state selection hints
to the power driver.
Signed-off-by: Morten Rasmussen
CC: Ingo Molnar
CC: Peter Zijlstra
CC: Catalin Marinas
From: Oleksandr Kravchenko
This patch adds IIO driver for APDS9300 ambilent light sensor (ALS).
http://www.avagotech.com/docs/AV02-1077EN
The driver allows to read raw data from ADC registers or calculate
lux value. It also can handle threshold inrerrupt.
Signed-off-by: Oleksandr Kravchenko
* On RX-51 probing for acx565akm driver is later then for omapfb which cause
that omapfb probe fail and framebuffer is not working
* EPROBE_DEFER causing that kernel try to probe for omapfb later again which
fixing this problem
* Without this patch display on Nokia RX-51 (N900) phone not
also, it almost looks like there is a fundamental assumption in the code
that you can get the current effective P state to make scheduler decisions on;
on Intel at least that is basically impossible... and getting more so with
every generation
(likewise for AMD afaics)
(you can get what
This mail is to inform you that my late Client Mr James Campbell bequeathed his
inheritance to you. I seek your attention on this issue.
Barr Colin Lee
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo
Other secure functions omap_smc1() and omap_smc2() calling instruction smc #0
but Nokia RX-51 board needs to call smc #1 for PPA access.
Signed-off-by: Ivaylo Dimitrov
Signed-off-by: Pali Rohár
---
arch/arm/mach-omap2/omap-secure.h |1 +
arch/arm/mach-omap2/omap-smc.S| 22
Gleb, Paolo,
based on the work from Martin and Carsten, this implementation enables async
page faults.
To the guest it will provide the pfault interface, but internally it uses the
async page fault common code.
The inital submission and it's discussion can be followed on
In case of a fault retry exit sie64() with gmap_fault indication for the
running thread set. This makes it possible to handle async page faults
without the need for mm notifiers.
Based on a patch from Martin Schwidefsky.
Signed-off-by: Dominik Dingel
Acked-by: Christian Borntraeger
---
Closed and signed Nokia X-Loader bootloader stored in RX-51 nand does not set
IBE bit in ACTLR and starting kernel in non-secure mode. So direct write to
ACTLR by our kernel does not working and the code for ARM errata 430973 in
commit 7ce236fcd6fd45b0441a2d49acb2ceb2de2e8a47 that sets IBE bit is
By setting a Kconfig option, the architecture can control when
guest notifications will be presented by the apf backend.
So there is the default batch mechanism, working as before, where the vcpu
thread
should pull in this information. On the other hand there is now the direct
mechanism, this
301 - 400 of 1208 matches
Mail list logo
