Hello Thomas,
On Mon, Mar 18, 2013 at 02:20:26PM +0100, Uwe Kleine-König wrote:
> This interrupt controller is found on Cortex-M3 and Cortex-M4 machines.
>
> Support for this controller appeared in Catalin's Cortex tree based on
> 2.6.33 but was nearly completely rewritten.
>
> Signed-off-by:
On Thursday 28 March 2013 13:05:56 Tvrtko Ursulin wrote:
> Hi,
>
> On Thursday 28 March 2013 11:03:51 Ram Pai wrote:
> > I tried these commands on a 3.8.0-rc1+ kernel and did not find the
> > problem. Is this on a recent kernel?
>
> I am on Fedora 17 latest, but I've seen this problem with
Hi Aaron, Rajob, PeterA and everybody else,
(sorry for the late reply)
>On 03/27/2013 11:22 PM, Rajiv Andrade wrote:
>> Sorry for the delay. Can you send us the dmesg output after setting
>> loglevel=7 at boot time? Additionally, can you send us the TPM manufacturer
>> model/version
>>> On
On 13-03-28 04:34 AM, Jiri Slaby wrote:
> Guys,
>
> how is this supposed to work?
>
> #define SYSRQ_KEY_RESET_MAX 20 /* Should be plenty */
> static unsigned short sysrq_reset_seq[SYSRQ_KEY_RESET_MAX];
> ...
> unsigned short platform_sysrq_reset_seq[] __weak = { KEY_RESERVED };
> ...
>
Would you be able to incorporate the GMAC ESN bug fix in 3.9?
Thanks,
Chaoxing
Thanks Jussi, the patch fixes the problem.
You may commit it officially.
Chaoxing
-Original Message-
From: Jussi Kivilinna [mailto:jussi.kivili...@iki.fi]
Sent: Tuesday,
Populate OF_DEV_AUXDATA with desired device name expected by
davinci_mmc driver. Without this clk_get of davinci_mmc DT driver
fails.
Signed-off-by: Manjunathappa, Prakash
Cc: linux-...@vger.kernel.org
Cc: linux-arm-ker...@lists.infradead.org
Cc: linux-kernel@vger.kernel.org
Cc:
Add DT entry for MMC. Also add entry for pinmux information.
Tested:
1) Without GPIO card detection and EDMA support as DT support for
GPIO and EDMA are yet come.
2) By creating/deleting files and mounting/unmounting the partition.
Signed-off-by: Manjunathappa, Prakash
Cc:
2013/3/28 Ingo Molnar :
>
> * Frederic Weisbecker wrote:
>
>> + cpulist_scnprintf(nohz_ext_buf, sizeof(nohz_ext_buf),
>> nohz_extended_mask);
>> + pr_info("NO_HZ: Experimental full dynticks CPUs: %s.\n", nohz_ext_buf);
>
> I'd suggest removing the 'experimental' word. We are not sending
On Thu, Mar 28, 2013 at 01:08:22PM +, Arnd Bergmann wrote:
> On Thursday 28 March 2013, Mark Brown wrote:
> > That still looks like it'll reference the function?
> Yes, that is intentional. The idea is to create a reference to the
> function so gcc doesn't complain about unused symbols if
2013/3/28 Ingo Molnar :
>
> * Frederic Weisbecker wrote:
>
>> The timekeeping job must be able to run early on boot
>> because there may be some pre-SMP (and thus pre-initcalls )
>> components that rely on it. The IO-APIC is one such users
>> as it tests the timer health by watching jiffies
On Thursday 28 March 2013, Mark Brown wrote:
> On Thu, Mar 28, 2013 at 12:39:46PM +, Arnd Bergmann wrote:
>
> > Axel Lin reported the same problem and I fixed the below code earlier
> > today by using the correct __attribute__((unused)) and dropping the
> > section magic for the non-OF case.
Hi,
On Thursday 28 March 2013 11:03:51 Ram Pai wrote:
> I tried these commands on a 3.8.0-rc1+ kernel and did not find the
> problem. Is this on a recent kernel?
I am on Fedora 17 latest, but I've seen this problem with different kernels.
Pretty sure from 3.5 something to 3.8 something. All
Hi Linus,
Please pull the arm64 fix below. Thanks.
The following changes since commit a937536b868b8369b98967929045f1df54234323:
Linux 3.9-rc3 (2013-03-17 15:59:32 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/cmarinas/linux-aarch64.git
On Thu, Mar 28, 2013 at 12:39:46PM +, Arnd Bergmann wrote:
> Axel Lin reported the same problem and I fixed the below code earlier
> today by using the correct __attribute__((unused)) and dropping the
> section magic for the non-OF case. My patch now looks contains the
That still looks like
Recent commit 6fac4829 "cputime: Use accessors to read task cputime
stats" introduced a bug, that make we account many times cputime of
the first thread, instead of cputimes of all threads.
Signed-off-by: Stanislaw Gruszka
---
kernel/sched/cputime.c |2 +-
1 files changed, 1 insertions(+),
On 03/25/2013 04:08 PM, John Stultz wrote:
>
> The problem of course, is that the new asynchronous behavior the
> shadow updates breaks some of the assumptions on how the NTP state
> is used. Thus to correct this, we really need to serialize the ntp
> state updates along with the timekeeping
Ingo,
Please pull the latest tip/perf/urgent tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
tip/perf/urgent
Head SHA1: cc1e2627b179f0fccb3285fe565e893b570558b8
Jan Kiszka (1):
ftrace: Consistently restore trace function on sysctl
From: "Steven Rostedt (Red Hat)"
The function tracing control loop used by perf spits out a warning
if the called function is not a control function. This is because
the control function references a per cpu allocated data structure
on struct ftrace_ops that is not allocated for other types of
From: "Steven Rostedt (Red Hat)"
The commit 34600f0e9 "tracing: Fix race with max_tr and changing tracers"
fixed the updating of the main buffers with the race of changing
tracers, but left out the fix to the updating of just a per cpu buffer.
Signed-off-by: Steven Rostedt
---
On Wed, Mar 27, 2013 at 10:28 PM, Yinghai Lu wrote:
> Matthem found that 3.8.3 is having problems with an old (ancient)
> PCI-to-EISA bridge, the Intel 82375. It worked with the 3.2 kernel.
> He identified the 82375, but doesn't assign the struct resource *res
> pointer inside the struct
From: Jan Kiszka
If we reenable ftrace via syctl, we currently set ftrace_trace_function
based on the previous simplistic algorithm. This is inconsistent with
what update_ftrace_function does. So better call that helper instead.
Link: http://lkml.kernel.org/r/5151d26f.1070...@siemens.com
Cc:
On Wed, 27 Mar 2013, Will Deacon wrote:
> On Wed, Mar 27, 2013 at 04:23:15PM +, Stefano Stabellini wrote:
> > OK, let's see if I can make this acceptable to you.
> >
> >
> > Would you agree on a patch that moves virt_smp_ops out of mach-virt and
> > renames them to psci_smp_ops (maybe to
On Thu, Mar 28, 2013 at 1:41 AM, Yinghai Lu wrote:
> On Wed, Mar 27, 2013 at 3:56 PM, Bjorn Helgaas wrote:
>>
>> Why can't we set all the ASPM flags *first*, before calling
>> pci_acpi_scan_root()? That way we could just do the correct ASPM
>> setup as we discover devices during enumeration,
On Wed, Mar 27, 2013 at 11:08 AM, Kyle McMartin wrote:
> On Wed, Mar 27, 2013 at 11:03:26AM -0400, Josh Boyer wrote:
>> On Mon, Mar 18, 2013 at 5:32 PM, Matthew Garrett
>> wrote:
>> > Any hardware that can potentially generate DMA has to be locked down from
>> > userspace in order to avoid it
On 28 March 2013 13:35, Amit Daniel Kachhap wrote:
> +++ b/drivers/cpufreq/exynos5440-cpufreq.c
> +static int exynos_cpufreq_cpu_init(struct cpufreq_policy *policy)
> +{
> + policy->cur = dvfs_info->cur_frequency;
> + cpufreq_frequency_table_get_attr(dvfs_info->freq_table,
we handle that?
In particular:
arch/arm/mach-shmobile/setup-r8a73a4.c
arch/arm/mach-shmobile/intc-r8a7779.c
arch/arm/mach-shmobile/setup-r8a7778.c
You can find these in the renesas-next-20130328 tag of
my renesas tree on kernel.org. They are or will soon
be in linux-next.
--
To unsubscr
On Thursday 28 March 2013, Mark Brown wrote:
> Commit 4d10f054 (clocksource: make CLOCKSOURCE_OF_DECLARE type safe)
> made CLOCKSOURCE_OF_DECLARE reference the function pointer in both the
> OF and non-OF cases. In the non-OF case this is likely to introduce
> build failures as users may
[ +cc Matt Carlson, Michael Chan, netdev because this is a tg3-related oops]
On Thu, 2013-03-28 at 09:31 +0100, Fabio Coatti wrote:
> 2013/3/27 Fabio Coatti :
> > Hi all,
> > we are experiencing crashes on some servers, right now running 3.7.10;
> > I've been able to get only screenshots from
Commit 4d10f054 (clocksource: make CLOCKSOURCE_OF_DECLARE type safe)
made CLOCKSOURCE_OF_DECLARE reference the function pointer in both the
OF and non-OF cases. In the non-OF case this is likely to introduce
build failures as users may reasonably conditionally compile the OF
specific code, either
Hi Linus,
Since Florian is still away/inactive, I volunteered to collect fbdev fixes for
3.9 and changes for 3.10. I didn't receive any other fbdev fixes than OMAP yet,
but I didn't want to delay this further as there's a compilation fix for OMAP1.
So there could be still some fbdev fixes on the
Dave Hansen wrote:
> On 03/14/2013 10:50 AM, Kirill A. Shutemov wrote:
> > From: "Kirill A. Shutemov"
> >
> > For now we still write/read at most PAGE_CACHE_SIZE bytes a time.
> >
> > This implementation doesn't cover address spaces with backing store.
> ...
> > --- a/mm/filemap.c
> > +++
Hi Philip,
On 02/01/2013 06:37 AM, Philip Avinash wrote:
> DT field of "interrupts" was mentioned wrongly as "interrupt" in SPI
> node. This went unnoticed as spi-omap2 driver not making use of
> interrupt. Fixes the typo.
>
> Signed-off-by: Philip Avinash
> ---
> arch/arm/boot/dts/am33xx.dtsi
On Wed, Mar 27, 2013 at 11:34:53PM +0100, Linus Walleij wrote:
> On Wed, Mar 27, 2013 at 11:11 PM, Woodhouse, David
> wrote:
> > On Wed, 2013-03-27 at 23:06 +0100, Linus Walleij wrote:
> >> Is it so critical that it needs to be tagged for stable as well
> >> then tell me.
> >>
> >> If it's
From: "Luis R. Rodriguez"
Commit 3cf2667 as of next-20130301 extended the struct fb_info
with a skip_vt_switch to allow drivers to skip the VT switch
at suspend/resume time. For older kernels we can skip this
as all this switch does is call pm_vt_switch_required() with true
or false depending on
On Thu, Mar 28, 2013 at 02:40:33AM -0400, CAI Qian wrote:
> System hung when running xfstests-dev 013 test case on an s390x guest. Never
> saw
> this on 3.9-rc3 before but need to double-check. Any idea?
>
> Ý 1113.795759¨ Ý cut here ¨
> Ý 1113.795771¨ kernel BUG at
From: "Luis R. Rodriguez"
This adds helpers to enable and test for the skip_vt_switch.
This gets us two things:
1) It allows us to require less collateral evolutions
should we need changes on the fb_info data structure
later (perhaps a bitmap flag).
2) Allows this feature to be
From: "Luis R. Rodriguez"
The collateral evolution (CE) on the fb_info data structure
that added the skip_vt_switch element can be simplified
further by replacing the #ifdef hell with a static inline.
Furthermore, if the static inline is added upstream it'd mean
we can get rid of all these
From: "Luis R. Rodriguez"
I maintain the the compat-drivers project [0] which aims at backporting the
Linux kernel drivers down to older kernels, automatically [1]. Thanks to
Ozan Caglayan as a GSoC project we now backport DRM drivers.
The initial framework we had set up to help with the
From: "Luis R. Rodriguez"
Commit 3cf2667 as of next-20130301 extended the struct fb_info
with a skip_vt_switch to allow drivers to skip the VT switch
at suspend/resume time. For older kernels we can skip this
as all this switch does is call pm_vt_switch_required() with true
or false depending on
On 19/03/13 10:28, Will Deacon wrote:
On Tue, Mar 19, 2013 at 06:39:38AM +, Santosh Shilimkar wrote:
On Monday 18 March 2013 10:36 PM, Will Deacon wrote:
Any chance you could follow up with your firmware/hardware guys about this
please? I'd really like to understand how we end up in this
In unapply_new_state, the old state is re-applied, but p->state is not
set back as it should.
Signed-off-by: Richard Genoud
---
This one can be squshed with commit:
50cf7c8ab324de348990bb028ad9ed10872d527a
pinctrl: re-enable old state in case of error in pinctrl_select_state
If needed.
And remove superfluous brackets.
Signed-off-by: Richard Genoud
---
If it's not too late, it can be squashed with commit:
3102a76cfbf9ac4ae0cf54c7452f7ba4292a4760
"pinctrl: disable and free setting in select_state in case of error"
drivers/pinctrl/core.c |5 ++---
1 files changed, 2
As Stephen Warren suggested, checking first if the setting->node entry
is the first in the list or not is superfluous, as it is checked again
in the list_for_each_entry bellow.
So, remove it, the code will be simpler and lighter !
Signed-off-by: Richard Genoud
---
If can also be squashed whit
On Thursday 28 March 2013, Ley Foon Tan wrote:
> On Thu, 2013-03-28 at 10:40 +, Arnd Bergmann wrote:
> > On Thursday 28 March 2013, Ley Foon Tan wrote:
> > > We will working on generic ABI for kernel and Glibc. This might take
> > > some times.
> >
> > Ok. Don't let that hold you up from
On Sunday 03 March 2013 04:39 AM, Grant Likely wrote:
On Fri, 22 Feb 2013 19:59:11 +0530, Manish Badarkhe
wrote:
On Fri, Feb 22, 2013 at 6:07 PM, Laxman Dewangan wrote:
Add SPI driver for NVIDIA's Tegra114 SPI controller. This controller
is different than the older SoCs SPI controller in
On Wed, 2013-03-27 at 12:58 +0100, Linus Walleij wrote:
> On Tue, Mar 12, 2013 at 6:37 AM, wrote:
>
> > From: Tien Hock Loh
> >
> > Adds a new driver for Altera soft GPIO IP. The driver is able to
> > do read/write and allows GPIO to be a interrupt controller.
> >
> > Tested on Altera GHRD on
On Thu, Mar 28, 2013 at 12:58:22PM +0530, Mugunthan V N wrote:
> --- a/scripts/checkpatch.pl
> +++ b/scripts/checkpatch.pl
> @@ -281,6 +281,7 @@ our $signature_tags = qr{(?xi:
> Tested-by:|
> Reviewed-by:|
> Reported-by:|
> + Suggested-by:|
> To:|
> Cc:
> )};
2013/3/28 Stephen Warren :
> On 03/25/2013 08:47 AM, Richard Genoud wrote:
>> If a new state is applied, the groups configured in the old state but
>> not in the new state are disabled.
>> If something goes wrong and the new state can't be applied, we have to
>> re-enable those groups.
>
> What is
Hi Michael,
This very small patch against man-pages-3.50 adds a description of the
way in which a shared file descriptor table, as created by the
CLONE_FILES flag of clone(2), is unshared when a process calls execve(2).
It's easy to see this from the source - there's an unshare_files()
call
On Thu, 2013-03-28 at 10:40 +, Arnd Bergmann wrote:
> On Thursday 28 March 2013, Ley Foon Tan wrote:
> > We will working on generic ABI for kernel and Glibc. This might take
> > some times.
>
> Ok. Don't let that hold you up from submitting the kernel patches
> for review though.
>
>
Hi
Am Dienstag, den 26.03.2013, 12:57 +0100 schrieb Peter Meerwald:
> regarding your patch against arch/arm/Kconfig:
>
> @@ -1215,7 +1215,7 @@ config ARM_ERRATA_430973
> depends on CPU_V7
> help
> This option enables the workaround for the 430973 Cortex-A8
> -
2013/3/28 Stephen Warren :
> On 03/25/2013 08:47 AM, Richard Genoud wrote:
>> If enabling a pin fails in pinctrl_select_state_locked(), all the
>> previous enabled pins have to be disabled to get back to the previous
>> state.
>
>> diff --git a/drivers/pinctrl/core.c b/drivers/pinctrl/core.c
>
>>
Hi Andrew,
thanks for taking care of these patches.
Am Mittwoch, den 27.03.2013, 15:27 -0700 schrieb Andrew Morton:
> On Wed, 20 Mar 2013 11:52:45 +0100 Philipp Zabel
> wrote:
>
> > This driver requests and remaps a memory region as configured in the
> > device tree. It serves memory from
Hi Mike,
On Wednesday 27 March 2013 21:45:56 Mike Turquette wrote:
> This fifth attempt at allowing calls to the clk api to reenter splits
> the last patch into two parts. The first patch abstracts out the
> locking details into some helper functions and converts all of the
> direct calls to the
On Thursday 28 March 2013, Ley Foon Tan wrote:
> We will working on generic ABI for kernel and Glibc. This might take
> some times.
Ok. Don't let that hold you up from submitting the kernel patches
for review though.
Arnd
--
To unsubscribe from this list: send the line "unsubscribe
Arnd, Olof,
A pull-request for 3.10 that is dedicated to the introduction of
Atmel's new Cortex-A5 based product: SAMA5D3.
This tag is built on top of the material already provided that resides on your
side in at91/cleanup branch.
The second revision of this pull-request includes a patch from
Guys,
how is this supposed to work?
#define SYSRQ_KEY_RESET_MAX 20 /* Should be plenty */
static unsigned short sysrq_reset_seq[SYSRQ_KEY_RESET_MAX];
...
unsigned short platform_sysrq_reset_seq[] __weak = { KEY_RESERVED };
...
static inline void sysrq_register_handler(void)
{
...
for
Well, according to kernel source the driver is 3.125 September 26, 2012
(drivers/net/ethernet/broadcom/tg3.c) while the latest source downloadable
from broadcom site is 3.124c Aug 14, 2012 so I guess that the driver in
vanilla kernel is the latest available.
> In data giovedì 28 marzo 2013
Hi!
On a whim, I tried fiddling with ALPHA_LEGACY_START_ADDRESS.
While this necessitates switching the system type to
GENERIC_ALPHA, it makes the whole thing work. I suspect the
change in segment size shifted stuff around enough to make the
DP264 layout a "legacy" one.
Regards,
Tobias
--
On Thu, Mar 28, 2013 at 2:09 PM, Jingoo Han wrote:
> Instead of using legacy suspend/resume methods, using newer dev_pm_ops
> structure allows better control over power management.
>
> Signed-off-by: Jingoo Han
> ---
> drivers/rtc/rtc-spear.c | 18 --
> 1 files changed, 8
Hi Laurent,
On Thu, Mar 28, 2013 at 3:40 PM, Laurent Pinchart
wrote:
> Hi Prabhakar,
>
> On Thursday 28 March 2013 15:36:11 Prabhakar Lad wrote:
>> On Thu, Mar 28, 2013 at 2:39 PM, Laurent Pinchart wrote:
>> > On Thursday 28 March 2013 14:20:32 Prabhakar lad wrote:
>> >> From: Lad, Prabhakar
>>
I am announcing the release of the 3.5.7.9 tree of stable patches.
This tree picks up the latest 3.5 stable release upstream, and add patches
on top that were later marked for stable but can't be added to 3.5, as
it is not anymore an stable series maintained upstream.
The tree is maintained by
Hi Prabhakar,
On Thursday 28 March 2013 15:36:11 Prabhakar Lad wrote:
> On Thu, Mar 28, 2013 at 2:39 PM, Laurent Pinchart wrote:
> > On Thursday 28 March 2013 14:20:32 Prabhakar lad wrote:
> >> From: Lad, Prabhakar
> >>
> >> Add pm_runtime support to the TI Davinci VPIF driver.
> >> Along side
Hi Laurent,
Thanks for the quick review!
On Thu, Mar 28, 2013 at 2:39 PM, Laurent Pinchart
wrote:
> Hi Prabhakar,
>
> Thanks for the patch.
>
> On Thursday 28 March 2013 14:20:32 Prabhakar lad wrote:
>> From: Lad, Prabhakar
>>
>> Add pm_runtime support to the TI Davinci VPIF driver.
>> Along
On Thursday 28 March 2013 03:20 PM, Russell King - ARM Linux wrote:
> On Wed, Mar 27, 2013 at 01:56:07PM -0700, Tony Lindgren wrote:
>> * Pali Rohár [130324 07:31]:
>>> it is possible to upstream errata 430973 workaround for RX-51?
>>
>> I think we should make the SMC handling a generic function
On 03/28/2013 10:23 AM, Axel Lin wrote:
Don't update info->update_val if write to the register fails.
Signed-off-by: Axel Lin
---
v2:
On the second thought, I think it's ok to update info->update_val when
regulator is disabled, the mode will change when the regulator is enabled.
That is
On Tue, Mar 26, 2013 at 05:09:59PM -0400, Douglas Gilbert wrote:
> On 13-03-26 03:27 PM, Johan Hovold wrote:
> > On Fri, Mar 15, 2013 at 06:37:12PM +0100, Nicolas Ferre wrote:
> >> On some revisions of AT91 SoCs, the RTC IMR register is not working.
> >> Instead of elaborating a workaround for
Add match table for device tree binding and dts binding doc.
Signed-off-by: Mischa Jonker
---
.../devicetree/bindings/serio/snps-arc_ps2.txt | 16
drivers/input/serio/arc_ps2.c | 14 --
2 files changed, 28 insertions(+), 2 deletions(-)
On Wed, Mar 27, 2013 at 02:09:18PM -0700, Tony Lindgren wrote:
> > + setup_timer(_timer, omap3_rom_idle_rng, 0);
> > + rng_clk = clk_get_sys("omap_rng", "ick");
Why is this using clk_get_sys when it should be using clk_get() with the
platform device?
--
To unsubscribe from this list: send the
On Wed, Mar 27, 2013 at 01:56:07PM -0700, Tony Lindgren wrote:
> * Pali Rohár [130324 07:31]:
> > it is possible to upstream errata 430973 workaround for RX-51?
>
> I think we should make the SMC handling a generic function for ARM.
>
> AFAIK just the SMC call numbering is different for various
Now that the arm core code calls irqchip_init, we can remove it from all
the machines that were using it.
Signed-off-by: Maxime Ripard
---
arch/arm/mach-bcm/board_bcm.c |1 -
arch/arm/mach-msm/board-dt-8660.c |1 -
arch/arm/mach-msm/board-dt-8960.c
More and more sub-architectures are using only the irqchip_init
function. Make the core code call this function if no init_irq field is
provided in the machine description to remove some boilerplate code.
Signed-off-by: Maxime Ripard
---
arch/arm/kernel/irq.c |6 +-
1 file changed, 5
- Original Message -
> From: "CAI Qian"
> To: "LKML"
> Cc: "linux-s390" , "Steve Best"
> , "Theodore Ts'o" ,
> linux-e...@vger.kernel.org
> Sent: Thursday, March 28, 2013 2:40:33 PM
> Subject: s390x: kernel BUG at fs/ext4/inode.c:1591!
>
> System hung when running xfstests-dev 013
On Wed, 27 Mar 2013, Mike Turquette wrote:
> Reentrancy into the clock framework is necessary for clock operations
> that result in nested calls to the clk api. A common example is a clock
> that is prepared via an i2c transaction, such as a clock inside of a
> discrete audio chip or a power
On Wed, 27 Mar 2013, Mike Turquette wrote:
> Create locking helpers for the global mutex and global spinlock. The
> definitions of these helpers will be expanded upon in the next patch
> which introduces reentrancy into the locking scheme.
This looks way better. Nitpick below.
> +static void
On Mon 2013-03-11 19:00:47, Grant Likely wrote:
> On Mon, Mar 11, 2013 at 1:05 PM, Olof Johansson wrote:
> > On Thu, Mar 07, 2013 at 01:50:54PM -0700, Stephen Warren wrote:
> >> On 03/07/2013 07:45 AM, Pavel Machek wrote:
> >> > Hi!
> >> >>> commit 499cd8298628eeabf0eb5eb6525d4faa0eec80d8
> >>
On Thu, 28 Mar 2013, Chris Zankel wrote:
> For Xtensa:
> Acked-by: Chris Zankel
>
> Thanks for going the extra mile and test-compiling it.
Though, the build fails later with:
arch/xtensa/kernel/built-in.o:(.init.literal+0x90): undefined reference to
`platform_pcibios_init'
check for '/cpus' presence before blindly dereferencing it:
[4.181793] Unable to handle kernel NULL pointer dereference at virtual
address 001c
[4.181793] pgd = c0004000
[4.181823] [001c] *pgd=
[4.181823] Internal error: Oops: 5 [#1] SMP ARM
[4.181823] Modules
Don't update info->update_val if write to the register fails.
Signed-off-by: Axel Lin
---
v2:
On the second thought, I think it's ok to update info->update_val when
regulator is disabled, the mode will change when the regulator is enabled.
Hi Bengt,
I just got your Ack for v1.
Can you review
Hi!
I have a kind of trivial suggestion for improving the kernel messages for
ext3-fs mounts to be more consistent and useful:
Most messages for ext3-mounting include the device, like:
kernel: [ 823.233892] EXT3-fs (dm-7): using internal journal
kernel: [ 823.233899] EXT3-fs (dm-7): mounted
Hi Prabhakar,
Thanks for the patch.
On Thursday 28 March 2013 14:20:32 Prabhakar lad wrote:
> From: Lad, Prabhakar
>
> Add pm_runtime support to the TI Davinci VPIF driver.
> Along side this patch replaces clk_get() with devm_clk_get()
> to simplify the error handling.
>
> Signed-off-by: Lad,
Am Donnerstag, den 28.03.2013, 10:54 +0800 schrieb Shawn Guo:
> On Wed, Mar 20, 2013 at 11:52:47AM +0100, Philipp Zabel wrote:
> > Signed-off-by: Philipp Zabel
> > Reviewed-by: Shawn Guo
> > Acked-by: Grant Likely
> > ---
> > Changes since v8:
> > - Changed device tree compatible string to
On 03/28/2013 09:40 AM, Axel Lin wrote:
This fixes 2 issues:
1. Don't update info->update_val if write to the register fails.
2. Don't update info->update_val if regulator is disabled, this avoid
inconsistent status between the register value and info->update_val.
Signed-off-by: Axel Lin
On 03/27/2013 08:01 PM, Arnd Bergmann :
> On Wednesday 27 March 2013, Nicolas Ferre wrote:
>
>>
>> Introduction of new Atmel Cortex-A5: SAMA5D3 family.
>> - Modify AT91 Kconfig to plit ARMv4/5 and ARMv7 arch
>> - Modify PMC driver
On 28 March 2013 13:35, Amit Daniel Kachhap wrote:
> This patch adds dvfs support for exynos5440 SOC. This soc has 4 cores and
> they scale at same frequency. The nature of exynos5440 clock controller is
> different from previous exynos controllers so not using the common exynos
> cpufreq
On Wed 27-03-13 15:19:24, Naoya Horiguchi wrote:
> On Wed, Mar 27, 2013 at 02:52:50PM +0100, Michal Hocko wrote:
> > On Tue 26-03-13 16:59:40, Aneesh Kumar K.V wrote:
> > > Naoya Horiguchi writes:
> > [...]
> > > > diff --git v3.9-rc3.orig/mm/memory-failure.c
> > > > v3.9-rc3/mm/memory-failure.c
On 03/23/2013 12:23 PM, Jens Axboe wrote:
> On Sat, Mar 23 2013, Aaron Lu wrote:
>> In August 2010, Jens and Alan discussed about "Runtime PM and the block
>> layer". http://marc.info/?t=12825910841=1=2
>> And then Alan has given a detailed implementation guide:
>>
From: Lad, Prabhakar
Add pm_runtime support to the TI Davinci VPIF driver.
Along side this patch replaces clk_get() with devm_clk_get()
to simplify the error handling.
Signed-off-by: Lad, Prabhakar
---
drivers/media/platform/davinci/vpif.c | 21 +++--
1 files changed, 11
On 2013-03-27 22:33, Bjorn Helgaas wrote:
> On Tue, Mar 26, 2013 at 4:55 PM, Matthew Garrett
> wrote:
>> On Tue, 2013-03-26 at 16:53 -0600, Bjorn Helgaas wrote:
>>
>>> I've been on vacation and didn't follow this closely, but it seems
>>> like this fixes a regression and should be merged before
On 03/27/2013 11:22 PM, Rajiv Andrade wrote:
> Hey Aaron,
>
> Sorry for the delay. Can you send us the dmesg output after setting
> loglevel=7 at boot time? Additionally, can you send us the TPM
> manufacturer model/version?
>
> # cat /sys/devices/pnp0/00\:0*/caps
>
> Adding Kent.
Thanks
This fix introduced a bug in SRIOV.
Should squash into it, the upstream commit:
f74d525bc973f2003b55b1f71f377e31fb5d3c8b - "net/mlx4_en: Disable RFS in
SRIOV virtual functions"
Thanks,
Amir
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
This fixes 2 issues:
1. Don't update info->update_val if write to the register fails.
2. Don't update info->update_val if regulator is disabled, this avoid
inconsistent status between the register value and info->update_val.
Signed-off-by: Axel Lin
---
drivers/regulator/ab8500.c | 41
Instead of using legacy suspend/resume methods, using newer dev_pm_ops
structure allows better control over power management.
Signed-off-by: Jingoo Han
---
drivers/rtc/rtc-stmp3xxx.c | 17 -
1 files changed, 8 insertions(+), 9 deletions(-)
diff --git
Instead of using legacy suspend/resume methods, using newer dev_pm_ops
structure allows better control over power management.
Signed-off-by: Jingoo Han
---
drivers/rtc/rtc-twl.c | 16 ++--
1 files changed, 6 insertions(+), 10 deletions(-)
diff --git a/drivers/rtc/rtc-twl.c
Instead of using legacy suspend/resume methods, using newer dev_pm_ops
structure allows better control over power management.
Signed-off-by: Jingoo Han
---
drivers/rtc/rtc-spear.c | 18 --
1 files changed, 8 insertions(+), 10 deletions(-)
diff --git a/drivers/rtc/rtc-spear.c
Instead of using legacy suspend/resume methods, using newer dev_pm_ops
structure allows better control over power management.
Signed-off-by: Jingoo Han
---
drivers/rtc/rtc-puv3.c | 27 ---
1 files changed, 12 insertions(+), 15 deletions(-)
diff --git
Instead of using legacy suspend/resume methods, using newer dev_pm_ops
structure allows better control over power management.
Signed-off-by: Jingoo Han
---
drivers/rtc/rtc-omap.c | 24 ++--
1 files changed, 10 insertions(+), 14 deletions(-)
diff --git
Instead of using legacy suspend/resume methods, using newer dev_pm_ops
structure allows better control over power management.
Signed-off-by: Jingoo Han
---
drivers/rtc/rtc-coh901331.c | 24 +++-
1 files changed, 11 insertions(+), 13 deletions(-)
diff --git
Instead of using legacy suspend/resume methods, using newer dev_pm_ops
structure allows better control over power management.
Signed-off-by: Jingoo Han
---
drivers/rtc/rtc-bfin.c | 18 ++
1 files changed, 6 insertions(+), 12 deletions(-)
diff --git a/drivers/rtc/rtc-bfin.c
Instead of using legacy suspend/resume methods, using newer dev_pm_ops
structure allows better control over power management.
Signed-off-by: Jingoo Han
---
drivers/rtc/rtc-at91sam9.c | 23 ++-
1 files changed, 10 insertions(+), 13 deletions(-)
diff --git
401 - 500 of 1168 matches
Mail list logo
