Hello,
On Tue, 12 Mar 2013 23:43:48 -0700
ebied...@xmission.com (Eric W. Biederman) wrote:
> Joonsoo Kim writes:
>
> > From: Joonsoo Kim
> >
> > Although our intention is to unexport internal structure entirely,
> > but there is one exception for kexec. kexec dumps address of vmlist
> > and
On Fri, Mar 15, 2013 at 01:36:40AM +, Mark Brown wrote:
> On Thu, Mar 14, 2013 at 03:26:19PM +, Dimitris Papastamos wrote:
> > There is no point having this. The space gains are trivial if there
> > are any at all.
>
> Applied, but numbers would have been nice and...
>
> > Change-Id:
On Fri, Mar 15, 2013 at 01:35:34AM +, Mark Brown wrote:
> On Thu, Mar 14, 2013 at 02:52:35PM +, Dimitris Papastamos wrote:
>
> > if (rbnode) {
> > reg_tmp = (reg - rbnode->base_reg) / map->reg_stride;
> > + /* Does this register exist? If not bail out. */
> > +
于 2013年03月15日 18:56, Arnd Bergmann 写道:
> Right. The fact that as prints a warning for those instructions makes sense
> given that we are telling it we want to run on *all* ARM architectures,
> and that ARMv8 has deprecated them officially.
>
> Of course, what is bogus about this is the "NULL"
Le 03/14/13 19:08, Florian Fainelli a écrit :
This patch converts the Marvell MV643XX ethernet driver to use the
Marvell Orion MDIO driver. As a result, PowerPC and ARM platforms
registering the Marvell MV643XX ethernet driver are also updated to
register a Marvell Orion MDIO driver. This driver
From: Linus Walleij
Recently as adoption of the pinctrl framework is reaching
niches where the pins are reconfigured during system sleep
and datasheets often talk about something called "GPIO mode",
some engineers become confused by this, thinking that since
it is named "GPIO (something
Apologies for the long email ...
Following on from another thread, I have encountered an issue with crc32 within
the mtd system, seemingly only on my AM335x cpu board.
In function ubi_eba_atomic_leb_change() in drivers/mtd/ubi/eba.c, there is a
call
to crc32.
During a remount of my ubifs
On Fri, 2013-03-15 at 10:24 +0100, Johan Hovold wrote:
> On Wed, Mar 13, 2013 at 03:43:43PM -0400, Peter Hurley wrote:
> > On Thu, 2013-03-07 at 15:55 +0100, Johan Hovold wrote:
> > > Make sure to check ASYNC_INITIALISED before raising DTR when waking up
> > > from blocked open in
Using rwsem_atomic_update to try stealing the write lock forced us to
undo the adjustment in the failure path. We can have simpler and faster
code by using cmpxchg instead.
Signed-off-by: Michel Lespinasse
---
lib/rwsem.c | 26 ++
1 file changed, 6 insertions(+), 20
In rwsem_down_write_failed(), if there are active locks after we wake up
(i.e. the lock got stolen from us), skip taking the wait_lock and go back
to sleep immediately.
Signed-off-by: Michel Lespinasse
---
lib/rwsem.c | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git
These patches extend Alex Shi's work (which added write lock stealing
on the rwsem slow path) in order to provide rwsem write lock stealing
on the fast path (that is, without taking the rwsem's wait_lock).
I initially sent a shorter series shortly before v3.9, however some
patches were doing too
This change reduces the size of the spinlocked and TASK_UNINTERRUPTIBLE
sections in rwsem_down_failed_common():
- We only need the sem->wait_lock to insert ourselves on the wait_list;
the waiter node can be prepared outside of the wait_lock.
- The task state only needs to be set to
On Friday 15 March 2013, Andrea Adami wrote:
> On Fri, Mar 15, 2013 at 1:52 AM, Chen Gang wrote:
> > 于 2013年03月15日 07:43, Russell King - ARM Linux 写道:
> >> So our wonderful toolchain has decided to start producing NULL warnings
> >> for every "mcr p15, 0, rX, c7, c10, 4" instruction? I'd
Remove the rwsem_down_failed_common function and replace it with two
identical copies of its code in rwsem_down_{read,write}_failed.
This is because we want to make different optimizations in
rwsem_down_{read,write}_failed; we are adding this pure-duplication
step as a separate commit in order to
When trying to acquire a read lock, the RWSEM_ACTIVE_READ_BIAS adjustment
doesn't cause other readers to block, so we never have to worry about waking
them back after canceling this adjustment in rwsem_down_read_failed().
We also never want to steal the lock in rwsem_down_read_failed(), so we
We are not planning to add some new waiter flags, so we can convert the
waiter type into an enumeration.
Background: David Howells suggested I do this back when I tried adding
a new waiter type for unfair readers. However, I believe the cleanup
applies regardless of that use case.
Signed-off-by:
This is mostly for cleanup value:
- We don't need several gotos to handle the case where the first
waiter is a writer. Two simple tests will do (and generate very
similar code).
- In the remainder of the function, we know the first waiter is a reader,
so we don't have to double check that.
Some small code simplifications can be achieved by doing more agressive
lock stealing:
- When rwsem_down_write_failed() notices that there are no active locks
(and thus no thread to wake us if we decided to sleep), it used to wake
the first queued process. However, stealing the lock is also
When we decide to wake up readers, we must first grant them as many
read locks as necessary, and then actually wake up all these readers.
But in order to know how many read shares to grant, we must first
count the readers at the head of the queue. This might take a while
if there are many readers,
This change fixes a race condition where a reader might determine it
needs to block, but by the time it acquires the wait_lock the rwsem
has active readers and no queued waiters.
In this situation the reader can just in parallel with the existing active
readers; it does not need to block until
Hi,
I encounter trouble that I can't explain when labelling my files.
Here are steps to reproduce (on both 3.2.37 and 3.7.3, with selinux, on
an ext4 fs):
0 - have a regular file "f", with a "before_t" security.selinux attribute
1 - reboot with selinux=0
2 - change the label to "after_t" (setfattr
We can skip the initial trylock in rwsem_down_write_failed() if there are
known active lockers already, thus saving one likely-to-fail cmpxchg.
Signed-off-by: Michel Lespinasse
---
lib/rwsem.c | 17 +
1 file changed, 9 insertions(+), 8 deletions(-)
diff --git a/lib/rwsem.c
modify __down_write[_nested] and __down_write_trylock to grab the write
lock whenever the active count is 0, even if there are queued waiters
(they must be writers pending wakeup, since the active count is 0).
Note that this is an optimization only; architectures without this
optimization will
When waking writers, we never grant them the lock - instead, they have
to acquire it themselves when they run, and remove themselves from the
wait_list when they succeed.
As a result, we can do a few simplifications in rwsem_down_write_failed():
- We don't need to check for !waiter.task since
On Fri, Mar 15, 2013 at 9:01 AM, Stephane Eranian wrote:
> On Fri, Mar 15, 2013 at 2:06 AM, Linus Torvalds
> wrote:
>> On Thu, Mar 14, 2013 at 5:24 PM, Stephane Eranian wrote:
>>>
>>> I bet if you force the affinity of your perf record to be on
>>> a CPU other than CPU0, you will not get the
On 3/13/2013 12:21 PM, Vishwanathrao Badarkhe, Manish wrote:
> From: Vishwanathrao Badarkhe, Manish
>
> Update the code to use devm_* API so that driver
> core will manage resources.
>
> Signed-off-by: Vishwanathrao Badarkhe, Manish
Tested on DA850 EVM.
Tested-by: Sekhar Nori
Thanks,
Use module_platform_driver_probe() macro which makes the code smaller
and simpler.
Signed-off-by: Fabio Porcedda
Cc: Matt Porter
Cc: Greg Kroah-Hartman
---
drivers/parport/parport_amiga.c | 15 +--
1 file changed, 1 insertion(+), 14 deletions(-)
diff --git
Hi,
On Thu, Mar 14, 2013 at 06:16:30PM +0100, Rafael J. Wysocki wrote:
> Sorry for the sluggish response, I've been travelling recently. ->
[...]
> > > > So, I'd suggest the following changes.
> > > > - Remove the "uevents" attribute. KOBJ_ONLINE/OFFLINE are not used for
> > > > ACPI device
On Friday 15 March 2013, Alexander Shiyan wrote:
> > On 14 March 2013 01:34, Alexander Shiyan wrote:
> > > This patch allow using syscon driver from the platform data, i.e.
> > > possibility using driver on systems without oftree support.
> > > For search syscon device from the client drivers,
>
On Friday 15 March 2013, Stephen Boyd wrote:
> Can you pick this patch up from the mailing list? Otherwise I can try to
> route it through David's msm tree.
Ok, applied to the fixes branch now.
Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
Hi Mark,
On 3/7/2013 11:56 AM, Vishwanathrao Badarkhe, Manish wrote:
> Add device tree data for regulator via tps6507x mfd device
> in da850-evm.
> Applies on top of v3.9-rc1 of linus tree.
I would like to take this series via the davinci tree to manage
dependencies with rest of the DT patches.
于 2013年03月15日 17:31, Andrea Adami 写道:
> AFAIK Arnd is aware and waiting for feedback about his patch:
>
> ARM: compressed/head.S: work around new binutils warning Arnd Bergmann
>
> http://lists.infradead.org/pipermail/linux-arm-kernel/2013-January/144846.html
excuse me, I am not familiar
Hi Kishon,
On 03/13/2013 10:11 AM, kishon wrote:
> Benoit,
>
> Will you be queuing this patch series?
I'm reviewing them right now.
Regards,
Benoit
>
> Thanks
> Kishon
>
> On Thursday 07 March 2013 07:05 PM, Kishon Vijay Abraham I wrote:
>> Hi Benoit,
>>
>> Here are the dt data patches to
Doug,
On 14 March 2013 02:10, Doug Anderson wrote:
> Hook up the exynos5250-snow thermistors via the device tree now that
> there's a driver available to use them.
>
> Signed-off-by: Doug Anderson
> ---
> Changes in v2:
> - Match 'uV' -> 'uv' change in Naveen's bindings.
>
>
ge.
>
Hi,
I just looked into modules-next...
The improved version is in [1]...
...and contains a file called "kernel/modsign_certificate.S" which is
NOT in the latest Linux-Next tree [2].
So, I thought about reverting the one in -next and apply the new one
from modules-next.
This
On Friday 15 March 2013, Samuel Ortiz wrote:
> On Thu, Mar 14, 2013 at 10:56:39PM +0100, Arnd Bergmann wrote:
> >
> > Please apply to MFD tree for 3.9
> Already applied to mfd-fixes.
>
For some reason I did not see it when I rebased my patches on top of linux-next
to make sure I don't send any
On 03/15/2013 12:03 AM, Arnd Bergmann :
> On Wednesday 13 March 2013, Nicolas Ferre wrote:
>> In case we end-up with an agreement on the path those fixes should
>> follow, here is the location of my updated material rebased on top of
>> 3.9-rc2:
>>
>> The following changes since commit
On Friday 15 March 2013, Geert Uytterhoeven wrote:
> On Thu, Mar 14, 2013 at 10:56 PM, Arnd Bergmann wrote:
> > Disabling CONFIG_VIRT_TO_BUS on ARM showed that the hisax netjet
> > driver depends on this deprecated functionality but is not
> > marked so in Kconfig.
> >
> > Rather than adding ARM
Arnd, Olof,
Following our conversation about these framebuffer patches for
Atmel LCD driver, here are the remaining three patches that can be
pushed for 3.10. As suggested by Arnd, I have kept them on top of last
commit concerning this topic that have already been merged in arm-soc 3.9
fixes
The value initially read via _BQC also needs to be offset by 2 to
compensate for the first 2 special items in _BCL. Introduce a helper
function that does the BQC-value-to-level conversion in order to not
needlessly duplicate code.
Signed-off-by: Danny Baumann
---
drivers/acpi/video.c | 52
Make code paths a little easier to follow, and don't needlessly continue
list iteration.
Signed-off-by: Danny Baumann
---
drivers/acpi/video.c | 13 +++--
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/drivers/acpi/video.c b/drivers/acpi/video.c
index 9c33871..5ef329a
In particular, this fixes brightness control initialization for all
devices that return index values from _BQC and don't happen to have the
initial index set by the BIOS in their _BCL table. One example for that
is the Dell Inspiron 15R SE (model number 7520).
What happened for those devices is
On 15 March 2013 10:39, Peter De Schrijver wrote:
> On Fri, Mar 15, 2013 at 06:22:47AM +0100, Stephen Warren wrote:
>> On 03/14/2013 07:20 PM, Bill Huang wrote:
>> > On Fri, 2013-03-15 at 01:54 +0800, Stephen Warren wrote:
>> >> On 03/14/2013 03:28 AM, Bill Huang wrote:
>> >>> On Thu, 2013-03-14
On Thu 14-03-13 15:42:43, Darrick J. Wong wrote:
> On Wed, Mar 13, 2013 at 10:02:16PM +0100, Jan Kara wrote:
> > On Wed 13-03-13 12:44:29, Darrick J. Wong wrote:
> > > On Wed, Mar 13, 2013 at 09:50:21AM +0100, Jan Kara wrote:
> > > > On Tue 12-03-13 18:10:20, Darrick J. Wong wrote:
> > > > > On
Il 14/03/2013 15:37, Toshi Kani ha scritto:
By the boot failure, are you referring the one that is partially
captured in screeshot3.png?
yes
If so, we need full error messages (i.e.
the top of the stack trace) to see what happened.
I'll try to get it, but it could take some time (I hope
to
Il 14/03/2013 18:27, Rafael J. Wysocki ha scritto:
On Thursday, March 14, 2013 09:20:51 AM Roberto Oppedisano wrote:
As Toshi said, this particular commit doesn't make any functional
changes. Can you please verify if the immediately preceding commit
6af9a803f4d2e4137d9f74a8fc9af4857fbda001
On 2013-03-15 08:14, Kumar Amit Mehta wrote:
fix a missing end-of-statement by adding a semicolon.
Signed-off-by: Kumar Amit Mehta
---
drivers/staging/comedi/drivers/ni_atmio.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/comedi/drivers/ni_atmio.c
On Fri, Mar 15, 2013 at 06:22:47AM +0100, Stephen Warren wrote:
> On 03/14/2013 07:20 PM, Bill Huang wrote:
> > On Fri, 2013-03-15 at 01:54 +0800, Stephen Warren wrote:
> >> On 03/14/2013 03:28 AM, Bill Huang wrote:
> >>> On Thu, 2013-03-14 at 17:21 +0800, Peter De Schrijver wrote:
> On Thu,
On Fri, Mar 15, 2013 at 12:29 AM, Jani Nikula
wrote:
> Fun. The BIOS seems to ask for zero backlight. Maybe it means something
> else for Windows 8. White is the new black or something.
I did some experiment, I go to intel_backlight directory.
It show brightness is 4648, but actual_brightness
On Fri, Mar 15, 2013 at 1:52 AM, Chen Gang wrote:
> 于 2013年03月15日 07:43, Russell King - ARM Linux 写道:
>> So our wonderful toolchain has decided to start producing NULL warnings
>> for every "mcr p15, 0, rX, c7, c10, 4" instruction? I'd just ignore
>> them and hope that the toolchain people
From: Erwan YVIN
Refactor code for creating virtio queues and prepare
for accommodating the new host virtio rings.
This refactoring moves all handing of struct virtqueue
to a separate function __create_new_virtqueue().
A more generic function __rproc_virtio_find_rings()
allocates the virtio
From: Erwan Yvin
Implement the vringh callback functions in order
to manage host virtio rings and handle kicks.
This allows virtio device to request host-virtio-rings.
Signed-off-by: Erwan Yvin
---
drivers/remoteproc/remoteproc_virtio.c | 115 +++-
From: Erwan Yvin
This driver depends on Rusty's new host virtio ring implementation,
so this patch-set is based on the vringh branch in Rusty's git.
with the vringh wrapper patch on top. They do not apply cleanly on top of the
remoteproc virtio config patches from Sjur, but it merges fine.
CAIF
On Wed, Mar 13, 2013 at 03:50:32PM -0400, Peter Hurley wrote:
> On Thu, 2013-03-07 at 15:55 +0100, Johan Hovold wrote:
> > These patches against 3.9-rc1 fix a few issues with tty-port hangup and
> > close.
> >
> > The first and fifth patch are essentially clean ups.
> >
> > The second and third
On Wed, Mar 13, 2013 at 03:43:43PM -0400, Peter Hurley wrote:
> On Thu, 2013-03-07 at 15:55 +0100, Johan Hovold wrote:
> > Make sure to check ASYNC_INITIALISED before raising DTR when waking up
> > from blocked open in tty_port_block_til_ready.
> >
> > Currently DTR could get raised at hang up as
On 03/14/2013 06:54 PM, Tony Lindgren wrote:
> * Roger Quadros [130314 08:45]:
>>
>> OK. Let me know how the below patch looks. After that, the board code
>> will look like.
>>
>> static struct usbhs_phy_data phy_data[] = {
>> {
>> .reset_gpio = 147,
>> .vcc_gpio =
Hi,
On debian 3.8-trunk-amd64 3.8.2-1~experimental.1 on Atom D2550 board Jetway
NF9I-2550. When I run
modprobe -r gma500_gfx
i get the following oops.
[ 117.598660] BUG: unable to handle kernel NULL pointer dereference at
03a8
[ 117.606591] IP: [] mutex_lock+0x10/0x2d
[
I have the same problem on my Lenovo T500. I think the graphics card is
involved.
This laptop has "hybrid graphics" - one Intel GMA 4500MHD and one ATI
Mobility Radeon HD 3650. When I boot with the Intel card, I get "irq 16:
nobody cared" during boot, not when I boot with the ATI card.
And
Use the wrapper functions for getting and setting the driver data
using spi_device instead of using dev_{get|set}_drvdata with
>dev, so we can directly pass a struct spi_device.
Signed-off-by: Jingoo Han
---
drivers/gpio/gpio-mc33880.c |8
1 files changed, 4 insertions(+), 4
Use the wrapper functions for getting and setting the driver data
using spi_device instead of using dev_{get|set}_drvdata with
>dev, so we can directly pass a struct spi_device.
Signed-off-by: Jingoo Han
---
drivers/gpio/gpio-74x164.c |8
1 files changed, 4 insertions(+), 4
dev_err() is more preferred than printk().
Signed-off-by: Jingoo Han
---
drivers/gpio/gpio-mc33880.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/drivers/gpio/gpio-mc33880.c b/drivers/gpio/gpio-mc33880.c
index b161489..3395879 100644
---
Use devm_kzalloc() to make cleanup paths simpler.
Signed-off-by: Jingoo Han
---
drivers/gpio/gpio-pcf857x.c |7 ++-
1 files changed, 2 insertions(+), 5 deletions(-)
diff --git a/drivers/gpio/gpio-pcf857x.c b/drivers/gpio/gpio-pcf857x.c
index a19b745..4f76514 100644
---
Use devm_kzalloc() to make cleanup paths simpler.
Signed-off-by: Jingoo Han
---
drivers/gpio/gpio-mc33880.c |8 +++-
1 files changed, 3 insertions(+), 5 deletions(-)
diff --git a/drivers/gpio/gpio-mc33880.c b/drivers/gpio/gpio-mc33880.c
index 6a8fdc2..b161489 100644
---
Use devm_kzalloc() to make cleanup paths simpler.
Signed-off-by: Jingoo Han
---
drivers/gpio/gpio-max732x.c |5 ++---
1 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/gpio/gpio-max732x.c b/drivers/gpio/gpio-max732x.c
index 1e0467c..d4b51b1 100644
---
Use devm_kzalloc() to make cleanup paths simpler.
Signed-off-by: Jingoo Han
---
drivers/gpio/gpio-max7301.c |4 +---
1 files changed, 1 insertions(+), 3 deletions(-)
diff --git a/drivers/gpio/gpio-max7301.c b/drivers/gpio/gpio-max7301.c
index c6c535c..6e1c984 100644
---
Use devm_kzalloc() to make cleanup paths simpler.
Signed-off-by: Jingoo Han
---
drivers/gpio/gpio-max7300.c |4 +---
1 files changed, 1 insertions(+), 3 deletions(-)
diff --git a/drivers/gpio/gpio-max7300.c b/drivers/gpio/gpio-max7300.c
index 4b6b9a0..40ab6df 100644
---
Use devm_kzalloc() to make cleanup paths simpler.
Signed-off-by: Jingoo Han
---
drivers/gpio/gpio-adp5520.c |4 +---
1 files changed, 1 insertions(+), 3 deletions(-)
diff --git a/drivers/gpio/gpio-adp5520.c b/drivers/gpio/gpio-adp5520.c
index 8afa95f..f33f78d 100644
---
On Fri, Mar 15, 2013 at 12:29 AM, Jani Nikula
wrote:
> I've never used the acpi_osi= kernel parameter, but it looks like you
> could workaround this with acpi_osi="!Windows 2012". Please check that
> running the "bad" kernel.
That did not work for me. Still have black screen on the tip of git.
I
From: Lin Ming
Add a flag REQ_PM to identify the request is PM related, such requests
will not change the device request queue's runtime status. It is
intended to be used in driver's runtime PM callback, so that driver can
perform some IO to the device there with the queue's runtime status
From: Lin Ming
Uses block layer runtime pm helper functions in
scsi_runtime_suspend/resume for devices that take advantage of it.
Remove scsi_autopm_* from sd open/release path and check_events path.
Signed-off-by: Lin Ming
Signed-off-by: Aaron Lu
Acked-by: Alan Stern
---
From: Lin Ming
When a request is added:
If device is suspended or is suspending and the request is not a
PM request, resume the device.
When the last request finishes:
Call pm_runtime_mark_last_busy().
When pick a request:
If device is resuming/suspending, then only PM request
From: Lin Ming
Add runtime pm helper functions:
void blk_pm_runtime_init(struct request_queue *q, struct device *dev)
- Initialization function for drivers to call.
int blk_pre_runtime_suspend(struct request_queue *q)
- If any requests are in the queue, mark last busy and return -EBUSY.
In August 2010, Jens and Alan discussed about "Runtime PM and the block
layer". http://marc.info/?t=12825910841=1=2
And then Alan has given a detailed implementation guide:
http://marc.info/?l=linux-scsi=133727953625963=2
To test:
# ls -l /sys/block/sda
On 03/15/2013 04:55 PM, Danny Baumann wrote:
> Hi,
>
> >> +static unsigned long long
>>> +acpi_video_index_to_level(struct acpi_video_device *device,
>>> + unsigned long long index)
>>> +{
>>> + if (device->brightness->flags._BCL_reversed)
>>> + index =
Hi,
I added a test case for this. Please take a look on it too.
This patch is based on my previous evlist cleanup patchset:
https://lkml.org/lkml/2013/3/15/47
Thanks,
Namhyung
>From df86ff1984a2ab89331a10f5e1fc93f09e260ed9 Mon Sep 17 00:00:00 2001
From: Namhyung Kim
Date: Fri, 15 Mar
Hi,
>> +static unsigned long long
+acpi_video_index_to_level(struct acpi_video_device *device,
+ unsigned long long index)
+{
+ if (device->brightness->flags._BCL_reversed)
+ index = device->brightness->count - 3 - index;
+
+ return
On 03/14/2013 08:39 PM, Hillf Danton wrote:
On Sat, Mar 9, 2013 at 10:14 AM, Will Huck wrote:
Cc experts. Hugh, Johannes,
On 03/04/2013 08:21 PM, Lenky Gao wrote:
2013/3/4 Zlatko Calusic :
The drop_caches mechanism doesn't free dirty page cache pages. And your
bash
script is creating a lot
In of_dma_controller_register() routine we are calling of_get_property() as an
parameter to be32_to_cpup(). In case the property doesn't exist we will get a
crash.
This patch changes this code to check if we got a valid property first and then
runs be32_to_cpup() on it.
Signed-off-by: Viresh
DA9052/53 MFD core handles only virtual irq therefore rtc driver needs
to be updated to work on virtual irq. Without this update DA9052/53 rtc
driver will fail during its registration.
Also getting irq by it name is no longer supported in DA9052/53 core.
Signed-off-by: Ashish Jangam
---
On 03/14/2013 06:34 PM, Danny Baumann wrote:
> The value initially read via _BQC also needs to be offset by 2 to
> compensate for the first 2 special items in _BCL. Introduce a helper
> function to do the conversion in order to not needlessly duplicate code.
> ---
> drivers/acpi/video.c | 23
On 03/14/2013 06:14 PM, Michal Hocko wrote:
On Mon 04-03-13 17:52:22, Lenky Gao wrote:
Hi,
When i just run a test on Centos 6.2 as follows:
#!/bin/bash
while true
do
file="/tmp/filetest"
echo $file
dd if=/dev/zero of=${file} bs=512 count=204800 &> /dev/null
On Thu, 2013-03-14 at 11:13 +0200, Artem Bityutskiy wrote:
> On Wed, 2013-03-13 at 11:12 +, Mark Jackson wrote:
> > Sorry ... this just locks up the unit.
>
> OK, I've reproduced the issue with 3.9-rc2 in nandsim, see the details
> below. The patch I proposed did not get the error path
On Thu, 2013-03-14 at 13:40 +, Mark Jackson wrote:
> On 14/03/13 12:23, Artem Bityutskiy wrote:
> > On Thu, 2013-03-14 at 14:18 +0200, Artem Bityutskiy wrote:
> >>> Is this size larger than the allocated buffer ?
> >>
> >> I believe so.
> >
> > Err, I mean, the buffer is large enough. I do
On 03/14/2013 06:34 PM, Danny Baumann wrote:
> Make code paths a little easier to follow, and don't needlessly continue
> list iteration.
Same here, please add Signed-off-by tag.
Reviewed-by: Aaron Lu
Thanks,
Aaron
> ---
> drivers/acpi/video.c | 13 +++--
> 1 file changed, 7
On 03/14/2013 06:34 PM, Danny Baumann wrote:
> In particular, this fixes brightness control initialization for all
> devices that return index values from _BQC and don't happen to have the
> initial index set by the BIOS in their _BCL table. One example for that
> is the Dell Inspiron 15R SE
On Fri, 2013-03-15 at 11:58 +1100, Stephen Rothwell wrote:
> Hi Artem,
>
> Today's linux-next merge of the l2-mtd tree got a conflict in
> include/linux/mtd/nand.h between commit 5bc7c33ca93a ("mtd: nand:
> reintroduce NAND_NO_READRDY as NAND_NEED_READRDY") from the mtd tree and
> commit
On Thu, Mar 14, 2013 at 09:50:04PM -0700, Ben Widawsky wrote:
> On Thu, Mar 14, 2013 at 12:59:57PM +, Chris Wilson wrote:
> > In order to prevent a potential NULL deference with hostile userspace,
> > we need to check whether the ioctl was passed an invalid args pointer.
> >
> > Reported-by:
fix a missing end-of-statement by adding a semicolon.
Signed-off-by: Kumar Amit Mehta
---
drivers/staging/comedi/drivers/ni_atmio.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/comedi/drivers/ni_atmio.c
b/drivers/staging/comedi/drivers/ni_atmio.c
index
On Fri, 2013-03-15 at 05:13 +, Al Viro wrote:
> On Fri, Mar 15, 2013 at 02:09:14PM +0900, J. R. Okajima wrote:
>
> > If so, it has a big disadvantage for the layer-fs (or branch-fs) to have
> > to implement a new method for whiteout.
> >
> > Overlayfs implements whiteout as symlink+xattr
Doug,
On 14 March 2013 02:09, Doug Anderson wrote:
> The exynos ADC won't work without a regulator called "vdd" and a clock
> called "adc". Document this fact in the device tree bindings.
>
> Signed-off-by: Doug Anderson
Thanks for the correction. Clocks and regulator is needed.
I missed it
Document device tree binding information as required by the
Samsung' USB 3.0 controller.
Signed-off-by: Vivek Gautam
---
.../devicetree/bindings/usb/exynos-usb.txt | 34
1 files changed, 34 insertions(+), 0 deletions(-)
diff --git
Adding DWC3 device tree node for Exynos5250 needed to
parse device tree data.
Signed-off-by: Vivek Gautam
---
arch/arm/boot/dts/exynos5250.dtsi | 20 ++--
1 files changed, 18 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/exynos5250.dtsi
This patch-set is in continuation with patch-series:
[PATCH v4 0/4] Enable ehci, ohci and dwc3 devices on exynos5250
out of which follwowing patches have been picked up:
ARM: Exynos5250: Enabling ehci-s5p driver
ARM: Exynos5250: Enabling ohci-exynos driver
Based on following patch-set for
This patch enables support for XHCI on exynos5 series of SOCs,
to support host side USB 3.0 support.
Signed-off-by: Vivek Gautam
---
arch/arm/mach-exynos/Kconfig |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-exynos/Kconfig b/arch/arm/mach-exynos/Kconfig
On Fri, Mar 15, 2013 at 2:06 AM, Linus Torvalds
wrote:
> On Thu, Mar 14, 2013 at 5:24 PM, Stephane Eranian wrote:
>>
>> I bet if you force the affinity of your perf record to be on
>> a CPU other than CPU0, you will not get the crash.
>>
>> This is what I am seeing now. I appears on resume,
>>
On Thu, 14 Mar 2013, Rafael J. Wysocki wrote:
> > > commit 181380b702eee1a9aca51354d7b87c7b08541fcf
> > > Author: Yinghai Lu
> > > Date: Sat Feb 16 11:58:34 2013 -0700
> > >
> > > PCI/ACPI: Don't cache _PRT, and don't associate them with bus numbers
> >
> > This patch __fixed__ this
Adding usb3.0 phy node for Exynos5250 along with the
necessary device data to be parsed.
Signed-off-by: Vivek Gautam
---
arch/arm/boot/dts/exynos5250.dtsi | 14 ++
1 files changed, 14 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/exynos5250.dtsi
Adding usbphy node for Exynos5250 along with the
necessary device data to be parsed.
Signed-off-by: Vivek Gautam
---
arch/arm/boot/dts/exynos5250.dtsi | 15 +++
1 files changed, 15 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/exynos5250.dtsi
Based on 'for-next' of linux-samsung tree with following patches
from Doug on top:
usb: Document clocks in samsung, exynos4210-ehci/ohci bindings
ARM: dts: add usb 2.0 clock references to exynos5250 device tree
Also depending upon following patch-series for Samsung-usb-phy driver:
[PATCH v7 0/2]
Some drivers depends on transport_header to do packet transmission, but it was
unset in some cases (one example is macvtap driver which build skbs from
userspace and generate CHECKSUM_NONE packets). The driver may crash in those
cases since the transport_header was not valid. The problem becomes
501 - 600 of 1244 matches
Mail list logo
