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. Also twl4030-usb driver is moved
to
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
The PHY framework uses the phy consumer data populated in platform data in the
case of non-dt boot to return the reference to the PHY when the controller
(PHY consumer) requests for it. So populated the phy consumer data in the
platform
data of twl usb.
Signed-off-by: Kishon Vijay Abraham I
---
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.
The omap-usb2 driver is also moved to driver/phy.
However using the old USB PHY library cannot be completely removed
because OTG is intertwined
On 08/21/2013 01:31 PM, Cyrill Gorcunov wrote:
> On Wed, Aug 21, 2013 at 10:21:22AM +0800, Chen Gang wrote:
>> mpol_to_str() may fail, and not fill the buffer (e.g. -EINVAL), so need
>> check about it, or buffer may not be zero based, and next seq_printf()
>> will cause issue.
>>
>> Signed-off-by:
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/phy/phy-omap-usb2.c | 25 -
1 file
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
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
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/phy/phy-twl4030-usb.c | 57
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
On Thu, Aug 08, 2013 at 05:24:41PM +0200, Miklos Szeredi wrote:
> Here's a series for fixing issues with d_drop on a directory dentry with
> children and adding support for such dropped directories in fuse.
>
> This one fixes a couple of issues I found with the previous incarnation and
> split
On Tue, Aug 20, 2013 at 05:49:24PM -0700, Greg KH wrote:
> On Tue, Aug 20, 2013 at 08:41:23PM -0400, Josh Boyer wrote:
> > On Tue, Aug 20, 2013 at 7:57 PM, Greg KH wrote:
> > >> I like this overall. The only thing I might change is "wait for -rc2"
> > >> for patches tagged with CC: stable that
On Wed, Aug 21, 2013 at 2:14 AM, Stephen Rothwell wrote:
> Hi Dave,
>
> On Tue, 20 Aug 2013 14:13:15 -0500 Dave Kleikamp
> wrote:
>>
>> Would you be willing to pick up
>> git://github.com/kleikamp/linux-shaggy.git for-next
>> into linux-next?
>
> I have added that from today.
>
>> There will be
On Wed, Aug 21, 2013 at 10:21:22AM +0800, Chen Gang wrote:
> mpol_to_str() may fail, and not fill the buffer (e.g. -EINVAL), so need
> check about it, or buffer may not be zero based, and next seq_printf()
> will cause issue.
>
> Signed-off-by: Chen Gang
> Cc: Cyrill Gorcunov
Looks good to me,
On Tue, Aug 20, 2013 at 04:12:32PM -0700, Greg KH wrote:
> On Wed, Aug 21, 2013 at 12:58:15AM +0200, Willy Tarreau wrote:
> > Hi Greg,
> >
> > On Tue, Aug 20, 2013 at 03:40:32PM -0700, Greg KH wrote:
> > > Hi all,
> > >
> > > Given that I had to just revert a patch in the recent stable releases
v8: added `extended = false;` line
ideapad_slidebar is a new driver which enables slidebars on some
Lenovo IdeaPad laptops (the slidebars work with SlideNav/Desktop
Navigator under Windows)
Fixes this: https://bugzilla.kernel.org/show_bug.cgi?id=16004
Registers 'IdeaPad Slidebar' input device
On 08/16/13 11:41, Sudeep KarkadaNagesha wrote:
On 15/08/13 18:09, Sudeep KarkadaNagesha wrote:
From: Sudeep KarkadaNagesha
This patch removes the declaration of the function 'of_get_cpu_node'
which is not defined for openrisc. This is in preparation to move
it's definition from PPC to DT
On Tue, 20 Aug 2013 22:46:30 +0200
Arnd Bergmann wrote:
> On Tuesday 20 August 2013, Dwight Engen wrote:
> > diff --git a/arch/powerpc/platforms/cell/spufs/inode.c
> > b/arch/powerpc/platforms/cell/spufs/inode.c index f390042..90fb308
> > 100644 --- a/arch/powerpc/platforms/cell/spufs/inode.c
>
Acked-by: Mike Frysinger
-mik
--
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.tux.org/lkml/
On Tue, Aug 20, 2013 at 8:20 PM, Josh Triplett wrote:
> +FILE *fopen_or_die(const char *path, const char *mode)
> +{
> + FILE *filep = fopen(path, "r");
not a big deal, but would be nice to add the "e" flag
-mike
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
On 08/20/2013 07:45 PM, Libin wrote:
> [3.158023] [ cut here ]
> [3.162626] WARNING: CPU: 0 PID: 1 at
> arch/x86/mm/kmemcheck/kmemcheck.c:634 kmemcheck_fault+0xb1/0xc0()
...
> [3.314877] [] ? kmemcheck_trap+0x17/0x30
> [3.320507] <> <#DB> []
On Tue, Aug 20, 2013 at 8:11 PM, Wanpeng Li wrote:
> Hi Yinghai,
> On Tue, Aug 20, 2013 at 05:02:17PM -0700, Yinghai Lu wrote:
- /* ok, last chunk */
- sparse_early_usemaps_alloc_node(usemap_map, pnum_begin,
NR_MEM_SECTIONS,
-
Hi Jiri,
Today's linux-next merge of the trivial tree got a conflict in
drivers/net/wireless/iwlwifi/mvm/time-event.c between commit 057397943eee
("iwlwifi: mvm: disconnect if time event scheduling fails") from the
wireless tree and commit 0b1587b18bfe ("treewide: Fix typo in printk")
from the
On 08/20/2013 11:40 PM, Fabio Estevam wrote:
> On Tue, Aug 20, 2013 at 5:38 AM, Liu Ying wrote:
>
>> diff --git a/Documentation/devicetree/bindings/clock/imx6q-clock.txt
>> b/Documentation/devicetree/bindings/clock/imx6q-clock.txt
>> index 5a90a72..90e923e 100644
>> ---
Hi Jiri,
Today's linux-next merge of the trivial tree got a conflict in
drivers/net/ethernet/qlogic/qlcnic/qlcnic_83xx_hw.c between commit
068a8d197e00 ("qlcnic: Replace poll mode mailbox interface with interrupt
based mailbox interface") from the tree and commit 0b1587b18bfe
("treewide: Fix
On 08/20/2013 10:37 PM, Oleg Nesterov wrote:
> On 08/20, Serge Hallyn wrote:
>>
>> Quoting Chen Gang (gang.c...@asianux.com):
>>> When unshare_userns() succeed, recommend to always set the return
>>> parameter which may be used by caller.
>>>
>>> The caller has rights to call it with 'new_cred'
On 08/21/2013 09:59 AM, Shawn Guo wrote:
> Hi Ying,
>
> On Tue, Aug 20, 2013 at 06:08:48PM +0800, Liu Ying wrote:
>>> While I admit to having introduced the combination of 1/3.5 fixed
>>> divider and configurable 1/1,1/2 divder clocks to describe this
>>> fractional divider for the reasons you
On Tue, 2013-08-20 at 20:36 -0500, Rob Landley wrote:
> On 08/20/2013 07:22:36 PM, Joe Perches wrote:
> > I'm also saying that the trivial tree should
> > have some visibility about whether or not a
> > patch or series will be handled by the trivial
> > maintainer or not.
[]
> > Jiri has not
Hi Jiri,
Today's linux-next merge of the trivial tree got a conflict in
drivers/crypto/ux500/hash/hash_core.c between commit 69d2884debaa
("crypto: ux500 - Fix logging, make arrays const, neatening") from the
crypto tree and commit 0b1587b18bfe ("treewide: Fix typo in printk") from
the trivial
On 08/21/2013 12:19 AM, Darren Hart wrote:
> HopingOn Tue, 2013-08-20 at 11:07 +0800, Chen Gang wrote:
>
>
> Hi Chen,
>
>> rt_mutex_finish_proxy_lock() can return failure code (e.g. -EINTR,
>> -ETIMEDOUT).
>>
>> Original implementation has already noticed about it, but not check it
>> before
At present, irq handler function name is not printed out when
irq_handler_entry is added into trace event, which is inconvenient
for debugging.
In order to improve the debugging efficiency, print out the handler
function name in irq_handler_entry.
Signed-off-by: Li Fei
Acked-by: Liu Chuansheng
On Tue, Aug 20, 2013 at 10:41:53PM -0400, Steven Rostedt wrote:
> > I get that there's a problem, but the bcache code REALLY IS USING THE
> > RWSEM AS A LOCK; the answer isn't to open code the lock!
>
> Actually, it is using it as a semaphore. The problem with Linux
> was that it only had spin
On Tue, 20 Aug 2013 19:19:37 -0500, Rob Landley wrote:
> Because some people actually read the commit logs and changes that
> don't do anything add noise for no benefit? (Your fourth change was a
> single typo fix. The previous three changes _combined_ were less
> valuable than that single typo
On 08/21/2013 11:17 AM, Paul E. McKenney wrote:
> On Sat, Aug 10, 2013 at 08:07:15AM -0700, Paul E. McKenney wrote:
>> On Sat, Aug 10, 2013 at 11:43:59AM +0800, Lai Jiangshan wrote:
>
> [ . . . ]
>
>>> So I have to narrow the range of suspect locks. Two choices:
>>> A) don't call
On Sat, Aug 10, 2013 at 08:07:15AM -0700, Paul E. McKenney wrote:
> On Sat, Aug 10, 2013 at 11:43:59AM +0800, Lai Jiangshan wrote:
[ . . . ]
> > So I have to narrow the range of suspect locks. Two choices:
> > A) don't call rt_mutex_unlock() from rcu_read_unlock(), only call it
> >from
Signed-off-by: Xiubo Li
---
arch/arm/boot/dts/vf610.dtsi | 83 +++-
1 file changed, 82 insertions(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/vf610.dtsi b/arch/arm/boot/dts/vf610.dtsi
index 67d929c..b3a0b6e 100644
--- a/arch/arm/boot/dts/vf610.dtsi
Signed-off-by: Xiubo Li
---
arch/arm/boot/dts/vf610-twr.dts | 17 +
1 file changed, 17 insertions(+)
diff --git a/arch/arm/boot/dts/vf610-twr.dts b/arch/arm/boot/dts/vf610-twr.dts
index b3905f5..6f93d8d 100644
--- a/arch/arm/boot/dts/vf610-twr.dts
+++
Signed-off-by: Xiubo Li
---
.../devicetree/bindings/pwm/fsl-ftm-pwm.txt| 52 ++
1 file changed, 52 insertions(+)
create mode 100644 Documentation/devicetree/bindings/pwm/fsl-ftm-pwm.txt
diff --git a/Documentation/devicetree/bindings/pwm/fsl-ftm-pwm.txt
Add freescale ftm pwm driver support. The ftm pwm device
can be found on Vybrid VF610 and Layerscape LS-1 SoCs.
Signed-off-by: Xiubo Li
Signed-off-by: Jingchang Lu
---
drivers/pwm/Kconfig | 10 +
drivers/pwm/Makefile | 1 +
drivers/pwm/pwm-fsl-ftm.c | 586
Hello,
This patch series is the freescale ftm pwm implementation.
There are 8 channels most supported by the ftm pwm,
and there are two pwm modes:
- Center-Aligned PWM (CPWM) mode
- Edge-Aligned PWM (EPWM) mode
This implementation is only compatible with device tree definition.
Please feel free
On Wed, Aug 21, 2013 at 10:40:15AM +0800, Lai Jiangshan wrote:
> On 08/21/2013 02:38 AM, Paul E. McKenney wrote:
> > On Tue, Aug 20, 2013 at 06:02:39PM +0800, Lai Jiangshan wrote:
> >> On 08/20/2013 10:51 AM, Paul E. McKenney wrote:
> >>> From: "Paul E. McKenney"
> >>>
> >>> This commit adds a
On 08/20/2013 11:31 AM, Alexander Fyodorov wrote:
Hi Waiman,
I'm not subscribed to the lkml so I'm writing to you instead. In your patch you
put smp_wmb() at the end of spin_unlock():
+static __always_inline void queue_spin_unlock(struct qspinlock *lock)
+{
+ /*
+* This unlock
mpol_to_str() may fail, and not fill the buffer (e.g. -EINVAL), so need
check about it, or buffer may not be zero based, and next seq_printf()
will cause issue.
Signed-off-by: Chen Gang
Cc: Cyrill Gorcunov
---
mm/shmem.c |5 -
1 files changed, 4 insertions(+), 1 deletions(-)
diff
On Tue, 20 Aug 2013 19:19:00 -0700
Kent Overstreet wrote:
> On Tue, Aug 20, 2013 at 11:16:02AM -0400, Steven Rostedt wrote:
> >
> I _really_ disagree with this approach.
I had a feeling you would love it.
>
> I get that there's a problem, but the bcache code REALLY IS USING THE
> RWSEM AS A
On 08/21/2013 02:38 AM, Paul E. McKenney wrote:
> On Tue, Aug 20, 2013 at 06:02:39PM +0800, Lai Jiangshan wrote:
>> On 08/20/2013 10:51 AM, Paul E. McKenney wrote:
>>> From: "Paul E. McKenney"
>>>
>>> This commit adds a object_debug option to rcutorture to allow the
>>> debug-object-based checks
On Tue, Aug 20, 2013 at 10:07:42PM -0400, Tejun Heo wrote:
> Hello, Kent.
>
> On Tue, Aug 20, 2013 at 07:01:32PM -0700, Kent Overstreet wrote:
> > I think Tejun and I might be at a bit of an impasse with the ida rewrite
> > itself, but I don't think there were any outstanding objections to the
>
mpol_to_str() may fail, and not fill the buffer (e.g. -EINVAL), so need
check about it, or buffer may not be zero based, and next seq_printf()
will cause issue.
The failure return need after mpol_cond_put() to match get_vma_policy().
Signed-off-by: Chen Gang
Cc: Cyrill Gorcunov
---
Just return once a match found makes the code simpler and shorter.
Signed-off-by: Axel Lin
---
drivers/pinctrl/pinctrl-rockchip.c | 21 ++---
1 file changed, 6 insertions(+), 15 deletions(-)
diff --git a/drivers/pinctrl/pinctrl-rockchip.c
b/drivers/pinctrl/pinctrl-rockchip.c
On 08/20/2013 02:04 PM, Rusty Russell wrote:
> Chen Gang writes:
>
>> For some strings, they are permitted to be larger than PAGE_SIZE, so
>> need use scnprintf() instead of sprintf(), or it will cause issue.
>>
>> One case is:
>>
>> if a module version is crazy defined (length more than
Let shmem_show_mpol() return value, since it may fail.
Signed-off-by: Chen Gang
Cc: Cyrill Gorcunov
---
mm/shmem.c | 11 ++-
1 files changed, 6 insertions(+), 5 deletions(-)
diff --git a/mm/shmem.c b/mm/shmem.c
index 75010ba..e59d332 100644
--- a/mm/shmem.c
+++ b/mm/shmem.c
@@
Hello device tree maintainers,
I (sub)maintain the Linux MTD subsystem and hang out on the
linux-...@infradead.org mailing list. I have been seeing an increasing
number of submissions that involve device-tree changes. Many of these
changes are ill thought out and may even cause ABI breakage.
It's not allowed to clear masks of a cpuset if there're tasks in it,
but it's broken:
# mkdir /cgroup/sub
# echo 0 > /cgroup/sub/cpuset.cpus
# echo 0 > /cgroup/sub/cpuset.mems
# echo $$ > /cgroup/sub/tasks
# echo > /cgroup/sub/cpuset.cpus
(should fail)
This bug was introduced by
mpol_to_str() may fail, and not fill the buffer (e.g. -EINVAL), so need
check about it, or buffer may not be zero based, and next seq_printf()
will cause issue.
Signed-off-by: Chen Gang
Cc: Cyrill Gorcunov
---
fs/proc/task_mmu.c |4 +++-
mm/shmem.c | 16 ++--
2 files
On Wed, Aug 21, 2013 at 11:08:29AM +0900, Joonsoo Kim wrote:
> On Mon, Aug 19, 2013 at 06:01:02PM +0200, Peter Zijlstra wrote:
> > +static inline void init_sd_lb_stats(struct sd_lb_stats *sds)
> > +{
> > + /*
> > +* struct sd_lb_stats {
> > +* struct sched_group * busiest;
On Tue, Aug 20, 2013 at 11:16:02AM -0400, Steven Rostedt wrote:
>
> The down/up_read_non_owner() is a nasty hack in the API of the rwsem
> operations. It was once removed, but then resurrected for use with
> bcache. Not only is the API an abomination to the rwsem API, it also
> prevents bcache
On Mon, Aug 19, 2013 at 06:00:58PM +0200, Peter Zijlstra wrote:
>
> After poking at them a little more I feel somewhat more confident.
>
> I found one more bug, but this one was my own fault, we should also clear
> sds->busiest_stat.avg_load because update_sd_pick_busiest() reads that before
>
> -Original Message-
> From: Dan Carpenter [mailto:dan.carpen...@oracle.com]
> Sent: Tuesday, August 20, 2013 4:30 PM
> To: Ma, Xindong
> Cc: gre...@linuxfoundation.org; ccr...@android.com;
> de...@driverdev.osuosl.org; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH] LMK: Optimize
On Mon, Aug 19, 2013 at 06:01:02PM +0200, Peter Zijlstra wrote:
> +static inline void init_sd_lb_stats(struct sd_lb_stats *sds)
> +{
> + /*
> + * struct sd_lb_stats {
> + * struct sched_group * busiest; // 0 8
> + * struct sched_group *
Hello, Kent.
On Tue, Aug 20, 2013 at 07:01:32PM -0700, Kent Overstreet wrote:
> I think Tejun and I might be at a bit of an impasse with the ida rewrite
> itself, but I don't think there were any outstanding objections to the
> percpu ida code itself - and this is a standalone version.
The
On 08/20/2013 02:05 PM, Rusty Russell wrote:
> Chen Gang writes:
>
>> For some strings (e.g. version string), they are permitted to be larger
>> than PAGE_SIZE (although meaningless), so recommend to use scnprintf()
>> instead of sprintf().
>
> Applied.
>
Thanks.
> Thanks,
> Rusty.
>
>>
>>
On Tue, Aug 20, 2013 at 02:29:56PM -0700, Andrew Morton wrote:
> On Tue, 20 Aug 2013 14:19:06 -0700 "Nicholas A. Bellinger"
> wrote:
>
> > On Thu, 2013-08-08 at 14:32 +, Christoph Lameter wrote:
> > > On Wed, 7 Aug 2013, Kent Overstreet wrote:
> > >
> > > > One thing that was bugging me -
Hi Ying,
On Tue, Aug 20, 2013 at 06:08:48PM +0800, Liu Ying wrote:
> > While I admit to having introduced the combination of 1/3.5 fixed
> > divider and configurable 1/1,1/2 divder clocks to describe this
> > fractional divider for the reasons you state, I think the correct
> > solution would be
In current implementation for reboot type CF9 and CF9_COND,
warm and cold reset are not differentiated, and both are
performed by writing 0x06 to port 0xCF9 as warm reset. It's not
correct.
This commit will differentiate warm and cold reset, and perform
them correctly as below:
For warm reset,
From: Wei WANG
Update copyright date, and remove author address.
Signed-off-by: Wei WANG
---
drivers/memstick/host/rtsx_pci_ms.c |3 +--
drivers/mmc/host/rtsx_pci_sdmmc.c |3 +--
2 files changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/memstick/host/rtsx_pci_ms.c
From: Leon Ma
Date: Mon, 19 Aug 2013 14:22:38 +0800
Subject: [PATCH] LMK: Optimize lowmem_shrink.
By comparing with selected_oom_score_adj instead of min_score_adj,
we may do less calculation.
Signed-off-by: Leon Ma
---
drivers/staging/android/lowmemorykiller.c | 12
1 files
From: Wei WANG
If switching voltage fails, SD_CLK toggle enable bit should been cleared
so that SD host can control SD clock automatically.
Signed-off-by: Wei WANG
---
drivers/mmc/host/rtsx_pci_sdmmc.c |9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git
From: Wei WANG
The default phase can meet most cards' requirement, but it is not the
optimal one. In some extreme situation, the rx phase point produced by
the following tuning process will drift quite a distance.
Before tuning UHS card, this patch will set a more proper initial tx
phase point,
From: Wei WANG
Wei WANG (3):
mfd:mmc:rtsx: Change default tx phase
mmc:rtsx:Clear SD_CLK toggle enable bit if switching voltage fail
mmc:memstick:rtsx: Modify copyright comments
drivers/memstick/host/rtsx_pci_ms.c |3 +-
drivers/mfd/rtl8411.c |4 ++
On Tue, Aug 20, 2013 at 02:18:27PM -0700, Mike Turquette wrote:
> Quoting Fabio Estevam (2013-08-20 08:40:52)
> > On Tue, Aug 20, 2013 at 5:38 AM, Liu Ying wrote:
> >
> > > diff --git a/Documentation/devicetree/bindings/clock/imx6q-clock.txt
> > >
On 08/20/2013 07:22:36 PM, Joe Perches wrote:
On Tue, 2013-08-20 at 19:10 -0500, Rob Landley wrote:
> The important question is does he want to handle patches that you're
> flipping out about not going in before the next merge window because
> they are SO IMPORTANT that the trivial tree must
On Tue, Aug 20, 2013 at 05:47:10PM -0700, Andy Lutomirski wrote:
> On Tue, Aug 20, 2013 at 3:43 PM, Dave Chinner wrote:
> > On Tue, Aug 20, 2013 at 02:54:01PM -0700, Andy Lutomirski wrote:
> >> On Tue, Aug 20, 2013 at 2:48 PM, Dave Chinner wrote:
> >> > On Tue, Aug 20, 2013 at 09:42:34AM -0700,
Hi Sebastian
On Sun, 11 Aug 2013, Sebastian Reichel wrote:
> From: Sebastian Reichel
>
> This patch adds Synchronous Serial Interface (SSI) hwmod support for
> OMAP34xx SoCs.
a few comments:
- please add your Signed-off-by: to the patch description, per
Documentation/SubmittingPatches
-
Chen Gang writes:
> For some strings, they are permitted to be larger than PAGE_SIZE, so
> need use scnprintf() instead of sprintf(), or it will cause issue.
>
> One case is:
>
> if a module version is crazy defined (length more than PAGE_SIZE),
> 'modinfo' command is still OK (print full
Chen Gang writes:
> For some strings (e.g. version string), they are permitted to be larger
> than PAGE_SIZE (although meaningless), so recommend to use scnprintf()
> instead of sprintf().
Applied.
Thanks,
Rusty.
>
> Signed-off-by: Chen Gang
> ---
> kernel/params.c |7 ---
> 1 files
Hi Geert,
On Tue, 20 Aug 2013 21:38:03 +0200 Geert Uytterhoeven
wrote:
>
> commit 40b313608ad4ea655addd2ec6cdd106477ae8e15 ("Finally eradicate
> CONFIG_HOTPLUG") removed remaining references to CONFIG_HOTPLUG, but missed
> a few plain English references in the CONFIG_KEXEC help texts.
>
>
On Tue, Aug 20, 2013 at 09:03:12PM -0400, Josh Boyer wrote:
[ ... ]
>
> Suspend/Resume is broken on a variety of Thinkpad T400 and T500
> machines in 3.10. This was true with 3.10.0 afaik. Current thinking
> is that it's related to the Intel mei/mei_me driver(s). Blacklisting
Reminds me ...
On Tue, Aug 20, 2013 at 8:49 PM, Greg KH wrote:
> On Tue, Aug 20, 2013 at 08:41:23PM -0400, Josh Boyer wrote:
>> On Tue, Aug 20, 2013 at 7:57 PM, Greg KH wrote:
>> >> I like this overall. The only thing I might change is "wait for -rc2"
>> >> for patches tagged with CC: stable that go in during
On 08/20/2013 07:57 AM, Lokesh Vutla wrote:
> Hi Joel,
>
> On Sunday 18 August 2013 08:12 AM, Joel Fernandes wrote:
>> In early version of this driver, assumptions were made such as DMA layer
>> requires contiguous buffers etc. Due to this, new buffers were allocated,
>> mapped and used for DMA.
From: Xiong Zhou
Fix randconfig build failure for Amilo x86 platform driver.
AMILO_RFKILL requires SERIO_I8042 being available.
amilo-rfkill.c:(.text+0x108b5b): undefined reference to `i8042_lock_chip'
amilo-rfkill.c:(.text+0x108b69): undefined reference to `i8042_command'
This patch set doesn't make any functional differences.
Libin (3):
workqueue: Comment correction in file header
workqueue: Fix manage_workers() RETURNS description
workqueue: Correct/Drop references to gcwq in Documentation
Documentation/workqueue.txt | 72
No functional changes. This patch fixes the post gcwq comments in
Documentation/workqueue.txt.
Signed-off-by: Libin
---
Documentation/workqueue.txt | 72 ++---
1 file changed, 36 insertions(+), 36 deletions(-)
diff --git a/Documentation/workqueue.txt
No functional change. There are two worker pools for each cpu in
current implementation(one for normal work items and the other for
high priority ones).
Signed-off-by: Libin
---
kernel/workqueue.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/kernel/workqueue.c
No functional change. The comment of function manage_workers()
RETURNS description is obvious wrong, same as the CONTEXT.
Fix it.
Signed-off-by: Libin
---
kernel/workqueue.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/kernel/workqueue.c b/kernel/workqueue.c
index
On Tue, Aug 20, 2013 at 3:43 PM, Dave Chinner wrote:
> On Tue, Aug 20, 2013 at 02:54:01PM -0700, Andy Lutomirski wrote:
>> On Tue, Aug 20, 2013 at 2:48 PM, Dave Chinner wrote:
>> > On Tue, Aug 20, 2013 at 09:42:34AM -0700, Andy Lutomirski wrote:
>> >> On Tue, Aug 20, 2013 at 9:00 AM, Jan Kara
On Tue, Aug 20, 2013 at 08:41:23PM -0400, Josh Boyer wrote:
> On Tue, Aug 20, 2013 at 7:57 PM, Greg KH wrote:
> >> I like this overall. The only thing I might change is "wait for -rc2"
> >> for patches tagged with CC: stable that go in during the merge window.
> >> It seems those are the ones
In func blk_queue_bio, if list of plug is empty,it will call
blk_trace_plug.
If process deal with a single device,it't ok.But if process deal with
multi devices,it only trace the first device.
Using request_count to judge, it can soleve this problem.
In addition, i modify the comment.
On Tue, Aug 20, 2013 at 7:57 PM, Greg KH wrote:
> On Tue, Aug 20, 2013 at 07:40:49PM -0400, Josh Boyer wrote:
>> On Tue, Aug 20, 2013 at 6:40 PM, Greg KH wrote:
>> > Hi all,
>> >
>> > Given that I had to just revert a patch in the recent stable releases
>> > that didn't get enough time to "bake"
On Tue, Aug 20, 2013 at 05:11:11PM -0700, Guenter Roeck wrote:
> On Tue, Aug 20, 2013 at 04:17:43PM -0700, Greg KH wrote:
> > On Tue, Aug 20, 2013 at 04:11:17PM -0700, Guenter Roeck wrote:
> > > It would be even better if you could find the time to push -rc releases
> > > into the stable
On Fri, Jul 19, 2013 at 7:13 AM, Lee Jones wrote:
> Signed-off-by: Lee Jones
> ---
> arch/arm/boot/dts/{snowball.dts => ste-snowball.dts} | 0
> 1 file changed, 0 insertions(+), 0 deletions(-)
> rename arch/arm/boot/dts/{snowball.dts => ste-snowball.dts} (100%)
>
> diff --git
From: "John W. Linville"
Date: Mon, 19 Aug 2013 14:59:40 -0400
> This is a batch of fixes intended for the 3.11 stream...
>
> Regarding the iwlwifi bits, Johannes says:
>
> "We revert an rfkill bugfix that unfortunately caused more bugs, shuffle
> some code to avoid touching the PCIe device
On Mon, Aug 19, 2013 at 4:59 PM, Pali Rohár wrote:
> On Friday 16 August 2013 14:57:07 Pali Rohár wrote:
>> In commit 77145f1cbdf8d28b46ff8070ca749bad821e0774 was
>> introduced error which cause that reclocking on nv40 not
>> working anymore. There is missing assigment of return value
>> from
Hi Ben,
On Tue, 20 Aug 2013 14:28:44 -0500 Ben Myers wrote:
>
> I'd prefer not to break Stephen's tree two days in a row. We could just
> revert
> d6970d4b726c in the xfs tree for the time being as Stephen has done, but given
> the choice would prefer the fix. Do you have a preference between
On Tue, 2013-08-20 at 19:10 -0500, Rob Landley wrote:
> The important question is does he want to handle patches that you're
> flipping out about not going in before the next merge window because
> they are SO IMPORTANT that the trivial tree must promote them out of
> sequence.
You're
turbostat uses the format %zx to print an off_t. However, %zx wants a
size_t, not an off_t. On 32-bit targets, those refer to different
types, potentially even with different sizes. Use %llx and a cast
instead, since printf does not have a length modifier for off_t.
Without this patch, when
Several different functions in turbostat contain the same pattern of
opening a file and exiting on failure. Factor out a common fopen_or_die
function for that.
Signed-off-by: Josh Triplett
---
tools/power/x86/turbostat/turbostat.c | 31 ---
1 file changed, 16
Some systems declare fscanf with the warn_unused_result attribute. On
such systems, turbostat generates the following warnings:
turbostat.c: In function 'get_core_id':
turbostat.c:1203:8: warning: ignoring return value of 'fscanf', declared with
attribute warn_unused_result [-Wunused-result]
turbostat uses inline assembly to call cpuid. On 32-bit x86, on systems
that have certain security features enabled by default that make -fPIC
the default, this causes a build error:
turbostat.c: In function ‘check_cpuid’:
turbostat.c:1906:2: error: PIC register clobbered by ‘ebx’ in ‘asm’
Many different chunks of code in turbostat open a file, parse a single
int out of it, and close it. Factor that out into a common function.
Signed-off-by: Josh Triplett
---
tools/power/x86/turbostat/turbostat.c | 81 +++
1 file changed, 24 insertions(+), 57
turbostat's Makefile puts arch/x86/include/uapi/ in the include path, so
that it can include from it. It isn't in general safe to
include even uapi headers directly from the kernel tree without
processing them through scripts/headers_install.sh, but asm/msr.h
happens to work.
However, that
Signed-off-by: Josh Triplett
---
tools/power/x86/turbostat/.gitignore | 1 +
1 file changed, 1 insertion(+)
create mode 100644 tools/power/x86/turbostat/.gitignore
diff --git a/tools/power/x86/turbostat/.gitignore
b/tools/power/x86/turbostat/.gitignore
new file mode 100644
index
1 - 100 of 1548 matches
Mail list logo
