On Fri, Jan 18, 2013 at 03:53:44PM -0500, Tom St Denis wrote:
> Admittedly I'm new to the kernel scene but what exactly is a "maintainer"
> then?
Maintainers are ultimately responsible for content that flows into a tree
or subsystem. That means they must command a level of expertise on
On Friday, January 18, 2013 11:11:07 PM Sedat Dilek wrote:
> On Fri, Jan 18, 2013 at 5:37 AM, Stephen Rothwell
> wrote:
> > Hi all,
> >
> > Changes since 20130117:
> >
> > Undropped tree: samung
> >
> > The powerpc tree still had a build failure.
> >
> > The driver-core tree gained a build
>From 4983f3b51e18d008956dd113e0ea2f252774cefc Mon Sep 17 00:00:00 2001
From: Tejun Heo
Date: Fri, 18 Jan 2013 14:05:57 -0800
Synchronous requet_module() from an async worker can lead to deadlock
because module init path may invoke async_synchronize_full(). The
async worker waits for
>From 84b233adcca3cacd5cfa8013a5feda7a3db4a9af Mon Sep 17 00:00:00 2001
From: Tejun Heo
Date: Fri, 18 Jan 2013 14:05:56 -0800
This function queries whether %current is an async worker executing an
async item. This will be used to implement warning on synchronous
request_module() from async
>From 2eaebdb33e1911c0cf3d44fd3596c42c6f502fab Mon Sep 17 00:00:00 2001
From: Tejun Heo
Date: Fri, 18 Jan 2013 14:05:55 -0800
This will be used to implement an inline function to query whether
%current is a workqueue worker and, if so, allow determining which
work item it's executing.
On Friday, January 18, 2013 10:43:45 PM Olivier Doucet wrote:
> > Olivier, may I see the kernel .config file?
> >
> > Rafael
>
> I put it online, cause I didn't want to spam lkml with a long text file :
> https://gist.github.com/4567342
OK, thanks.
It looks like the value returned by
>From ea138446e51f7bfe55cdeffa3f1dd9cafc786bd8 Mon Sep 17 00:00:00 2001
From: Tejun Heo
Date: Fri, 18 Jan 2013 14:05:55 -0800
Workqueue wants to expose more interface internal to kernel/. Instead
of adding a new header file, repurpose kernel/workqueue_sched.h.
Rename it to workqueue_internal.h
>From 111c225a5f8d872bc9327ada18d13b75edaa34be Mon Sep 17 00:00:00 2001
From: Tejun Heo
Date: Thu, 17 Jan 2013 17:16:24 -0800
PF_WQ_WORKER is used to tell scheduler that the task is a workqueue
worker and needs wq_worker_sleeping/waking_up() invoked on it for
concurrency management. As rescuers
Ensure all fields of the struct fb_deferred_io are zeroed out on init,
otherwise the fbdefio->first_io function pointer can contain garbage,
and fb_deferred_io_mkwrite() will end up jumping to this garbage address.
Signed-off-by: Nickolai Zeldovich
---
drivers/gpu/drm/udl/udl_fb.c |2 +-
1
On 01/18/2013 03:26 PM, Jeff Moyer wrote:
> Dave Kleikamp writes:
>
>> @@ -1315,10 +1317,10 @@ static ssize_t aio_rw_vect_retry(struct kiocb *iocb)
>>
>> if ((iocb->ki_opcode == IOCB_CMD_PREADV) ||
>> (iocb->ki_opcode == IOCB_CMD_PREAD)) {
>> -rw_op =
On Friday, January 18, 2013 09:50:59 AM Yinghai Lu wrote:
> On Fri, Jan 18, 2013 at 9:35 AM, Bjorn Helgaas wrote:
> > If you want "pci=nopciehp" as a way for users to deal with this
> > problem by forcing the use of acpiphp, I object. Windows manages to
> > make these slots work without having
On Fri, Jan 18, 2013 at 10:05:45PM +0100, Cong Ding wrote:
> On Tue, Dec 11, 2012 at 2:21 AM, Hans J. Koch wrote:
> > On Thu, Nov 29, 2012 at 05:40:00PM +, Cong Ding wrote:
> >> In version 1, I forgot to modify the same bug in the first loop.
> >>
> >> we have to call kobject_put() to clean
>
> > Right, that information is gathered from the MSRs. I think the Xen would
> > need to do this since it can do the MSRs correctly and modify the P-states.
> >
> > So something like this in the hypervisor maybe (not even tested):
>
> Yeah, something like that. Basically you can copy the
Please don't start another "SCST Vs. LIO" holy war here. We all know why LIO
belongs to Linux kernel and SCST does not.
On Friday, January 18, 2013 3:54:18 AM UTC+2, Vladislav Bolkhovitin wrote:
> Andreas Steinmetz, on 01/16/2013 08:19 PM wrote:
>
> > Thus, lio (http://www.linux-iscsi.org/)
On Fri, Jan 18, 2013 at 01:24:22PM -0800, Dan Magenheimer wrote:
> [V2: no code changes, patchset now generated via git format-patch -M]
>
> Hi Greg --
>
> With "old zcache" now removed, we can now move "new zcache" from its
> temporary home (in drivers/staging/ramster) to reclaim sole
On Friday, January 18, 2013 10:35:46 AM Bjorn Helgaas wrote:
> On Fri, Jan 18, 2013 at 9:07 AM, Jiang Liu wrote:
> > If user specifies "pci=nopciehp" on kernel boot command line, OSPM
> > won't claim PCIe native hotplug service from firmware and no PCIe
> > port devices will be created for PCIe
Invalid number of parentheses if macro COMPAT is defined
Signed-off-by: Cong Ding
---
fs/timerfd.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/timerfd.c b/fs/timerfd.c
index 14ad4f3..0e606b1 100644
--- a/fs/timerfd.c
+++ b/fs/timerfd.c
@@ -396,7 +396,7 @@
ree lost the majority of its conflicts but gained more
>> against the arm-soc and slave-dma tree.
>>
>> ----
>>
>
> I pulled Linux v3.8-rc4 (one commit) into next-20130118.
>
> When CONFIG_SYSTEM_TRUSTED_KEYRING=n I see these error-messages on AMD64:
On Friday, January 18, 2013 09:47:21 AM Yinghai Lu wrote:
> On Fri, Jan 18, 2013 at 4:35 AM, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > The only difference between acpi_bus_scan() into acpi_bus_add() is
> > the invocation of acpi_update_all_gpes() in the latter which in fact
>
Dave Kleikamp writes:
> On 01/18/2013 11:56 AM, Jeff Moyer wrote:
>> Jeff Moyer writes:
>>
>>> ./check -g aio
>>>
>>> and here is the summary:
>>>
>>> Ran: 112 113 198 207 208 209 210 211 212 239 240
>>> Failures: 112 198 207 239 240
>>> Failed 5 of 11 tests
>>>
>>> To be fair, I have not yet
On Fri, Jan 18, 2013 at 01:24:22PM -0800, Dan Magenheimer wrote:
> [V2: no code changes, patchset now generated via git format-patch -M]
>
> Hi Greg --
>
> With "old zcache" now removed, we can now move "new zcache" from its
> temporary home (in drivers/staging/ramster) to reclaim sole
On Fri, Jan 18, 2013 at 09:08:59PM +, Russell King - ARM Linux wrote:
> On Fri, Jan 18, 2013 at 02:24:15PM -0600, Matt Sealey wrote:
> > Hello all,
> >
> > I wonder if anyone can shed some light on this linking problem I have
> > right now. If I configure my kernel without SMP support (it is
> Olivier, may I see the kernel .config file?
>
> Rafael
I put it online, cause I didn't want to spam lkml with a long text file :
https://gist.github.com/4567342
Olivier
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
----
>
I pulled Linux v3.8-rc4 (one commit) into next-20130118.
When CONFIG_SYSTEM_TRUSTED_KEYRING=n I see these error-messages on AMD64:
CC security/keys/keyring.o
CC kernel/module_signing.o
CC [M] arch/x86/kvm/i8259.o
kernel/module_signing.c: In function 'reque
On Friday, January 18, 2013 10:24:48 PM Borislav Petkov wrote:
> Good description.
>
> I'm leaving the whole email in for reference, see below:
>
> On Fri, Jan 18, 2013 at 10:05:41PM +0100, Olivier Doucet wrote:
> > Hello,
> >
> > I think I found a performance issue in kernel. This problem was
On Fri, 18 Jan 2013 10:33:24 +0100
Michal Hocko wrote:
> CONFIG_PARAVIRT defines set_pmd_at only for CONFIG_TRANSPARENT_HUGEPAGE
> which leads to the following compile errors when randconfig selected
> CONFIG_NUMA_BALANCING && CONFIG_PARAVIRT && !CONFIG_TRANSPARENT_HUGEPAGE:
>
> mm/mprotect.c:
On Fri, Jan 18 2013 at 4:25pm -0500,
Darrick J. Wong wrote:
> Since Joe is putting together a testing tree to compare the three caching
> things, what do you all think of having a(nother) session about ssd caching at
> this year's LSFMM Summit?
>
> [Apologies for hijacking the thread.]
>
On Fri, Jan 18, 2013 at 08:12:43PM +0100, Raoul Bhatia wrote:
> commit 72585d2428fa3a0daab02ebad1f41e5ef517dbaa upstream
>
> Please include upstream patch
> 72585d2428fa3a0daab02ebad1f41e5ef517dbaa into 3.2.y.
> Patch from git below.
What about 3.4 and 3.7-stable kernels?
thanks,
greg k-h
--
On Wed, Jan 16, 2013 at 6:12 PM, Minchan Kim wrote:
> Lockdep complains about recursive deadlock of zram->init_lock.
> [1] made it false positive because we can't request IO to zram
> before setting disksize. Anyway, we should shut lockdep up to
> avoid many reporting from user.
>
> This patch
Signed-off-by: Maxime Ripard
---
arch/arm/boot/dts/sun5i-a13.dtsi |9 +
1 file changed, 9 insertions(+)
diff --git a/arch/arm/boot/dts/sun5i-a13.dtsi b/arch/arm/boot/dts/sun5i-a13.dtsi
index 59a2d26..707bef5 100644
--- a/arch/arm/boot/dts/sun5i-a13.dtsi
+++
On Thu, Jan 17, 2013 at 5:09 PM, John Stultz wrote:
> On 01/17/2013 04:48 PM, Greg KH wrote:
>>
>> On Fri, Jan 11, 2013 at 03:46:21PM -0800, John Stultz wrote:
>>>
>>> Here is the second revision at implementing compat_ioctl support for
>>> Android's alarm-dev driver in staging.
>>>
>>> The first
Use pinctrl to configure the SoCs pins directly from the driver.
Signed-off-by: Maxime Ripard
---
drivers/tty/serial/of_serial.c |7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/tty/serial/of_serial.c b/drivers/tty/serial/of_serial.c
index e7cae1c..e9f3289 100644
---
Signed-off-by: Maxime Ripard
---
arch/arm/boot/dts/sun5i-a13.dtsi | 14 ++
1 file changed, 14 insertions(+)
diff --git a/arch/arm/boot/dts/sun5i-a13.dtsi b/arch/arm/boot/dts/sun5i-a13.dtsi
index 707bef5..e112189 100644
--- a/arch/arm/boot/dts/sun5i-a13.dtsi
+++
The Allwinner SoCs have an IP module that handle both the muxing and the
GPIOs.
This IP has 8 banks of 32 bits, with a number of pins actually useful
for each of these banks varying from one to another, and depending on
the SoC used on the board.
This driver only implements the pinctrl part, the
Since the Allwinner SoCs variants don't have the same set of pins to
handle, we need to declare the pin ranges available.
Signed-off-by: Maxime Ripard
---
drivers/pinctrl/pinctrl-sunxi.c | 253 +++
1 file changed, 253 insertions(+)
diff --git
Signed-off-by: Maxime Ripard
---
arch/arm/boot/dts/sun5i-a13-olinuxino.dts |2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/sun5i-a13-olinuxino.dts
b/arch/arm/boot/dts/sun5i-a13-olinuxino.dts
index 498a091..4a1e45d 100644
--- a/arch/arm/boot/dts/sun5i-a13-olinuxino.dts
Some pin configurations IP allows to set the current output to the pin.
This patch adds such a parameter to the pinconf-generic mechanism.
This parameter takes as argument the drive strength in mA.
Signed-off-by: Maxime Ripard
---
include/linux/pinctrl/pinconf-generic.h |3 +++
1 file
On Thu, Jan 17, 2013 at 10:56:50PM -0500, Theodore Ts'o wrote:
> On Fri, Jan 18, 2013 at 01:47:48AM -0200, Herton Ronaldo Krzesinski wrote:
> > > > By the description and looking at commit c278531d39, this change isn't
> > > > needed for 3.0 or 3.4 kernels (anything <= 3.6), they don't contain
> >
[V2: no code changes, patchset now generated via git format-patch -M]
Hi Greg --
With "old zcache" now removed, we can now move "new zcache" from its
temporary home (in drivers/staging/ramster) to reclaim sole possession
of the name "zcache".
(Note that [PATCH 2/5] is just a git mv.)
This
In staging, re-enable config/build of zcache after ramster->zcache renaming.
Signed-off-by: Dan Magenheimer
---
drivers/staging/Kconfig |2 ++
drivers/staging/Makefile |1 +
2 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/drivers/staging/Kconfig b/drivers/staging/Kconfig
Dave Kleikamp writes:
> @@ -1315,10 +1317,10 @@ static ssize_t aio_rw_vect_retry(struct kiocb *iocb)
>
> if ((iocb->ki_opcode == IOCB_CMD_PREADV) ||
> (iocb->ki_opcode == IOCB_CMD_PREAD)) {
> - rw_op = file->f_op->aio_read;
> + rw_op = do_aio_read;
>
[V2: no code changes, patchset now generated via git format-patch -M]
In staging/zcache, adjust config/build due to ramster->zcache renaming
Signed-off-by: Dan Magenheimer
---
drivers/staging/zcache/Kconfig | 17 ++---
drivers/staging/zcache/Makefile |2 +-
2 files changed,
Since Joe is putting together a testing tree to compare the three caching
things, what do you all think of having a(nother) session about ssd caching at
this year's LSFMM Summit?
[Apologies for hijacking the thread.]
[Adding lsf-pc to the cc list.]
--D
On Fri, Jan 18, 2013 at 12:36:42PM -0600,
This should have been Cc'd to linux-arch.
-- Steve
On Wed, 2013-01-09 at 18:09 -0500, Sasha Levin wrote:
> Modify the parameters of all the lookup and the bookkeeping functions which
> should be const to const.
>
> For example, jump_label_text_reserved() doesn't modify the memory it works on,
[V2: no code changes, patchset now generated via git format-patch -M]
In staging, disable ramster build in anticipation of renaming to zcache
Signed-off-by: Dan Magenheimer
---
drivers/staging/Kconfig |2 --
drivers/staging/Makefile |1 -
2 files changed, 0 insertions(+), 3
[V2: no code changes, patchset now generated via git format-patch -M]
Fix unitialized variable in zcache which generates warning during build
Signed-off-by: Dan Magenheimer
---
drivers/staging/zcache/zcache-main.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git
On Wed, 16 Jan 2013, Aaron Lu wrote:
> From: Lin Ming
>
> Uses block layer runtime pm helper functions in
> scsi_runtime_suspend/resume.
> Remove scsi_autopm_* from sd open/release path and check_events path.
> And remove the quiesce call in runtime suspend path, as we know there is
> no
On Wed, 2013-01-09 at 18:09 -0500, Sasha Levin wrote:
> Modify the parameters of all the lookup and the bookkeeping functions which
> should be const to const.
>
> For example, jump_label_text_reserved() doesn't modify the memory it works on,
> it just checks whether there are any jump labels
Good description.
I'm leaving the whole email in for reference, see below:
On Fri, Jan 18, 2013 at 10:05:41PM +0100, Olivier Doucet wrote:
> Hello,
>
> I think I found a performance issue in kernel. This problem was
> introduced in 3.2.6 and is affecting all version, including 3.7.1
> (latest
If pci_iomap() fails in mwl8k_probe(), it breaks off initialization,
deallocates all resources, but returns zero.
There is a similar issue when priv->rxd_ops is NULL in mwl8k_probe_hw().
The patch adds proper error code return values.
Found by Linux Driver Verification project
[V2: no code changes, patchset now generated via git format-patch -M]
In staging, rename ramster to zcache
The original zcache in staging was a "demo" version, and this new zcache
is a significant rewrite. While certain disagreements were being resolved,
both "old zcache" and "new zcache"
On Fri, Jan 18, 2013 at 02:24:15PM -0600, Matt Sealey wrote:
> Hello all,
>
> I wonder if anyone can shed some light on this linking problem I have
> right now. If I configure my kernel without SMP support (it is a very
> lean config for i.MX51 with device tree support only) I hit this error
> on
Quoting Prashant Gaikwad (2013-01-03 21:51:45)
> Not all clocks are required to be decomposed into basic clock
> types but at the same time want to use the functionality
> provided by these basic clock types instead of duplicating.
>
> For example, Tegra SoC has ~100 clocks which can be
On Fri, Jan 18, 2013 at 03:53:58PM -0500, Dave Jones wrote:
> On Wed, Jan 02, 2013 at 10:37:44AM -0500, Dave Jones wrote:
> > This happened a few times to my test boxes I left running over the
> holidays..
> >
> > [ 8419.797533] [ cut here ]
> > [ 8419.798341]
On Fri, 2013-01-18 at 09:56 -0800, Mike Turquette wrote:
> Quoting Prashant Gaikwad (2013-01-03 23:00:56)
> > Use common of_clk_init() function for clock initialization.
> >
> > Signed-off-by: Prashant Gaikwad
>
> Tony,
>
> Can I get a Tested-by from you before I take this in?
>
Tested-by:
On 2013-01-16 Florian Fainelli wrote:
> On 01/15/2013 07:11 PM, Lasse Collin wrote:
> > On 2013-01-15 Florian Fainelli wrote:
> >> config XZ_DEC_X86
> >>bool "x86 BCJ filter decoder" if EXPERT
> >> - default y
> >> + default y if X86
> >>select XZ_DEC_BCJ
> > [...]
> >
> > I think the
Hello,
I think I found a performance issue in kernel. This problem was
introduced in 3.2.6 and is affecting all version, including 3.7.1
(latest tested).
I measured several kernel builds with a homebrew LAMP platform
benchmark (250 runs, average value kept).
Kernel 3.2.0 was on production so
On Tue, Dec 11, 2012 at 2:21 AM, Hans J. Koch wrote:
> On Thu, Nov 29, 2012 at 05:40:00PM +, Cong Ding wrote:
>> In version 1, I forgot to modify the same bug in the first loop.
>>
>> we have to call kobject_put() to clean up the kobject after function
>> kobject_init(), kobject_add(), or
On Fri, Jan 18, 2013 at 12:07:30AM +0100, Sebastian Ehrenfels wrote:
> From: Sebastian Wankerl
>
> Signed-off-by: Sebastian Wankerl
> Signed-off-by: Sebastian Ehrenfels
Why did you do this? What does this fix? Please always say that in the
change log entry part of the patch, empty ones
Hi all, is this still in the queue or...?
- cong
On Mon, Dec 3, 2012 at 11:19 AM, Cong Ding wrote:
> We do not allow old-style function definition. Always spell foo(void) if
> a function does not take any parameters.
>
> Signed-off-by: Cong Ding
> ---
> drivers/scsi/gdth.c |2 +-
> 1
On Fri, Jan 18, 2013 at 12:07:32AM +0100, Sebastian Ehrenfels wrote:
> From: Sebastian Wankerl
>
> We are uncertain if the netdev_struct is properly initialized in each function
> call. Please be sure to really review this patch.
If you are uncertian, then I'm sure not going to take this.
On Fri, Jan 18, 2013 at 12:07:31AM +0100, Sebastian Ehrenfels wrote:
> From: Sebastian Wankerl
>
> Signed-off-by: Sebastian Wankerl
> Signed-off-by: Sebastian Ehrenfels
>
> ---
> drivers/staging/wlan-ng/prism2mgmt.c | 20 +++-
> 1 file changed, 11 insertions(+), 9
On Fri, Jan 18, 2013 at 10:42 PM, Cong Ding wrote:
> The pointer obj is dereferenced in line 146 and 149 respectively, so it is not
> necessary to check null again in line 149 and 175. And I have checked that all
> the callers of these two functions guarantee the parameter obj passed is not
>
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Subject: Re: [PATCH 0/5] staging: zcache: move new zcache code base from
> ramster
>
> On Thu, Jan 17, 2013 at 09:26:32AM -0800, Dan Magenheimer wrote:
> > Hi Greg --
> >
> > With "old zcache" now removed, we can now move "new zcache" from
On Wed, Jan 02, 2013 at 10:37:44AM -0500, Dave Jones wrote:
> This happened a few times to my test boxes I left running over the holidays..
>
> [ 8419.797533] [ cut here ]
> [ 8419.798341] WARNING: at drivers/tty/tty_buffer.c:476
> flush_to_ldisc+0x1de/0x1f0()
> [
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Sent: Friday, January 18, 2013 1:47 PM
> To: Dan Magenheimer
> Cc: de...@linuxdriverproject.org; linux-kernel@vger.kernel.org;
> linux...@kvack.org; ngu...@vflare.org;
> Konrad Wilk; sjenn...@linux.vnet.ibm.com; minc...@kernel.org
> Subject:
On Fri, Jan 18, 2013 at 11:06:59PM +0900, HATAYAMA Daisuke wrote:
[..]
> > These are impressive improvements. I missed the discussion on mmap().
> > So why couldn't we provide mmap() interface for /proc/vmcore. If that
> > works then application can select to mmap/unmap bigger chunks of file
> >
- Original Message -
> From: "David Miller"
> To: tstde...@elliptictech.com
> Cc: "steffen klassert" ,
> herb...@gondor.apana.org.au, linux-kernel@vger.kernel.org,
> net...@vger.kernel.org
> Sent: Friday, 18 January, 2013 2:50:05 PM
> Subject: Re: IPsec AH use of ahash
>
> From: Tom St
Is this patch still queued or...?
- cong
On Wed, Dec 5, 2012 at 6:10 PM, Cong Ding wrote:
> the following compilation warning is caused by Commit-ID:
> c566e8e9e44b72b53091da20e2dedefc730f2ee2
>
> kernel/sched/debug.c: In function ‘print_cfs_rq’:
> kernel/sched/debug.c:225:2: warning: format
On Thu, Jan 17, 2013 at 09:26:34AM -0800, Dan Magenheimer wrote:
> In staging, rename ramster to zcache
>
> The original zcache in staging was a "demo" version, and this new zcache
> is a significant rewrite. While certain disagreements were being resolved,
> both "old zcache" and "new zcache"
On Thu, Jan 17, 2013 at 09:26:32AM -0800, Dan Magenheimer wrote:
> Hi Greg --
>
> With "old zcache" now removed, we can now move "new zcache" from its
> temporary home (in drivers/staging/ramster) to reclaim sole possession
> of the name "zcache".
>
> Note that [PATCH 2/5] will require a manual:
On Thu, Jan 17, 2013 at 10:49:36PM -0500, Jake Champlin wrote:
> Fixed camel case style issue.
>
> Signed-off-by: Jake Champlin
> ---
> drivers/staging/comedi/drivers/addi_apci_035.c | 34
> +-
> 1 file changed, 17 insertions(+), 17 deletions(-)
Did you even build the
The pointer obj is dereferenced in line 146 and 149 respectively, so it is not
necessary to check null again in line 149 and 175. And I have checked that all
the callers of these two functions guarantee the parameter obj passed is not
null.
Signed-off-by: Cong Ding
---
no user of that should ever change that pointer,
so let's mark it const to prevent that from
happening.
Signed-off-by: Felipe Balbi
---
include/linux/debugfs.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/debugfs.h b/include/linux/debugfs.h
index
Hi!
I have USB speakers
Bus 004 Device 002: ID 04fa:4201 Dallas Semiconductor DS4201 Audio DAC
... which make problems again
(https://lkml.org/lkml/2008/3/20/274). They refuse to produce sound,
so I updated to 3.8.0-rc2 in hope that would help... and tried testing
them by "cat /bin/bash >
Hi Lubomir,
> It actually times out on a 8688 present in GuruPlug with sd8688.bin
> (md5=7233401e9687f8c880da547beed4324e) firmware (that's present in
> linux-firmware tree), but the adapter works fine.
>
> For that firmware times out with libertas_uap [1] as well, though it succeeds
> with
Dear Rafael,
thank you for applying Daniel's patch. I tested 3.8-rc4 and found that one
patch ist still missing to fix the problem of not usable C-state after
disconnect. I had it attached with my last e-mail as patch 1. For your
conveniency, I have attached it here again.
With that patch the
On Fri, 18 Jan 2013, David Miller wrote:
> > + ret = fn(dev, cmd, USB_DIR_IN | USB_TYPE_VENDOR |
> > + USB_RECIP_DEVICE, value, index, data, size);
>
> This is not indented properly. When a function call takes up
> multiple lines, the text on the second and subsequent lines
Hi Roger,
On Fri, 18 Jan 2013, Roger Quadros wrote:
> We don't need multiple aliases for the OMAP USB host clocks and neither
> the dummy clocks so remove them.
>
> CC: Paul Walmsley
> CC: Rajendra Nayak
> CC: Benoit Cousson
> CC: Mike Turquette
>
> Signed-off-by: Roger Quadros
>
Hello all,
I wonder if anyone can shed some light on this linking problem I have
right now. If I configure my kernel without SMP support (it is a very
lean config for i.MX51 with device tree support only) I hit this error
on linking:
MODPOST 216 modules
LZMA
> From: Greg Kroah-Hartman [mailto:gre...@linuxfoundation.org]
> Sent: Thursday, January 17, 2013 5:42 PM
> To: Minchan Kim
> Cc: linux...@kvack.org; linux-kernel@vger.kernel.org; Nitin Gupta; Seth
> Jennings; Dan Magenheimer;
> Konrad Rzeszutek Wilk; Jerome Marchand; Pekka Enberg
> Subject: Re:
On Fri, Jan 18, 2013 at 04:08:48PM +0100, Linus Walleij wrote:
> - Abstain from using IS_ERR_OR_NULL() in the driver core,
> Russell recently sent a patch to remove it. Handle the
> NULL case explicitly even though it's a bogus case.
H... I assume you're talking about this:
> + p
On Fri, Jan 18, 2013 at 02:00:15PM -0500, Konrad Rzeszutek Wilk wrote:
> I did not explain myself well. The fix is OK - it just that the
> hypervisor causes the quirk to not work correctly. Hmm, I wonder if
> there BIOSes that do the same thing (cause the MSR to return 0). Per
> you estimation of
On Fri, Jan 11, 2013 at 4:45 PM, Lee Jones wrote:
> The Nomadik Pinctrl driver requires access to some PRCMU registers
> in order to run with full functionality. When Device Tree is
> disabled the required PRCMU base address is passed in via platform
> data, so in order for Device Tree booting
On Fri, Jan 18, 2013 at 07:38:34PM +, Matthew Garrett wrote:
> On Fri, Jan 18, 2013 at 08:36:56PM +0100, Borislav Petkov wrote:
>
> > Ok, how much can we rely on ACPI to have this ACPI_ADR_SPACE_SYSTEM_IO
> > properly set on K8? Because the thing is, we want to use acpi-cpufreq on
> > F10h
OPP pointers are protected by RCU locks, the pointer validity is
permissible only under the section of rcu_read_lock to rcu_read_unlock
Add documentation to the effect.
Signed-off-by: Nishanth Menon
---
drivers/devfreq/devfreq.c |5 +
1 file changed, 5 insertions(+)
diff --git
OPP pointers cannot be expected to be valid beyond the boundary
of rcu_read_lock and rcu_read_unlock. Unfortunately, the current
exynos4 busfreq driver does not honor the usage constraint and stores
the OPP pointer in struct busfreq_data. This could potentially
become invalid later such as: across
OPP pointer is RCU protected, hence after finding it, de-reference
also should be protected with the same RCU context else the OPP
pointer may become invalid.
Reported-by: Jack Mitchell
Tested-by: Alexander Holler
Tested-by: Jack Mitchell
Acked-by: Alexander Holler
Signed-off-by: Nishanth
The following changes since commit 8cf65dc386f3634a43312f436cc7a935476a40c4:
usb: ftdi_sio: Crucible Technologies COMET Caller ID - pid added (2013-01-13
13:44:23 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/ tags/usb-3.8-rc4
The following changes since commit 9931faca02c604c22335f5a935a501bb2ace6e20:
Linux 3.8-rc3 (2013-01-09 18:59:55 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/ tags/tty-3.8-rc4
for you to fetch changes up to
OPP pointer is RCU protected, hence after finding it, de-reference
also should be protected with the same RCU context else the OPP
pointer may become invalid.
Reported-by: Alexander Holler
Tested-by: Alexander Holler
Acked-by: Alexander Holler
Signed-off-by: Nishanth Menon
---
Hi,
Despite being documented in function documentation and in
Documentation/power/opp.txt, many of the users of OPP APIs
dont honor RCU lock usage appropriately.
This recently appeared in IRC discussion earlier today [1].
I did an audit of current usage and the following series
is a result of
The following changes since commit 397c60668aa5ae7130b5ad4e73870d7b8a787085:
staging: zram: fix invalid memory references during disk write (2013-01-13
19:40:02 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/
Only display the trace info if using the default event display. When
invoking scripts we assume they have complete control of what's
displayed so we shouldn't unconditionally display the trace info, and
when generating scripts we don't expect to see trace info obscuring
the output message.
Hi Greg,
On Jan 18, 2013, at 9:47 PM, Greg Kroah-Hartman wrote:
> On Fri, Jan 18, 2013 at 11:05:14AM +0200, Pantelis Antoniou wrote:
>> It might make sense for the of_device_* functions that are duplicating
>> platform_device_* functions to be removed, and their functionality to
>> be subsumed
The following changes since commit e6028db0146cf5a68dbd1508225ea49840997880:
mei: fix mismatch in mutex unlock-lock in mei_amthif_read() (2013-01-07
10:28:03 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git/
The tracepoints used by the workqueue-stats script no longer exist so
trying to run the script results in:
# perf script record workqueue-stats
invalid or unsupported event: 'workqueue:workqueue_creation'
Run 'perf list' for a list of valid events
So remove the script until it can be
Hi,
This patchset fixes various problems I hit while doing a run-through
of the existing 'perf script' scripts.
Also, sometimes when running rwtop I get a 'failed to read event
header' error, which this patch fixes:
https://lkml.org/lkml/2012/9/14/401
Not sure if that was meant to get picked
For some reason the libtraceevent tracepoint-parsing code is missing
the FIELD_IS_SIGNED flag-setting code, which causes problems for the
Perl trace event binding at least, since it ends up unable to
recognize negative numbers. Things like checking for negative return
values therefore fail,
Running the check-perf-trace scripts causes segfaults in both the Perl
and Python cases:
# perf script record check-perf-trace
# perf script -s libexec/perf-core/scripts/python/check-perf-trace.py
trace_begin
Segmentation fault (core dumped)
The reason is that the 'pevent' field was
201 - 300 of 1376 matches
Mail list logo
