Hi Samuel,
The series needs to go via mfd or arm-soc tree as a whole. In case
you want to take it through mfd tree, here is my ack.
Acked-by: Shawn Guo
Otherwise, I can take it via arm-soc tree with your ack.
Regards,
Shawn
On Wed, Sep 05, 2012 at 10:57:12AM +0800, Dong Aisheng wrote:
>
On 09/05/2012 01:48 PM, Michael S. Tsirkin wrote:
> On Wed, Sep 05, 2012 at 12:22:58PM +0800, Asias He wrote:
>> On 09/04/2012 02:23 PM, Rusty Russell wrote:
>>> Kent Overstreet writes:
>>>
CONFIG_VIRTIO isn't exposed, everything else is supposed to select it
instead.
>>>
>>> This is a
At Wed, 5 Sep 2012 09:15:34 +0800,
Ming Lei wrote:
>
> On Wed, Sep 5, 2012 at 12:10 AM, Takashi Iwai wrote:
> > At Tue, 4 Sep 2012 23:52:15 +0800,
> > Ming Lei wrote:
> >>
> >> On Tue, Sep 4, 2012 at 9:06 PM, Takashi Iwai wrote:
> >> > Hi,
> >> >
> >> > as I've got recently a few bug reports
Hi Vojtech,
On Tue, Aug 14, 2012 at 12:11:54AM +0200, Vojtech Bocek wrote:
> Initial input event has not yet arrived in joydev_connect()
> where values are set, which means default values of input_absinfo
> are used for init event, not the actual values from joystick.
So what guarantees that
Should not do that in every calling of init_memory_mapping.
Actually in early time, only need do once.
Also move down early_memtest.
-v2: fix one early_memtest with 32bit by passing max_pfn_mapped instead.
Signed-off-by: Yinghai Lu
---
arch/x86/mm/init.c | 72
On Wed, Sep 05, 2012 at 12:22:58PM +0800, Asias He wrote:
> On 09/04/2012 02:23 PM, Rusty Russell wrote:
> > Kent Overstreet writes:
> >
> >> CONFIG_VIRTIO isn't exposed, everything else is supposed to select it
> >> instead.
> >
> > This is a slight mis-understanding. It's supposed to be
it should take physical address range that will need to be mapped.
and find_early_table_space should take range that pgt buff should be in.
Separate those two to reduce confusion.
Signed-off-by: Yinghai Lu
Reviewed-by: Pekka Enberg
---
arch/x86/mm/init.c | 39
So later could make it call split_mem_range...
Signed-off-by: Yinghai Lu
Reviewed-by: Pekka Enberg
---
arch/x86/mm/init.c | 116 ++--
1 files changed, 58 insertions(+), 58 deletions(-)
diff --git a/arch/x86/mm/init.c b/arch/x86/mm/init.c
index
memblock_x86_fill() could double memory array.
and we set max_pfn_mapped to 512M, so memory array could be around 512M.
So kdump will not get big range (like 512M) under 1024M.
Try to put it down under 1M, it could use about 4k or so.
Also we need this one when we try to only map ram range only
from init_memory_mapping, so make init_memory_mapping readable.
Suggested-by: Ingo Molnar
Signed-off-by: Yinghai Lu
Reviewed-by: Pekka Enberg
---
arch/x86/mm/init.c | 42 ++
1 files changed, 26 insertions(+), 16 deletions(-)
diff --git
detect if need to use 1G or 2M and store them in page_size_mask.
Only probe them one time.
Suggested-by: Ingo Molnar
Signed-off-by: Yinghai Lu
Reviewed-by: Pekka Enberg
---
arch/x86/include/asm/pgtable.h |1 +
arch/x86/kernel/setup.c|1 +
arch/x86/mm/init.c | 66
Only create mapping for E820_820 and E820_RESERVED_KERN.
Seperate calculate_table_space_size and find_early_page_table out with
init_memory_mapping.
For all ranges, will allocate page table one time, but init mapping
only for E820 RAM and E820_RESERVED_KERN.
Could be found at:
From: Jacob Shin
Update code that previously assumed pfns [ 0 - max_low_pfn_mapped ) and
[ 4GB - max_pfn_mapped ) were always direct mapped, to now look up
pfn_mapped ranges instead.
-v2: change applying sequence to keep git bisecting working.
so add dummy pfn_range_is_mapped(). - Yinghai
From: Jacob Shin
There could be cases where user supplied memmap=exactmap memory
mappings do not mark the region where the kernel .text .data and
.bss reside as E820_RAM, as reported here:
https://lkml.org/lkml/2012/8/14/86
Handle it by complaining, and adding the range back into the e820.
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/staging/ipack/ipack.c: In function 'ipack_device_read_id':
drivers/staging/ipack/ipack.c:291:2: error: implicit declaration of function
'ioread8'
From: Jacob Shin
Current logic finds enough space for direct mapping page tables from 0
to end. Instead, we only need to find enough space to cover mr[0].start
to mr[nr_range].end -- the range that is actually being mapped by
init_memory_mapping()
This patch also reportedly fixes suspend/resume
They all need to go over ram range in same sequence. So add shared function
to reduce duplicated code.
-v2: Change to walk_ram_ranges() according to Pekka Enberg.
Signed-off-by: Yinghai Lu
---
arch/x86/mm/init.c | 64 ++-
1 files changed, 23
so could reduce one loop.
Signed-off-by: Yinghai Lu
---
arch/x86/mm/init.c | 21 ++---
1 files changed, 14 insertions(+), 7 deletions(-)
diff --git a/arch/x86/mm/init.c b/arch/x86/mm/init.c
index 6663f61..e69f832 100644
--- a/arch/x86/mm/init.c
+++ b/arch/x86/mm/init.c
@@
from setup.c to mm/init.c
So could update all related calling together later
Signed-off-by: Yinghai Lu
Reviewed-by: Pekka Enberg
---
arch/x86/include/asm/init.h|1 -
arch/x86/include/asm/pgtable.h |2 +-
arch/x86/kernel/setup.c| 13 +
arch/x86/mm/init.c
From: Jacob Shin
Currently direct mappings are created for [ 0 to max_low_pfn<
Signed-off-by: Yinghai Lu
Reviewed-by: Pekka Enberg
---
arch/x86/include/asm/page_types.h |8 +--
arch/x86/kernel/setup.c |8 ++-
arch/x86/mm/init.c| 119
So we could put page table high again for 64bit.
Signed-off-by: Yinghai Lu
---
arch/x86/mm/init.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/x86/mm/init.c b/arch/x86/mm/init.c
index 15a6a38..cca9b7d 100644
--- a/arch/x86/mm/init.c
+++ b/arch/x86/mm/init.c
@@
On Wed, Sep 05, 2012 at 03:26:59PM +1000, Benjamin Herrenschmidt wrote:
> On Fri, 2012-08-24 at 13:01 +0530, Ananth N Mavinakayanahalli wrote:
> > From: Ananth N Mavinakayanahalli
> >
> > This is the port of uprobes to powerpc. Usage is similar to x86.
>
> Guys, can you do a minimum of build
Hi Linus,
these are some smallish GPIO regression fixes for the v3.6 series,
should be no big deal, please pull them in! Details in the tag.
Yours,
Linus Walleij
The following changes since commit d9875690d9b89a866022ff49e3fcea892345ad92:
Linux 3.6-rc2 (2012-08-16 14:51:24 -0700)
are
> -Original Message-
> From: Shi, Alex
> Sent: Wednesday, September 05, 2012 1:35 PM
> To: Jan Beulich
> Cc: Konrad Rzeszutek Wilk; t...@linutronix.de; mi...@redhat.com;
> linux-kernel@vger.kernel.org; h...@zytor.com; Ren, Yongjie
> Subject: Re: [PATCH] xen: fix logical error in tlb
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
net/ipv6/netfilter/nf_nat_l3proto_ipv6.c: In function 'nf_nat_ipv6_csum_recalc':
net/ipv6/netfilter/nf_nat_l3proto_ipv6.c:144:4: error: implicit declaration of
function 'csum_ipv6_magic'
On 08/25/2012 03:45 AM, Jan Beulich wrote:
On 24.08.12 at 20:17, Konrad Rzeszutek Wilk wrote:
>> On Fri, Aug 24, 2012 at 04:16:39PM +0100, Jan Beulich wrote:
>> On 24.08.12 at 10:55, Alex Shi wrote:
While TLB_FLUSH_ALL gets passed as 'end' argument to
flush_tlb_others(), the
On Fri, 2012-08-24 at 13:01 +0530, Ananth N Mavinakayanahalli wrote:
> From: Ananth N Mavinakayanahalli
>
> This is the port of uprobes to powerpc. Usage is similar to x86.
Guys, can you do a minimum of build testing ?
This one breaks due to uprobe_get_swbp_addr() being defined in both
asm and
On Wed, 2012-09-05 at 12:11 +1000, Michael Ellerman wrote:
> On Tue, 2012-09-04 at 10:05 -0600, David Ahern wrote:
> > On 9/4/12 4:32 AM, Maciek Borzecki wrote:
> > > When analyzing perf data from hosts of other architecture than one of the
> > > local
> > > host it's useful to call objdump that
Dave Chinner writes:
> On Wed, Aug 29, 2012 at 02:31:26AM -0700, Eric W. Biederman wrote:
>>
>> Dave thanks for taking the time to take a detailed look at this code.
>>
>> Dave Chinner writes:
>>
>> > On Tue, Aug 28, 2012 at 12:09:56PM -0700, Eric W. Biederman wrote:
>> > How did you
On Tue, Sep 04, 2012 at 09:33:31PM -0700, Eric W. Biederman wrote:
> Matthew Garrett writes:
> > The full implementation should trust keys that are trusted by the
> > platform, so it'd boot any kexec image you cared to sign. Or simply
> > patch this code out and rebuild and self-sign, or
From: Namhyung Kim
Like others, the numbers can be saved in a different endian format
than a host machine. Swap them if needed.
Cc: Robert Richter
Signed-off-by: Namhyung Kim
---
tools/perf/util/header.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/tools/perf/util/header.c
Hi,
This is a v2 of my perf header cleanup series. The v1 can be found
here [1].
Currently the perf header information is used only at initial setup
time and discarded. If it's saved we could reuse the information for
various purpose in the future.
The patch 1-3 are cleanups so that they can
From: Namhyung Kim
Number of events (evsels) in a evlist is kept on nr_entries field
so that we don't need to recalculate it.
Signed-off-by: Namhyung Kim
---
tools/perf/util/header.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/tools/perf/util/header.c
From: Namhyung Kim
The struct perf_header_info will preserve environment information at
the time of perf record. It can be accessed anytime after parsing a
perf.data file if needed.
Cc: Stephane Eranian
Cc: Robert Richter
Signed-off-by: Namhyung Kim
---
tools/perf/util/header.h | 24
From: Namhyung Kim
The event name can be set already by processing a event_desc data.
So check it before setting to prevent possible leak.
Signed-off-by: Namhyung Kim
---
tools/perf/util/header.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/perf/util/header.c
Hi Sakari,
Thanks for the review.
On Wednesday 05 September 2012 12:42 AM, Sakari Ailus wrote:
> Hi Prabhakar,
>
> Thanks for the patch. I've got a few comments below.
>
> On Tue, Sep 04, 2012 at 11:07:52AM +0530, Prabhakar Lad wrote:
>> From: Lad, Prabhakar
>>
>> add V4L2_CID_DPCM_PREDICTOR
From: Namhyung Kim
As the @feat arg is not used anywhere, get rid of it from the signature.
Cc: Stephane Eranian
Cc: Robert Richter
Signed-off-by: Namhyung Kim
---
tools/perf/util/header.c | 59
1 file changed, 25 insertions(+), 34
>From now on each feature information is processed and saved in perf
header so that it can be used wherever needed. The BRANCH_STACK
feature is an exception since it needs nothing to be done.
Cc: Stephane Eranian
Cc: Robert Richter
Signed-off-by: Namhyung Kim
---
tools/perf/util/header.c |
>From now on each feature information is processed and saved in perf
header so that it can be used for printing. The event desc and branch
stack features are not touched since they're not saved.
Cc: Stephane Eranian
Cc: Robert Richter
Signed-off-by: Namhyung Kim
---
tools/perf/util/header.c
Hi,
How can I see source files applied your patch?
(I'm very new to kernel development.)
You patch looks like a patch for another patch.
Masatake YAMATO
> Hi all,
>
> Today's linux-next merge of the net-next tree got a conflict in
> net/socket.c between commits f8a78429cc70 ("take descriptor
The platform specific configuration(general_config) is optional.
However, the DVS settings should be configured explicitly while
loading the driver.
This patch enables configuring the default DVS mode even though
the platform data is not defined.
Signed-off-by: Milo(Woogyom) Kim
---
On Wed, 5 Sep 2012 00:36:15 +0200
Stephen Warren wrote:
> From: Stephen Warren
>
> There's no need to place these defines into arch/arm/mach-tegra/include/.
> Move them into the SMMU driver to clean up mach-tegra, as a pre-requisite
> for single-zImage.
>
> Signed-off-by: Stephen Warren
>
The lp872x_check_dvs_validity() is used for checking DVS platform data.
If the DVS platform data is not defined, return as error code.
Now, this is unnecessary because the default DVS mode is set in this case.
Signed-off-by: Milo(Woogyom) Kim
---
drivers/regulator/lp872x.c | 28
The lp872x_set_dvs() is used for changing the DVS pin state.
This function works only when the DVS platform data is defined.
So don't assume that DVS data is always valid.
In case the platform data is not defined, the DVS data is set to NULL
for skipping the DVS pin control.
DVS selection
The lp872x driver has the DVS platform data which select the register address
of the BUCK voltage.
This patch enables updating the default DVS mode when the DVS platform data
is not defined.
Signed-off-by: Milo(Woogyom) Kim
---
drivers/regulator/lp872x.c | 15 ++-
1 file
This patch enables registering the regulator driver even though
the regulator_init_data is not defined in the platform side.
Signed-off-by: Milo(Woogyom) Kim
---
drivers/regulator/lp872x.c | 16 +++-
1 file changed, 7 insertions(+), 9 deletions(-)
diff --git
This patch-set removes the platform data dependency.
The LP872x driver should be run even if the platform data is not defined.
5 patches enable running the driver in case the LP8720/8725
platform data has no configuration.
[PATCH 1/5] regulator: lp872x: remove regulator platform data dependency
Hello, Dave.
On Wed, Sep 05, 2012 at 01:57:59PM +1000, Dave Chinner wrote:
> > But, yeah, this can't be solved by enlarging the stack size. The
> > upper limit is unbound.
>
> Sure, but recursion issue is isolated to the block layer.
>
> If we can still submit IO directly through the block
Hi, Feng Guang
On 09/05/2012 09:11 AM, Fengguang Wu wrote:
> Hi,
>
> Here is an old problem that happens also in 3.4. It's very unreliable:
> it may only happen once per 3000 boots..
>
> [ 10.968565] reboot: machine restart
> [ 10.983510] [ cut here ]
> [
Matthew Garrett writes:
> On Tue, Sep 04, 2012 at 03:12:52PM -0700, Eric W. Biederman wrote:
>> Matthew Garrett writes:
>> > The driving force behind this code right now is that our choices are
>> > either (1) do something like this, or (2) disable kexec entirely.
>>
>> Actually there is an
On 09/04/2012 02:23 PM, Rusty Russell wrote:
> Kent Overstreet writes:
>
>> CONFIG_VIRTIO isn't exposed, everything else is supposed to select it
>> instead.
>
> This is a slight mis-understanding. It's supposed to be selected by
> the particular driver, probably virtio_pci in your case.
Ease the deployment of clkdev by providing a default asm/clkdev.h for
use if the arch does not have an include/asm/clkdev.h.
Due to limitations in Kbuild we manually add clkdev.h to all
architectures that don't have one rather than having the header appear
by default.
Signed-off-by: Mark Brown
On Mon, Sep 03, 2012 at 06:02:06PM +0200, Philipp Zabel wrote:
> +static struct platform_driver sram_driver = {
> + .driver = {
> + .name = "sram",
> + .of_match_table = of_match_ptr(sram_dt_ids),
> + },
> + .probe = sram_probe,
> + .remove =
On Tue, Sep 04, 2012 at 11:26:33AM -0700, Tejun Heo wrote:
> Hello,
>
> On Tue, Sep 04, 2012 at 09:54:23AM -0400, Vivek Goyal wrote:
> > > Given that we are working around stack depth issues in the
> > > filesystems already in several places, and now it seems like there's
> > > a reason to work
Hi Paul,
Today's linux-next merge of the rcu tree got a conflict in
kernel/sched/core.c between commit f319da0c6894 ("sched: Fix load avg vs
cpu-hotplug") from the tip tree and commit ead504e5600e ("sched: Fix load
avg vs cpu-hotplug") from the rcu tree.
These are 2 slightly different versions
Dear Stephen Rothwell,
> Hi Mark,
>
> Today's linux-next merge of the spi-mb tree got a conflict in
> drivers/mmc/host/mxs-mmc.c between commit fc108d24d3a6 ("mmc: mxs-mmc:
> fix deadlock caused by recursion loop") from the mmc tree and commit
> 829c1bf40b92 ("mmc: spi: Pull out parts shared
Hi Greg,
Initially I pushed patch to linux-next with https://lkml.org/lkml/2012/8/29/40 .
In this patch, my mail id for "Signed-off-by" is correctly shown.
However as Felipe wanted me to push the patch to his branch, I synced to his
code base and pushed the patch.
Am still not sure, why my mail
On Tue, Sep 04, 2012 at 08:43:12AM -0700, Subodh Nijsure wrote:
> MX28 is ARM device. I removed following from my config and these
> warnings went away.
>
> CONFIG_CPU_IDLE=y
> CONFIG_CPU_IDLE_GOV_LADDER=y
> CONFIG_CPU_IDLE_GOV_MENU=y
>
There is no cpuidle implemented on imx28. I do not
Not sure, why it appeared like that.
However my actual mail id is: vbyravar...@nvidia.com
Shall I resend the patch, or this mail id can be added in the patch?
Thanks,
Venu
> -Original Message-
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Sent: Tuesday, September 04, 2012 10:51
On Wed, 2012-08-22 at 16:42 -0500, Kent Yoder wrote:
> On Wed, Aug 22, 2012 at 04:17:43PM -0500, Ashley Lai wrote:
> > This patch adds a new device driver to support IBM virtual TPM
> > (vTPM) for PPC64. IBM vTPM is supported through the adjunct
> > partition with firmware release 740 or higher.
Quoting Aristeu Rozanski (a...@redhat.com):
> The original model of device_cgroup is having a whitelist where all the
> allowed devices are listed. The problem with this approach is that is
> impossible to have the case of allowing everything but few devices.
>
> The reason for that lies in the
On Tue, Sep 04, 2012 at 04:51:00PM -0700, Randy Dunlap wrote:
> This build error still happens in linux-next of 20120904.
> Can we get the patch merged for linux-next?
Greg's the one managing extcon in -next.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel&q
Quoting Aristeu Rozanski (a...@redhat.com):
> Internally device_cgroup now uses a default rule (behavior) and an exception
> list and this interface reflects it.
>
> The new files, devices.behavior ('allow' or 'deny') and devices.exceptions map
> directly to the internal state.
>
> Also, update
Quoting Aristeu Rozanski (a...@redhat.com):
> This patch replaces the "whitelist" usage in the code and comments and replace
> them by exception list related information.
>
> v2:
> - fix checkpatch warnings
>
> Cc: Tejun Heo
> Cc: Li Zefan
> Cc: James Morris
> Cc: Pavel Emelyanov
> Cc: Serge
Quoting Aristeu Rozanski (a...@redhat.com):
> This patch converts the code to use kstrtou32() instead of simple_strtoul()
> which is deprecated. The real size of the variables are u32, so use kstrtou32
> instead of kstrtoul
>
> Signed-off-by: Aristeu Rozanski
phew, i'm afraid i'm not up on the
> -Original Message-
> From: David Laight [mailto:david.lai...@aculab.com]
> Sent: Tuesday, September 04, 2012 10:51 PM
> To: Xie Shaohui-B21989; jgar...@pobox.com; linux-...@vger.kernel.org
> Cc: linuxppc-...@lists.ozlabs.org; linux-kernel@vger.kernel.org; Bhartiya
> Anju-B07263
>
From: Dong Aisheng
The anatop registers are accessed via syscon now, no one will use
mfd anatop driver anymore, remove it.
Acked-by: Stephen Warren
Signed-off-by: Dong Aisheng
---
drivers/mfd/Kconfig|8 ---
drivers/mfd/Makefile |1 -
drivers/mfd/anatop-mfd.c | 124
From: Dong Aisheng
Include headfile for easy using.
Acked-by: Stephen Warren
Signed-off-by: Dong Aisheng
---
ChangeLog v4-v5:
* renamed: include/linux/fsl/imx6q-iomuxc-gpr.h ->
include/linux/mfd/syscon/imx6q-iomuxc-gpr.h
* a minor typo fix
---
arch/arm/boot/dts/imx6q.dtsi
From: Dong Aisheng
Using syscon to access anatop register.
Acked-by: Mark Brown
Acked-by: Stephen Warren
Signed-off-by: Dong Aisheng
---
ChangeLog v5->v6:
* of_node_put after using syscon_node_to_regmap
ChangeLog v4->v5:
* merge patch 3,4,5,6 to avoid break bisect.
ChangeLog v2->v3:
*
From: Dong Aisheng
Add regmap based syscon driver.
This is usually used for access misc bits in registers which does not belong
to a specific module, for example, IMX IOMUXC GPR and ANATOP.
With this driver, client can use generic regmap API to access registers
which are registered into syscon.
This patch series mainly adds an syscon driver which is used to access
general system controller registers like FSL IOMUXC GPR and ANATOP,
after that, we convert all the exist private access general registers code to
use
standard API from regmap to access registers.
Finally we remove the old mfd
Hi Mark,
Today's linux-next merge of the spi-mb tree got a conflict in
drivers/mmc/host/mxs-mmc.c between commit fc108d24d3a6 ("mmc: mxs-mmc:
fix deadlock caused by recursion loop") from the mmc tree and commit
829c1bf40b92 ("mmc: spi: Pull out parts shared between MMC and SPI") from
the spi-mb
Quoting Aristeu Rozanski (a...@redhat.com):
> The original model of device_cgroup is having a whitelist where all the
> allowed devices are listed. The problem with this approach is that is
> impossible to have the case of allowing everything but few devices.
>
> The reason for that lies in the
Quoting Aristeu Rozanski (a...@redhat.com):
> This function cleans all the items in a whitelist and will be used by the next
> patches.
>
> v2:
> - no changes
>
> Cc: Tejun Heo
> Cc: Li Zefan
> Cc: James Morris
> Cc: Pavel Emelyanov
> Cc: Serge Hallyn
Acked-by: Serge Hallyn
>
Quoting Aristeu Rozanski (a...@redhat.com):
> behavior will determine if the default policy is to deny all device access
> unless for the ones in the exception list.
>
> This variable will be used in the next patches to convert device_cgroup
> internally into a default policy + rules.
>
> v2:
>
On Thu, 2012-08-02 at 09:10 +0200, Jiri Kosina wrote:
> Directly comparing current->personality against PER_LINUX32 doesn't work
> in cases when any of the personality flags stored in the top three bytes
> are used.
>
> Directly forcefully setting personality to PER_LINUX32 or PER_LINUX
>
From: Michael Wang
DEADLOCK will be report while running a kernel with NUMA and LOCKDEP enabled,
the process of this fake report is:
kmem_cache_free()//free obj in cachep
-> cache_free_alien() //acquire cachep's l3 alien lock
-> __drain_alien_cache()
->
On Tue, Sep 04, 2012 at 10:18:48PM -0400, Don Dutile wrote:
> > /*
> >+ * Some devices may provide ROMs via a source other than the BAR
> >+ */
> >+if (pdev->rom&& pdev->romlen) {
> >+*size = pdev->romlen;
> >+return phys_to_virt((phys_addr_t)pdev->rom);
>
> -Original Message-
> From: devel [mailto:devel-boun...@linuxdriverproject.org] On Behalf Of KY
> Srinivasan
> Sent: Tuesday, September 04, 2012 8:29 PM
> To: Greg KH
> Cc: o...@aepfle.de; tho...@redhat.com; linux-kernel@vger.kernel.org;
> d...@redhat.com; a...@canonical.com;
To keep the KVP daemon code free of distro specific details, we invoke an
external script to retrieve the DHCP state. This is an example script that
was used to test the KVP code. This script has to be implemented in a Distro
specific fashion. For instance on distros that ship with Network Manager
Signed-off-by: Axel Lin
---
drivers/hid/hid-lcpower.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/hid/hid-lcpower.c b/drivers/hid/hid-lcpower.c
index c4fe9bd0..22bc14a 100644
--- a/drivers/hid/hid-lcpower.c
+++ b/drivers/hid/hid-lcpower.c
@@ -24,7 +24,7 @@
On 08/23/2012 12:36 PM, Matthew Garrett wrote:
Platforms may provide their own mechanisms for obtaining ROMs. Add support
for using data provided by the platform in that case.
Signed-off-by: Matthew Garrett
---
drivers/pci/rom.c | 11 +--
include/linux/pci.h | 2 ++
2 files
On Tue, 2012-09-04 at 10:05 -0600, David Ahern wrote:
> On 9/4/12 4:32 AM, Maciek Borzecki wrote:
> > When analyzing perf data from hosts of other architecture than one of the
> > local
> > host it's useful to call objdump that is part of a toolchain for that
> > architecture. Instead of calling
On Tue, 2012-08-28 at 13:35 -0700, Mark Brown wrote:
> Rather than requiring platforms to select the generic clock API to make
> it available make the API available as a user selectable option unless the
> user either selects HAVE_CUSTOM_CLK (if they have their own implementation)
> or selects
Hi all,
Today's linux-next merge of the net-next tree got a conflict in
net/socket.c between commits f8a78429cc70 ("take descriptor handling from
sock_alloc_file() to callers") and 32b529f92ea7 ("unexport sock_map_fd(),
switch to sock_alloc_file()") from the vfs tree and commit 600e177920df
From: liu chuansheng
Subject: [PATCH] drm_irq: Introducing the irq_thread support
For some GPUs, the irq handler need >1ms to handle the irq action.
And it will delay the whole system irq handler.
This patch is adding the irq thread support, it will make the drm_irq
interface more flexible.
This patch is for introducing the irq thread support in drm_irq.
Why we need irq thread in drm_irq code?
In our GPU system, the gpu interrupt handler need some time even > 1ms to
finish,
in that case, the whole system will stay in irq disable status. One case is:
when audio is playing, it
On 09/05/2012 09:15 AM, Tejun Heo wrote:
> On Sun, Sep 02, 2012 at 12:28:28AM +0800, Lai Jiangshan wrote:
>> Currently is single pass, we can wait on idle_done instead wait on
>> rebind_hold.
>> So we can remove rebind_hold and make the code simpler.
>
> As I wrote before, in general, I do like
At 09/05/2012 07:16 AM, Andrew Morton Wrote:
> On Mon, 03 Sep 2012 13:51:10 +0800
> Wen Congyang wrote:
>
+static void release_firmware_map_entry(struct kobject *kobj)
+{
+ struct firmware_map_entry *entry = to_memmap_entry(kobj);
+ struct page *page;
+
+ page =
Hello,
On Wed, Sep 05, 2012 at 09:28:38AM +0800, Lai Jiangshan wrote:
> I see that this patch's idea is same as mine but reuses
> @idle_rebind.cnt and @idle_rebind.done.
>
> I don't think it is consistent to avoid adding new field
> and to reuse old field for different purpose
It's not
On 09/05/2012 08:54 AM, Tejun Heo wrote:
> How about something like the following? This is more consistent with
> the existing code and as the fixes need to go separately through
> for-3.6-fixes, it's best to stay consistent regardless of the end
> result after all the restructuring. It's not
On Sat, Sep 01, 2012 at 06:09:35PM -0700, Josh Triplett wrote:
> On Thu, Aug 30, 2012 at 11:18:17AM -0700, Paul E. McKenney wrote:
> > From: "Paul E. McKenney"
> >
> > RCU grace-period initialization is currently carried out with interrupts
> > disabled, which can result in 200-microsecond
On Tue, Sep 4, 2012 at 5:28 AM, Liu Qiang-B32616 wrote:
>> Will this engine be coordinating with another to handle memory copies?
>> The dma mapping code for async_tx/raid is broken when dma mapping
>> requests overlap or cross dma device boundaries [1].
>>
>> [1]:
Hi Steven,
On 8/17/12, Steven Rostedt wrote:
> On Fri, 2012-08-17 at 09:03 -0300, Ezequiel Garcia wrote:
>> This patch splits trace event initialization in two stages:
>> * ftrace enable
>> * sysfs event entry creation
>>
>> This allows to capture trace events from an earlier point
>> by using
Hello, Lai.
On Wed, Sep 05, 2012 at 09:05:37AM +0800, Lai Jiangshan wrote:
> Thank you for accepting this one.
Thanks a lot for bearing with me. I was at kernel summit / plumbers
last week so my reviews were shaky. My apologies.
> I'm waiting for your comments on the other patches.
> I need
On Wed, Sep 5, 2012 at 12:10 AM, Takashi Iwai wrote:
> At Tue, 4 Sep 2012 23:52:15 +0800,
> Ming Lei wrote:
>>
>> On Tue, Sep 4, 2012 at 9:06 PM, Takashi Iwai wrote:
>> > Hi,
>> >
>> > as I've got recently a few bug reports regarding the stuck with
>> > request_firmware() in module_init of some
On Tue, Sep 4, 2012 at 5:01 PM, Flavio Leitner wrote:
> On Tue, 4 Sep 2012 15:25:45 -0700
> kdump works when using your branch:
>
> [0.00] Linux version 3.6.0-rc4-00012-g9389673 (r...@f17i7.rh) (gcc
> version 4.7.0 20120507 (Red Hat 4.7.0-5) (GCC) ) #1 SMP Tue Sep 4 20:36:43
> BRT 2012
On Sun, Sep 02, 2012 at 12:28:28AM +0800, Lai Jiangshan wrote:
> Currently is single pass, we can wait on idle_done instead wait on
> rebind_hold.
> So we can remove rebind_hold and make the code simpler.
As I wrote before, in general, I do like this approach; however, the
implementation in this
Hello, Lai.
On Sun, Sep 02, 2012 at 12:28:22AM +0800, Lai Jiangshan wrote:
> If hotplug code grabbed the manager_mutex and worker_thread try to create
> a worker, the manage_worker() will return false and worker_thread go to
> process work items. Now, on the CPU, all workers are processing work
On Fri, Aug 31, 2012 at 12:07:33PM -0700, Josh Triplett wrote:
> On Thu, Aug 30, 2012 at 02:05:18PM -0700, Paul E. McKenney wrote:
> > From: Frederic Weisbecker
> >
> > RCU currently insists that only idle tasks can enter RCU idle mode, which
> > prohibits an adaptive tickless kernel (AKA nohz
1 - 100 of 1298 matches
Mail list logo
