Hi Andrew,
Today's linux-next merge of the akpm tree got a conflict in mm/memory.c
between changes in commits from the tip tree and commit "mm: thp: set the
accessed flag for old pages on access fault" from the akpm tree.
I fixed it up (I think - see below) and can carry the fix as necessary
(no
Thanks Tushar,
On 7 December 2012 17:33, Tushar Behera wrote:
> On 12/03/2012 05:46 PM, Giridhar Maruthy wrote:
>> This patch adds slave support to i2c. The dt entry i2c-mode
>> decides at probe time if the controller needs to work in
>> slave mode and the controller is accordingly programmed.
>>
Hi Andrew,
Today's linux-next merge of the akpm tree got conflicts in mm/migrate.c
and include/linux/migrate.h between commits 070059b28578 ("mm/compaction:
Move migration fail/success stats to migrate.c") and 2d85cca46951
("mm/migrate: Add a tracepoint for migrate_pages") from the tip tree and
co
On Thursday, December 06, 2012 4:22 AM, Russell King - ARM Linux wrote
> On Wed, Dec 05, 2012 at 07:20:00PM +0100, Marko Katić wrote:
> > On Wed, Dec 5, 2012 at 10:30 AM, Russell King - ARM Linux
> > wrote:
> > > On Wed, Dec 05, 2012 at 09:59:07AM +0900, Jingoo Han wrote:
> > >> - if (gpio_is_
Hi Andrew,
Today's linux-next merge of the akpm tree got a conflict in
mm/mempolicy.c between commit d9f1eb872704 ("numa, mempolicy: Improve
CONFIG_NUMA_BALANCING=y OOM behavior") from the tip tree and commit "mm,
mempolicy: remove duplicate code" from the akpm tree.
I can't tell if the akpm tree
This is the documentation for the Xillybus driver. It's intended for kernel
maintainers, since actual users will most likely rely on other documentation.
Signed-off-by: Eli Billauer
---
Documentation/misc-devices/xillybus.txt | 402 +++
1 files changed, 402 insertion
Hi Andrew,
Today's linux-next merge of the akpm tree got a conflict in
mm/huge_memory.c between commit 2083d67027ad ("mm/mempolicy: Implement
change_prot_numa() in terms of change_protection()") from the tip, tree
and commit "thp: change_huge_pmd(): make sure we don't try to make a page
writable"
07.12.2012 20:52, J. Bruce Fields пишет:
On Tue, Dec 04, 2012 at 04:50:16PM +0300, Stanislav Kinsbursky wrote:
diff --git a/fs/nfsd/nfssvc.c b/fs/nfsd/nfssvc.c
index 21cba3d..6448391 100644
--- a/fs/nfsd/nfssvc.c
+++ b/fs/nfsd/nfssvc.c
@@ -334,10 +334,9 @@ static int nfsd_get_default_max_blksize
There is 4 situations in the function:
1, no task allowed group;
so min_load = ULONG_MAX, this_load = 0, idlest = NULL
2, only local group task allowed;
so min_load = ULONG_MAX, this_load assigned, idlest = NULL
3, only non-local task group allowed;
so min_load assigned, thi
This reverts commit f4e26b120b9de84cb627bc7361ba43cfdc51341f
Signed-off-by: Alex Shi
---
include/linux/sched.h |8 +---
kernel/sched/core.c |7 +--
kernel/sched/fair.c | 13 ++---
kernel/sched/sched.h |9 +
4 files changed, 5 insertions(+), 32 deletions
This patch add power aware scheduling in fork/exec/wake. It try to
select cpu from the busiest while still has utilization group. That's
will save power for other groups.
The trade off is adding a power aware statistics collection in group
seeking. But since the collection just happened in power s
This patch add the power aware scheduler knob into sysfs:
$cat /sys/devices/system/cpu/sched_policy/available_sched_policy
performance powersaving balance
$cat /sys/devices/system/cpu/sched_policy/current_sched_policy
powersaving
This means the using sched policy is 'powersaving'.
User can chang
In power aware scheduling, we don't care load weight and
want not to pull tasks just because local group has capacity.
Because the local group maybe no tasks at the time, that is the power
balance hope so.
Signed-off-by: Alex Shi
---
kernel/sched/fair.c |6 +-
1 files changed, 5 insertio
This patch enabled the power aware consideration in load balance.
As mentioned in the power aware scheduler proposal, Power aware
scheduling has 2 assumptions:
1, race to idle is helpful for power saving
2, shrink tasks on less sched_groups will reduce power consumption
The first assumption make
When active task number in sched domain wave around the powersaving
scheduling creteria, scheduling will thresh between the powersaving
balance and performance balance, bring unnecessary task migration.
The typical benchmark generate the issue is 'make -j x'.
To remove such issue, introduce a u64
In power balance, we hope some sched groups are fully empty to save
CPU power of them. So, we want to move all tasks from them.
Signed-off-by: Alex Shi
---
kernel/sched/fair.c |7 +--
1 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
If the cpu condition is suitable for power balance, power_lb
will be set, perf_lb will be clean. If the condition is suitable for
performance balance, their value will will set oppositely.
If the domain is suitable for power balance, but balance should not
be down by this cpu, both of perf_lb and
The cpu's utilization is to measure how busy is the cpu.
util = cpu_rq(cpu)->avg.runnable_avg_sum
/ cpu_rq(cpu)->avg.runnable_avg_period;
Since the util is no more than 1, we use its percentage value in later
caculations.
Considering there are interval between balancing, i
Guess the search cpu from bottom to up in domain tree come from
commit 3dbd5342074a1e sched: multilevel sbe sbf, the purpose is
balancing over tasks on all level domains.
This balancing cost much if there has many domain/groups in a large
system. And force spreading task among different domains ma
New task has no runnable sum at its first runnable time, that make
burst forking just select few idle cpus to put tasks.
Set initial load avg of new forked task as its load weight to resolve
this issue.
Signed-off-by: Alex Shi
---
include/linux/sched.h |1 +
kernel/sched/core.c |2 +-
They are the base values in load balance, update them with rq runnable
load average, then the load balance will consider runnable load avg
naturally.
Signed-off-by: Alex Shi
---
kernel/sched/core.c |4 ++--
kernel/sched/fair.c |4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
di
Except using runnable load average in background, move_tasks is also
the key functions in load balance. We need consider the runnable load
average in it in order to the apple to apple load comparison.
Signed-off-by: Alex Shi
---
kernel/sched/fair.c | 11 ++-
1 files changed, 10 inserti
Current scheduler behavior is just consider the for larger performance
of system. So it try to spread tasks on more cpu sockets and cpu cores
To adding the consideration of power awareness, the patchset adds
2 kinds of scheduler policy: powersaving and balance, the old scheduling
was taken as perf
We need initialize the se.avg.{decay_count, load_avg_contrib} to zero
after a new task forked.
Otherwise random values of above variable cause mess when do new task
enqueue:
enqueue_task_fair
enqueue_entity
enqueue_entity_load_avg
Signed-off-by: Alex Shi
---
kernel/sched/
This patchset base on tip/sched/core tree temporary, since it is more
steady than tip/master. and it's easy to rebase on tip/master.
It includes 3 parts changes.
1, simplified fork, patch 1~4, that simplified the fork/exec/wake log in
find_idlest_group and select_task_rq_fair. it can increase 10
If parent sched domain has no task allowed cpu find. neither find in
it's child. So, go out to save useless checking.
Signed-off-by: Alex Shi
---
kernel/sched/fair.c |6 ++
1 files changed, 2 insertions(+), 4 deletions(-)
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index b40b
Hi,
This is a new version of hists link patchset.
In this version, I've addressed Jiri's comment and added his acked-by's.
Also added a comment on hist_entry__cmp() in order to clarify the reason
of the change of the argument order exchange as Arnaldo suggested.
Hoping that I didn't miss any of r
From: Namhyung Kim
There's no reason to run hists_compute_resort() using output tree.
Convert it to use internal tree so that it can remove unnecessary
_output_resort.
Cc: Stephane Eranian
Acked-by: Jiri Olsa
Signed-off-by: Namhyung Kim
---
tools/perf/builtin-diff.c | 31
From: Namhyung Kim
As they are used from diff and event group report, add a test case to
verify their behaviors.
In this test I made a fake machine and two evsel. Each evsel got 10
samples (so hist entries) - 5 are common and the rests are not. So
after hists__match() both of them will have 5
From: Namhyung Kim
For matching and/or linking hist entries, they need to be sorted by
given sort keys. However current hists__match/link did this on the
output trees, so that the entries in the output tree need to be resort
before doing it.
This looks not so good since we have trees for collec
From: Namhyung Kim
When comparing entries for collapsing put the given entry first, and
then the iterated entry. This is not the case of hist_entry__cmp()
when called if given sort keys don't require collapsing. So change
the order for the sake of consistency. It will be required for
matching
Hi Andrew,
Today's linux-next merge of the akpm tree got a conflict in mm/mprotect.c
between commit ("2083d67027ad") from the tip tree and commit "thp:
change split_huge_page_pmd() interface" from the akpm tree.
I fixed it up (see below) and can carry the fix as necessary (no action
is required)
Mark Brown opensource.wolfsonmicro.com> writes:
[...]
> Binding documenation is mandatory for any new OF properties, please add
> this.
Patch 3/3 of this series adds documentation for the max77686-opmode property.
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
It is impossible to miss a task allowed cpu in a eligible group.
And since find_idlest_group only return a different group which
excludes old cpu, it's also imporissible to find a new cpu same as old
cpu.
Signed-off-by: Alex Shi
---
kernel/sched/fair.c |5 -
1 files changed, 0 insertion
Adding missed Cc's
On Mon, Dec 10, 2012 at 1:49 PM, Abhilash Kesavan
wrote:
> Mark Brown opensource.wolfsonmicro.com> writes:
>
> [...]
>> Binding documenation is mandatory for any new OF properties, please add
>> this.
> Patch 3/3 of this series adds documentation for the max77686-opmode proper
On Sun, Dec 09, 2012 at 11:17:09PM +0200, Kirill A. Shutemov wrote:
> On Sun, Dec 09, 2012 at 08:36:31PM +, Mel Gorman wrote:
> > Either way, last night I applied a patch on top of latest tip/master to
> > remove the nr_cpus_allowed check so that numacore would be enabled again
> > and tested t
On Mon, Dec 10, 2012 at 10:37:10AM +0530, Srikar Dronamraju wrote:
> >
> > Either way, last night I applied a patch on top of latest tip/master to
> > remove the nr_cpus_allowed check so that numacore would be enabled again
> > and tested that. In some places it has indeed much improved. In others
Hi Andrew,
After merging the akpm tree, today's linux-next build (x86_64
allmodconfig) failed like this:
mm/migrate.c: In function 'migrate_misplaced_transhuge_page_put':
mm/migrate.c:1666:2: error: incompatible type for argument 3 of
'update_mmu_cache_pmd'
arch/x86/include/asm/pgtable.h:792:20:
On Sun, Dec 09, 2012 at 01:31:50AM +0100, Cyril Roelandt wrote:
> On 12/05/2012 08:11 AM, Dan Carpenter wrote:
> >On Wed, Dec 05, 2012 at 02:22:02AM +0100, Cyril Roelandt wrote:
> >>In r8711_wx_get_wap(), make sure we do not call memcpy() on a memory area
> >>that
> >>has just been zeroed by a cal
We have quite a complicated hurdle we need to over-come, and this
patch aims to rectify it the best way possible. We're attempting
to move some MMC related voltage level-shifters out of platform
code and over to the new GPIO Regulator framework. The aim of this
change is to void the requirement for
The GPIO controlled MMCI regulator used on the ux5x0 boards takes
100us to settle. There's already a binding to provide such
information. Let's make use of it.
Signed-off-by: Lee Jones
---
arch/arm/boot/dts/dbx5x0.dtsi |1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/boot/dts/dbx5
Now MMCI on/off functionality is using the regulator framework
from the MMCI driver, there is no need to keep the ios_handler
laying around, duplicating functionality. So we're removing it.
Signed-off-by: Lee Jones
---
arch/arm/mach-ux500/board-mop500-sdi.c | 52 ---
In an effort to move platform specific GPIO controlled regulators
out from platform code we've created a new mechanism to specify
them from within the MMCI driver using the supply name 'vmmc-ios'.
For that to happen when booting device tree, we need to supply it
in the MMCI (SDI) node.
Signed-off-
To prevent lots of unnecessary call-backs into platform code, we're
now using the GPIO regulator framework to control the 'enable' (en)
and 'voltage select' (vsel) GPIO pins which in turn control the
MMCI's secondary regulator settings. This already works with Device
Tree, but when booting with ATA
If a regulator is specified as always-on, then it can't have an
enable/disable pin, as it can't be turned off.
Cc: Mark Brown
Signed-off-by: Lee Jones
---
drivers/regulator/gpio-regulator.c |9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/drivers/regulator/gpio-reg
The voltages for the MMCI GPIO controlled voltage regulation differ
depending on who you believe and where you pick the information up
from. More recent internal code suggests that the true upper voltage
from the shifter is actually v3.3, instead of the previously
indicated v2.9. Let's mirror that
Correct a typo in the Device Tree source file, where instead of
specifying property 'enable-gpio', which the driver is expecting
we specified 'gpio-enable' instead.
Signed-off-by: Lee Jones
---
arch/arm/boot/dts/hrefprev60.dts |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
If not specified, the GPIO control bit is inverted by default i.e.
low-enable and high-disable. This is not the case with the MMCI
regulator, hence it will turn on during a disable and off when
regulator_enable() is invoked.
Signed-off-by: Lee Jones
---
arch/arm/boot/dts/dbx5x0.dtsi |2 ++
1
Hi Andrew,
After merging the akpm tree, today's linux-next build (x86_64
allmodconfig) failed like this:
ERROR: "do_take_over_console" [drivers/video/console/fbcon.ko] undefined!
Caused by commit "fb: rework locking to fix lock ordering on takeover".
I have reverted that commit (and the followi
The main purpose of this patch-set is to move the MMCI's secondary
(platform specific) regulator implementation out of platform code
and into use the regulator frame-work. A few bugs were encountered
along the way, so we've fixed those too and bundled them in for
completeness.
arch/arm/boot/dts/d
The cond-statement of this particular for() loop will always be
true as long as at least one voltage-shifting GPIO is present.
If it wasn't for the break below, we'd be stuck in a forever loop.
This patch inserts the correct cond-statement into the statement.
Cc: Mark Brown
Signed-off-by: Lee Jon
There are currently two instances of the ios_handler being used.
Both of which mearly toy with some regulator settings. Now there
is a GPIO regulator API, we can use that instead, and lessen the
per platform burden. By doing this, we also become more Device
Tree compatible.
Cc: Chris Ball
Cc: Rus
If it's possible for gpio_set_value to sleep, we should be using
the *_cansleep call instead. This patch fixes multiple warnings
from gpiolib.
Cc: Mark Brown
Signed-off-by: Lee Jones
---
drivers/regulator/gpio-regulator.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
On Fri, Dec 07, 2012 at 07:20:10AM -0600, Ed Cashin wrote:
> On Dec 7, 2012, at 1:19 AM, Dan Carpenter wrote:
>
> > We should return NULL on failure instead of returning a freed pointer.
> >
> > Signed-off-by: Dan Carpenter
> >
> > diff --git a/drivers/block/aoe/aoedev.c b/drivers/block/aoe/aoe
On 09/12/12 18:30, Anca Emanuel wrote:
> Oh, you need more testing with ARM Nexus 7 ?
If that's an offer, feel free to drop in on #upstart / #ubuntu-arm and get
involved ;)
>
> On Sun, Dec 9, 2012 at 8:28 PM, Anca Emanuel wrote:
>> Do will see this in Raring ?
>> And when ?
This week - we're cur
On 12/6/2012 1:38 PM, Manjunathappa, Prakash wrote:
> Hi Tomi,
>
> On Wed, Oct 31, 2012 at 10:52:59, Manjunathappa, Prakash wrote:
>> Hi,
>>
>> On Wed, Oct 31, 2012 at 21:26:08, Pantelis Antoniou wrote:
>>> This driver can be used for AM33xx devices, like the popular beaglebone.
>>>
>>> Signed-o
Hi Bjorn,
After merging the pci tree, today's linux-next build (powerpc
ppc44x_defconfig) produced this warning:
drivers/pci/rom.c: In function 'pci_map_rom':
drivers/pci/rom.c:125:23: warning: cast from pointer to integer of different
size [-Wpointer-to-int-cast]
Introduced by commit 84c1b80e3
On Saturday 08 December 2012 01:47:21 Hans J. Koch wrote:
> On Fri, Dec 07, 2012 at 05:00:54PM +0200, Vitalii Demianets wrote:
> > > On second thought, we can't call enable_irq()/disable_irq()
> > > unconditionally because of the potential disable counter
> > > (irq_desc->depth) disbalance. That's
On Fri, Dec 07, 2012 at 04:15:39PM +0530, Srikar Dronamraju wrote:
>
> Got a chance to run autonuma-benchmark on a 8 node, 64 core machine.
> the results are as below. (for each kernel I ran 5 iterations of
> autonuma-benchmark)
>
Thanks, a test of v10 would also be appreciated. The differences
Hi
Here is a minor hardware ID addition to sdhci-acpi.
Please consider this for Linux 3.8, in which case it must go via
Rafael's linux-pm tree because that is where the new driver is.
Adrian Hunter (1):
mmc: sdhci-acpi: enable runtime-pm for device HID INT33C6
drivers/mmc/host/sdhci-acp
On 2012/12/10 16:33, Wanpeng Li wrote:
> On Fri, Dec 07, 2012 at 02:11:02PM -0800, Andrew Morton wrote:
>> On Fri, 7 Dec 2012 16:48:45 +0800
>> Xishi Qiu wrote:
>>
>>> On x86 platform, if we use "/sys/devices/system/memory/soft_offline_page"
>>> to offline a
>>> free page twice, the value of mce
sdhci-acpi supports ACPI devices which have compatibility ID
PNP0D40, however it is not possible to know if those devices
will all work correctly with runtime-pm, so that must be configured
per hardware ID.
For INT33C6, several related quirks, capabilities and flags are set:
MMC_CAP_NONRE
Changelog:
There are some changes from Marcelo and Gleb's review, thank you all!
- access indirect_shadow_pages in the protection of mmu-lock
- fix the issue when unhandleable instruction access on large page
- add a new test case for large page
The current reexecute_instruction can not well detec
Then, no mmu specified code exists in the common function and drop two
parameters in set_spte
Signed-off-by: Xiao Guangrong
---
arch/x86/kvm/mmu.c | 47 ---
arch/x86/kvm/paging_tmpl.h | 25 ++
2 files changed, 33 insertions(
On Mon, Dec 10, 2012 at 09:29:17AM +0200, Jani Nikula wrote:
> On Fri, 07 Dec 2012, Tim Gardner wrote:
> > smatch warning:
> >
> > drivers/gpu/drm/i915/intel_display.c:7019 intel_set_mode() warn: function
> > puts
> > 500 bytes on stack
> >
> > Refactor so that saved_mode and saved_hwmode are dyn
We have two issues in current code:
- if target gfn is used as its page table, guest will refault then kvm will use
small page size to map it. We need two #PF to fix its shadow page table
- sometimes, say a exception is triggered during vm-exit caused by #PF
(see handle_exception() in vmx.c),
This patch replace the obsolete simple_strto with kstrto
Signed-off-by: Abhijit Pawar
---
net/core/netpoll.c |5 -
net/ipv4/netfilter/ipt_CLUSTERIP.c |9 +++--
net/mac80211/debugfs_sta.c |3 +++
net/netfilter/nf_conntrack_core.c |5 -
4 files
Little cleanup for reexecute_instruction, also use gpa_to_gfn in
retry_instruction
Signed-off-by: Xiao Guangrong
---
arch/x86/kvm/x86.c | 13 ++---
1 files changed, 6 insertions(+), 7 deletions(-)
diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
index e87be93b..1c67873 100644
---
Currently, reexecute_instruction refused to retry all instructions. If
nested npt is used, the emulation may be caused by shadow page, it can
be fixed by dropping the shadow page
Signed-off-by: Xiao Guangrong
---
arch/x86/kvm/x86.c | 19 +--
1 files changed, 13 insertions(+), 6
The current reexecute_instruction can not well detect the failed instruction
emulation. It allows guest to retry all the instructions except it accesses
on error pfn
For example, some cases are nested-write-protect - if the page we want to
write is used as PDE but it chains to itself. Under this c
10.12.2012 12:25, Stanislav Kinsbursky пишет:
07.12.2012 20:52, J. Bruce Fields пишет:
On Tue, Dec 04, 2012 at 04:50:16PM +0300, Stanislav Kinsbursky wrote:
diff --git a/fs/nfsd/nfssvc.c b/fs/nfsd/nfssvc.c
index 21cba3d..6448391 100644
--- a/fs/nfsd/nfssvc.c
+++ b/fs/nfsd/nfssvc.c
@@ -334,10 +3
This patch series consists of two patches fixing different issues but in the
same file, so the second patch depends on the first:
1. Fix memory freeing issues
2. Fix concurrency issue on SMP systems.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a mess
Precursor patch. Hard-coded "init_net" will be replaced by proper one in
future.
Signed-off-by: Stanislav Kinsbursky
---
fs/nfsd/nfssvc.c | 15 ++-
1 files changed, 6 insertions(+), 9 deletions(-)
diff --git a/fs/nfsd/nfssvc.c b/fs/nfsd/nfssvc.c
index 9fd8496..21cba3d 100644
--- a
Precursor patch. Hard-coded "init_net" will be replaced by proper one in
future.
Signed-off-by: Stanislav Kinsbursky
---
fs/nfsd/nfsctl.c |4 +++-
fs/nfsd/nfsd.h |2 +-
fs/nfsd/nfssvc.c |3 +--
3 files changed, 5 insertions(+), 4 deletions(-)
diff --git a/fs/nfsd/nfsctl.c b/fs/nfs
Precursor patch. Hard-coded "init_net" will be replaced by proper one in
future.
Signed-off-by: Stanislav Kinsbursky
---
fs/nfsd/nfsctl.c |3 ++-
fs/nfsd/nfsd.h |2 +-
fs/nfsd/nfssvc.c |3 +--
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/fs/nfsd/nfsctl.c b/fs/nfsd
Precursor patch. Hard-coded "init_net" will be replaced by proper one in
future.
Signed-off-by: Stanislav Kinsbursky
---
fs/nfsd/nfsctl.c | 16
1 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/fs/nfsd/nfsctl.c b/fs/nfsd/nfsctl.c
index 58f0ae4..8536100 100644
---
Precursor patch. Hard-coded "init_net" will be replaced by proper one in
future.
Signed-off-by: Stanislav Kinsbursky
---
fs/nfsd/nfsctl.c |4 ++--
fs/nfsd/nfsd.h |2 +-
fs/nfsd/nfssvc.c |5 ++---
3 files changed, 5 insertions(+), 6 deletions(-)
diff --git a/fs/nfsd/nfsctl.c b/fs/n
There could be a situation, when NFSd was started in one network namespace, but
stopped in another one.
This will trigger kernel panic, because RPCBIND client is stored on per-net
NFSd data, and will be NULL on NFSd shutdown.
Signed-off-by: Stanislav Kinsbursky
---
fs/nfsd/nfssvc.c |3 +--
1
Precursor patch. Hard-coded "init_net" will be replaced by proper one in
future.
Signed-off-by: Stanislav Kinsbursky
---
fs/nfsd/nfssvc.c |8
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/fs/nfsd/nfssvc.c b/fs/nfsd/nfssvc.c
index 9beace6..9fd8496 100644
--- a/fs/nfs
Drop this series, please.
--
Best regards,
Stanislav Kinsbursky
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tu
Hard-coded "init_net" pointer is widely used in NFSd code.
This patch replaces "init_net" references by passed struct net pointer where
requied.
In future, proper network namespace context will be taken from NFSd file
system superblock private data or, where it's impossible, from current.
The foll
On Fri, Dec 7, 2012 at 12:53 PM, Sachin Kamat wrote:
> devm_regulator_get() is device managed and makes error handling
> and code cleanup simpler.
>
> Cc: Arun R Murthy
> Signed-off-by: Sachin Kamat
Looks good to me!
Acked-by: Linus Walleij
Yours,
Linus Walleij
--
To unsubscribe from this l
> devm_regulator_get() is device managed and makes error handling and code
> cleanup simpler.
>
> Cc: Arun R Murthy
> Signed-off-by: Sachin Kamat
> ---
> Compile tested using linux-next.
> ---
> drivers/power/ab8500_charger.c | 11 +++
> 1 files changed, 3 insertions(+), 8 deletions(-
Hi Russel,
Thanks for review and please find my replies below.
On 7 December 2012 18:03, Russell King - ARM Linux
wrote:
> On Fri, Dec 07, 2012 at 05:33:17PM +0530, Tushar Behera wrote:
>> On 12/03/2012 05:46 PM, Giridhar Maruthy wrote:
>> > This patch adds slave support to i2c. The dt entry i2c
On Sun, Dec 09, 2012 at 10:15:09AM +, Przemo Firszt wrote:
> A clean up change suggested by checkpatch.pl
>
> Signed-off-by: Przemo Firszt
> ---
> drivers/staging/rtl8712/rtl871x_ioctl_linux.c | 6 ++
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/staging/rtl
On Mon 10-12-12 02:20:38, azurIt wrote:
[...]
> Michal,
Hi,
> this was printing so many debug messages to console that the whole
> server hangs
Hmm, this is _really_ surprising. The latest patch didn't add any new
logging actually. It just enahanced messages which were already printed
out previ
1. uioinfo was kfreed based on the presence of pdev->dev.of_node, which was
obviously wrong and unrelated to the fact if uioinfo was allocated statically
or dynamically. This patch introduces new flag which clearly shows if uioinfo
was allocated dynamically and kfrees uioinfo based on that flag;
2.
On Mon, Dec 10, 2012 at 11:02:25AM +0200, Noam Camus wrote:
> Target "scripts_basic" by itself is indeed not creating the dependency issue.
> The relevant target is "scripts".
> Sorry for the confusion, thanks for the example.
> So I call target "defconfig" and then I call target "vmlinux" which by
In a SMP case there was a race condition issue between
uio_pdrv_genirq_irqcontrol() running on one CPU and irq handler on another
CPU. Fix it by spin_locking shared resources access inside irq handler.
Also:
- Change disable_irq to disable_irq_nosync to avoid deadlock, because
disable_irq waits fo
On Sun, Dec 09, 2012 at 10:15:10AM +, Przemo Firszt wrote:
> Replace leading spaces with tab
>
> Signed-off-by: Przemo Firszt
> ---
> drivers/staging/rtl8712/rtl871x_ioctl_linux.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/rtl8712/rtl871x_ioctl_
On Fri, Dec 7, 2012 at 3:01 PM, Mathias Nyman
wrote:
> Add gpio support for Intel Lynxpoint chipset.
> Lynxpoint supports 94 gpio pins which can generate interrupts.
> Driver will fail requests for pins that are marked as owned by ACPI, or
> set in an alternate mode (non-gpio).
>
> Signed-off-by:
On Sun, Dec 09, 2012 at 03:19:09PM +, Cong Ding wrote:
> ping!
>
Calm your buns. :P If you don't hear back from anyone, it probably
means that your patch is going to be merged. But you've caught us
at a bad moment because the 3.8 merge window is about to open. It
could take over a month b
On Mon, Dec 10, 2012 at 11:03:59AM +0200, Vitalii Demianets wrote:
> On Saturday 08 December 2012 01:47:21 Hans J. Koch wrote:
> > On Fri, Dec 07, 2012 at 05:00:54PM +0200, Vitalii Demianets wrote:
> > > > On second thought, we can't call enable_irq()/disable_irq()
> > > > unconditionally because o
On Sat, Dec 8, 2012 at 3:36 AM, Vivien Didelot
wrote:
> Technologic Systems TS-5500 provides digital I/O lines exposed through
> pin blocks. On this platform, there are three of them, named DIO1, DIO2
> and LCD port, that may be used as a DIO block.
>
> The TS-5500 pin blocks are described in the
Update the driver to use the new API for requesting pwm so we can take
advantage of the pwm_lookup table to find the correct pwm to be used for the
LED functionality.
If the devm_get_pwm fails we fall back to legacy mode to try to get the pwm.
Signed-off-by: Peter Ujfalusi
---
drivers/leds/leds-
Allow client driver to use of_pwm_request() to get the pwm they need. This
is needed for drivers which handle more than one pwm separately, like
leds-pwm driver which have:
pwmleds {
compatible = "pwm-leds";
kpad {
label = "omap4::keypad";
pwms = <&t
Support for device tree booted kernel.
For usage see:
Documentation/devicetree/bindings/leds/leds-pwm.txt
Signed-off-by: Peter Ujfalusi
---
.../devicetree/bindings/leds/leds-pwm.txt | 46
drivers/leds/leds-pwm.c| 124 +
2 files
In order to be able to add device tree support for leds-pwm driver we need
to rearrange the data structures used by the drivers.
Signed-off-by: Peter Ujfalusi
---
drivers/leds/leds-pwm.c | 39 +++
1 file changed, 23 insertions(+), 16 deletions(-)
diff --git a
Hello,
Changes since v2:
- rebased on top of linux-next
- DT bindings now alligned with Grant's request
- exporting of_pwm_request() from PWM core to allow clean DT bindings
- DT binding documentation changed to reflect the changes
Changes since v1:
- As suggested by Bryan Wu: the legacy pwm_requ
The main changes for the mempressure cgroup:
- Added documentation, describes APIs and the purpose;
- Implemented shrinker interface, this is based on Andrew's idea and
supersedes my "balance" level idea;
- The shrinker interface comes with a stress-test utility, that is what
Andrew was also
1 - 100 of 670 matches
Mail list logo
