Hi Andrew,
Thanks for the detailed code review! I'll have a look at all the
problems you've pointed out, however, one quick question:
- ret = seq_printf(m, "eventfd-count: %16llx\n",
-(unsigned long long)ctx->count);
+ if (ctx->flags& EFD_MASK) {
+
smatch complains about the following functions:
panel.c:188:1: warning: symbol 'logical_inputs' was not declared. Should it be
static?
panel.c:569:6: warning: symbol 'old_keypad_profile' was not declared. Should it
be static?
panel.c:580:6: warning: symbol 'new_keypad_profile' was not declared.
On 02/15/2013 06:26 AM, Arnd Bergmann wrote:
Patch fe527ea5a "mfd: max8925: Support dt for backlight"
added a new function for DT probing but introduced a
build warning for the case where CONFIG_OF is disabled:
drivers/video/backlight/max8925_bl.c: In function 'max8925_backlight_probe':
acpi_numa is used to prevent srat table
being parsed, seems a little miss-named,
if 'noacpi' was specified by cmdline and
CONFIG_ACPI_NUMA was enabled, acpi_numa
will be operated directly from everywhere
it needed to disable/enable numa in acpi
mode which was a bad thing, so, try to
export a
This is a note to let you know that I have just added a patch titled
net: calxedaxgmac: throw away overrun frames
to the linux-3.5.y-queue branch of the 3.5.y.z extended stable tree
which can be found at:
according to ACPI SPEC v5.0, page 152,
5.2.16.1 Processor Local APIC/SAPIC Affinity Structure,
the last member of it is clock_domain.
Reviewed-by: Yasuaki Ishimatsu
Acked-by: David Rientjes
Signed-off-by: liguang
---
include/acpi/actbl1.h |2 +-
1 files changed, 1 insertions(+), 1
just do some trivial changes to make acpi's numa info
operation more cleaner.
ChangeLog
v3->v4
1.fix srat_disabled function
spotted by Yasuaki Ishimatsu
v2->v3
1. rebase on linux-next
2. bring back lost Makefile changes
spotted by David Rientjes
spotted by Yasuaki Ishimatsu
v1->v2
1.
srat table should present only on acpi domain,
seems mm/ is not the right place for it.
Reviewed-by: Yasuaki Ishimatsu
Signed-off-by: liguang
---
arch/x86/kernel/acpi/Makefile |1 +
arch/x86/kernel/acpi/srat.c | 198 +
arch/x86/mm/Makefile
process_driver.c include linux/acpi.h which already
include asm/acpi.h, so remove it.
Reviewed-by: Yasuaki Ishimatsu
Acked-by: David Rientjes
Signed-off-by: liguang
---
drivers/acpi/processor_driver.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git
On Thu, Feb 14, 2013 at 04:02:43PM +0100, Roger Pau Monné wrote:
> On 14/02/13 14:23, Konrad Rzeszutek Wilk wrote:
> > On Thu, Feb 14, 2013 at 11:12:09AM +0100, Roger Pau Monne wrote:
> >> With current persistent grants implementation we are not freeing the
> >> persistent grants after we
Signed-off-by: Tony Prisk
---
arch/arm/Kconfig |4 +-
arch/arm/boot/dts/wm8850-w70v2.dts | 15 +
arch/arm/boot/dts/wm8850.dtsi |7 +-
arch/arm/mach-vt8500/Kconfig |1 +
drivers/pinctrl/Kconfig| 10 +
drivers/pinctrl/Makefile |
Before I get all carried away and start filling in all the data for
this driver, I was hoping someone (or a few people) could review the
basic design in case it requires changes to the data structures.
This driver is based on pinctrl-bcm2835.c as it seems to be similar in
design. The pin
2013/2/8 Martin Sustrik :
> When implementing network protocols in user space, one has to implement
> fake user-space file descriptors to represent the sockets for the protocol.
[...]
> This patch implements new EFD_MASK flag which attempts to solve this problem.
[...]
> @@ -55,6 +64,9 @@ __u64
Hey Linus,
Please git pull one more tag (or if you haven't pulled the earlier one,
then just pull this one instead).
git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git
stable/for-linus-3.8-rc7-tag-two
This has two reverts for patches added in the v3.8 time-frame. They introduced
a
Hi all,
After merging the drm-intel tree, today's linux-next build (x86_64
allmodconfig) failed like this:
ERROR: "pm_vt_switch_unregister" [drivers/video/fb.ko] undefined!
I have dropped the tree for today.
--
Cheers,
Stephen Rothwells...@canb.auug.org.au
On Fri, Oct 05, 2012 at 11:16:12AM -0700, Anatol Pomozov wrote:
> Hi, AlViro
>
> Is any reason why this change is ignored? For me it looks like a
> straightforward bugfix.
>
> A little bit of context for this change. We at Google work on a test
> framework that shows how kernel behaves under
On Thu, Feb 14, 2013 at 6:09 PM, Hugh Dickins wrote:
>
> Which won't affect my case since I never enabled it.
Well, in theory, you may have the same bug Dave just made it easier to
trigger for himself with the forced config option.
In reality, your bug behavior differences were already big
On Thu, 14 Feb 2013, Dave Jones wrote:
> On Wed, Feb 13, 2013 at 11:56:25AM -0800, Linus Torvalds wrote:
> > On Wed, Feb 13, 2013 at 11:34 AM, Dave Jones wrote:
> > >
> > > My test was a loop of 100 suspend/resume cycles before calling something
> > > 'good'. The 'bad' cases all failed within
On Thu, Feb 14, 2013 at 5:15 PM, Dave Jones wrote:
>
> Given I never saw this on a Fedora kernel, just my self-built ones, I
> eventually
> gave up on bisecting code, and switched to bisecting config options.
> I should have started this way, as I figured it out within an hour.
>
> 3.7 merge
On 02/13/2013 01:08 PM, Eric W. Biederman wrote:
Bruno Prémont writes:
CCing containers list
On Fri, 08 February 2013 miny...@acm.org wrote:
From: Corey Minyard
The console redirect - ioctl(fd, TIOCCONS) - is not in a namespace,
thus a container can do a redirect and grab all the I/O on
Hi all
I tried to push an NMI button on HP DL380p Gen8's iLO4.
and then I received an IOCK NMI error.
When panic_on_io_nmi is set to 0, it seems that IOCK NMI error is sent
repeatedly.
In case of panic_on_io_nmi=1 and kdump is available,
the second kernel started. But IOCK NMI is sent
Frederic Weisbecker writes:
> Ingo,
>
> Please pull the new full dynticks cputime accounting code that
> can be found at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
> tags/full-dynticks-cputime-for-mingo
>
> My last concern is the dependency on
On Thu, Feb 14, 2013 at 12:05:01PM -0800, Greg Kroah-Hartman wrote:
> On Thu, Feb 14, 2013 at 01:55:12PM -0600, Ben Myers wrote:
> > > Ok, how about I never apply any xfs stable kernel patch, unless you send
> > > it to sta...@vger.kernel.org?
> >
> > Dave has made it clear that he doesn't want
On Fri, Feb 15, 2013 at 6:26 AM, Arnd Bergmann wrote:
> Patch fe527ea5a "mfd: max8925: Support dt for backlight"
> added a new function for DT probing but introduced a
> build warning for the case where CONFIG_OF is disabled:
>
> drivers/video/backlight/max8925_bl.c: In function
Hi Rafael,
Today's linux-next merge of the pm tree got conflicts in
drivers/acpi/scan.c and drivers/pci/hotplug/acpiphp_glue.c between
commits 668192b67820 ("PCI: acpiphp: Move host bridge hotplug to
pci_root.c") and be6d2867b4f6 ("PCI: acpiphp: Remove dead code for PCI
host bridge hotplug") from
On Wed, Feb 13, 2013 at 11:56:25AM -0800, Linus Torvalds wrote:
> On Wed, Feb 13, 2013 at 11:34 AM, Dave Jones wrote:
> >
> > My test was a loop of 100 suspend/resume cycles before calling something
> > 'good'. The 'bad' cases all failed within 10 cycles (usually 2-3).
>
> Considering that
[Adding dave jones to CC]
On Thu, Feb 14, 2013 at 5:35 PM, Thomas Gleixner wrote:
> On Thu, 14 Feb 2013, Tim Sander wrote:
>> > That's true, but w/o seing the OOM output I can't tell what's
>> > exhausting the memory.
>> When fuzzing the serial port one probably should switch of sysreq. It seems
On Wed, Jan 09, 2013 at 12:44:38AM -0500, Mikulas Patocka wrote:
> We maintain a history of kcopyd usage in variables io_period and
> total_period. The actual kcopyd activity is "(100 * io_period /
> total_period)" percent of time. If we exceed user-defined percentage
> threshold, we sleep.
On Thu, Feb 14, 2013 at 4:23 PM, Stephen Rothwell wrote:
> Hi Greg,
>
> On Thu, 14 Feb 2013 16:02:29 -0800 Greg KH wrote:
>> On Fri, Feb 15, 2013 at 10:55:19AM +1100, Stephen Rothwell wrote:
>> >
>> > Also, has someone checked to see if any of the CONFIG_ symbols that had a
>> > dependency on
On Tue, Feb 12, 2013 at 12:22 PM, Rafael J. Wysocki wrote:
> On Tuesday, February 12, 2013 11:11:23 AM Yinghai Lu wrote:
>> Peter Hurley found "irq 18 nobody cared" with pci-next, and dmesg has
>>
>> [8.983246] pci :00:1e.0: can't derive routing for PCI INT A
>> [8.983600] snd_ctxfi
On Fri, Feb 15, 2013 at 12:01:30AM +, Andrew Price wrote:
> Hi,
>
> On 03/02/13 18:39, Paul E. McKenney wrote:
> >On Wed, Jan 30, 2013 at 07:07:57PM +, Steven Whitehouse wrote:
> >>
> >>Abhi noticed that we were getting a complaint from the RCU subsystem
> >>about access of an RCU
On Fri, 2013-02-15 at 01:23 +0100, Rafael J. Wysocki wrote:
> On Thursday, February 14, 2013 11:45:27 PM Moore, Robert wrote:
> >
> > > -Original Message-
> > > From: Rafael J. Wysocki [mailto:r...@sisk.pl]
> > > Sent: Thursday, February 14, 2013 12:59 PM
> > > To: Moore, Robert
> > > Cc:
On Thu, 14 Feb 2013, Kent Yoder wrote:
> The following changes since commit e0751257a64ea10cca96ccb06522bfb10e36cb5b:
>
> ima: digital signature verification using asymmetric keys (2013-02-06
> 21:22:18 -0500)
>
> are available in the git repository at:
>
>
Hi Greg,
On Thu, 14 Feb 2013 16:02:29 -0800 Greg KH wrote:
>
> On Fri, Feb 15, 2013 at 10:55:19AM +1100, Stephen Rothwell wrote:
> >
> > The patch below is needed in the tty tree (which introduced CONFIG_TTY).
>
> Ok, now done.
Thanks.
> > Also, has someone checked to see if any of the
Now that we have i2c-arbitrator in place on bus 4 we can add the
sbs-battery driver. Future devices will be added onto bus 4 once
drivers are in good shape.
Signed-off-by: Doug Anderson
---
Changes in v2: None
arch/arm/boot/dts/exynos5250-snow.dts | 6 ++
1 file changed, 6 insertions(+)
We need to use the i2c-arbitrator to talk to any of the devices on i2c
bus 4 on exynos5250-snow so that we don't confuse the embedded
controller (EC). Add the i2c-arbitrator to the device tree. As we
add future devices (keyboard, sbs, tps65090) we'll add them on top of
this.
The arbitrated bus
On Thursday, February 14, 2013 11:45:27 PM Moore, Robert wrote:
>
> > -Original Message-
> > From: Rafael J. Wysocki [mailto:r...@sisk.pl]
> > Sent: Thursday, February 14, 2013 12:59 PM
> > To: Moore, Robert
> > Cc: Toshi Kani; ACPI Devel Maling List; LKML; Bjorn Helgaas; Jiang Liu;
> >
On Wed, 2013-02-13 at 15:28 +, Marc Zyngier wrote:
> Well, the spec clearly says that the registers reflect the endianess of
> the guest, and it makes sense: when performing the MMIO access, KVM
> needs to convert between host and guest endianess.
It's actually a horrible idea :-)
What does
From: Ben Chan
This patch makes wait_for_dump_helpers() not to abort piping the core
dump data when the crashing process has received any but a fatal signal
(SIGKILL). The rationale is that a crashing process may still receive
uninteresting signals such as SIGCHLD when its core dump data is
On Fri, Feb 15, 2013 at 10:55:19AM +1100, Stephen Rothwell wrote:
> Hi Greg,
>
> The patch below is needed in the tty tree (which introduced CONFIG_TTY).
Ok, now done.
> Also, has someone checked to see if any of the CONFIG_ symbols that had a
> dependency on TTY added are selected anywhere
Hi,
On 03/02/13 18:39, Paul E. McKenney wrote:
On Wed, Jan 30, 2013 at 07:07:57PM +, Steven Whitehouse wrote:
Abhi noticed that we were getting a complaint from the RCU subsystem
about access of an RCU protected list under the write side bit lock.
This patch adds additional annotation to
On Thu, Feb 14, 2013 at 2:54 PM, Andrew Morton
wrote:
> On Fri, 8 Feb 2013 09:11:17 +0100
> Martin Sustrik wrote:
>
>> When implementing network protocols in user space, one has to implement
>> fake user-space file descriptors to represent the sockets for the protocol.
>
>> if (count <
On Fri, 1 Feb 2013 15:41:39 -0600
"Philip J. Kelleher" wrote:
> From: Joshua H Morris
> Philip J Kelleher
>
> This patch includes the device driver for the IBM RamSan family
> of PCI SSD flash storage cards. This driver will inlcude support for the
> RamSan 70 and 80. The driver
Hi Greg,
The patch below is needed in the tty tree (which introduced CONFIG_TTY).
Also, has someone checked to see if any of the CONFIG_ symbols that had a
dependency on TTY added are selected anywhere else?
On Thu, 14 Feb 2013 10:55:06 -0800 Randy Dunlap wrote:
>
> On 02/14/13 10:45, Randy
On Thu, Feb 14, 2013 at 11:37 AM, Alex Williamson
wrote:
> A bus reset can trigger a presence detection change and result in a
> suprise hotplug. This is generally not what we want to happen when
> trying to reset a device. Disable the presence detection control on
> on bridges around bus
> -Original Message-
> From: Rafael J. Wysocki [mailto:r...@sisk.pl]
> Sent: Thursday, February 14, 2013 12:59 PM
> To: Moore, Robert
> Cc: Toshi Kani; ACPI Devel Maling List; LKML; Bjorn Helgaas; Jiang Liu;
> Yinghai Lu; Yasuaki Ishimatsu; Myron Stowe; linux-...@vger.kernel.org
>
On 02/14/2013 03:47 PM, Arnd Bergmann wrote:
> Patch c08e20d24 "arm: Add v7_invalidate_l1 to cache-v7.S"
> moves the v7_invalidate_l1 symbol out of imx/headsmp.S,
> which seems to cause a link error because it is now
> too far away from v7_cpu_resume when building an
> allyesconfig kernel.
Is the
Replace the for loop with a simple if.
Signed-off-by: Mandeep Singh Baines
CC: Oleg Nesterov
CC: Tejun Heo
CC: Andrew Morton
CC: Rafael J. Wysocki
CC: Ingo Molnar
---
kernel/exit.c | 7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/kernel/exit.c b/kernel/exit.c
Prevents hung_task detector from panicing the machine. This is also
needed to prevent this wait from blocking suspend.
(It doesnt' currently block suspend but it would once the next
patch in this series is applied.)
Signed-off-by: Mandeep Singh Baines
CC: Oleg Nesterov
CC: Tejun Heo
CC:
We shouldn't try_to_freeze if locks are held. Verified that
I get no lockdep warnings after applying this patch and
"vfork: don't freezer_count() for in-kernel users of CLONE_VFORK".
Signed-off-by: Mandeep Singh Baines
CC: Oleg Nesterov
CC: Tejun Heo
CC: Andrew Morton
CC: Rafael J. Wysocki
We don't need to call freezer_do_not_count() for in-kernel users
of CLONE_VFORK since exec will get called in bounded time.
We don't want to call freezer_count() for in-kernel users because
they may be holding locks. freezer_count() calls try_to_freeze().
We don't want to freeze an in-kernel user
On Wed, Feb 13, 2013 at 12:06:30PM +0530, Vineet Gupta wrote:
> Hi Al,
>
> linux-next contains ksignal conversion for some of the architectures. Are you
> planning to complete that in 3.9 merge window. The reason I ask is so that the
> newer architectures (arc/metag - for a likely 3.9 merge) can
Commit-ID: 95c9608478d639dcffc14ea47b31bff021a99ed1
Gitweb: http://git.kernel.org/tip/95c9608478d639dcffc14ea47b31bff021a99ed1
Author: H. Peter Anvin
AuthorDate: Thu, 14 Feb 2013 14:02:52 -0800
Committer: H. Peter Anvin
CommitDate: Thu, 14 Feb 2013 15:21:25 -0800
x86, mm: Move
On 02/14/2013 01:34 PM, Hiroshi Doyu wrote:
> Stephen Warren wrote @ Thu, 14 Feb 2013 21:15:28
> +0100:
>
>> Oh, and I don't think you updated e.g. nvidia,tegra20-car.txt to remove
>> the list of clocks.
>
> Not yet removed. I think that this could be done with the patch which
> allows kernel
Hi Daniel,
On Thu, 14 Feb 2013 15:19:53 +0100 Borislav Petkov wrote:
>
> On Thu, Feb 14, 2013 at 03:12:02PM +0100, Daniel Vetter wrote:
> >
> > Since about a year ago we've switched drm/i915 to buffer around 2
> > weeks worth of patches so that we can do decent QA before breaking
> > everyone's
Hey Jens,
Please git pull the following branch:
git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git stable/for-jens-3.8
which has fixes to the blkback that I hope you can push to Linus for 3.8.
The one that is quite vicious is the "xen-blkfront: drop the use of
On Thu, Feb 14, 2013 at 11:26:54PM +0100, Arnd Bergmann wrote:
> Patch eac036ef9e "ARM: shmobile: streamline mackerel SD and MMC devices"
> made the use of the sh_mmcif_device variable for mackarel optional,
> but the definition is always provided, causing a build warning.
>
>
On Thu, Feb 14, 2013 at 05:50:53PM -0500, Konrad Rzeszutek Wilk wrote:
> On Thu, Feb 14, 2013 at 09:18:04AM -0500, Josh Boyer wrote:
> > On Wed, Feb 13, 2013 at 3:50 PM, Konrad Rzeszutek Wilk
> > wrote:
> > > - CVE-2013-0228/XSA-42: x86/xen: don't assume %ds is usable in xen_iret
> > > for
On Sat, 02 Feb 2013 13:04:52 +0800
Jeff Liu wrote:
> The return statement after BUG() is invalid, move BUG() to the default choice
> of the switch.
>
> Signed-off-by: Jie Liu
> ---
> kernel/res_counter.c |5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git
Hi Alex,
I was just going to ask you whether your patch would "explain" why pciehp has
in my experience broken presence detection while acpiphp has not (on 3.7 kernel)
and whether the patch will fix it.
Some testing I have done in the past on 3.2 kernel and on 3.7.1, with no
fixes.
Maybe you
On Thursday 14 February 2013, Tony Lindgren wrote:
> I left it out intentionally as these are private to mach-omap2,
> and I'd like to simplify the indirect includes there further.
> So I'd rather just remove the duplicate soc.h from drm.c.
>
> If people really think this should be applied, I
On Wed, Feb 13, 2013 at 3:10 AM, Ingo Molnar wrote:
>
> Setting up Logical Volume Management: [ 13.14] BUG: spinlock lockup
> suspected on CPU#1, lvm.static/139
> [ 13.14] BUG: spinlock lockup suspected on CPU#1, lvm.static/139
> [ 13.14] lock: 0x97fe9fc0, .magic: dead4ead,
On Thu, Feb 14, 2013 at 11:26:56PM +0100, Arnd Bergmann wrote:
> Patch 16559ae "kgdb: remove #include from kgdb.h"
> removed an implicit inclusion of linux/platform_device.h
> In a number of places. This adds back explicit inclusions in a few
> more places I found.
>
> Signed-off-by: Arnd
On Thu, 14 Feb 2013, Arnd Bergmann wrote:
> The newly created omap_hwmod_reset.c is missing an
> include of linux/errno.h in commit c02060d8 "ARM:
> OMAP4+: AESS: enable internal auto-gating during
> initial setup". It still works in omap2_defconfig,
> but not in all other combinations.
>
>
On Thu, Feb 14, 2013 at 09:29:26AM -0800, Greg KH wrote:
> On Thu, Feb 14, 2013 at 09:02:47AM -0800, Dan Magenheimer wrote:
> > > From: Greg KH [mailto:gre...@linuxfoundation.org]
> > > Subject: Re: [PATCH] Various cleanups/fixes to zcache (v3).
> > >
> > > On Thu, Feb 14, 2013 at 08:56:01AM
* Arnd Bergmann [130214 14:51]:
> It is now possible to build the davinci vpss code
> on multiplatform kernels, which causes a problem
> since the driver tries to incude the davinci
> platform specific mach/hardware.h file. Fortunately
> that file is not required at all in the driver,
> so we can
On Thu, Feb 14, 2013 at 10:38 AM, wrote:
> From: Dirk Brandewie
>
> When intel_pstate is configured into the kernel it will become the
> perferred scaling driver for processors that is supports. Allow the
> user to override this by adding:
>intel_pstate=disable
> on the kernel command
* Arnd Bergmann [130214 14:51]:
> Patch a62a6e98 "ARM: OMAP2+: Disable code that currently does not work
> with multiplaform" makes the OMAP_MBOX_FWK option depend on !MULTIPLATFORM,
> which means we cannot simply select that symbol from OMAP_REMOTEPROC.
>
> Turning the 'select' into 'depends
* Arnd Bergmann [130214 14:51]:
> Commit e4c060db "ARM: OMAP: Split plat/cpu.h into local soc.h for
> mach-omap1 and mach-omap2" moved the bulk of "plat/cpu.h" into "cpu.h"
> but did not add an include guard for the new file that was present
> in the old one. There are cases where the file is
On Fri, 8 Feb 2013 09:11:17 +0100
Martin Sustrik wrote:
> When implementing network protocols in user space, one has to implement
> fake user-space file descriptors to represent the sockets for the protocol.
>
> While all the BSD socket API functionality for such descriptors may be faked
> as
From: Arnd Bergmann
Date: Thu, 14 Feb 2013 23:47:48 +0100
> With the support for ARM AM33xx in multiplatform kernels
> in 3.9, an older bug appears in ARM allmodconfig:
> When the cpsw driver is built as a module with cpdma
> support enabled, it uses symbols that the cpdma driver
> does not
On Thursday 14 February 2013, Fabio Estevam wrote:
> Bjorn has already sent a fix for this problem:
> http://www.spinics.net/lists/arm-kernel/msg224425.html
Ok, excellent.
The result seems to be identical, although patch is formatted
differently.
Acked-by: Arnd Bergmann
for Bjorn's patch.
--
* Arnd Bergmann [130214 14:51]:
> The newly created omap_hwmod_reset.c is missing an
> include of linux/errno.h in commit c02060d8 "ARM:
> OMAP4+: AESS: enable internal auto-gating during
> initial setup". It still works in omap2_defconfig,
> but not in all other combinations.
>
> Without this
On Thu, Feb 14, 2013 at 09:18:04AM -0500, Josh Boyer wrote:
> On Wed, Feb 13, 2013 at 3:50 PM, Konrad Rzeszutek Wilk
> wrote:
> > - CVE-2013-0228/XSA-42: x86/xen: don't assume %ds is usable in xen_iret
> > for 32-bit PVOPS.
>
> > Jan Beulich (1):
> > x86/xen: don't assume %ds is usable
Commit e4c060db "ARM: OMAP: Split plat/cpu.h into local soc.h for
mach-omap1 and mach-omap2" moved the bulk of "plat/cpu.h" into "cpu.h"
but did not add an include guard for the new file that was present
in the old one. There are cases where the file is indeed included
multiple times, probably by
MACH_MX31ADS_WM1133_EV1 already depends on REGULATOR_WM8350,
but that still allows REGULATOR_WM8350 to be a loadable
module. Depending on REGULATOR_WM8350 to be built-in
ensures we cannot create a broken configuration.
Without this patch, building allmodconfig results in:
It is now possible to build the davinci vpss code
on multiplatform kernels, which causes a problem
since the driver tries to incude the davinci
platform specific mach/hardware.h file. Fortunately
that file is not required at all in the driver,
so we can simply remove the #include statement.
With the support for ARM AM33xx in multiplatform kernels
in 3.9, an older bug appears in ARM allmodconfig:
When the cpsw driver is built as a module with cpdma
support enabled, it uses symbols that the cpdma driver
does not export.
Without this patch, building allmodconfig results in:
ERROR:
Patch 8a4da6e "arm: arch_timer: move core to drivers/clocksource"
moved a lot of code out of arch_timer.c, but ended up deleting
too much, which broke some configurations.
Obviously, include linux/errno.h is required to return error
values.
Without this patch, building allmodconfig results in:
On Thu, Feb 14, 2013 at 8:26 PM, Arnd Bergmann wrote:
> commit dd66cc2e1 "drm/pci: Use PCI Express Capability accessors"
> introduced the use of the pcie_capability_read_dword function
> in the drm_pci code, which is only defined when PCI is enabled.
> While most of the file is already hidden
Since the exynos DRM driver can now be built as a module on
all multiplatform configurations, an existing bug has
become visible: The exynos driver uses the drm_vm_open_locked
function that is not exported. The obvious solution is to
export that symbol.
Without this patch, building ARM
These are the patches I still need to cleanly build allyesconfig
and allmodconfig on arm-soc/for-next. Please review and provide
Acks where appropriate so we can add the fixes directly to the
branches that introduce the problems, or apply them directly
to a maintainer tree where appropriate.
The
ot used.
[1.008406] kvm: already loaded the other module
[1.206776] [ cut here ]
[1.211395] kernel BUG at mm/slab.c:2772!
[1.215400] invalid opcode: [#1] SMP DEBUG_PAGEALLOC
[1.220846] Modules linked in:
[1.223917] CPU 15
[1.225842] Pid: 1, comm
Patch c08e20d24 "arm: Add v7_invalidate_l1 to cache-v7.S"
moves the v7_invalidate_l1 symbol out of imx/headsmp.S,
which seems to cause a link error because it is now
too far away from v7_cpu_resume when building an
allyesconfig kernel.
If we move the v7_cpu_resume function from the .data
section
Patch a62a6e98 "ARM: OMAP2+: Disable code that currently does not work
with multiplaform" makes the OMAP_MBOX_FWK option depend on !MULTIPLATFORM,
which means we cannot simply select that symbol from OMAP_REMOTEPROC.
Turning the 'select' into 'depends on' ensures that all dependencies
are correct
The newly created omap_hwmod_reset.c is missing an
include of linux/errno.h in commit c02060d8 "ARM:
OMAP4+: AESS: enable internal auto-gating during
initial setup". It still works in omap2_defconfig,
but not in all other combinations.
Without this patch, building allmodconfig results in:
This v2 patch replaces both "aio: fix kioctx not being freed after
cancellation at exit time" and "aio: only suppress events from cancelled
kiocbs if free_ioctx() is in progress". Kent's feedback is indeed correct.
The recent changes overhauling fs/aio.c introduced a bug that results in the
On Thu, 14 Feb 2013, Tim Sander wrote:
> > That's true, but w/o seing the OOM output I can't tell what's
> > exhausting the memory.
> When fuzzing the serial port one probably should switch of sysreq. It seems
> as if there is a break send somehow and then it selects the OOM option.
> So when
commit dd66cc2e1 "drm/pci: Use PCI Express Capability accessors"
introduced the use of the pcie_capability_read_dword function
in the drm_pci code, which is only defined when PCI is enabled.
While most of the file is already hidden away behind an #ifdef
CONFIG_PCI, this function is not, and that
I hope that this is the right place, but I am using a Samsung Series 7 Gamer
(i7 + Nvidia) with proprietary graphics drivers. Using 3.7.0 when restarting
the machine or powering down, things work as expected. However, in 3.7.7 and
3.7.8 (which is what I have tested so far), the machine does not
Patch fe527ea5a "mfd: max8925: Support dt for backlight"
added a new function for DT probing but introduced a
build warning for the case where CONFIG_OF is disabled:
drivers/video/backlight/max8925_bl.c: In function 'max8925_backlight_probe':
drivers/video/backlight/max8925_bl.c:177:3: warning:
Patch 16559ae "kgdb: remove #include from kgdb.h"
removed an implicit inclusion of linux/platform_device.h
from the exynos framebuffer driver. This adds back the required
explicit header file inclusions.
Signed-off-by: Arnd Bergmann
Cc: Greg Kroah-Hartman
Cc: Ajay Kumar
Cc: Florian Tobias
commit 76cc18874 "thermal: rcar: add Device Tree support"
added device tree support for this driver, but also added
an instance of __devinitconst, which is no longer defined
Signed-off-by: Arnd Bergmann
Cc: Kuninori Morimoto
Cc: Zhang Rui
---
drivers/thermal/rcar_thermal.c | 2 +-
1 file
Patch eac036ef9e "ARM: shmobile: streamline mackerel SD and MMC devices"
made the use of the sh_mmcif_device variable for mackarel optional,
but the definition is always provided, causing a build warning.
arch/arm/mach-shmobile/board-mackerel.c:1120:31: warning: 'sh_mmcif_device'
defined
Patch 16559ae "kgdb: remove #include from kgdb.h"
removed an implicit inclusion of linux/platform_device.h
In a number of places. This adds back explicit inclusions in a few
more places I found.
Signed-off-by: Arnd Bergmann
Cc: Greg Kroah-Hartman
Cc: Florian Tobias Schandinat
---
I have tried building all ARM default configurations in
linux-next today, and found a number of obvious problems
that came in from somewhere other than the arm-soc tree
(I have a separate series for those).
Here are the fixes I came up with. Please apply or merge
into the original patch that
56bc911 "[media] s5p-fimc: Redefine platform data structure for fimc-is"
changed the bus_type member of struct fimc_source_info treewide, but
got one instance wrong in mach-s5pv210, which was evidently not
even build tested.
This adds the missing change to get s5pv210_defconfig to build again.
Patch 85a18198 "clk: sunxi: Use common of_clk_init() function"
removed the clk-sunxi.c file but left the Makefile entry, which
causes a build error in multi_v7_defconfig:
make[4]: *** No rule to make target `drivers/clk/clk-sunxi.o', needed by
`drivers/clk/built-in.o'.
The obvious fix is to
Patch "16559ae kgdb: remove #include from kgdb.h
caused assabet_defconfig to fail, since assabet.c did not
itself include linux/platform_device.h, although it needs it:
In file included from include/linux/mfd/ucb1x00.h:13:0,
from arch/arm/mach-sa1100/assabet.c:19:
On Thu, 7 Feb 2013 10:40:26 +0200 (EET)
Julian Anastasov wrote:
> > Another question about the sysctl_sync_qlen_max:
> > This variable is assigned as:
> >
> > ipvs->sysctl_sync_qlen_max = nr_free_buffer_pages() / 32;
> >
> > The function nr_free_buffer_pages actually means: counts of pages
> >
101 - 200 of 1149 matches
Mail list logo
