Il 19/06/2013 11:09, Xiao Guangrong ha scritto:
> Update the document to match the current reverse mapping of
> parent_pte
>
> Signed-off-by: Xiao Guangrong
> ---
> Documentation/virtual/kvm/mmu.txt | 12 ++--
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/Documentat
'lru' may be used without initialized, so need regressing part of the
related patch.
The related patch:
"3abf380 mm: remove lru parameter from __lru_cache_add and lru_cache_add_lru"
Signed-off-by: Chen Gang
---
mm/vmscan.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --g
On 06/18/2013 06:17 PM, Linus Walleij wrote:
On Tue, Jun 18, 2013 at 1:33 PM, Mathias Nyman
wrote:
Add support for gpio on Intel BayTrail platforms. BayTrail supports 3 banks
of gpios called SCORE, NCORE ans SUS with 102, 28 and 44 gpio pins.
Supports gpio interrupts and ACPI gpio events
Pin
On 06/19/2013 05:59 PM, Thomas Gleixner wrote:
> I'm well aware how that works. And there is no difference whether you
> do:
>
> local_irq_save(flags);
> spin_lock(&lock);
> or
> spin_lock_irqsave(&lock, flags);
if CONFIG_LOCKDEP is not defined, they are not semantically the sam
On Tue 18-06-13 15:01:21, Johannes Weiner wrote:
> On Tue, Jun 18, 2013 at 02:09:39PM +0200, Michal Hocko wrote:
> > My primary test case was a parallel kernel build with 2 groups (make
> > is running with -j4 with a distribution .config in a separate cgroup
> > without any hard limit) on a 8 CPU m
On 06/19/2013 04:41 PM, Tejun Heo wrote:
> On Wed, Jun 19, 2013 at 12:03:38PM +0800, Chen Gang wrote:
>> >
>> > Since "WARN_ON(worker->task)", we can not assume that 'worker->task'
>> > will be NULL before set 'current' to it.
>> >
>> > So need let 'worker' lock protected too, just like it alread
EXYNOS4412 cpufreq driver requires the range of vdd_arm regulator to
be from .9v to 1.35v. Since vdd_arm regulator (BUCK2 on S5M8767) has
a supported range of .6v to 1.6v, the constraints are updated to
match the requirement from cpufreq driver.
Signed-off-by: Tushar Behera
---
arch/arm/boot/dts
On Fri, Jun 07, 2013 at 11:09:26AM +0200, Wolfram Sang wrote:
> Class based instantiation can cause huge delays when booting. This
> mechanism was used when it was not possible to describe slaves on I2C
> busses. We now have other mechanisms, so most embedded I2C will not need
> classes and it was
On 06/19/2013 02:46 AM, Tony Lindgren wrote:
* Roger Quadros [130619 00:42]:
Hi Benoit,
On 06/19/2013 04:17 AM, Benoit Cousson wrote:
Hi Roger,
On 06/18/2013 11:04 AM, Roger Quadros wrote:
Provide the RESET and Power regulators for the USB PHY,
the USB Host port mode and the PHY device.
Al
> Even you prefer to extend v4l2, you still need this helper.
> The idea is just to move the unregister/register from a specific ISP driver
> to v4l2.
>
> I think you misunderstood my pionts somehow. Let me clarfiy a little bit:
>
> Current solution:
> 1. Platform codes(on top of DT/ACPI5/SFI) d
On 06/19/2013 05:59 PM, Thomas Gleixner wrote:
> Lockdep tracks lock ordering and the context in which a lock is
> taken. The timer base lock can be taken in interrupt context, so it
> always needs to be taken with interrupts disabled. That's what lockdep
> cares about.
>
> And
> spin_lock_
Hi Lee,
On Wed, Jun 19, 2013 at 10:54:36AM +0100, Lee Jones wrote:
> Sam,
>
> Just a small pre-vacation pull-request for MFD:
>
> The following changes since commit e578438820cdca91cb5eab477ec062236433ce5f:
>
> mfd: ssbi: Use devm_* and simplify code (2013-06-18 09:41:15 +0200)
>
> are avail
Hi Wolfram,
On Wed, Jun 19, 2013 at 12:00:20PM +0200, Wolfram Sang wrote:
> > > Applied with Stephen's Reviewed-by, thanks.
> > According to Wolfgang, this is not needed as he will revert the i2c
> > commits that are causing those crashes.
> > I would not take it for now.
>
> "Wolfram", please ;)
Il 19/06/2013 03:42, Alexey Kardashevskiy ha scritto:
> Signed-off-by: Alexey Kardashevskiy
> ---
> Documentation/virtual/kvm/api.txt |8
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/virtual/kvm/api.txt
> b/Documentation/virtual/kvm/api.txt
> ind
On Tue, Jun 18, 2013 at 01:19:12PM -0700, Yinghai Lu wrote:
> On Tue, Jun 18, 2013 at 10:10 AM, Vasilis Liaskovitis
> wrote:
> >> could be found at:
> >>
> >> git://git.kernel.org/pub/scm/linux/kernel/git/yinghai/linux-yinghai.git
> >> for-x86-mm
> >>
> >> and it is based on today's Linu
ddaney.c...@gmail.com wrote:
> From: David Daney
>
> We need to pick up the definition of raw_smp_processor_id() from
> asm/smp.h. For the !SMP case, we need to supply a definition of
> raw_smp_processor_id().
>
> Because of the include dependencies we cannot use smp_call_func_t in
> asm/smp.h
On Wed, Jun 19, 2013 at 10:39:38AM +0100, Mark Brown wrote:
> On Wed, Jun 19, 2013 at 10:25:08AM +0100, Russell King - ARM Linux wrote:
> > On Tue, Jun 18, 2013 at 07:09:48PM +0100, Mark Brown wrote:
>
> > > This sounds like a problem which will affect a lot of devices and hence
> > > ought to be
select/poll busy-poll support.
Split sysctl value into two separate ones, one for read and one for poll.
updated Documentation/sysctl/net.txt
Add a new poll flag POLL_LL. When this flag is set, sock poll will call
sk_poll_ll() if possible. sock_poll sets this flag in its return value
to indicate
David,
Here is a rework of the select/poll patch.
One question: do we need in sock_poll() to test that sock->sk is not null?
(Thanks to Willem de Bruijn for pointing this out.)
When select or poll are used on a lot of sockets the sysctl value
needs to be set higher than 50. For 300 sockets a se
On Mon, Jun 03, 2013 at 10:37:20AM +0300, Oleksandr Dmytryshyn wrote:
> We've been lucky not to have any interrupts fire during the suspend
> path, otherwise we would have unpredictable behaviour in the kernel.
>
> Based on the logic of the kernel code interrupts from i2c should be
> prohibited du
Hi Tang,
On Wed, Jun 19, 2013 at 03:29:06PM +0800, Tang Chen wrote:
> Hi Vasilis, Yinghai,
>
> On 06/19/2013 01:05 AM, Vasilis Liaskovitis wrote:
> ..
> >
> >This could be a design problem of part3: if we allow local pagetable memory
> >to not be offlined but allow the offlining to return succ
On Tuesday 18 June 2013 12:12:53 David Daney wrote:
> +static unsigned int dw8250_serial_inq(struct uart_port *p, int offset)
> +{
> + offset <<= p->regshift;
> +
> + return (u8)__raw_readq(p->membase + offset);
> +}
> +
> +static void dw8250_serial_outq(struct uart_port *p, int offset,
On 19.06.2013, at 06:59, Benjamin Herrenschmidt wrote:
> On Wed, 2013-06-19 at 13:05 +0930, Rusty Russell wrote:
>> symbol_get() won't try to load a module; it'll just fail. This is what
>> you want, since they must have vfio in the kernel to get a valid fd...
>
> Ok, cool. I suppose what we wa
On Wed, 19 Jun 2013, Chen Gang wrote:
> On 06/19/2013 04:41 PM, Thomas Gleixner wrote:
> > On Wed, 19 Jun 2013, Chen Gang wrote:
> >
> >> >
> >> > When CONFIG_LOCKDEP is not defined, spin_lock_irqsave() is not equal to
> >> > spin_lock() + local_irq_save().
> >> >
> >> > In __mod_timer(), After
Hi Lee,
On 18 June 2013 15:35, Sachin Kamat wrote:
> Include the missing header file to fix the following build error:
> drivers/mfd/davinci_voicecodec.c: In function ‘davinci_vc_probe’:
> drivers/mfd/davinci_voicecodec.c:86:3: error: implicit declaration of function
> ‘io_v2p’ [-Werror=implicit-
On Wed, Jun 19, 2013 at 10:27:40AM +0200, Samuel Ortiz wrote:
> Hi Lee,
>
> On Wed, Jun 19, 2013 at 09:18:59AM +0100, Lee Jones wrote:
> > On Tue, 18 Jun 2013, Tuomas Tynkkynen wrote:
> >
> > > Commit "i2c: core: make it possible to match a pure device tree driver"
> > > changed semantics of the
On 06/19/2013 04:53 PM, Mel Gorman wrote:
> On Wed, Jun 19, 2013 at 02:55:13PM +0800, Chen Gang wrote:
>> >
>> > 'lru' may be used without initialized, so need regressing part of the
>> > related patch.
>> >
>> > The related patch:
>> > "3abf380 mm: remove lru parameter from __lru_cache_add and
On Wed, 2013-06-19 at 12:11 +0300, Michael S. Tsirkin wrote:
> Well KVM supports up to 160 VCPUs on x86.
>
> Creating a queue per CPU is very reasonable, and
> assuming cache line size of 64 bytes, netdev_queue seems to be 320
> bytes, that's 320*160 = 51200. So 12.5 pages, order-4 allocation.
>
By default the SH scheduler rejects connections that are hashed onto a
realserver of weight 0. This patch adds a flag to make SH choose a
different realserver in this case, instead of rejecting the connection.
The patch also adds a flag to make SH include the source port (TCP, UDP,
SCTP) in the h
Sam,
Just a small pre-vacation pull-request for MFD:
The following changes since commit e578438820cdca91cb5eab477ec062236433ce5f:
mfd: ssbi: Use devm_* and simplify code (2013-06-18 09:41:15 +0200)
are available in the git repository at:
git://git.linaro.org/people/ljones/linux-3.0-ux500.g
On 06/17/2013 10:01 PM, Peter Zijlstra wrote:
> On Mon, Jun 17, 2013 at 05:20:46AM -0700, Paul Turner wrote:
>> > On Fri, Jun 7, 2013 at 12:20 AM, Alex Shi wrote:
>>> > > blocked_load_avg sometime is too heavy and far bigger than runnable load
>>> > > avg, that make balance make wrong decision. So
On Wed, 19 Jun 2013, Samuel Ortiz wrote:
> Hi Lee,
>
> On Wed, Jun 19, 2013 at 09:18:59AM +0100, Lee Jones wrote:
> > On Tue, 18 Jun 2013, Tuomas Tynkkynen wrote:
> >
> > > Commit "i2c: core: make it possible to match a pure device tree driver"
> > > changed semantics of the i2c probing for devi
On Wed, Jun 19, 2013 at 11:11:27AM +0200, Samuel Ortiz wrote:
> On Wed, Jun 19, 2013 at 10:40:04AM +0200, Linus Walleij wrote:
> > Not really my business, but I think if I was to implement this
> > inter-module API I would use regmap for this read/write marshalling
> > right here.
> I thought abo
On 06/19/2013 04:41 PM, Thomas Gleixner wrote:
> On Wed, 19 Jun 2013, Chen Gang wrote:
>
>> >
>> > When CONFIG_LOCKDEP is not defined, spin_lock_irqsave() is not equal to
>> > spin_lock() + local_irq_save().
>> >
>> > In __mod_timer(), After call spin_lock_irqsave() with 'base->lock' in
>> > loc
Hi,
On Tue, 2013-06-18 at 17:02 -0700, Kent Overstreet wrote:
> This is a new, from scratch implementation of ida that should be
> simpler, faster and more space efficient.
>
[...]
>
> This does mean that the entire bitmap is stored in one contiguous memory
> allocation - and as currently imple
Hi,
On Wed, Jun 12, 2013 at 04:47:45PM +0200, Christian Ruppert wrote:
> On Mon, Jun 10, 2013 at 05:29:55PM +0200, Wolfram Sang wrote:
> > On Tue, May 14, 2013 at 03:04:02PM +0200, Christian Ruppert wrote:
> > > This patch makes the SDA hold time configurable through device tree.
> > >
> > > [reb
On Wed, Jun 19, 2013 at 10:25:08AM +0100, Russell King - ARM Linux wrote:
> On Tue, Jun 18, 2013 at 07:09:48PM +0100, Mark Brown wrote:
> > This sounds like a problem which will affect a lot of devices and hence
> > ought to be handled better by the PM core or at least frameworks in
> > general.
Hi Pawel,
On Tue, Jun 11, 2013 at 11:56:02AM +0100, Pawel Moll wrote:
> The driver can be used on either arm or arm64 platforms, but
> the latter doesn't have any platform-specific configuration
> options, so it must be possible to manually enable the driver.
>
> As the gpiolib is optional for ar
On Tue, Jun 18, 2013 at 05:01:23PM -0700, David Rientjes wrote:
> On Tue, 18 Jun 2013, Alex Thorlton wrote:
>
> > Thanks for your input, however, I believe the method of using a malloc
> > hook falls apart when it comes to static binaries, since we wont' have
> > any shared libraries to hook into.
Dave Chiluk writes:
> 1d2ef5901483004d74947bbf78d5146c24038fe7 caused a regression in ncpfs such
> that
> directories could no longer be removed. This was because ncp_rmdir checked
> to see if a dentry could be unhashed before allowing it to be removed. Since
> 1d2ef5901483004d74947bbf78d5146c2
Hi Pawel,
On Tue, Jun 18, 2013 at 10:29:42AM +0100, Pawel Moll wrote:
> On Tue, 2013-06-18 at 10:09 +0100, Samuel Ortiz wrote:
> > Hi Pawell,
>
> Double l in the wrong place ;-)
Apologies...
> > > If you feel strongly about it, I'm ready to split it into mfd_cells and
> > > move the gpio and l
Various sparc bug fixes, in particular:
1) TSB hashes have to be flushed before TLB on sparc64, from
Dave Kleikamp.
2) LEON timer interrupts can get stuck, from Andreas Larsson.
3) Sparc64 needs to handle lack of address-congruence devicetree
property, from Bob Picco.
Please pull, thanks
On Wed, Jun 19, 2013 at 4:10 PM, Stephen Rothwell wrote:
> Hi all,
>
> After merging the final tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> In file included from
> drivers/staging/lustre/include/linux/libcfs/libcfs.h:203:0,
> from drivers/staging/
On 06/19/2013 05:13 PM, David Miller wrote:
> From: Chen Gang
> Date: Thu, 30 May 2013 11:35:22 +0800
>
>>
>> When "cp >= barg_buf + BARG_LEN-2", it breaks internel looping 'while',
>> but outside loop 'for' still has effect, so "*cp++ = ' '" will continue
>> repeating which may cause memory over
On Tue, Jun 18, 2013 at 07:09:48PM +0100, Mark Brown wrote:
> On Tue, Jun 18, 2013 at 05:29:45PM +0300, Mika Westerberg wrote:
> > Current code calls pm_runtime_suspended() in the interrupt handler to check
> > if the device is suspended or not. However, runtime PM status of the device
> > is only
On Tue, Jun 18, 2013 at 4:20 PM, Peng Tao wrote:
> On Tue, Jun 18, 2013 at 7:36 AM, Dilger, Andreas
> wrote:
>> On 2013/17/06 2:52 AM, "Peng Tao" wrote:
>>
>>>On Thu, Jun 13, 2013 at 9:56 AM, Fengguang Wu
>>>wrote:
Greetings,
I got the below dmesg and the first bad commit is
On Wednesday 19 June 2013 16:38:38 Chao Xie wrote:
> >> index 000..f8674f7
> >> --- /dev/null
> >> +++ b/Documentation/devicetree/bindings/input/pxa27x-keypad.txt
> >> @@ -0,0 +1,60 @@
> >> +* Marvell PXA Keypad controller
> >> +
> >> +Required Properties
> >> +- compatible : should be "marvell
On Wed, Jun 19, 2013 at 10:44:37AM +0300, Mika Westerberg wrote:
> I agree that it is better handled outside of the driver (or provide some
> API for drivers). One thing that immediately came to mind is
> adding pm_runtime_suspending() that could be used here like:
> ssp_int()
> {
> if (pm_
In the Power7 PMU guide:
https://www.power.org/documentation/commonly-used-metrics-for-performance-analysis/
PM_BRU_MPRED is referred to as PM_BR_MPRED.
This patch fix the typo by changing the name of the event in kernel and
documentation accordingly.
Signed-off-by: Runzhen Wang
---
.../testing
From: Tushar Behera
Date: Mon, 17 Jun 2013 14:37:44 +0530
> Commit 75096579c3ac ("lib: devres: Introduce devm_ioremap_resource()")
> introduced devm_ioremap_resource() and deprecated the use of
> devm_request_and_ioremap().
>
> While at it, also remove the error message as devm_ioremap_resource(
Document it to Documentation/virtual/kvm/mmu.txt
Signed-off-by: Xiao Guangrong
---
Documentation/virtual/kvm/mmu.txt | 4
arch/x86/include/asm/kvm_host.h | 5 +
arch/x86/kvm/mmu.c| 7 ---
3 files changed, 13 insertions(+), 3 deletions(-)
diff --git a/Documentation
From: Chen Gang
Date: Thu, 30 May 2013 11:35:22 +0800
>
> When "cp >= barg_buf + BARG_LEN-2", it breaks internel looping 'while',
> but outside loop 'for' still has effect, so "*cp++ = ' '" will continue
> repeating which may cause memory overflow.
>
> So need additional length check for it in
Document it to Documentation/virtual/kvm/mmu.txt
Signed-off-by: Xiao Guangrong
---
Documentation/virtual/kvm/mmu.txt | 11 +--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/Documentation/virtual/kvm/mmu.txt
b/Documentation/virtual/kvm/mmu.txt
index 5a6b2e2..4fb442b 10064
On Tue, 18 Jun 2013, Kevin Strasser wrote:
This patch set looks reasonable now, except a formal issue.
> Signed-off-by: Kevin Strasser
> Signed-off-by: Michael Brunner
This is wrong, as it says:
Kevin authored the code, sent it to Michael and Michael sent it to
LKML.
The original code wa
Document fast page fault to Documentation/virtual/kvm/mmu.txt
Signed-off-by: Xiao Guangrong
---
Documentation/virtual/kvm/mmu.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/virtual/kvm/mmu.txt
b/Documentation/virtual/kvm/mmu.txt
index 4fb442b..b5ce7dd 100644
--- a/Docu
Hi Linus,
On Wed, Jun 19, 2013 at 10:40:04AM +0200, Linus Walleij wrote:
> On Tue, Jun 18, 2013 at 11:04 PM, Kevin Strasser
> wrote:
> > Add core MFD driver for the on-board PLD found on some Kontron embedded
> > modules. The PLD device may provide functions like watchdog, GPIO, UART
> > and I2C
Document write_flooding_count to Documentation/virtual/kvm/mmu.txt
Signed-off-by: Xiao Guangrong
---
Documentation/virtual/kvm/mmu.txt | 8
arch/x86/include/asm/kvm_host.h | 5 +
2 files changed, 13 insertions(+)
diff --git a/Documentation/virtual/kvm/mmu.txt
b/Documentation/vir
Update the document to match the current reverse mapping of
parent_pte
Signed-off-by: Xiao Guangrong
---
Documentation/virtual/kvm/mmu.txt | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/Documentation/virtual/kvm/mmu.txt
b/Documentation/virtual/kvm/mmu.txt
index
As Paolo pointed out that this is the time to update the documentation, this
patchest does it to let mmu.txt matches with the current mmu implementation
Xiao Guangrong (7):
KVM: MMU: update the documentation for reverse mapping of parent_pte
KVM: MMU: document clear_spte_count
KVM: MMU: docu
Document it to Documentation/virtual/kvm/mmu.txt
Signed-off-by: Xiao Guangrong
---
Documentation/virtual/kvm/mmu.txt | 25 +
1 file changed, 25 insertions(+)
diff --git a/Documentation/virtual/kvm/mmu.txt
b/Documentation/virtual/kvm/mmu.txt
index f5c4de9..9b7cfb3 100644
On Tue, Jun 18, 2013 at 11:31:58PM -0700, Eric Dumazet wrote:
> On Wed, 2013-06-19 at 13:40 +0800, Jason Wang wrote:
> > Currently, we use kcalloc to allocate rx/tx queues for a net device which
> > could
> > be easily lead to a high order memory allocation request when initializing a
> > multique
Document it to Documentation/virtual/kvm/mmu.txt
Signed-off-by: Xiao Guangrong
---
Documentation/virtual/kvm/mmu.txt | 23 +++
arch/x86/include/asm/kvm_host.h | 5 +
2 files changed, 28 insertions(+)
diff --git a/Documentation/virtual/kvm/mmu.txt
b/Documentation/virt
On 06/19/2013 12:56 PM, Alexey Brodkin wrote:
[]
> For (2) I may expect that plain change of used accessor from "le" to
> "be" will break "xsysace" on PPC/Micropblaze.
Just recalled that discussion of the first patch continued in another
thread: https://patchwork.kernel.org/patch/2130081/
It has
From: Geert Uytterhoeven
Date: Tue, 7 May 2013 11:55:55 +0200
> Signed-off-by: Geert Uytterhoeven
Applied, thanks.
--
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/maj
FYI, Since you intend to resubmit anyway I just dropped the entire series
from patchwork.
Ralf
--
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
Pleas
Hi Tomas,
Am 19.06.2013 10:52, schrieb Winkler, Tomas:
>> So it is not yet fixed, unfortunately.
>
> Not sure I understand how to reproduce it. it is still falling on
> suspend/resume or just unbind/bind?
> Would you be so kind and send me the whole log.
Both is still broken. I'm actually not
In order for controllers to get PHY in case of non dt boot, the phy
binding information (phy label) should be added in the platform
data of the controller.
Signed-off-by: Kishon Vijay Abraham I
Acked-by: Felipe Balbi
Tested-by: Tomi Valkeinen
---
arch/arm/mach-omap2/usb-musb.c |6 +-
i
After the devices are created using PLATFORM_DEVID_AUTO,
devm_usb_get_phy_dev and usb_get_phy_dev can't be used reliably
as it relies on the device_names passed in usb_bind_phy. So
added a new API to get the PHY reference by PHY label (PHY label
should be filled which creating the PHY).
Signed-off
After the devices are created using PLATFORM_DEVID_AUTO,
devm_usb_get_phy_dev and usb_get_phy_dev can't be used reliably
as it relies on the device_names passed in usb_bind_phy. So used the
new API devm_usb_get_phy_by_name to get the PHY reference.
Signed-off-by: Kishon Vijay Abraham I
Acked-by:
PRECHANGE and POSTCHANGE notifiers must be called in groups, i.e either both
should be called or both shouldn't be.
In case we have started PRECHANGE notifier and found an error, we must call
POSTCHANGE notifier with freqs.new = freqs.old to guarantee that sequence of
calling notifiers is complete
On 6/19/2013 2:22 PM, Viresh Kumar wrote:
> PRECHANGE and POSTCHANGE notifiers must be called in groups, i.e either both
> should be called or both shouldn't be.
>
> In case we have started PRECHANGE notifier and found an error, we must call
> POSTCHANGE notifier with freqs.new = freqs.old to guar
Now that MUSB for OMAP started using devm_usb_get_phy_by_name
which does not require PHY library to already have the binding
information, removed usb_bind_phy calls that binds the MUSB controller
with the PHY from the board files.
Signed-off-by: Kishon Vijay Abraham I
Acked-by: Felipe Balbi
Test
PRECHANGE and POSTCHANGE notifiers must be called in groups, i.e either both
should be called or both shouldn't be.
In case we have started PRECHANGE notifier and found an error, we must call
POSTCHANGE notifier with freqs.new = freqs.old to guarantee that sequence of
calling notifiers is complete
Hi all,
I've been trying to get "xsysace" driver working properly on ARC
architecture.
And I was able to get it built and running, but it required me to do 2
changes - please refer to description below. Now I'd like to get this
driver working for me righ from upstream sources and this is where
Whenever we are changing frequency of a cpu, we are calling PRECHANGE and
POSTCHANGE notifiers. They must be serialized. i.e. PRECHANGE or POSTCHANGE
shouldn't be called twice contiguously.
This can happen due to bugs in users of __cpufreq_driver_target() or actual
cpufreq drivers who are sending
PRECHANGE and POSTCHANGE notifiers must be called in groups, i.e either both
should be called or both shouldn't be.
In case we have started PRECHANGE notifier and found an error, we must call
POSTCHANGE notifier with freqs.new = freqs.old to guarantee that sequence of
calling notifiers is complete
PRECHANGE and POSTCHANGE notifiers must be called in groups, i.e either both
should be called or both shouldn't be.
In case we have started PRECHANGE notifier and found an error, we must call
POSTCHANGE notifier with freqs.new = freqs.old to guarantee that sequence of
calling notifiers is complete
PRECHANGE and POSTCHANGE notifiers must be called in groups, i.e either both
should be called or both shouldn't be.
In case we have started PRECHANGE notifier and found an error, we must call
POSTCHANGE notifier with freqs.new = freqs.old to guarantee that sequence of
calling notifiers is complete
PRECHANGE and POSTCHANGE notifiers must be called in groups, i.e either both
should be called or both shouldn't be.
In case we have started PRECHANGE notifier and found an error, we must call
POSTCHANGE notifier with freqs.new = freqs.old to guarantee that sequence of
calling notifiers is complete
PRECHANGE and POSTCHANGE notifiers must be called in groups, i.e either both
should be called or both shouldn't be.
In case we have started PRECHANGE notifier and found an error, we must call
POSTCHANGE notifier with freqs.new = freqs.old to guarantee that sequence of
calling notifiers is complete
PRECHANGE and POSTCHANGE notifiers must be called in groups, i.e either both
should be called or both shouldn't be.
In case we have started PRECHANGE notifier and found an error, we must call
POSTCHANGE notifier with freqs.new = freqs.old to guarantee that sequence of
calling notifiers is complete
PRECHANGE and POSTCHANGE notifiers must be called in groups, i.e either both
should be called or both shouldn't be.
In case we have started PRECHANGE notifier and found an error, we must call
POSTCHANGE notifier with freqs.new = freqs.old to guarantee that sequence of
calling notifiers is complete
PRECHANGE and POSTCHANGE notifiers must be called in groups, i.e either both
should be called or both shouldn't be.
In case we have started PRECHANGE notifier and found an error, we must call
POSTCHANGE notifier with freqs.new = freqs.old to guarantee that sequence of
calling notifiers is complete
PRECHANGE and POSTCHANGE notifiers must be called in groups, i.e either both
should be called or both shouldn't be.
In case we have started PRECHANGE notifier and found an error, we must call
POSTCHANGE notifier with freqs.new = freqs.old to guarantee that sequence of
calling notifiers is complete
PRECHANGE and POSTCHANGE notifiers must be called in groups, i.e either both
should be called or both shouldn't be.
In case we have started PRECHANGE notifier and found an error, we must call
POSTCHANGE notifier with freqs.new = freqs.old to guarantee that sequence of
calling notifiers is complete
On Wed, Jun 19, 2013 at 02:55:13PM +0800, Chen Gang wrote:
>
> 'lru' may be used without initialized, so need regressing part of the
> related patch.
>
> The related patch:
> "3abf380 mm: remove lru parameter from __lru_cache_add and
> lru_cache_add_lru"
>
>
> Signed-off-by: Chen Gang
> ---
In the case of non-dt boot, the platform specific initialization file
(board file) will do usb_bind_phy that binds the usb controller with the
PHY using device names. After the device names are created using
PLATFORM_DEVID_AUTO, our original method of binding by device names doesn't
work reliably
The 0xa restriction applies to BIOS really...
"m...@console-pimps.org" wrote:
>On Tue, 18 Jun, at 10:12:22PM, Zachary Bobroff wrote:
>> > Okay, I'm fine with that aspect then. Let's hope everyone plays by
>> > that rule.
>> This is all according to specification, so if they are not following
PRECHANGE and POSTCHANGE notifiers must be called in groups, i.e either both
should be called or both shouldn't be.
In case we have started PRECHANGE notifier and found an error, we must call
POSTCHANGE notifier with freqs.new = freqs.old to guarantee that sequence of
calling notifiers is complete
On Wed, Jun 19, 2013 at 04:00:32PM +0800, Wanpeng Li wrote:
> On Wed, Jun 19, 2013 at 03:33:55PM +0900, Joonsoo Kim wrote:
> >In free path, we don't check number of cpu_partial, so one slab can
> >be linked in cpu partial list even if cpu_partial is 0. To prevent this,
> >we should check number of
On Wed, Jun 19, 2013 at 11:35:27AM +0400, Glauber Costa wrote:
> On Wed, Jun 19, 2013 at 09:13:46AM +0200, Michal Hocko wrote:
> > On Tue 18-06-13 10:26:24, Glauber Costa wrote:
> > [...]
> > > Michal, would you mind testing the following patch?
> > >
> > > diff --git a/fs/inode.c b/fs/inode.c
> >
>
> However, it still does not work, commit
> 42f132febff3b7b42c6c9dbfc151f29233be3132 does not seem to help enough
> on my hardware.
>
> Still just unbinding and rebinding with
> echo :00:03.0 > /sys/bus/pci/drivers/mei_me/unbind
> echo :00:03.0 > /sys/bus/pci/drivers/mei_me/bind
>
> tr
__cpufreq_notify_transition() is used only in cpufreq.c, make it static.
Signed-off-by: Viresh Kumar
---
drivers/cpufreq/cpufreq.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
index 7c38842..8a9a23a 100644
--- a/drivers
On Sat, Apr 20, 2013 at 12:19:23PM -0700, Andi Kleen wrote:
> From: Andi Kleen
>
> Add support to perf stat to print the basic transactional execution
> statistics:
> Total cycles, Cycles in Transaction, Cycles in aborted transsactions
> using the intx and intx_checkpoint qualifiers.
> Transacti
There were few noticeable formatting issues present in core cpufreq code. This
patch tries to fix them to make code look better. These are:
- Removing few extra blank lines
- Adding few blank lines
- replacing spaces with tabs
- removing unnecessary spaces
- rearranging code a bit
- Fixing multilin
On Fri, Jun 07, 2013 at 02:19:09PM +0200, Paul Walmsley wrote:
> Add DFLL DVCO reset line control functions to the CAR IP block driver.
>
> The DVCO present in the DFLL IP block has a separate reset line,
> exposed via the CAR IP block. This reset line is asserted upon SoC
> reset. Unless someth
Fixes checkpatch error:
There were assignments in if conditions, so I extracted them.
Signed-off-by: Lorenz Haspel
Signed-off-by: Michael Banken
---
v2: removed some buggy extra lines and fixed white space issues
v3: fixed some more extra lines
---
drivers/staging/silicom/bpctl_mod.c | 179 +++
On 19/06/13 09:26, Russell King wrote:
On Wed, Jun 19, 2013 at 10:44:09AM +1000, Stephen Rothwell wrote:
Hi Lorenzo,
Today's linux-next merge of the arm-mpidr tree got a conflict in
arch/arm/kernel/suspend.c between commit aa1aadc3305c ("ARM: suspend: fix
CPU suspend code for !CONFIG_MMU config
On Tue, 18 Jun, at 10:12:22PM, Zachary Bobroff wrote:
> > Okay, I'm fine with that aspect then. Let's hope everyone plays by
> > that rule.
> This is all according to specification, so if they are not following
> these rules they should be corrected. The link to where the current
> public version
On Wed, 19 Jun 2013, Chen Gang wrote:
>
> Since "WARN_ON(worker->task)", we can not assume that 'worker->task'
> will be NULL before set 'current' to it.
It better is NULL and all that WARN_ON does is to verify that.
> So need let 'worker' lock protected too, just like it already lock
> protec
701 - 800 of 859 matches
Mail list logo
