From: "Guillermo A. Amaral"
Fixed a few minor coding style issues in xpad driver.
Signed-off-by: "Guillermo A. Amaral B."
---
drivers/input/joystick/xpad.c |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/input/joystick/xpad.c b/drivers/input/joystick/xpad.
On Sat, 2012-12-01 at 14:03 -0800, Linus Torvalds wrote:
> On Sat, Dec 1, 2012 at 1:44 PM, Ingo Molnar wrote:
> >
> > You are not missing anything. That flag is my fault not Mike's:
> > I booted the initial version of that patch but was unsure
> > whether autogroups was enabled - it's a pretty tr
Hi Myungjoo/Chanwoo/Aneesh/Anton,
Could you please review this. This is a follow up patch for "PATCH] extcon :
callback function to read cable property"
-jtc
> Subject: [PATCH] EXTCON: Get and set cable properties
>
> Existing EXTCON implementation doesn't give a mechanim to read the cable
>
From: "Guillermo A. Amaral"
Added popular VP combinations for MadCatz, PDP and PowerA (new).
Removed Pelican 'TSZ' Wired Xbox 360 Controller since it's clashing with Edge
wireless Controller and I failed to confirm the PID.
Signed-off-by: "Guillermo A. Amaral B."
---
drivers/input/joystick/xp
From: "Guillermo A. Amaral"
Fixed a few minor coding style issues in xpad driver.
Signed-off-by: "Guillermo A. Amaral B."
---
drivers/input/joystick/xpad.c |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/input/joystick/xpad.c b/drivers/input/joystick/xpad.
The current sp5100_tco driver only supports SP5100/SB7x0 chipset, doesn't
support SB8x0 chipset, because current sp5100_tco driver doesn't know that the
offset address for watchdog timer was changed from SB8x0 chipset.
The offset address of SP5100 and SB7x0 chipsets are as follows, quote from the
In order to avoid constantly allocating and deallocating there is a fixed
buffer which spi_write_then_read() uses for transfers, with an early error
check to ensure that the transfer fits within the buffer. This limits the
size of transfers to this size, currently max(32, SMP_CACHE_BYTES).
Since w
On Mon, 2012-11-26 at 15:13 +, Steven Whitehouse wrote:
> Hi,
>
> On Sun, 2012-11-25 at 14:11 +0100, Ben Hutchings wrote:
> > On Wed, 2012-11-14 at 20:11 -0800, Greg Kroah-Hartman wrote:
> > > 3.6-stable review patch. If anyone has any objections, please let me
> > > know.
> > >
> > > -
This call is followed by a call to memcpy() on the same memory area, so it can
be safely removed.
Signed-off-by: Cyril Roelandt
---
drivers/scsi/megaraid/megaraid_sas_fusion.c |2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/scsi/megaraid/megaraid_sas_fusion.c
b/drivers/scsi/mega
These calls are followed by calls to memcpy() on the same memory area, so they
can be safely removed.
Signed-off-by: Cyril Roelandt
---
drivers/scsi/bnx2fc/bnx2fc_hwi.c |4
1 file changed, 4 deletions(-)
diff --git a/drivers/scsi/bnx2fc/bnx2fc_hwi.c b/drivers/scsi/bnx2fc/bnx2fc_hwi.c
i
On Fri, 2012-11-30 at 10:54 -0800, Greg Kroah-Hartman wrote:
> 3.4-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Dan Carpenter
>
> commit 5bc9ad774c063f6b41965e7314f2c26aa5e465a0 upstream.
>
> Gcc 4.6.2 complains that:
>
> drivers/l
On Tue, Oct 09, 2012 at 10:15:08AM +0100, David Howells wrote:
> Can you merge the following branch into the alpha tree please.
>
> This is to complete part of the UAPI disintegration for which the preparatory
> patches were pulled recently.
I think the alpha-next tree is currently inactive so no
On Sat, 2012-12-01 at 19:50 +0100, Stefan Beller wrote:
> Hello,
>
> I was just browsing the shortlog and it looked to
> me as if there are many double entries, i.e. the same person
> being there with multiple email addresses.
>
> So I wrote a script, which finds double names and adds them
> to
I'd like to be able to run programs (like bash!) as nonroot but with
some capabilities granted. After all these years, it's almost, but
not quite, possible. This is because the transition rule (if root
isn't involved or NOROOT is set) is pP' = (pB' & fP) | (pI' & fI),
and, when execing a program
This call is followed by a call to memcpy() on the same memory area, so it can
be safely removed.
Signed-off-by: Cyril Roelandt
---
drivers/staging/vt6656/bssdb.c |1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/staging/vt6656/bssdb.c b/drivers/staging/vt6656/bssdb.c
index 6a13941..
These calls are followed by calls to memcpy() on the same memory area, so they
can be safely removed.
Signed-off-by: Cyril Roelandt
---
drivers/staging/rtl8712/mlme_linux.c|2 --
drivers/staging/rtl8712/rtl871x_cmd.c |1 -
drivers/staging/rtl8712/rtl871x_ioctl_set.c |2
These calls are followed by calls to memcpy() on the same memory area, so they
can safely be removed.
Signed-off-by: Cyril Roelandt
---
drivers/net/ethernet/brocade/bna/bfa_ioc.c |4
1 file changed, 4 deletions(-)
diff --git a/drivers/net/ethernet/brocade/bna/bfa_ioc.c
b/drivers/net/e
These calls are followed by calls to memcpy() on the same memory area, so they
can safely be removed.
Signed-off-by: Cyril Roelandt
---
drivers/scsi/bfa/bfa_ioc.c |1 -
drivers/scsi/bfa/bfad_bsg.c |1 -
2 files changed, 2 deletions(-)
diff --git a/drivers/scsi/bfa/bfa_ioc.c b/drivers/s
The following six patches remove useless calls to memset(). They have been found
with this Coccinelle script:
@@
expression E;
expression S;
@@
-memset(E, 0, S);
memcpy(E, ..., S);
They have only been tested by compilation.
WBR,
Cyril Roelandt.
Cyril Roelandt (6):
bna: remove useless call
Evaluation of revision B of WM5102 suggests updates to the register patch
for optimal performance, and make this the default behaviour for new
devices.
Signed-off-by: Mark Brown
---
drivers/mfd/wm5102-tables.c | 16 +++-
1 file changed, 15 insertions(+), 1 deletion(-)
diff --git a
Make sure that we don't race with the initial device boot by only doing
the initialisation after we've waited for the boot to complete.
The runtime PM code already waits for the boot to complete before it
syncs the register patches so in most systems if a race does occur we will
power down very so
On Sun, Dec 02, 2012 at 02:11:51AM +0900, Mark Brown wrote:
> Make sure that we don't race with the initial device boot by only doing
> the initialisation after we've waited for the boot to complete.
This is broken, will send a fixed version soon.
signature.asc
Description: Digital signature
Sorry for top posting this - I forgot to email while still at work.
I've been poking at this, and think (a) it's possible that I'm being too
paranoid, and (b) it looks like it'll work with some of the future stuff. So
I'll back off my objections for the moment, and give these changes a try,
po
On Sat, Dec 1, 2012 at 9:50 AM, Greg Kroah-Hartman
wrote:
> On Sat, Dec 01, 2012 at 11:58:28PM +0900, Satoru Takeuchi wrote:
>> At Fri, 30 Nov 2012 10:55:31 -0800,
>> Greg Kroah-Hartman wrote:
>> >
>> > This is the start of the stable review cycle for the 3.6.9 release.
>> > There are 54 patches i
On Sat, Dec 1, 2012 at 8:35 AM, Satoru Takeuchi
wrote:
> At Fri, 30 Nov 2012 10:54:52 -0800,
> Greg Kroah-Hartman wrote:
>>
>> This is the start of the stable review cycle for the 3.4.21 release.
>> There are 56 patches in this series, all will be posted as a response
>> to this one. If anyone ha
On Fri, Nov 30, 2012 at 11:45 AM, Greg Kroah-Hartman
wrote:
> This is the start of the stable review cycle for the 3.0.54 release.
> There are 37 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Re
it's not necessary to lock the buffers because no one touches them
beyond the file system.
Signed-off-by: Cong Ding
---
fs/ext3/resize.c |4
1 files changed, 0 insertions(+), 4 deletions(-)
diff --git a/fs/ext3/resize.c b/fs/ext3/resize.c
index 0f814f3..f76fcd6 100644
--- a/fs/ext3/res
vhost-blk is an in-kernel virito-blk device accelerator.
Due to lack of proper in-kernel AIO interface, this version converts
guest's I/O request to bio and use submit_bio() to submit I/O directly.
So this version any supports raw block device as guest's disk image,
e.g. /dev/sda, /dev/ram0. We ca
>From 8852aac25e79e38cc6529f20298eed154f60b574 Mon Sep 17 00:00:00 2001
From: Tejun Heo
Date: Sat, 1 Dec 2012 16:23:42 -0800
8376fe22c7 ("workqueue: implement mod_delayed_work[_on]()")
implemented mod_delayed_work[_on]() using the improved
try_to_grab_pending(). The function is later used, among
Hello, Linus.
Unfortunately, I have two really late fixes. One was for a
long-standing bug and queued for 3.8 but I found out about a
regression introduced during 3.7-rc1 two days ago, so I'm sending out
the two fixes together.
The first (long-standing) one is rescuer_thread() entering exit path
Dave, Shuah,
At Sat, 1 Dec 2012 10:15:21 -0700,
Shuah Khan wrote:
>
> On Sat, Dec 1, 2012 at 9:24 AM, David Miller wrote:
> >
> > Satoru, I just want to let you know that, because you encode your
> > emails using ISO-2022-JP-2, nearly half of the subscribers to
> > the vger.kernel.org mailing li
On Sat, 1 Dec 2012, Tejun Heo wrote:
> Can you please test this one too? Thanks!
>
> […]
> + if (!delay) {
> + __queue_work(cpu, wq, &dwork->work);
> + return;
> + }
> +
> […]
> - if (!delay)
> - return queue_work_on(cpu, wq, &dwork->work);
> -
Yes
Hello all,
Somewhere between v3.6.8 [vanilla] and 3.7.0-rc7 the ability to control the LCD
brightness was broken on this laptop [details below]. Basically it locks the
brightness as full brightness and cannot be changed. It works properly in
v3.6.8 though [and below...].
Details:
00:02.0 VG
it is unnecessary to check i<4 after the loop. just do it before the break.
Signed-off-by: Cong Ding
---
fs/ext4/hash.c |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/fs/ext4/hash.c b/fs/ext4/hash.c
index fa8e491..3d586f0 100644
--- a/fs/ext4/hash.c
+++ b/fs/ext4/h
On Wed, Nov 28, 2012 at 7:42 AM, Axel Lin wrote:
> This makes PINCTRL related config options visible.
> Otherwise there is no way to build pinctrl drivers for MMP2, PXA168 and
> PXA910.
>
> Signed-off-by: Axel Lin
> ---
> This patch was sent on https://lkml.org/lkml/2012/11/12/10
> Resend to Ha
On Wed, Nov 28, 2012 at 7:37 AM, Axel Lin wrote:
> These drivers do not need to select PINCONF.
>
> Signed-off-by: Axel Lin
> ---
> This patch was sent on https://lkml.org/lkml/2012/11/12/12.
> Resend to Haojian's correct email address.
Applied. PXA guys can scream if they don't like it :-)
Yo
On Tue, Nov 27, 2012 at 3:49 PM, Axel Lin wrote:
> I got below build error with random config if CONFIG_PINCTRL_SAMSUNG=y &&
> CONFIG_PINCTRL_EXYNOS5440=y.
>
> Fix the build error by making pcfgs static.
>
> LD drivers/pinctrl/built-in.o
> drivers/pinctrl/pinctrl-exynos5440.o: In function
I've extensively tested 2844a48706e5 (tip at the time I compiled) for
the last few days and have been unable to reproduce.
This bug appears to be fixed.
Thanks.
-JimC
--
James Cloos OpenPGP: 1024D/ED7DAEA6
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
th
Varun Sethi wrote:
> Following is a brief description of the PAMU hardware:
> PAMU determines what action to take and whether to authorize the action on
> the basis of the memory address, a Logical IO Device Number (LIODN), and
> PAACT table (logically) indexed by LIODN and address. Hardware device
On Sun, Dec 02, 2012 at 07:42:06AM +1000, Dave Airlie wrote:
> Guys I think you guys might be overthniking things here.
>
> I know you have some sort of upstream/downstream split, but really in
> the upstream kernel, we don't care about that, so don't make it our
> problem.
>
> There is no need f
On 12/01/2012 01:30 PM, Roger Heflin wrote:
> On Sat, Dec 1, 2012 at 6:04 AM, Richard Yao wrote:
>> Standard Microsystems Corp. 8-in-1 Card
>> Reader
>
> Does that card reader support SDHC cards?The older readers don't
> support >2GB (ie sdhc)
> cards, and that would mean a 2GB card works and
On 01.12.2012 20:13, Tejun Heo wrote:
Hello,
On Sat, Dec 01, 2012 at 06:11:10PM +0100, Zlatko Calusic wrote:
Sure. Please clarify, should I apply it on top of the previous one
or standalone?
It's a replacement, so by itself.
Thanks!
I have good news, again. The kernel with the patch appli
On Sat, Dec 1, 2012 at 1:44 PM, Ingo Molnar wrote:
>
> You are not missing anything. That flag is my fault not Mike's:
> I booted the initial version of that patch but was unsure
> whether autogroups was enabled - it's a pretty transparent
> feature. So I figured that having that flag (but readonl
Update: laptop don't resume working not only after a long time held in suspend,
but also after a short period of time for example 3 minutes.
As for a long time - it about 24-36 hours.
On Sun, Dec 2, 2012 at 12:59 AM, Azat Khuzhin wrote:
> I tried this patch - https://bugzilla.kernel.org/attachme
* Ingo Molnar wrote:
> You are not missing anything. That flag is my fault not
> Mike's: I booted the initial version of that patch but was
> unsure whether autogroups was enabled - it's a pretty
> transparent feature. So I figured that having that flag (but
> readonly) would give us this in
* Linus Torvalds wrote:
> On Sat, Dec 1, 2012 at 3:16 AM, Ingo Molnar wrote:
> >
> > Please [RFC] pull the latest sched-urgent-for-linus git tree
> > from:
>
> No. That patch is braindead. I wouldn't pull it even if it
> wasn't this late.
>
> Why the hell leave a read-only 'sched_autogroup_e
Guys I think you guys might be overthniking things here.
I know you have some sort of upstream/downstream split, but really in
the upstream kernel, we don't care about that, so don't make it our
problem.
There is no need for any sort of stable API between host1x and the sub
drivers, we change API
On Fri, Nov 30, 2012 at 01:58:18PM +, Myklebust, Trond wrote:
> The reason for the choice of d_drop over d_invalidate() is the d_count
> checks. It really doesn't matter whether or not the client thinks it has
> users for a directory if the server is telling you that it is ESTALE. So
> we forc
On Sat, Dec 1, 2012 at 3:16 AM, Ingo Molnar wrote:
>
> Please [RFC] pull the latest sched-urgent-for-linus git tree
> from:
No. That patch is braindead. I wouldn't pull it even if it wasn't this late.
Why the hell leave a read-only 'sched_autogroup_enabled' proc file?
What the f*ck is the point?
I tried this patch - https://bugzilla.kernel.org/attachment.cgi?id=73510
from https://bugzilla.kernel.org/show_bug.cgi?id=14733.
And I don't see such messages any more.
But another problem surfaced - laptop can't resume working after a
long time held in suspend,
end there is not messages in kern.
Signed-off-by: Philippe Reynes
---
drivers/rtc/rtc-ds1374.c |8
1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/drivers/rtc/rtc-ds1374.c b/drivers/rtc/rtc-ds1374.c
index 9663160..174c532 100644
--- a/drivers/rtc/rtc-ds1374.c
+++ b/drivers/rtc/rtc-ds1374.c
@@ -49,6 +49,
On Saturday 01 December 2012, Philip Balister wrote:
> On 11/30/2012 09:36 AM, Greg KH wrote:
> > Yes, I know of at least one more device other than the ones listed above
> > that wants this type of functionality as well, so defining it in a
> > standard user/kernel api manner would be very good to
A SMSC PHY in power down mode can't be used.
If a SMSC PHY is in this mode in the config_init
stage, the mode "all capable" is set. So the PHY
could then be used.
Signed-off-by: Philippe Reynes
---
drivers/net/phy/smsc.c | 27 ++-
include/linux/smscphy.h |5 +
Hi all,
While fuzzing with trinity inside a KVM tools guest, running latest -next, I've
stumbled on:
[ 3130.099477] ==
[ 3130.104862] [ INFO: possible circular locking dependency detected ]
[ 3130.104862] 3.7.0-rc7-next-20121130-sasha-00015-g06f
On 12/01/2012 03:15 PM, Ingo Molnar wrote:
Index: linux/include/linux/rmap.h
===
--- linux.orig/include/linux/rmap.h
+++ linux/include/linux/rmap.h
@@ -128,6 +128,17 @@ static inline void anon_vma_unlock(struc
up_write(&anon
On Sat, Dec 01, 2012 at 11:30:55AM -0800, Philip Balister wrote:
> On 12/01/2012 08:56 AM, Greg KH wrote:
> >On Fri, Nov 30, 2012 at 07:19:16PM -0800, Philip Balister wrote:
[..]
> >
> >>I've been engaged in design discussions today with my customer. Our
> >>target is the Xilinx Zynq hardware. The
On Wed, 28 Nov 2012 at 16:41, Li Zhong wrote:
> On Tue, 2012-11-27 at 19:22 -0800, Christian Kujau wrote:
> > On Tue, 27 Nov 2012 at 19:06, Christian Kujau wrote:
> > > the same thing[0] happened again in 3.7-rc7, after ~20h uptime:
> >
> > I found the following on patchwork, but this seems to dea
On 12/01/2012 03:10 PM, Ingo Molnar wrote:
Convert the struct anon_vma::mutex to an rwsem, which will help
in solving a page-migration scalability problem. (Addressed in
a separate patch.)
The conversion is simple and straightforward: in every case
where we mutex_lock()ed we'll now down_write()
Note, with this optimization I went a farther than the
boundaries of the migration code - it seemed worthwile to do and
I've reviewed all the other users of page_lock_anon_vma() as
well and none seemed to be modifying the list inside that lock.
Please review this patch carefully - in particula
Convert the struct anon_vma::mutex to an rwsem, which will help
in solving a page-migration scalability problem. (Addressed in
a separate patch.)
The conversion is simple and straightforward: in every case
where we mutex_lock()ed we'll now down_write().
Suggested-by: Linus Torvalds
Cc: Andrew M
On Sat, 2012-12-01 at 09:59 -0500, Peter Hurley wrote:
> From instrumenting the tty_release() path, it's clear that tty_buffer
> work is still scheduled even after tty_release_ldisc() has run. For
> example, with this patch I get the warning below it.
>
> [Further analysis to follow in subseq
On Sat, Dec 1, 2012 at 8:34 PM, Linus Walleij wrote:
> The crucial question is: can the STMPE controllers be
> used for GPIO, PWM, keypad and touchscreen at the
> *same time* or are they nailed to *one* usecase during
> electronics design?
Looking closer at the datasheet it seems to mux pins on
On Mon, Nov 26, 2012 at 12:28 PM, Lee Jones wrote:
> On Fri, 23 Nov 2012, Shiraz Hashim wrote:
[About st-norequest-mask]
>> This is a board dependent parameter which just informs gpio driver
>> about pins, which must not be requested. It may happen for a stmpe
>> variant where such gpio pins are
On 12/01/2012 08:56 AM, Greg KH wrote:
On Fri, Nov 30, 2012 at 07:19:16PM -0800, Philip Balister wrote:
On 11/30/2012 09:36 AM, Greg KH wrote:
On Fri, Nov 30, 2012 at 05:28:47PM +, Arnd Bergmann wrote:
On Wednesday 28 November 2012, Eli Billauer wrote:
Xillybus is a general-purpose frame
On 01.12.2012 19:34, Lucas Stach wrote:
> This would certainly make life easier, but personally I don't think it's
> the right thing to do. The separation of the Linux kernel into different
> subsystems was done for a reason and just because the specific hardware
> at hands happens to work a bit di
On Sat, Dec 01, 2012 at 07:08:12PM +0200, Terje Bergström wrote:
> On 01.12.2012 16:45, Thierry Reding wrote:
> > I did some prototyping on how a libdrm API could look like a few weeks
> > back. I should clean the patches up some and push them to a public
> > repository or to the mailing lists for
Hello,
On Sat, Dec 01, 2012 at 06:11:10PM +0100, Zlatko Calusic wrote:
> Sure. Please clarify, should I apply it on top of the previous one
> or standalone?
It's a replacement, so by itself.
Thanks!
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body
On 12/01/2012 01:38 PM, Linus Torvalds wrote:
On Sat, Dec 1, 2012 at 4:26 AM, Ingo Molnar wrote:
So as a quick concept hack I wrote the patch attached below.
(It's not signed off, see the patch description text for the
reason.)
Well, it confirms that anon_vma locking is a big problem, but a
On Sat, Dec 1, 2012 at 10:41 AM, Ingo Molnar wrote:
>
> I'll try the rwsem and see how it goes?
Yeah. That should be an easy conversion (just convert everything to
use the write-lock first, and then you can make one or two migration
places use the read version).
Side note: The mutex code tends t
Hello,
I was just browsing the shortlog and it looked to
me as if there are many double entries, i.e. the same person
being there with multiple email addresses.
So I wrote a script, which finds double names and adds them
to the .mailmap file. However manual checking, whether these
are really t
On Fri, Nov 30, 2012 at 12:57 PM, Lee Jones wrote:
> The aim of this and subsequent patch-sets is to refactor battery
> management services provided by the ab8500 MFD. This first patch-set
> brings a few modifications to the collection which happened on the
> internal kernel, but were never Mainl
On Thu, Nov 29, 2012 at 6:34 PM, Grant Likely wrote:
> On Wed, 28 Nov 2012 12:38:38 +0900, Alex Courbot wrote:
>> On Monday 26 November 2012 19:14:31 Grant Likely wrote:
>> > I don't have any problem with a gpio_get function, but I do agree that
>> > making it return an opaque handle is how it sh
* Linus Torvalds wrote:
> On Sat, Dec 1, 2012 at 4:26 AM, Ingo Molnar wrote:
> >
> >
> > So as a quick concept hack I wrote the patch attached below.
> > (It's not signed off, see the patch description text for the
> > reason.)
>
> Well, it confirms that anon_vma locking is a big problem, but
On Sat, Dec 01, 2012 at 02:45:57AM +0900, Joonsoo Kim wrote:
> @@ -614,21 +616,35 @@ static int ashmem_pin_unpin(struct ashmem_area *asma,
> unsigned long cmd,
> pgstart = pin.offset / PAGE_SIZE;
> pgend = pgstart + (pin.len / PAGE_SIZE) - 1;
>
> - mutex_lock(&ashmem_mutex);
> +
On Sat, Dec 1, 2012 at 4:26 AM, Ingo Molnar wrote:
>
>
> So as a quick concept hack I wrote the patch attached below.
> (It's not signed off, see the patch description text for the
> reason.)
Well, it confirms that anon_vma locking is a big problem, but as
outlined in my other email it's complete
On Sat, Dec 1, 2012 at 10:05 PM, Linus Walleij wrote:
> On Mon, Nov 26, 2012 at 12:32 PM, Shiraz Hashim wrote:
>> On Mon, Nov 26, 2012 at 11:28:23AM +, Lee Jones wrote:
>>>
>>> Doesn't pinctrl normally handle this kind of stuff?
>>
>> Yes, but I think it is only for managing the SoC and its p
* Linus Torvalds wrote:
> On Sat, Dec 1, 2012 at 1:49 AM, Ingo Molnar wrote:
> >
> > I *think* you are right that for this type of migration that
> > we are using here we indeed don't need to take an exclusive
> > vma lock - in fact I think we don't need to take it at all:
>
> I'm pretty sur
On Sat, Dec 01, 2012 at 07:15:55PM +0100, Sebastian Hesselbarth wrote:
> On 12/01/2012 07:13 PM, Jason Cooper wrote:
> >On Sat, Dec 01, 2012 at 06:07:06PM +0100, Linus Walleij wrote:
> >>On Mon, Nov 26, 2012 at 10:18 AM, Sebastian Hesselbarth
> >> wrote:
> >>
> >>>During merge of the mvebu patches
On 12/01/2012 07:13 PM, Jason Cooper wrote:
On Sat, Dec 01, 2012 at 06:07:06PM +0100, Linus Walleij wrote:
On Mon, Nov 26, 2012 at 10:18 AM, Sebastian Hesselbarth
wrote:
During merge of the mvebu patches a clock gate for pinctrl was
lost. This patch just readds the clock gate.
Signed-off-by
On Sat, Dec 01, 2012 at 06:07:06PM +0100, Linus Walleij wrote:
> On Mon, Nov 26, 2012 at 10:18 AM, Sebastian Hesselbarth
> wrote:
>
> > During merge of the mvebu patches a clock gate for pinctrl was
> > lost. This patch just readds the clock gate.
> >
> > Signed-off-by: Sebastian Hesselbarth
>
On Thu, Nov 29, 2012 at 9:45 PM, Luis R. Rodriguez
wrote:
> From: "Luis R. Rodriguez"
>
> spinlock_t should always be used.
>
> I was unable to build test with allmodconfig:
>
> mcgrof@frijol ~/linux-next (git::(no branch))$ make C=1
> M=drivers/crypto/ux500/
>
> WARNING: Symbol version dump
Hi,
On 11/28/2012 08:27 PM, Rajanikanth H.V wrote:
> From: "Rajanikanth H.V"
>
> property, battery-type shall be one of supported technology type
> instead blank
> - refer: Documentation/devicetree/bindings/power_supply/ab8500/fg.txt
> for the list supported types
> - this patch appends to
This updates the IRQdomain documentation a bit, by adding a more
verbose explanation to why we need this, and by adding some
extended documentation of the irq_domain_simple() usecase.
Signed-off-by: Linus Walleij
---
Documentation/IRQ-domain.txt | 34 +-
1 file ch
On Sat, Dec 1, 2012 at 1:49 AM, Ingo Molnar wrote:
>
> I *think* you are right that for this type of migration that we
> are using here we indeed don't need to take an exclusive vma
> lock - in fact I think we don't need to take it at all:
I'm pretty sure we do need at least a read-side reference
On 1 December 2012 22:17, Linus Walleij wrote:
> If you can, try to avoid this:
> Content-Type: text/plain; charset=WINDOWS-1252
> Content-Transfer-Encoding: quoted-printable
>
> That kind om message encoding makes my life a living hell
> (but I fixed it, manually editing the whole patch) how did
Am Samstag, den 01.12.2012, 18:55 +0200 schrieb Terje Bergström:
> On 01.12.2012 17:10, Thierry Reding wrote:
> > On Sat, Dec 01, 2012 at 01:44:41PM +0200, Terje Bergström wrote:
> >> host1x module being in DRM directory hinders using nvhost from anywhere
> >> outside DRM in both upstream and downs
On Wed, Nov 28, 2012 at 12:52 PM, Rabin Vincent
wrote:
> When a clock has multiple users, the WARNING on imbalance of
> enable/disable may not show the guilty party since although they may
> have commited the error earlier, the warning is emitted later when some
> other user, presumably innocent,
On Wed, Nov 28, 2012 at 12:52 PM, Rabin Vincent
wrote:
> In order to provide per-user accounting, this separates the struct clk
> used in the common clock framework into two structures 'struct clk_core'
> and 'struct clk'. struct clk_core will be used for internal
> manipulation and struct clk w
On Sat, Dec 1, 2012 at 9:24 AM, David Miller wrote:
>
> Satoru, I just want to let you know that, because you encode your
> emails using ISO-2022-JP-2, nearly half of the subscribers to
> the vger.kernel.org mailing lists bounce your postings.
>
> I know it's stupid, and it's mostly a Microsoft Ex
Signed-off-by: Mark Brown
---
drivers/mfd/wm5102-tables.c |2 ++
include/linux/mfd/arizona/registers.h |1 +
2 files changed, 3 insertions(+)
diff --git a/drivers/mfd/wm5102-tables.c b/drivers/mfd/wm5102-tables.c
index e9063ab..b82a003 100644
--- a/drivers/mfd/wm5102-tables.c
+
On 01.12.2012 16:58, Thierry Reding wrote:
> I don't know where you see politics in what I said. All I'm saying is
> that we shouldn't be making things needlessly complex. In my experience
> the technically cleanest solution is usually the one with the least
> complexity.
Let me come up with a pro
Evaluation of revision B of WM5102 suggests updates to the register patch
for optimal performance, and make this the default behaviour for new
devices.
Signed-off-by: Mark Brown
---
drivers/mfd/wm5102-tables.c | 16 +++-
1 file changed, 15 insertions(+), 1 deletion(-)
diff --git a
Make sure that we don't race with the initial device boot by only doing
the initialisation after we've waited for the boot to complete.
The runtime PM code already waits for the boot to complete before it
syncs the register patches so in most systems if a race does occur we will
power down very so
On 01.12.2012 15:38, Tejun Heo wrote:
Hello,
On Sat, Dec 01, 2012 at 12:06:41PM +0100, Zlatko Calusic wrote:
I have good news. The patch fixes the regression!
To doublecheck and provide you additional data, I updated to the latest Linus
kernel (commit 7c17e48), recompiled (WITHOUT the patch),
On 01.12.2012 16:45, Thierry Reding wrote:
> I did some prototyping on how a libdrm API could look like a few weeks
> back. I should clean the patches up some and push them to a public
> repository or to the mailing lists for review.
Ok. Sorry about the delay - I recently learned I need separate
p
On Mon, Nov 26, 2012 at 10:18 AM, Sebastian Hesselbarth
wrote:
> During merge of the mvebu patches a clock gate for pinctrl was
> lost. This patch just readds the clock gate.
>
> Signed-off-by: Sebastian Hesselbarth
Acked-by: Linus Walleij
So who's supposed to merge this patch? Me? The MVEBU-
On Fri, Nov 23, 2012 at 4:08 PM, Davide Ciminaghi wrote:
> From: Alessandro Rubini
>
> Signed-off-by: Alessandro Rubini
> Acked-by: Giancarlo Asnaghi
Acked-by: Linus Walleij
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a mess
On Sun, Nov 25, 2012 at 9:32 AM, Dmitry Torokhov
wrote:
> On Thu, Nov 22, 2012 at 01:23:36PM +, Lee Jones wrote:
>> From: Jonas Aaberg
>>
>> Disable hardware if active when suspending if the hw can not
>> wake the system from suspend.
>
> How about below instead (needs the other patch I have
On Sat, Dec 01, 2012 at 08:56:12AM -0800, Greg KH wrote:
> So, in the grand tradition of, "The first one there wins", why not base
> it all off of your driver, and how that works, and we can go from there :)
Oops, sorry s/your/Eli's/, my confusion.
greg k-h
--
To unsubscribe from this list: send
On Sun, Nov 25, 2012 at 9:31 AM, Dmitry Torokhov
wrote:
> Instead of reporting the initial stage when the device is registered we
> should do it when the device is opened (so there are users).
>
> Signed-off-by: Dmitry Torokhov
Makes perfect sense.
Acked-by: Linus Walleij
Yours,
Linus Walleij
1 - 100 of 191 matches
Mail list logo
