On Mon, 2012-12-10 at 14:14 -0700, Bjorn Helgaas wrote:
> On Wed, Nov 14, 2012 at 2:41 AM, Jan Glauber wrote:
> > Add PCI support for s390, (only 64 bit mode is supported by hardware):
> > - PCI facility tests
> > - PCI instructions: pcilg, pcistg, pcistb, stpcifc, mpcifc, rpcit
> > - map
Hi Linus,
please pull from the 'for-linus' branch of
git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git for-linus
to receive the following updates:
Add support to generate code for the latest machine zEC12, MOD and XOR
instruction support for the BPF jit compiler, the dasd
On Mon, 10 Dec 2012, Mark Brown wrote:
> On Mon, Dec 10, 2012 at 08:55:51AM +, Lee Jones wrote:
> > If a regulator is specified as always-on, then it can't have an
> > enable/disable pin, as it can't be turned off.
>
> Sometimes always on gets set for regulators which do have a physical
>
Hi rafael,
I tested the pachset in our IA64 machine, system boot up log seems ok, but
when do IOH hot plug, there are two small
problems that missing match and start acpi devices for the top acpi device(eg.
pci host bridge), refer https://lkml.org/lkml/2012/12/12/268.
Test Machine: IA64,2
On Wednesday, December 12, 2012 06:00:03 PM Bjorn Helgaas wrote:
> On Sun, Dec 9, 2012 at 4:00 PM, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > Currently, as soon as an ACPI device node object (struct acpi_device)
> > is created, the driver core attempts to probe ACPI drivers
On Thu, Dec 13, 2012 at 11:07:43AM +0800, Alex Shi wrote:
> >> now, on the other hand, if you have two threads of a process that
> >> share a bunch of data structures, and you'd spread these over 2
> >> sockets, you end up bouncing data between the two sockets a lot,
> >> running inefficient -->
On 13/12/12 11:27, Vasiliy Tolstov wrote:
If i apply this patch to kernel 3.6.7 does it needs to apply another
patches to work?
No, it should "just work". Obviously, if it doesn't, let me know.
--
Mats
2012/12/13 Mats Petersson :
One comment asked for more details on the improvements:
Using
Commit 8e22cc88d68ca1a46d7d582938f979eb640ed30f removes the (un)lock_super
function definitions but forgets to remove their prototypes.
Signed-off-by: Alessio Igor Bogani
---
include/linux/fs.h |4
1 file changed, 4 deletions(-)
diff --git a/include/linux/fs.h b/include/linux/fs.h
If i apply this patch to kernel 3.6.7 does it needs to apply another
patches to work?
2012/12/13 Mats Petersson :
> One comment asked for more details on the improvements:
> Using a small test program to map Guest memory into Dom0 (repeatedly
> for "Iterations" mapping the same first "Num Pages")
On Mon, 2012-12-10 at 19:12 +, Will Deacon wrote:
> From: Matthew Leach
>
> The {read,write}s{b,w,l} operations are not defined by all
> architectures and are being removed from the asm-generic/io.h
> interface.
>
> This patch replaces the usage of these string functions in the mtd
> gpio
On Wed, 2012-12-12 at 19:32 +1100, NeilBrown wrote:
>
> If you create a block2mtd device that is larger than main memory,
> and write to all of it, then lots of pages will be dirtied but
> they will never be flushed out as nothing calls any variant of
> balance_dirty_pages.
>
> It would be nice
On Thu, 13 Dec 2012, Dan Carpenter wrote:
> On Thu, Dec 13, 2012 at 11:18:53AM +0100, Julia Lawall wrote:
> > On Thu, 13 Dec 2012, Dan Carpenter wrote:
> >
> > > On Wed, Dec 12, 2012 at 01:25:56AM +0400, Evgeniy Polyakov wrote:
> > > > I suppose mdev will be automatically freed, but who will
Skip the wakeup interrupt registration for Exynos5250 if pinctrl support
is enabled for Exynos5250.
Signed-off-by: Thomas Abraham
---
arch/arm/mach-exynos/common.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-exynos/common.c
Skip exynos5250 gpiolib registration if pinctrl support for exynos5250
is enabled.
Signed-off-by: Thomas Abraham
---
drivers/gpio/gpio-samsung.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/gpio/gpio-samsung.c b/drivers/gpio/gpio-samsung.c
index
On Fri, Dec 07, 2012 at 10:48:56PM -0800, anish kumar wrote:
> On Fri, 2012-12-07 at 15:02 +0800, Han Pingtian wrote:
> > Hi there,
> >
> > I'm wondering this is a typo in Documentation/kernel-parameters.txt
> > about "kernelcore=":
> >
> > In the event, a node is too small to have
Add Samsung Exynos5250 SoC specific data to enable pinctrl support for
all platforms based on Exynos5250.
Signed-off-by: Thomas Abraham
---
drivers/pinctrl/pinctrl-exynos.c | 108 +
drivers/pinctrl/pinctrl-samsung.c |2 +
This patch series adds pinctrl driver support for Samsung's Exynos5250 SoC.
The first patch adds the required Exynos5250 SoC specific data which is
used by the Samsung pinctrl driver to setup the pinctrl/pinmux/eint
controllers. The second and third patches skips the wakeup interrupt and
gpiolib
On Thu, Dec 13, 2012 at 11:18:53AM +0100, Julia Lawall wrote:
> On Thu, 13 Dec 2012, Dan Carpenter wrote:
>
> > On Wed, Dec 12, 2012 at 01:25:56AM +0400, Evgeniy Polyakov wrote:
> > > I suppose mdev will be automatically freed, but who will release
> > > mdev->clk and other private members of
On Thu, Dec 06, 2012 at 01:11:41PM -0800, Laura Abbott wrote:
> The current calculation in pfn_to_bitidx assumes that
> (pfn - zone->zone_start_pfn) >> pageblock_order will return the
> same bit for all pfn in a pageblock. If zone_start_pfn is not
> aligned to pageblock_nr_pages, this may not
On Wed, Dec 12, 2012 at 04:43:39PM -0500, Johannes Weiner wrote:
> The restart logic for when reclaim operates back to back with
> compaction is currently applied on the lruvec level. But this does
> not make sense, because the container of interest for compaction is a
> zone as a whole, not the
On Thursday, December 13, 2012 10:36:38 AM Jiang Liu wrote:
> On 2012-12-12 22:37, Liu, Jinsong wrote:
> > Wen Congyang wrote:
> >> At 12/08/2012 06:19 AM, Rafael J. Wysocki Wrote:
> >>> On Tuesday, December 04, 2012 01:39:54 AM Liu, Jinsong wrote:
> Resend it, add Rafael and
On Wed, Dec 12, 2012 at 04:43:38PM -0500, Johannes Weiner wrote:
> Reclaim pressure balance between anon and file pages is calculated
> through a tuple of numerators and a shared denominator.
>
> Exceptional cases that want to force-scan anon or file pages configure
> the numerators and
* Oleg Nesterov [2012-12-10 20:12:32]:
> On 12/10, Srikar Dronamraju wrote:
> >
> > * Oleg Nesterov [2012-11-23 21:28:06]:
> >
> > > register/unregister verifies that inode/uc != NULL. For what?
> > > This really looks like "hide the potential problem", the caller
> > > should pass the valid
At Thu, 13 Dec 2012 21:39:22 +1100,
Stephen Rothwell wrote:
>
> Hi Takashi,
>
> On Thu, 13 Dec 2012 10:42:09 +0100 Takashi Iwai wrote:
> >
> > At Thu, 13 Dec 2012 15:32:37 +1100,
> > Stephen Rothwell wrote:
> > >
> > > If you have a tree that is included in linux-next, please clean it up
> > >
Hi,
Acked-by: Steven Whitehouse
Steve.
On Wed, 2012-12-12 at 10:19 -0800, Joe Perches wrote:
> Use the new vsprintf extension to avoid any possible
> message interleaving.
>
> Signed-off-by: Joe Perches
> ---
> fs/gfs2/glock.c |4 ++--
> fs/gfs2/trans.c |3 ++-
> 2 files changed, 4
* Oleg Nesterov [2012-11-23 21:28:17]:
> To support the filtering uprobe_register() should do
> register_for_each_vma(true) every time the new consumer comes,
> we need to install the previously nacked breakpoints.
>
> Note:
> - uprobes_mutex[] should die, what is actually protects is
>
Signed-off-by: Roger Pau Monné
Cc: Huang Ying
Cc: Konrad Rzeszutek Wilk
---
Changes since v3:
* Change n to use type *, to keep the same semantics as
list_for_each_entry_safe.
Changes since v2:
* Allow to pass a NULL node as the first entry of deleted list
entries.
---
Use llist_for_each_entry_safe in blkif_free. Previously grants where
freed while iterating the list, which lead to dereferences when trying
to fetch the next item.
Reported-by: Dan Carpenter
Signed-off-by: Roger Pau Monné
Cc: Konrad Rzeszutek Wilk
Cc: xen-de...@lists.xen.org
---
Change foreach_grant iterator to a safe version, that allows freeing
the element while iterating. Also move the free code in
free_persistent_gnts to prevent freeing the element before the rb_next
call.
Reported-by: Dan Carpenter
Signed-off-by: Roger Pau Monné
Cc: Konrad Rzeszutek Wilk
Cc:
Hi,
On Thu, Dec 13, 2012 at 12:44:22PM +0200, Roger Quadros wrote:
> Hi Samuel & Felipe,
>
> How can we proceed with this patchset?
>
> You can use the below pull request.
there are patches under arch/arm/ which need Tony's Acked-by, if we get
those, then sure, go ahead ;-)
--
balbi
On Wed, Dec 12, 2012 at 04:43:37PM -0500, Johannes Weiner wrote:
> Fix comment style and elaborate on why anonymous memory is
> force-scanned when file cache runs low.
>
> Signed-off-by: Johannes Weiner
Acked-by: Mel Gorman
--
Mel Gorman
SUSE Labs
--
To unsubscribe from this list: send the
On Wed, Dec 12, 2012 at 04:43:36PM -0500, Johannes Weiner wrote:
> There are currently several inter-LRU balancing heuristics that simply
> get disabled when the reclaimer is at the last reclaim cycle before
> giving up, but the code is quite cumbersome and not really obvious.
>
> Make the
Hi Samuel & Felipe,
How can we proceed with this patchset?
You can use the below pull request.
The following changes since commit 47f46768d3a3866bff7164649dab499bf5d8ed81:
Merge branch 'next/soc' into for-next (2012-12-07 16:35:14 -0800)
are available in the git repository at:
On Wed, Dec 12, 2012 at 04:43:35PM -0500, Johannes Weiner wrote:
> In certain cases (kswapd reclaim, memcg target reclaim), a fixed
> minimum amount of pages is scanned from the LRU lists on each
> iteration, to make progress.
>
> Do not make this minimum bigger than the respective LRU list size,
Hi Takashi,
On Thu, 13 Dec 2012 10:42:09 +0100 Takashi Iwai wrote:
>
> At Thu, 13 Dec 2012 15:32:37 +1100,
> Stephen Rothwell wrote:
> >
> > If you have a tree that is included in linux-next, please clean it up
> > after it has been merged into your upstream (i.e. Linus' tree in most
> >
On Wed, Dec 12, 2012 at 04:43:34PM -0500, Johannes Weiner wrote:
> When a reclaim scanner is doing its final scan before giving up and
> there is swap space available, pay no attention to swappiness
> preference anymore. Just swap.
>
> Note that this change won't make too big of a difference for
On Thu 13-12-12 09:43:31, Shaohua Li wrote:
> 2012/12/12 Jan Kara :
> > On Wed 12-12-12 10:55:15, Shaohua Li wrote:
> >> 2012/12/11 Jan Kara :
> >> > Hi,
> >> >
> >> > I was looking into IO starvation problems where streaming sync writes
> >> > (in
> >> > my case from kjournald but DIO would
On Thu, 13 Dec 2012, Dan Carpenter wrote:
> On Wed, Dec 12, 2012 at 01:25:56AM +0400, Evgeniy Polyakov wrote:
> > I suppose mdev will be automatically freed, but who will release
> > mdev->clk and other private members of mdev structure?
>
> + mdev->clk = devm_clk_get(>dev, NULL);
>
> ->clk is
On 12 December 2012 13:32, wrote:
> Hi Ulf,
>
> Sorry for the late response.
> See my reply below.
>
> Thanks,
> Maya
>
> On Thu, December 6, 2012 2:18 am, Ulf Hansson wrote:
>> Hi Maya,
>>
>> On 4 December 2012 22:17, wrote:
>>> Hi Ulf,
>>>
>>> Let me try to better explain:
>>> The idea
This is PWM driver to support 4 pwm for Exynos SoCs. Also this supports
device tree node.
The existing s3c24xx-pwm driver has many dependence with arch specific
codes and it is difficult to support device tree by static mapping of
PMW memory area. Also it can't support multi pwm to one device and
On 13 December 2012 03:17, Alex Shi wrote:
> On 12/12/2012 09:31 PM, Vincent Guittot wrote:
>> During the creation of sched_domain, we define a pack buddy CPU for each CPU
>> when one is available. We want to pack at all levels where a group of CPU can
>> be power gated independently from others.
On Wed, Dec 12, 2012 at 05:28:44PM -0500, Johannes Weiner wrote:
> On Wed, Dec 12, 2012 at 04:53:36PM -0500, Rik van Riel wrote:
> > On 12/12/2012 04:43 PM, Johannes Weiner wrote:
> > >dc0422c "mm: vmscan: only evict file pages when we have plenty" makes
You are using some internal tree for that
On Thu, Dec 13, 2012 at 10:13:00AM +0100, Paolo Pisati wrote:
> Signed-off-by: Paolo Pisati
> Tested-by: Robert Nelson
please read Documentation/stable_kernel_rules.txt, you'll see this is
wrong.
--
balbi
signature.asc
Description: Digital signature
Dear List:
Description of problem:
After installed Centos 6.3(RHEL6.3) on my Dell R710(lastest
bios:Version: 6.3.0,Release Date: 07/24/2012) server,and updated
lastest kernel "2.6.32-279.14.1.el6.x86_64",I want to use the Intel
82576 ET Dual Port nic's SR-IOV feature,assigning VFs to kvm guest
[CC += tglx]
On Mon, Nov 26, 2012 at 7:54 AM, Vince Weaver wrote:
> Hello
>
> Here is an updated version of the proposed manpage.
>
> Ingo, Peter Z., I know you're busy but would it be possible for you
> to give this a sanity check? This is likely to become the document
> that most users of the
>>> On 13.12.12 at 01:29, Daniel Santos wrote:
> Wow, it's really easy to miss parallel development on the same issue.
> Sorry for my late response to this thread. I started another thread
> addressing these issues (as well as a few others) back in September
>
At Thu, 13 Dec 2012 15:32:37 +1100,
Stephen Rothwell wrote:
>
> Hi all,
>
> If you have a tree that is included in linux-next, please clean it up
> after it has been merged into your upstream (i.e. Linus' tree in most
> cases).
What does "clean up" mean in this context exactly?
thanks,
Andreas Voellmy wrote:
> Using strace, I checked that my program is using epoll api as I
> described. Here is a fragment of the strace output that demonstrates
> my use:
>
> recvfrom(161, "GET / HTTP/1.1\r\nHost: 10.12.0.1:"..., 90, 0, NULL, NULL) = 90
> sendto(161, "HTTP/1.1 200 OK\r\nDate:
On Wed, Dec 12, 2012 at 01:25:56AM +0400, Evgeniy Polyakov wrote:
> I suppose mdev will be automatically freed, but who will release
> mdev->clk and other private members of mdev structure?
+ mdev->clk = devm_clk_get(>dev, NULL);
->clk is now a devm pointer as well.
regards,
dan carpenter
--
On Tue, Dec 11, 2012 at 11:07:17AM -0800, K. Y. Srinivasan wrote:
> -probe_error1:
> +probe_error2:
> kthread_stop(dm_device.thread);
>
> -probe_error0:
> +probe_error1:
> vmbus_close(dev->channel);
> +probe_error0:
> + kfree(send_buffer);
If you used labels that describe what
[resent with cc: stable and a bit more context]
I've been experiencing solid hangs on my beaglexm with v3.7 after
kexec:
Signed-off-by: Paolo Pisati
Tested-by: Robert Nelson
---
drivers/regulator/core.c | 16 ++--
1 file changed, 14 insertions(+), 2 deletions(-)
diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c
index e872c8b..c347fd0 100644
--- a/drivers/regulator/core.c
+++
On Thu, Dec 13, 2012 at 09:56:25AM +0100, Marek Szyprowski wrote:
> This change looks reasonable, I've missed the fact that there is a
> support for regulators with continuous voltage range. This change also
> shows that the n_voltages based workaround used earlier by mmc core was
> indeed only a
On Thu, Dec 13, 2012 at 05:15:33AM +, Mark Brown wrote:
> On Wed, Dec 12, 2012 at 12:45:52PM +0100, Paolo Pisati wrote:
> > And after a second look it's clear what's going on:
>
> After a second look at what? You've not provided any context, I've no
> idea what you're talking about here.
On Thu, Dec 13, 2012 at 10:48:55AM +0200, Terje Bergström wrote:
> On 12.12.2012 18:08, Thierry Reding wrote:
> > I've briefly discussed this with Stephen on IRC because I thought I had
> > remembered him objecting to the idea of adding a dummy device just for
> > this purpose. It turns out,
Hello,
On 12/12/2012 2:22 AM, Axel Lin wrote:
Regulator drivers with continuous_voltage_range flag set allows not setting
n_voltages. Thus if continuous_voltage_range is set, check the constraint range
instead.
Signed-off-by: Axel Lin
---
drivers/regulator/core.c | 12 +---
1
On 13 December 2012 03:24, Alex Shi wrote:
> On 12/12/2012 09:31 PM, Vincent Guittot wrote:
>> This new flag SD_SHARE_POWERDOMAIN is used to reflect whether groups of CPU
>> in
>> a sched_domain level can or not reach a different power state. If clusters
>> can
>> be power gated independently,
There's no need to use delayed work, convert to use work_struct and
cancel_work_sync().
Requested-by: Tejun Heo
Signed-off-by: Xiaotian Feng
Cc: Neela Syam Kolli
Cc: "James E.J. Bottomley"
Cc: linux-s...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
---
On 13.12.2012 04:06, Adam Lee wrote:
> On Wed, Dec 12, 2012 at 05:14:41PM -0500, Steven Rostedt wrote:
>> From: Steven Rostedt
>>
>> Commit fb16d891 "kconfig: replace 'oldnoconfig' with 'olddefconfig', and
>> keep the old name", changed ktest's default config update from
>> oldnoconfig to
On 12.12.2012 18:08, Thierry Reding wrote:
> I've briefly discussed this with Stephen on IRC because I thought I had
> remembered him objecting to the idea of adding a dummy device just for
> this purpose. It turns out, however, that what he didn't like was to add
> a dummy node to the DT just to
On 12/12/2012 11:57 AM, Preeti U Murthy wrote:
> Hi Alex,
> On 12/10/2012 01:52 PM, Alex Shi wrote:
>> 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.
>>
updated with UP config fix:
Signed-off-by: Axel Lin
---
drivers/regulator/tps6586x-regulator.c | 54 ++--
1 file changed, 10 insertions(+), 44 deletions(-)
diff --git a/drivers/regulator/tps6586x-regulator.c
b/drivers/regulator/tps6586x-regulator.c
index f86da67..1b5e8b9 100644
---
On Thu, Dec 13, 2012 at 04:44:08PM +0800, Axel Lin wrote:
> Some DVM regulators needs to update activate_bit after setting vsel_reg to
> initiate voltage change on the output. This patch adds activate_reg and
> activate_bit to struct regulator_desc and update
> regulator_set_voltage_sel_regmap()
Signed-off-by: Axel Lin
---
drivers/regulator/da9052-regulator.c | 41 +-
1 file changed, 6 insertions(+), 35 deletions(-)
diff --git a/drivers/regulator/da9052-regulator.c
b/drivers/regulator/da9052-regulator.c
index d096309..47455ad 100644
---
Signed-off-by: Axel Lin
---
drivers/regulator/88pm8607.c | 43 --
1 file changed, 12 insertions(+), 31 deletions(-)
diff --git a/drivers/regulator/88pm8607.c b/drivers/regulator/88pm8607.c
index 2b55711..21a7334 100644
--- a/drivers/regulator/88pm8607.c
We scale stime, utime values based on rtime (sum_exec_runtime converted
to jiffies). During scaling we multiple rtime * utime, what seems to be
fine, since both values are converted to u64, but is not.
Let assume HZ is 1000 - 1ms tick. Process consist of 64 threads, run
for 1 day, threads utilize
Some DVM regulators needs to update activate_bit after setting vsel_reg to
initiate voltage change on the output. This patch adds activate_reg and
activate_bit to struct regulator_desc and update
regulator_set_voltage_sel_regmap() to set activate_bit of activate_reg when
activate_bit is set.
Commit-ID: 8df383108f7b7eafcf89f26be5460b404c70ff29
Gitweb: http://git.kernel.org/tip/8df383108f7b7eafcf89f26be5460b404c70ff29
Author: Stephen Rothwell
AuthorDate: Mon, 10 Dec 2012 19:54:02 +1100
Committer: Ingo Molnar
CommitDate: Mon, 10 Dec 2012 13:37:30 +0100
mm/migrate: Fix
On 12/12/2012 08:31 PM, Linus Walleij wrote:
On Tue, Dec 11, 2012 at 10:11 PM, Stephen Warren wrote:
Since I assume those function are only supposed to be used by pinctrl
drivers themselves, should the prototypes go into drivers/pinctrl/core.h
or similar, rather than something in
On Wed, Dec 12, 2012 at 02:54:10PM +0100, Laurent Navet wrote:
> Bool initializations should use true and false. Bool tests don't need
> comparisons. Based on contributions from Joe Perches, Rusty Russell
> and Bruce W Allan.
>
> The semantic patch that makes this output is available
> in
Following oops were observed when disk error happened:
[ 4272.896937] sd 0:0:0:0: [sda] Unhandled error code
[ 4272.896939] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4272.896942] sd 0:0:0:0: [sda] CDB: Read(10): 28 00 00 5a de a7 00 00 08 00
[ 4272.896951]
Fix up the ->page_mkwrite handler to provide stable page writes if necessary.
Signed-off-by: Darrick J. Wong
---
fs/9p/vfs_file.c |1 +
1 file changed, 1 insertion(+)
diff --git a/fs/9p/vfs_file.c b/fs/9p/vfs_file.c
index c2483e9..357260b 100644
--- a/fs/9p/vfs_file.c
+++
This creates a per-backing-device flag that tracks whether or not pages must be
held immutable during writeout. Eventually it will be used to waive
wait_for_page_writeback() if nobody requires stable pages.
Signed-off-by: Darrick J. Wong
---
Documentation/ABI/testing/sysfs-class-bdi |5
Several complaints have been received regarding long file write latencies when
memory pages must be held stable during writeback. Since it might not be
acceptable to stall programs for the entire duration of a page write (which may
take many milliseconds even on good hardware), enable a second
Hi all,
This patchset ("stable page writes, part 2") makes some key modifications to
the original 'stable page writes' patchset. First, it provides creators
(devices and filesystems) of a backing_dev_info a flag that declares whether or
not it is necessary to ensure that page contents cannot
Create a helper function to check if a backing device requires stable page
writes and, if so, performs the necessary wait. Then, make it so that all
points in the memory manager that handle making pages writable use the helper
function. This should provide stable page write support to most
Hi all,
This patchset (stable page writes, part 2) makes some key modifications to
the original 'stable page writes' patchset. First, it provides creators
(devices and filesystems) of a backing_dev_info a flag that declares whether or
not it is necessary to ensure that page contents cannot
Create a helper function to check if a backing device requires stable page
writes and, if so, performs the necessary wait. Then, make it so that all
points in the memory manager that handle making pages writable use the helper
function. This should provide stable page write support to most
Several complaints have been received regarding long file write latencies when
memory pages must be held stable during writeback. Since it might not be
acceptable to stall programs for the entire duration of a page write (which may
take many milliseconds even on good hardware), enable a second
Fix up the -page_mkwrite handler to provide stable page writes if necessary.
Signed-off-by: Darrick J. Wong darrick.w...@oracle.com
---
fs/9p/vfs_file.c |1 +
1 file changed, 1 insertion(+)
diff --git a/fs/9p/vfs_file.c b/fs/9p/vfs_file.c
index c2483e9..357260b 100644
---
This creates a per-backing-device flag that tracks whether or not pages must be
held immutable during writeout. Eventually it will be used to waive
wait_for_page_writeback() if nobody requires stable pages.
Signed-off-by: Darrick J. Wong darrick.w...@oracle.com
---
Following oops were observed when disk error happened:
[ 4272.896937] sd 0:0:0:0: [sda] Unhandled error code
[ 4272.896939] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 4272.896942] sd 0:0:0:0: [sda] CDB: Read(10): 28 00 00 5a de a7 00 00 08 00
[ 4272.896951]
On Wed, Dec 12, 2012 at 02:54:10PM +0100, Laurent Navet wrote:
Bool initializations should use true and false. Bool tests don't need
comparisons. Based on contributions from Joe Perches, Rusty Russell
and Bruce W Allan.
The semantic patch that makes this output is available
in
On 12/12/2012 08:31 PM, Linus Walleij wrote:
On Tue, Dec 11, 2012 at 10:11 PM, Stephen Warrenswar...@wwwdotorg.org wrote:
Since I assume those function are only supposed to be used by pinctrl
drivers themselves, should the prototypes go into drivers/pinctrl/core.h
or similar, rather than
Commit-ID: 8df383108f7b7eafcf89f26be5460b404c70ff29
Gitweb: http://git.kernel.org/tip/8df383108f7b7eafcf89f26be5460b404c70ff29
Author: Stephen Rothwell s...@canb.auug.org.au
AuthorDate: Mon, 10 Dec 2012 19:54:02 +1100
Committer: Ingo Molnar mi...@kernel.org
CommitDate: Mon, 10 Dec 2012
Some DVM regulators needs to update activate_bit after setting vsel_reg to
initiate voltage change on the output. This patch adds activate_reg and
activate_bit to struct regulator_desc and update
regulator_set_voltage_sel_regmap() to set activate_bit of activate_reg when
activate_bit is set.
We scale stime, utime values based on rtime (sum_exec_runtime converted
to jiffies). During scaling we multiple rtime * utime, what seems to be
fine, since both values are converted to u64, but is not.
Let assume HZ is 1000 - 1ms tick. Process consist of 64 threads, run
for 1 day, threads utilize
Signed-off-by: Axel Lin axel@ingics.com
---
drivers/regulator/88pm8607.c | 43 --
1 file changed, 12 insertions(+), 31 deletions(-)
diff --git a/drivers/regulator/88pm8607.c b/drivers/regulator/88pm8607.c
index 2b55711..21a7334 100644
---
Signed-off-by: Axel Lin axel@ingics.com
---
drivers/regulator/da9052-regulator.c | 41 +-
1 file changed, 6 insertions(+), 35 deletions(-)
diff --git a/drivers/regulator/da9052-regulator.c
b/drivers/regulator/da9052-regulator.c
index d096309..47455ad 100644
On Thu, Dec 13, 2012 at 04:44:08PM +0800, Axel Lin wrote:
Some DVM regulators needs to update activate_bit after setting vsel_reg to
initiate voltage change on the output. This patch adds activate_reg and
activate_bit to struct regulator_desc and update
regulator_set_voltage_sel_regmap() to
Signed-off-by: Axel Lin axel@ingics.com
---
drivers/regulator/tps6586x-regulator.c | 54 ++--
1 file changed, 10 insertions(+), 44 deletions(-)
diff --git a/drivers/regulator/tps6586x-regulator.c
b/drivers/regulator/tps6586x-regulator.c
index f86da67..1b5e8b9
On 12/12/2012 11:57 AM, Preeti U Murthy wrote:
Hi Alex,
On 12/10/2012 01:52 PM, Alex Shi wrote:
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.
updated with UP config fix:
==
From
On 12.12.2012 18:08, Thierry Reding wrote:
I've briefly discussed this with Stephen on IRC because I thought I had
remembered him objecting to the idea of adding a dummy device just for
this purpose. It turns out, however, that what he didn't like was to add
a dummy node to the DT just to make
On 13.12.2012 04:06, Adam Lee wrote:
On Wed, Dec 12, 2012 at 05:14:41PM -0500, Steven Rostedt wrote:
From: Steven Rostedt srost...@redhat.com
Commit fb16d891 kconfig: replace 'oldnoconfig' with 'olddefconfig', and
keep the old name, changed ktest's default config update from
oldnoconfig to
There's no need to use delayed work, convert to use work_struct and
cancel_work_sync().
Requested-by: Tejun Heo t...@kernel.org
Signed-off-by: Xiaotian Feng dannyf...@tencent.com
Cc: Neela Syam Kolli megaraidli...@lsi.com
Cc: James E.J. Bottomley jbottom...@parallels.com
Cc:
On 13 December 2012 03:24, Alex Shi alex@intel.com wrote:
On 12/12/2012 09:31 PM, Vincent Guittot wrote:
This new flag SD_SHARE_POWERDOMAIN is used to reflect whether groups of CPU
in
a sched_domain level can or not reach a different power state. If clusters
can
be power gated
Hello,
On 12/12/2012 2:22 AM, Axel Lin wrote:
Regulator drivers with continuous_voltage_range flag set allows not setting
n_voltages. Thus if continuous_voltage_range is set, check the constraint range
instead.
Signed-off-by: Axel Lin axel@ingics.com
---
drivers/regulator/core.c | 12
On Thu, Dec 13, 2012 at 10:48:55AM +0200, Terje Bergström wrote:
On 12.12.2012 18:08, Thierry Reding wrote:
I've briefly discussed this with Stephen on IRC because I thought I had
remembered him objecting to the idea of adding a dummy device just for
this purpose. It turns out, however,
On Thu, Dec 13, 2012 at 05:15:33AM +, Mark Brown wrote:
On Wed, Dec 12, 2012 at 12:45:52PM +0100, Paolo Pisati wrote:
And after a second look it's clear what's going on:
After a second look at what? You've not provided any context, I've no
idea what you're talking about here.
forgot
On Thu, Dec 13, 2012 at 09:56:25AM +0100, Marek Szyprowski wrote:
This change looks reasonable, I've missed the fact that there is a
support for regulators with continuous voltage range. This change also
shows that the n_voltages based workaround used earlier by mmc core was
indeed only a
701 - 800 of 1552 matches
Mail list logo
