Used the generic PHY framework API to create the PHY. For powering on
and powering off the PHY, power_on and power_off ops are used. Once the
MUSB OMAP glue is adapted to the new framework, the suspend and resume
ops of usb phy library will be removed.
However using the old usb phy library cannot
On 07/18/2013 02:49 PM, Al Viro wrote:
> On Thu, Jul 18, 2013 at 02:28:49PM +0800, Chen Gang wrote:
>> > When "str >= end", necessary to reset 'str' to "end - 1", or the return
>> > value will be larger than the real one, the callers which depend on the
>> > return value, may cause memory overflow.
Used the generic PHY framework API to create the PHY. Now the power off and
power on are done in omap_usb_power_off and omap_usb_power_on respectively.
However using the old USB PHY library cannot be completely removed
because OTG is intertwined with PHY and moving to the new framework
will break
On 07/18/2013 02:42 PM, George Spelvin wrote:
>> When "str >= end", necessary to reset 'str' to "end - 1", or the return
>> > value will be larger than the real one, the callers which depend on the
>> > return value, may cause memory overflow.
> NAK. This is the documented (by both the function it
On Tue, Jul 16, 2013 at 08:01:46PM +1000, David Gibson wrote:
> On Tue, Jul 16, 2013 at 02:34:24PM +0900, Joonsoo Kim wrote:
> > On Mon, Jul 15, 2013 at 09:51:21PM -0400, Rik van Riel wrote:
> > > On 07/15/2013 03:24 AM, David Gibson wrote:
> > > >On Sun, Jul 14, 2013 at 08:16:44PM -0700, Davidlohr
Now that twl4030-usb is adapted to the new generic PHY framework,
*set_suspend* and *phy_init* ops can be removed from twl4030-usb driver.
Signed-off-by: Kishon Vijay Abraham I
Acked-by: Felipe Balbi
Reviewed-by: Sylwester Nawrocki
---
drivers/usb/phy/phy-twl4030-usb.c | 57 +
* Andrew Hunter wrote:
> Hi, I have a patch (following) that modifies handling of APIC id tables,
> trading a small amount of space in the (NR_CPUS - nr_cpu_ids) >> 0 case for
> faster accesses and slightly better cache layout (as APIC ids are mostly used
> cross-cpu.) I'm not an APIC expert so
On Thu, Jul 18, 2013 at 02:28:49PM +0800, Chen Gang wrote:
> When "str >= end", necessary to reset 'str' to "end - 1", or the return
> value will be larger than the real one, the callers which depend on the
> return value, may cause memory overflow.
You do realize that snprintf(s, 1, "abc") should
From: Jingoo Han
Add a PHY provider driver for the Samsung Exynos SoC Display Port PHY.
Signed-off-by: Jingoo Han
Reviewed-by: Tomasz Figa
Cc: Sylwester Nawrocki
Acked-by: Felipe Balbi
Signed-off-by: Kishon Vijay Abraham I
---
.../devicetree/bindings/phy/samsung-phy.txt|8 ++
d
From: Jingoo Han
Exynos Display Port can be used only for Exynos SoCs. In addition,
non-DT for EXYNOS SoCs is not supported from v3.11; thus, there is
no need to support non-DT for Exynos Display Port.
The 'include/video/exynos_dp.h' file has been used for non-DT
support and the content of file
From: Sylwester Nawrocki
Generic PHY drivers are used to handle the MIPI CSIS and MIPI DSIM
DPHYs so we can remove now unused code at arch/arm/plat-samsung.
In case there is any board file for S5PV210 platforms using MIPI
CSIS/DSIM (not any upstream currently) it should use the generic
PHY API to
From: Jingoo Han
Use the generic PHY API to control the DP PHY.
Signed-off-by: Jingoo Han
Reviewed-by: Tomasz Figa
Signed-off-by: Kishon Vijay Abraham I
---
.../devicetree/bindings/video/exynos_dp.txt | 18 +-
drivers/video/exynos/exynos_dp_core.c|
From: Sylwester Nawrocki
Use the generic PHY API instead of the platform callback to control
the MIPI DSIM DPHY. The 'phy_label' field is added to the platform
data structure to allow PHY lookup on non-dt platforms.
Signed-off-by: Sylwester Nawrocki
Signed-off-by: Kyungmin Park
Acked-by: Felip
From: Sylwester Nawrocki
Use the generic PHY API instead of the platform callback to control
the MIPI CSIS DPHY. The 'phy_label' field is added to the platform
data structure to allow PHY lookup on non-dt platforms
Signed-off-by: Sylwester Nawrocki
Signed-off-by: Kyungmin Park
Acked-by: Felipe
From: Sylwester Nawrocki
Add a PHY provider driver for the Samsung S5P/Exynos SoC MIPI CSI-2
receiver and MIPI DSI transmitter DPHYs.
Signed-off-by: Sylwester Nawrocki
Signed-off-by: Kyungmin Park
Acked-by: Felipe Balbi
Signed-off-by: Kishon Vijay Abraham I
---
.../devicetree/bindings/phy/s
Now that omap-usb2 is adapted to the new generic PHY framework,
*set_suspend* ops can be removed from omap-usb2 driver.
Signed-off-by: Kishon Vijay Abraham I
Acked-by: Felipe Balbi
Reviewed-by: Sylwester Nawrocki
---
drivers/usb/phy/phy-omap-usb2.c | 25 -
1 file chan
In order for controllers to get PHY in case of non dt boot, the phy
binding information (phy device name) should be added in the platform
data of the controller.
Signed-off-by: Kishon Vijay Abraham I
Reviewed-by: Sylwester Nawrocki
Acked-by: Felipe Balbi
---
arch/arm/mach-omap2/usb-musb.c |
Use the generic PHY framework API to get the PHY. The usb_phy_set_resume
and usb_phy_set_suspend is replaced with power_on and
power_off to align with the new PHY framework.
musb->xceiv can't be removed as of now because musb core uses xceiv.state and
xceiv.otg. Once there is a separate state mach
Updated the usb_otg_hs dt data to include the *phy* and *phy-names*
binding in order for the driver to use the new generic PHY framework.
Also updated the Documentation to include the binding information.
The PHY binding information can be found at
Documentation/devicetree/bindings/phy/phy-bindings
Added a generic PHY framework that provides a set of APIs for the PHY drivers
to create/destroy a PHY and APIs for the PHY users to obtain a reference to
the PHY with or without using phandle.
This framework will be of use only to devices that uses external PHY (PHY
functionality is not embedded w
The PHY framework provides a set of APIs for the PHY drivers to
create/destroy a PHY and APIs for the PHY users to obtain a reference to the
PHY with or without using phandle. For dt-boot, the PHY drivers should
also register *PHY provider* with the framework.
PHY drivers should create the PHY by
On Wed, Jul 17, 2013 at 10:00:48AM +0800, Jianguo Wu wrote:
> On 2013/7/15 17:52, Joonsoo Kim wrote:
>
> > Current node iteration code have a minor problem which do one more
> > node rotation if we can't succeed to allocate. For example,
> > if we start to allocate at node 0, we stop to iterate at
On 07/17/2013 03:30 PM, Grygorii Strashko wrote:
> On 07/17/2013 02:57 PM, Roger Quadros wrote:
>> Hi Grygorii,
>>
>> On 07/17/2013 02:41 PM, Grygorii Strashko wrote:
>>> Hi Tony, Kevin
>>>
>>> This patch series introduces dynamic pinctrl handling in OMAP device
>>> framework
>>> in the same way a
> When "str >= end", necessary to reset 'str' to "end - 1", or the return
> value will be larger than the real one, the callers which depend on the
> return value, may cause memory overflow.
NAK. This is the documented (by both the function itself and the
ANSI/ISO C standard) and desired return v
Hi Jiri,
On Thu, 11 Jul 2013 16:56:54 +0900, Namhyung Kim wrote:
> On Wed, 10 Jul 2013 16:18:20 +0200, Jiri Olsa wrote:
>> On Wed, Jun 26, 2013 at 04:14:09PM +0900, Namhyung Kim wrote:
>>> From: Namhyung Kim
>>>
>>> The -p (--pid) option enables to trace existing process by its pid.
>>
>> hi,
>>
When "str >= end", necessary to reset 'str' to "end - 1", or the return
value will be larger than the real one, the callers which depend on the
return value, may cause memory overflow.
When for copying constant string, 'str' is point to destination buffer,
so it need add 'copy' (for destination bu
On Thu, Jul 18, 2013 at 02:25:19PM +0800, Xiao Guangrong wrote:
> On 07/18/2013 02:06 PM, Gleb Natapov wrote:
> > On Thu, Jul 18, 2013 at 02:01:47PM +0800, Xiao Guangrong wrote:
> >> On 07/18/2013 01:31 PM, Gleb Natapov wrote:
> >>> On Thu, Jul 18, 2013 at 12:52:37PM +0800, Xiao Guangrong wrote:
>
On Thursday 18 July 2013 11:54 AM, Greg KH wrote:
> On Thu, Jul 18, 2013 at 11:33:17AM +0530, Kishon Vijay Abraham I wrote:
Wanted to group all the PHY drivers to be used by different subsystems
(SATA/USB/PCIE/HDMI/VIDEO) into a single entity. There were some comments
in my
ini
On 07/18/2013 02:06 PM, Gleb Natapov wrote:
> On Thu, Jul 18, 2013 at 02:01:47PM +0800, Xiao Guangrong wrote:
>> On 07/18/2013 01:31 PM, Gleb Natapov wrote:
>>> On Thu, Jul 18, 2013 at 12:52:37PM +0800, Xiao Guangrong wrote:
Currently, fast page fault tries to fix mmio page fault when the
On Thu, Jul 18, 2013 at 11:33:17AM +0530, Kishon Vijay Abraham I wrote:
> >> Wanted to group all the PHY drivers to be used by different subsystems
> >> (SATA/USB/PCIE/HDMI/VIDEO) into a single entity. There were some comments
> >> in my
> >> initial version [3] on using a bus_type instead of clas
I ressurected an old Athlon XP box for fun, and was stress-testing it
with mprime. (It had been stable before retirement.) After 34 hours
of successful torture test (suggesting a stable memory syatem), I found
this on the screen (hand-transcribed, top scrolled off):
h_rpcgss oid_registry exportf
On Thu, Jul 18, 2013 at 02:01:47PM +0800, Xiao Guangrong wrote:
> On 07/18/2013 01:31 PM, Gleb Natapov wrote:
> > On Thu, Jul 18, 2013 at 12:52:37PM +0800, Xiao Guangrong wrote:
> >> Currently, fast page fault tries to fix mmio page fault when the
> >> generation number is invalid (spte.gen != kvm.
- 原始邮件 -
> 发件人: "H. Peter Anvin"
> 收件人: "CAI Qian"
> 抄送: "Steven Rostedt" , "Thomas Gleixner"
> , "Sarah Sharp"
> , "Linus Torvalds"
> , "Ingo Molnar" ,
> "Guenter Roeck" , "Greg Kroah-Hartman"
> , "Dave Jones"
> , "Linux Kernel Mailing List"
> , "Andrew Morton"
> , "stable" , "Darr
Hi,
On Wednesday 17 July 2013 10:55 PM, Greg KH wrote:
> On Wed, Jul 17, 2013 at 03:02:59PM +0530, Kishon Vijay Abraham I wrote:
>> Hi,
>>
>> On Wednesday 17 July 2013 11:59 AM, Greg KH wrote:
>>> On Wed, Jun 26, 2013 at 05:17:29PM +0530, Kishon Vijay Abraham I wrote:
+menuconfig GENERIC_PHY
On 07/18/2013 01:31 PM, Gleb Natapov wrote:
> On Thu, Jul 18, 2013 at 12:52:37PM +0800, Xiao Guangrong wrote:
>> Currently, fast page fault tries to fix mmio page fault when the
>> generation number is invalid (spte.gen != kvm.gen) and returns to
>> guest to retry the fault since it sees the last s
Hi all,
Changes since 20130717:
The sound-asoc tree lost a build failure but still has another so I used
the version from next-20130715.
The drm-intel tree gained conflicts against the drm-intel-fixes tree.
The aio tree lost its build failure.
The akpm tree gained a conflict against the drm
From: Matthew Garrett
We have to call acpi_video_init_brightness() even if we're not going
to initialise the backlight - Thinkpads seem to use this as the
trigger for enabling ACPI notifications rather than handling it in
firmware.
[rjw: Drop the brightness object created by
acpi_video_init_bri
On 07/18/2013 01:36 PM, Yan, Zheng wrote:
> From: "Yan, Zheng"
>
> Compare to old atom, Silvermont has offcore and has more events
> that support PEBS.
>
> Silvermont has two offcore response configuration MSRs, but the
> event code for OFFCORE_RSP_1 is 0x02b7. To avoid complicating
> intel_fixu
From: Aaron Lu
Expose acpi_gbl_osi_data so that code outside of ACPICA can check
the value of the last successfull _OSI call. The definitions for
OSI versions are moved to actypes.h so that other components can
access them too.
Based on a patch from Matthew Garrett which in turn was based on
an
From: "Yan, Zheng"
Compare to old atom, Silvermont has offcore and has more events
that support PEBS.
Silvermont has two offcore response configuration MSRs, but the
event code for OFFCORE_RSP_1 is 0x02b7. To avoid complicating
intel_fixup_er(), use INTEL_UEVENT_EXTRA_REG to define offcore
MSRs.
On Thu, Jul 18, 2013 at 12:52:37PM +0800, Xiao Guangrong wrote:
> Currently, fast page fault tries to fix mmio page fault when the
> generation number is invalid (spte.gen != kvm.gen) and returns to
> guest to retry the fault since it sees the last spte is nonpresent
> which causes infinity loop
>
On 07/17/2013 11:17 PM, Eduardo Valentin wrote:
> This patch adds to lm75 temperature sensor the possibility
> to expose itself as thermal zone device, registered on the
> thermal framework.
>
> The thermal zone is built only if a device tree node
> describing a thermal zone for this sensor is pre
Hi Linus,
On Mon, 15 Jul 2013 10:57:35 -0400 Paul Gortmaker
wrote:
>
> Please pull the following to get phase two of the __cpuinit removal.
>
> With the __cpuinit infrastructure removed earlier, this group of commits
> only removes the function/data tagging that was done with the various
> (now
On 07/17/2013 09:01 PM, CAI Qian wrote:
>
> Please don't get me wrong. I did neither compare Linus to those child abusers
> nor Thomas to those children. I simply pointed out there is also some common
> sense need to consider.
>
Actually, you did.
-hpa
--
To unsubscribe from this list
On Wed, Jul 17, 2013 at 03:24:18PM -0700, Sarah Sharp wrote:
> > > Abuse is never justified, I hope that's clear for everybody.
> >
> > Depends on details of your definition of abuse.
[snip]
> http://outofthefog.net/CommonBehaviors/VerbalAbuse.html
" "Always" and "Never" Statements - "Always"
Hi Andrew,
Today's linux-next merge of the akpm tree got a conflict in
drivers/gpu/drm/i915/i915_gem.c between commit 5cef07e16283 ("drm/i915:
Move active/inactive lists to new mm") from the drm-intel tree and commit
"drivers-convert-shrinkers-to-new-count-scan-api-fix" from the akpm tree.
I fixe
On 07/18/2013 12:52 PM, Xiao Guangrong wrote:
> Currently, fast page fault tries to fix mmio page fault when the
> generation number is invalid (spte.gen != kvm.gen) and returns to
> guest to retry the fault since it sees the last spte is nonpresent
> which causes infinity loop
>
> It can be trigg
Currently, fast page fault tries to fix mmio page fault when the
generation number is invalid (spte.gen != kvm.gen) and returns to
guest to retry the fault since it sees the last spte is nonpresent
which causes infinity loop
It can be triggered only on AMD host since the mmio page fault is
recogni
I have given a simple test for it.
for current REISERFS_MAX_ERROR_BUF (error_buffer[4096]), it will report
the full message warnings.
[root@dhcp122 ~]# mount /dev/sda11 /mnt/sda11
[root@dhcp122 ~]# dmesg | grep reiser
[ 423.421532] REISERFS warning (device sda11): reiserfs_fill_super:
CONFIG_
- Original Message -
> From: "Steven Rostedt"
> To: "CAI Qian"
> Cc: "Thomas Gleixner" , "Sarah Sharp"
> , "Linus Torvalds"
> , "Ingo Molnar" , "Guenter
> Roeck" , "Greg
> Kroah-Hartman" , "Dave Jones" ,
> "Linux Kernel Mailing List"
> , "Andrew Morton" ,
> "stable" ,
> "Darren Hart
On Wed, 2013-07-17 at 20:01 +0200, Peter Zijlstra wrote:
> On Wed, Jul 17, 2013 at 01:51:51PM -0400, Rik van Riel wrote:
> > On 07/17/2013 12:18 PM, Peter Zijlstra wrote:
>
> > >So the way I see things is that the only way newidle balance can slow down
> > >things is if it runs when we could have
- Original Message -
> From: "Steven Rostedt"
> To: "CAI Qian"
> Cc: "Thomas Gleixner" , "Sarah Sharp"
> , "Linus Torvalds"
> , "Ingo Molnar" , "Guenter
> Roeck" , "Greg
> Kroah-Hartman" , "Dave Jones" ,
> "Linux Kernel Mailing List"
> , "Andrew Morton" ,
> "stable" ,
> "Darren Hart
Hi Scott,
> What specifically should I do to test it?
Could you double check perf annotate works? I'm 99% sure it will but
that is what was failing on ppc64.
Anton
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
Mo
> If you can point me to a single instance of Linus "abusing" someone
> who is not one of his trusted persons, who really should be able to
> deal with that, or someone who did not provoke him to go into rant
> mode, then I'm all on your side.
Well, the one that comes to mind is Alan Cox and the T
On Wed, 2013-07-17 at 23:16 -0400, CAI Qian wrote:
> > So if you talk about abuse, then you need an abuser and a victim. So
> > your argumentation falls flat because there is no victim.
> Could victim be someone else in the future since it is an example that
> people may follow?
> http://en.wikipe
Tim Chen wrote:
> > > Your approach is quite complicated. I think something simpler like the
> > > following will work:
> >
> > We cannot benefit from PCLMULQDQ. Is it acceptable for you?
>
>
> The following code in crct10dif-pclmul_glue.c
>
> static const struct x86_cpu_id crct10dif_cpu_id[] =
On Wed, Jul 17, 2013 at 05:17:36PM -0700, Linus Torvalds wrote:
> On Wed, Jul 17, 2013 at 4:40 PM, Ben Myers wrote:
> >>
> >> We're still talking at cross purposes then.
> >>
> >> How the hell do you handle mmap() and page faulting?
> >
> > __xfs_get_blocks serializes access to the block map with
On 07/17/2013 07:39 PM, Stephen Boyd wrote:
This patchset cleans up the last few stragglers using the sched_clock.h
header file in asm and removes the asm header.
A new one appeared in drivers/clocksource so I'm not sure who
wants to take that one.
Thanks for doing this!
I'll queue the driver
On Thu, Jul 18, 2013 at 03:33:01AM +0200, Frederic Weisbecker wrote:
> On Wed, Jul 17, 2013 at 05:41:41PM -0700, Paul E. McKenney wrote:
> > On Thu, Jul 18, 2013 at 01:31:21AM +0200, Frederic Weisbecker wrote:
> > > I'm missing a key here.
> > >
> > > Let's imagine that the timekeeper has finally
On Wed, Jul 17, 2013 at 09:03:11AM -0700, Linus Torvalds wrote:
> On Tue, Jul 16, 2013 at 10:51 PM, Dave Chinner wrote:
> >
> > But When i say "stale data" I mean that the data being returned
> > might not have originally belonged to the underlying file you are
> > reading.
>
> We're still talkin
- Original Message -
> From: "Thomas Gleixner"
> To: "Sarah Sharp"
> Cc: "Linus Torvalds" , "Ingo Molnar"
> , "Guenter Roeck"
> , "Greg Kroah-Hartman" ,
> "Steven Rostedt" ,
> "Dave Jones" , "Linux Kernel Mailing List"
> , "Andrew Morton"
> , "stable" , "Darren Hart"
>
> Sent: Thur
Add the regulator driver for PMIC 88pm800 including device tree
support.
88pm800 is an I2C-based power-management IC containing voltage
regulators, a real-time clock, and some general purpose ADC devices,
Signed-off-by: Yi Zhang
Signed-off-by: Chao Xie
---
.../devicetree/bindings/regulator/88pm
On Tue, 2013-06-18 at 21:21 +0200, Oleg Nesterov wrote:
> Hello.
>
> On top of "PATCH 0/3] tracing: more list_empty(perf_events) checks"
> series I sent yesterday.
>
> Compile tested only, not for inclusion yet.
Oleg, I know you sent me a mbox with these patches, but I rather pull
the real email
We try to linearize part of the skb when the number of iov is greater than
MAX_SKB_FRAGS. This is not enough since each single vector may occupy more than
one pages, so zerocopy_sg_fromiovec() may still fail and may break the guest
network.
Solve this problem by calculate the pages needed for iov
We try to linearize part of the skb when the number of iov is greater than
MAX_SKB_FRAGS. This is not enough since each single vector may occupy more than
one pages, so zerocopy_sg_fromiovec() may still fail and may break the guest
network.
Solve this problem by calculate the pages needed for iov
- Original Message -
> From: "Sarah Sharp"
> To: "CAI Qian"
> Cc: "Trond Myklebust" , "Ric Wheeler"
> , "David Lang"
> , ksummit-2013-disc...@lists.linuxfoundation.org, "Greg
> Kroah-Hartman" ,
> "Darren Hart" , "Ingo Molnar" ,
> "Olivier Galibert" ,
> "Linux Kernel Mailing List" , "
Peter,
These have been discussed, and they mostly live in the tracing
directory, but are perf related. Can you give me your Acked-by on them.
Thanks,
-- Steve
On Mon, 2013-06-17 at 19:01 +0200, Oleg Nesterov wrote:
> Hello.
>
> Steven, we already discussed this a bit some time ago...
>
> DEC
On Wed, Jul 17, 2013 at 05:58:13PM -0700, Hugh Dickins wrote:
> On Wed, 17 Jul 2013, Dave Hansen wrote:
> > On 07/17/2013 02:09 PM, Andrew Morton wrote:
> > > lock_page() is a pretty commonly called function, and I assume quite a
> > > lot of people run with CONFIG_DEBUG_VM=y.
> > >
> > > Is
Hi all,
Now i worked on omp2 and met a probelm which someplace close_irq for
3.6second.
The kernel version is 2.6.37. I used trace to find in irq_action:omap_hsmmc_irq.
This problem occured by removed the sdcard when there are io operations.
I found the read problem is in omap_hsmmc_rese
On 07/17/2013 07:06 PM, Michael S. Tsirkin wrote:
> On Wed, Jul 17, 2013 at 06:32:11PM +0800, Jason Wang wrote:
>> We try to linearize part of the skb when the number of iov is greater than
>> MAX_SKB_FRAGS. This is not enough since each single vector may occupy more
>> than
>> one pages, so zeroc
Fixes for iomem annotations in arch/x86/kernel/tboot.c
Signed-off-by: Qiaowei Ren
---
arch/x86/kernel/tboot.c | 21 -
1 file changed, 12 insertions(+), 9 deletions(-)
diff --git a/arch/x86/kernel/tboot.c b/arch/x86/kernel/tboot.c
index 3ff42d2..afe8cf8 100644
--- a/arch/x8
On Wed, 2013-07-17 at 11:51 -0700, Sarah Sharp wrote:
> Here's a gem from a senior software developer at Nvidia:
> https://picasaweb.google.com/116960357493251979546/Trolls#5901298464591248626
>
> And another email from a software developer in Portland, where I live:
> https://picasaweb.google.com
This header file is no longer needed now that the ARM sched_clock
framework is generic and all users have moved to linux/sched_clock.h
instead of asm/sched_clock.h. Remove it.
Signed-off-by: Stephen Boyd
---
arch/arm/include/asm/sched_clock.h | 4
1 file changed, 4 deletions(-)
delete mode
The sched_clock.h include is under include/linux now.
Cc: Sebastian Hesselbarth
Signed-off-by: Stephen Boyd
---
drivers/clocksource/time-orion.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/clocksource/time-orion.c b/drivers/clocksource/time-orion.c
index ecbeb68.
The sched_clock.h include is under include/linux now.
Cc: Alexander Shiyan
Signed-off-by: Stephen Boyd
---
arch/arm/mach-clps711x/common.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mach-clps711x/common.c b/arch/arm/mach-clps711x/common.c
index 4ca2f3c..134641d
This patchset cleans up the last few stragglers using the sched_clock.h
header file in asm and removes the asm header.
A new one appeared in drivers/clocksource so I'm not sure who
wants to take that one.
Stephen Boyd (3):
clocksource: orion: Use linux/sched_clock.h
ARM: clps711x: Use linux/s
(2013/07/17 23:51), Oleg Nesterov wrote:
> On 07/17, Masami Hiramatsu wrote:
>>
>> (2013/07/16 3:16), Oleg Nesterov wrote:
>>> On 07/09, Masami Hiramatsu wrote:
To avoid this, when opening events/*/*/enable, we have to ensure
the dentry of the file is not unlinked yet, under event_mu
Hi, Peter
Davidlohr has tested the v3 patch set and it work well as reported (and
in my test too), I thing your patch has solved the issue he found in v2 :)
Thus I think v3 is ready for next step now, I wish it has not yet been
removed out of your apply-queue ;-)
Regards,
Michael Wang
On 07/15/
Hi Mark,
On Thu, 18 Jul 2013 09:38:24 +1000 Stephen Rothwell
wrote:
>
> So these are the errors I got yesterday:
>
> sound/soc/fsl/imx-mc13783.c:23:28: fatal error: asm/mach-types.h: No such
> file or directory
> #include
> ^
>
> I didn't look closely enough, bec
On Wed, Jul 17, 2013 at 4:18 PM, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> Using the hotplug context objects introduced previously rework the
> ACPI-based PCI hotplug (ACPIPHP) core code so that all notifications
> for ACPI device objects corresponding to the hotplug PCI devices are
On Tue, Jul 16, 2013 at 7:06 PM, Alban Browaeys
wrote:
> Set fmt.pix.priv to zero in vidioc_g_fmt_vid_cap
> and vidioc_try_fmt_vid_cap.
Any reason not to have the v4l2 core do this before dispatching to the
driver? Set it to zero before the core calls g_fmt. This avoids all
the drivers (most o
Hi all,
Today's linux-next merge of the drm-intel tree got a conflict in
drivers/gpu/drm/i915/i915_gem.c between commit 067556084a0e ("drm/i915:
Correct obj->mm_list link to dev_priv->dev_priv->mm.inactive_list") from
the drm-intel-fixes tree and commit 5cef07e16283 ("drm/i915: Move
active/inactiv
On Wed, 2013-07-17 at 10:14 +0400, James Bottomley wrote:
> > OK, I am stupid enough to take a stab at this...
> >
> > 1.Does the Linux kernel community's health depend on the occasional
> > rant? [My guess is that we simply have no way of knowing.
> > That said, I would be intere
On Wed, Jul 17, 2013 at 4:17 PM, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> When either a new hotplug bridge or a new hotplug function is added
> by the ACPI-based PCI hotplug (ACPIPHP) code, attach a context object
> to its ACPI handle to store hotplug-related information in it. To
On Mon, 15 Jul 2013 16:20:17 +0100
Mel Gorman wrote:
> Ideally it would be possible to distinguish between NUMA hinting faults that
> are private to a task and those that are shared. If treated identically
> there is a risk that shared pages bounce between nodes depending on
Your patch 15 breaks
Hi Ben,
On 07/17/2013 09:44 PM, Benjamin LaHaise wrote:
> On Wed, Jul 17, 2013 at 05:22:30PM +0800, Gu Zheng wrote:
>> As the aio job will pin the ring pages, that will lead to mem migrated
>> failed. In order to fix this problem we use an anon inode to manage the aio
>> ring
>> pages, and setu
Hi all,
Today's linux-next merge of the drm-intel tree got a conflict in
drivers/gpu/drm/i915/i915_dma.c between commit 7dcd2677ea91 ("drm/i915:
fix long-standing SNB regression in power consumption after resume v2")
from the drm-intel-fixes tree and commit 59cdb63d529c ("drm/i915: kill
dev_priv->
On Wed, Jul 17, 2013 at 4:16 PM, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> The acpiphp_enumerate_slots() function is now split into two parts,
> acpiphp_enumerate_slots() proper and init_bridge_misc() which is
> only called by the former. If these functions are combined,
> it is pos
On Wed, Jul 17, 2013 at 05:41:41PM -0700, Paul E. McKenney wrote:
> On Thu, Jul 18, 2013 at 01:31:21AM +0200, Frederic Weisbecker wrote:
> > I'm missing a key here.
> >
> > Let's imagine that the timekeeper has finally set full_sysidle_state =
> > RCU_SYSIDLE_FULL_NOTED
> > with cmpxchg, what gua
Thanks for your reply.
> -Original Message-
> From: Ming Lei [mailto:tom.leim...@gmail.com]
> Sent: Wednesday, July 17, 2013 5:52 PM
> To: 김기오
> Cc: Alan Stern; linux-...@vger.kernel.org; linux-kernel@vger.kernel.org;
> Mark Salter; namhyung@lge.com; Minchan Kim; Chanho Min; Jong-Sung
David Miller writes:
> From: "Michael S. Tsirkin"
> Date: Wed, 17 Jul 2013 08:00:32 +0300
>
>> On Tue, Jul 16, 2013 at 12:33:26PM -0700, David Miller wrote:
>>> From: Rusty Russell
>>> Date: Mon, 15 Jul 2013 11:13:25 +0930
>>>
>>> > From: Michael S. Tsirkin
>>> >
>>> > For small packets we ca
From: Geert Uytterhoeven
Date: Wed, 17 Jul 2013 14:25:05 +0200
> drivers/net/ethernet/i825xx/sun3_82586.c: In function 'sun3_82586_timeout':
> drivers/net/ethernet/i825xx/sun3_82586.c:993:89: warning: array subscript is
> above array bounds [-Warray-bounds]
>
> Using the default NUM_XMIT_BUFFS
On Wed, 2013-07-17 at 17:03 -0600, Shuah Khan wrote:
> diff --git a/include/trace/events/power.h b/include/trace/events/power.h
> index 8e42410..24afd22 100644
> --- a/include/trace/events/power.h
> +++ b/include/trace/events/power.h
> @@ -66,6 +66,41 @@ TRACE_EVENT(machine_suspend,
> TP_pri
On Tue, Jul 16, 2013 at 10:34:08AM -0700, Richard Henderson wrote:
> The series seems pretty stable under QEMU, but I have no real hardware
> on which to test -- the whole reason I'm interested in QEMU of course.
> So I'm hoping that someone will notice this and help me out with testing.
Tested th
This patch adds new interfaces to create and destory cache,
ext4_xattr_create_cache() and ext4_xattr_destroy_cache(), and remove the cache
creation and destory calls from ex4_init_xattr() and ext4_exitxattr() in
fs/ext4/xattr.c.
fs/ext4/super.c has been changed so that when a filesystem is mounted
The patch increases the parallelism of mb_cache_entry utilization by
introducing new spinlocks to the mb_cache structure to protect the mb_cache
local block and index hash chains, while the global mb_cache_lru_list and
mb_cache_list continue to be protected by the global mb_cache_spinlock.
Signed-
On Wed, Jul 17, 2013 at 4:15 PM, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> Since acpi_pci_slot_enumerate() and acpiphp_enumerate_slots() can get
> the ACPI device handle they need from bus->bridge, it is not
> necessary to pass that handle to them as an argument.
>
> Drop the second
On Wed, 17 Jul 2013, Dave Hansen wrote:
> On 07/17/2013 02:09 PM, Andrew Morton wrote:
> > lock_page() is a pretty commonly called function, and I assume quite a
> > lot of people run with CONFIG_DEBUG_VM=y.
> >
> > Is the overhead added by this patch really worthwhile?
>
> I always thought of it
On Wed, Jul 17, 2013 at 04:19:34PM -0700, Guenter Roeck wrote:
> On Wed, Jul 17, 2013 at 04:08:31PM -0700, Paul E. McKenney wrote:
> > On Wed, Jul 17, 2013 at 03:49:23PM -0700, Randy Dunlap wrote:
> > > On 07/17/13 15:02, Guenter Roeck wrote:
> > > > On Wed, Jul 17, 2013 at 07:40:43AM -0700, Sarah
This patch intends to improve the scalability of an ext4 filesystem by
introducing higher degree of parallelism to the usages of its mb_cache and
mb_cache_entries.
Here are some of the benchmark results with the changes.
On a 90 core machine:
Here are the performance improvements in some of the
1 - 100 of 982 matches
Mail list logo
