On Wed, Jan 30, 2013 at 10:55:00AM +0100, Dirkjan Bussink wrote:
>
> On 30 Jan 2013, at 06:12, Greg Kroah-Hartman
> wrote:
>
> > It doesn't apply cleanly to the linux-next tree, can you refresh this
> > and resend it so that I can apply it? If you want it backported to the
> > stable kernel
On 2012-12-28 17:16, Andreas Larsson wrote:
This makes the cpu mode of the driver available outside of an FSL SOC
and even powerpc environment. This is accomplished by putting things
regarding fsl specific code and to cpm specific code within ifdefs.
Furthermore, this adds support for the
On Thu, Jan 24, 2013 at 10:31 AM, Sachin Kamat wrote:
> 'pinctrl_release' is used only in this file. Hence make it static.
>
> Without this patch we get the following sparse error:
> drivers/pinctrl/core.c:815:6: warning:
> symbol 'pinctrl_release' was not declared. Should it be static?
>
>
On Sun, Jan 27, 2013 at 01:40:40PM -0800, Hugh Dickins wrote:
> On Sun, 27 Jan 2013, Shaohua Li wrote:
> > On Sat, Jan 26, 2013 at 06:16:05PM -0800, Hugh Dickins wrote:
> > > On Fri, 25 Jan 2013, Shaohua Li wrote:
> > > > On Thu, Jan 24, 2013 at 10:45:57PM -0500, Sasha Levin wrote:
> > > >
> > >
Hi Jens,
Please consider to forward this fix for 3.8 to Linus.
The following changes since commit 949db153b6466c6f7cad5a427ecea94985927311:
Linux 3.8-rc5 (2013-01-25 11:57:28 -0800)
are available in the git repository at:
git://git.drbd.org/linux-drbd.git for-jens-3.8-fix
for you to
Hi Jens,
this is our contribution to the next merge-window:
With this release we have three important improvements to the activity log:
1 Starting with 8.4.3 the activity log has a variable size on disk
(before it was fixed 32KiByte).
-> The limitation of 6433 on the al-extents
On 30 Jan 2013, at 06:12, Greg Kroah-Hartman wrote:
> It doesn't apply cleanly to the linux-next tree, can you refresh this
> and resend it so that I can apply it? If you want it backported to the
> stable kernel releases, we can only do that after it gets into Linus's
> tree, see the file,
This change fixes a deadlock when the multiplexer is closed while there
are still client side ports open.
When the multiplexer is closed and there are active tty's it tries to
close them with tty_vhangup. This has a problem though, because
tty_vhangup needs the tty_lock. This patch changes it to
some of anatop's regulators(vppcpu, vddpu and vddsoc) have
register settings about LDO's step time, which will impact
the LDO ramp up speed, need to use set_voltage_time_sel
interface to add necessary delay everytime LDOs' voltage
is increased.
offset 0x170:
bit [24-25]: vddcpu
bit [26-27]: vddpu
Hello.
Where can i find an info about /proc/irq/*/affinity_hint ?
Documentation/filesystems/proc.txt says nothing about it (3.2.37 kernel).
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More
On Wed, Jan 30, 2013 at 5:08 AM, Kukjin Kim wrote:
> Sachin Kamat wrote:
>>
>> >> This patch is required along with the
>> >> patch "gpio: samsung: fix pinctrl condition for exynos and exynos5440"
>> >> (mainline commit Id: e4a5da51) which has already made it into
>> >> mainline. Without the
On Wed, 30 Jan 2013, Tang Chen wrote:
> The failure I'm trying to fix is that if all the memory is hotpluggable, and
> user
> specified movablemem_map, my code will set all the memory as ZONE_MOVABLE, and
> kernel
> will fail to allocate any memory, and it will fail to boot.
>
I'm curious, do
This fixes a build failure introduced by commit ac07b1f ("swap: add per-
partition lock for swapfile") which changed the access pattern of the
nr_swap_pages variable but failed to update the no-MMU case.
Signed-off-by: Thierry Reding
---
mm/nommu.c | 2 +-
1 file changed, 1 insertion(+), 1
29.01.2013 19:33, Don Zickus пишет:
The softlockup mechanism works scheduling a high priority task that kicks
the softlockups. If the unzip thread is taking too long, it could
accidentally trip the detection.
Inyerestingly, that a decompress of lzma -4 takes longer time than
decompress lzma
Arnd, Olof,
Here are two little DT fixes that will fix the use of
USART3 on at91sam9x5 platforms.
The following changes since commit 949db153b6466c6f7cad5a427ecea94985927311:
Linux 3.8-rc5 (2013-01-25 11:57:28 -0800)
are available in the git repository at:
some of anatop's regulators(vppcpu, vddpu and vddsoc) have
register settings about LDO's step time, which will impact
the LDO ramp up speed, need to use set_voltage_time_sel
interface to add necessary delay everytime LDOs' voltage
is increased.
offset 0x170:
bit [24-25]: vddcpu
bit [26-27]: vddpu
On Mon, Jan 28, 2013 at 03:00:58PM +0100, Florian Vaussard wrote:
> Calls to PWM drivers connected through I2C can sleep.
> Use the new can_sleep property.
>
> Acked-by: Peter Ujfalusi
> Signed-off-by: Florian Vaussard
> ---
> drivers/pwm/pwm-twl-led.c |1 +
> drivers/pwm/pwm-twl.c |
Hi,
On Jan 30, 2013, at 11:03 AM, Mugunthan V N wrote:
> On 1/30/2013 2:06 PM, Pantelis Antoniou wrote:
>> Hi Mugunthan,
>>
>> On Jan 29, 2013, at 1:45 PM, Mugunthan V N wrote:
>>
>>> On 1/28/2013 6:41 PM, Pantelis Antoniou wrote:
Fix interrupt storm on bone A4 cause by non-by-the-book
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
bdev_get_queue() needs to check for a valid bd_disk pointer,
otherwise it'll dereference a NULL pointer.
Signed-off-by: Hannes Reinecke
diff --git a/include/linux/blkdev.h b/include/linux/blkdev.h
index f94bc83..7e28aaa 100644
--- a/include/linux/blkdev.h
+++ b/include/linux/blkdev.h
@@ -794,7
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.
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
---
drivers/scsi/scsi_pm.c | 79
On Wednesday 30 January 2013, Matt Porter wrote:
> + dma_cap_set(DMA_SLAVE, edma_filter_info.dma_cap);
> + of_dma_controller_register(dev->of_node,
> + of_dma_simple_xlate,
> +
On Tue, Jan 29, 2013 at 10:12:45AM +0100, Ingo Molnar wrote:
>
> * Yuanhan Liu wrote:
>
> > On Tue, Jan 29, 2013 at 09:44:00AM +0100, Ingo Molnar wrote:
> > >
> > > * Yuanhan Liu wrote:
> > >
> > > > [...]
> > >
> > > Very nice measurements and analysis, thanks!
> > >
> > > > As stated
On Mon, Jan 28, 2013 at 03:00:59PM +0100, Florian Vaussard wrote:
> Call to led_pwm_set() can happen inside atomic context, like triggers.
> If the PWM call can sleep, defer using a worker.
>
> Cc: Peter Ujfalusi
> Signed-off-by: Florian Vaussard
> ---
> drivers/leds/leds-pwm.c | 50
On Wednesday 30 January 2013, Matt Porter wrote:
> Adds a dma_request_slave_channel_compat() wrapper which accepts
> both the arguments from dma_request_channel() and
> dma_request_slave_channel(). Based on whether the driver is
> instantiated via DT, the appropriate channel request call will be
>
Whenever a request has been aborted internally by the driver
there is no sense data to be had. And printing lots of messages
stalls the system, so better to print out a short one-liner.
Signed-off-by: Hannes Reinecke
---
drivers/s390/block/dasd_erp.c |8
1 files changed, 8
The DASD driver is using FASTFAIL as an equivalent to the
transport errors in SCSI. And the 'steal lock' function maps
roughly to a reservation error. So we should be returning the
appropriate error codes when completing a request.
Cc: Jens Axboe
Signed-off-by: Hannes Reinecke
---
rq_timed_out_fn might have been unset while the request
was in flight, so we need to check for it in blk_rq_timed_out().
Cc: Jens Axboe
Signed-off-by: Hannes Reinecke
---
block/blk-timeout.c |5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/block/blk-timeout.c
Instead of having the number of retries hard-coded in the various
functions we should be using a default retry value, which can
be modified via sysfs.
Signed-off-by: Hannes Reinecke
---
drivers/s390/block/dasd_devmap.c | 41 ++
This patch implements generic block layer timeout handling
callbacks for DASDs. When the timeout expires the respective
cqr is aborted.
With this timeout handler time-critical request abort
is guaranteed as the abort does not depend on the internal
state of the various DASD driver queues.
This patch adds a 'timeout' attibute to the DASD driver.
When set to non-zero, the blk_timeout function will
be enabled with the timeout specified in the attribute.
Setting 'timeout' to '0' will disable block timeouts.
Signed-off-by: Hannes Reinecke
---
drivers/s390/block/dasd.c|2 +
This patch series implements a block timeout handler for
DASDs. The main impetus was to allow for a fixed upper
timeout value after which a request is aborted.
This is required eg when implementing a host-based
mirroring system where otherwise the entire mirror
would stall under certain
Whenever a DASD request encounters a timeout we might
need to abort all outstanding requests on this or
even other devices.
This is especially useful if one wants to fail all
devices on one side of a RAID10 configuration, even
though only one device exhibited an error.
To handle this I've
dasd_cancel_req will never return 1, only 0.
Signed-off-by: Hannes Reinecke
---
drivers/s390/block/dasd.c |4 +---
1 files changed, 1 insertions(+), 3 deletions(-)
diff --git a/drivers/s390/block/dasd.c b/drivers/s390/block/dasd.c
index 29225e1..09ddf70 100644
---
Originally the DASD device tasklet would process the entries on
the ccw_queue until the first non-final request was found.
Which was okay as long as all requests have the same retries and
expires parameter.
However, as we're now allowing to modify both it is possible to
have requests _after_ the
On Wednesday 30 January 2013, Matt Porter wrote:
> +Optional properties:
> +- dmas: List of DMA controller phandle and DMA request ordered
> + pairs. One tx and one rx pair is required for each chip
> + select.
The binding looks ok, but the wording is slightly incorrect here:
strictly
2013/1/30 Bjørn Mork :
> Daniele Palmas writes:
>
>> The output of lsusb for interface #1 is the following:
>>
>> Interface Descriptor:
>> bLength 9
>> bDescriptorType 4
>> bInterfaceNumber1
>> bAlternateSetting 0
>>
On Thu, Jan 24, 2013 at 04:20:39PM +, Tiana Rakotovao Andriamahefa wrote:
> Le jeudi 24 janvier 2013 à 11:36:31, Michal Marek a écrit :
> > On 16.1.2013 13:26, Tiana Rakotovao Andriamahefa wrote:
> > > I have checked it and found that the error was effectively fixed in the
> > > last
> > >
Hello Viresh,
On Wed, Jan 30, 2013 at 12:33:40PM +0530, Viresh Kumar wrote:
> I am starting to follow cpufreq patches religiously now and so have to come
> back to this old thread due to some crash we got :)
>
> Its still not pushed upstream, so better to get it resolved before 3.9.
Definitely,
Hi Florian, all -
First, thanks for your work on adding the bugzilla comments when patches
referencing bugs get merged. I find it useful.
Recently however there was a comment about a commit referencing a commit
referencing the bug report. Turns out the comment was missing one level
of
We(Linux Kernel Performance project) found a regression introduced by
commit 5a50508, which just convert all mutex lock to rwsem write lock.
The semantics is same, but the results is quite huge in some cases.
After investigation, we found the root cause: mutex support lock
stealing. Here is the
On Wed, 2013-01-30 at 14:18 +0530, Santosh Shilimkar wrote:
> On Wednesday 30 January 2013 02:13 PM, Kumar, Anil wrote:
> > Hi Sourav,
> >
> > On Wed, Jan 30, 2013 at 12:10:18, Poddar, Sourav wrote:
> >> Hi Luciano,
> >> On Wednesday 30 January 2013 11:55 AM, Luciano Coelho wrote:
> >>> Hi Sourav,
On 01/30/2013 04:50 PM, David Rientjes wrote:
On Wed, 30 Jan 2013, Tang Chen wrote:
When using movablemem_map=acpi, always set node0 as unhotpluggable, otherwise
if all the memory is hotpluggable, the kernel will fail to boot.
When using movablemem_map=nn[KMG]@ss[KMG], we don't stop users
On 1/30/2013 2:06 PM, Pantelis Antoniou wrote:
Hi Mugunthan,
On Jan 29, 2013, at 1:45 PM, Mugunthan V N wrote:
On 1/28/2013 6:41 PM, Pantelis Antoniou wrote:
Fix interrupt storm on bone A4 cause by non-by-the-book interrupt handling.
While at it, added a non-NAPI mode (which is easier to
> > I tried to get my snowball board working on the latest kernel, but it
> > locks up hard very early on boot up.
> >
> > I bisected it down to this commit:
> >
> > commit ebc96db7632f987e0b9bffcb782cf5cfb8afb0dd
> > Author: Ulf Hansson
> > Date: Mon Aug 27 15:45:53 2012 +0200
> >
> > ARM:
>>> On 30.01.13 at 01:51, "K. Y. Srinivasan" wrote:
> --- a/arch/x86/kernel/cpu/mshyperv.c
> +++ b/arch/x86/kernel/cpu/mshyperv.c
> @@ -14,10 +14,15 @@
> #include
> #include
> #include
> +#include
> +#include
> #include
> #include
> #include
> #include
> +#include
> +#include
>
On Tue, Jan 29, 2013 at 04:47:13PM -0700, Bjorn Helgaas wrote:
> On Tue, Jan 29, 2013 at 4:44 PM, Bjorn Helgaas wrote:
> > A bus_type has a list of devices (klist_devices), but the list and the
> > subsys_private structure that contains it are not initialized until the
> > bus_type is registered
>>> On 30.01.13 at 01:51, "K. Y. Srinivasan" wrote:
> Xen emulates Hyper-V to host enlightened Windows. Looks like this
> emulation may be turned on by default even for Linux guests. Check and
> fail Hyper-V detection if we are on Xen.
>
> Signed-off-by: K. Y. Srinivasan
> ---
>
On Tue, Jan 29, 2013 at 2:00 AM, Andi Kleen wrote:
>
> On Tue, Jan 29, 2013 at 01:30:19AM +0100, Stephane Eranian wrote:
> > >> The counter is reinstated to its state before the critical section but
> > >> the PMI cannot be
> > >> cancelled and there is no state left behind to tell what to do
On Wed, 30 Jan 2013, Tang Chen wrote:
> When using movablemem_map=acpi, always set node0 as unhotpluggable, otherwise
> if all the memory is hotpluggable, the kernel will fail to boot.
>
> When using movablemem_map=nn[KMG]@ss[KMG], we don't stop users specifying
> node0 as hotpluggable, and
Hi Rafael,
After merging the pm tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
drivers/built-in.o: In function `ipc_init':
pl320-ipc.c:(.init.text+0xf96b): undefined reference to `amba_driver_register'
Caused by commit 970066f5b269 ("ARM / highbank: add support for pl320
On Wednesday 30 January 2013 02:13 PM, Kumar, Anil wrote:
Hi Sourav,
On Wed, Jan 30, 2013 at 12:10:18, Poddar, Sourav wrote:
Hi Luciano,
On Wednesday 30 January 2013 11:55 AM, Luciano Coelho wrote:
Hi Sourav,
On Mon, 2013-01-28 at 16:47 +0530, Sourav Poddar wrote:
Booting 3.8-rc4 om omap
Hi Sourav,
On Wed, Jan 30, 2013 at 12:10:18, Poddar, Sourav wrote:
> Hi Luciano,
> On Wednesday 30 January 2013 11:55 AM, Luciano Coelho wrote:
> > Hi Sourav,
> >
> > On Mon, 2013-01-28 at 16:47 +0530, Sourav Poddar wrote:
> >> Booting 3.8-rc4 om omap 4430sdp results in the following error
> >>
>
On Fri, Jan 25, 2013 at 4:54 PM, Dmitry Kasatkin
wrote:
> From: YOSHIFUJI Hideaki
>
> digsig_verify_rsa() does not free kmalloc'ed buffer returned by
> mpi_get_buffer().
>
> Signed-off-by: YOSHIFUJI Hideaki
> Signed-off-by: Dmitry Kasatkin
> Cc: sta...@vger.kernel.org
> ---
> lib/digsig.c |
On Wed, Jan 30, 2013 at 05:23:01PM +0900, Alex Courbot wrote:
> On 01/30/2013 04:40 PM, Thierry Reding wrote:
> >Thanks *a lot* for taking care of this Alexandre! From a quick look at
> >the patches they seem generally fine. I'll go over them in a bit more
> >detail though.
>
> Glad you like it
Hi Mugunthan,
On Jan 29, 2013, at 1:45 PM, Mugunthan V N wrote:
> On 1/28/2013 6:41 PM, Pantelis Antoniou wrote:
>> Fix interrupt storm on bone A4 cause by non-by-the-book interrupt handling.
>> While at it, added a non-NAPI mode (which is easier to debug), plus
>> some general fixes.
>>
>>
Hi Rafael,
Today's linux-next merge of the pm tree got a conflict in
drivers/acpi/internal.h between commit 668192b67820 ("PCI: acpiphp: Move
host bridge hotplug to pci_root.c") from the pci tree and commit
2c545601d933 ("ACPI / PCI: Make PCI root driver use struct
acpi_scan_handler") from the pm
Hi Peter,
On Jan 28, 2013, at 11:14 PM, Peter Korsgaard wrote:
>> "Pantelis" == Pantelis Antoniou writes:
>
> 'among other things' is not a very descriptive commit message.
>
> Pantelis> Fix interrupt storm on bone A4 cause by non-by-the-book
> Pantelis> interrupt handling. While at it,
On Thu, Jan 17, 2013 at 8:04 PM, David Howells wrote:
> Add KEY_FLAG_TRUSTED to indicate that a key either comes from a trusted source
> or had a cryptographic signature chain that led back to a trusted key the
> kernel already possessed.
>
> Add KEY_FLAGS_TRUSTED_ONLY to indicate that a keyring
On Wed, 2013-01-30 at 09:21 +0100, walter harms wrote:
> Am 29.01.2013 19:03, schrieb Joe Perches:
> > On Tue, 2013-01-29 at 18:49 +0100, Julia Lawall wrote:
> >> How about the following (from today's linux-next). They appear to be
> >> trying to do the same calculation, once with + and once with
On 01/30/2013 04:48 PM, Thierry Reding wrote:
I already said this in another thread. I think we should only be using
the CDF .get_modes() for static modes that cannot be obtained from EDID.
Thinking about it, I'm not quite sure why EDID would be needed for this
kind of panel anyway. Ventana
Daniele Palmas writes:
> The output of lsusb for interface #1 is the following:
>
> Interface Descriptor:
> bLength 9
> bDescriptorType 4
> bInterfaceNumber1
> bAlternateSetting 0
> bNumEndpoints 2
>
On 01/30/2013 04:40 PM, Thierry Reding wrote:
Thanks *a lot* for taking care of this Alexandre! From a quick look at
the patches they seem generally fine. I'll go over them in a bit more
detail though.
Glad you like it better than my previous attempts at controlling Tegra's
panels and
Hi Greg,
On Tue, Jan 29, 2013 at 11:20:06PM -0500, Greg Kroah-Hartman wrote:
> On Mon, Jan 28, 2013 at 09:38:23AM +0900, Minchan Kim wrote:
> > Now zram allocates new page with GFP_KERNEL in zram I/O path
> > if IO is partial. Unfortunately, It may cuase deadlock with
> > reclaim path so this
Am 29.01.2013 19:03, schrieb Joe Perches:
> On Tue, 2013-01-29 at 18:49 +0100, Julia Lawall wrote:
>> How about the following (from today's linux-next). They appear to be
>> trying to do the same calculation, once with + and once with |.
>
> (cc'ing the original developer and Russell King)
>
On Tue, Jan 29, 2013 at 10:01:52PM -0800, Kukjin Kim wrote:
> Vivek Gautam wrote:
> >
> > Adding PHY driver support for USB 3.0 controller for Samsung's
> > SoCs.
> >
> > Signed-off-by: Vivek Gautam
> > ---
> >
> > Changes from v3:
> > - Making SAMSUNG_USB3PHY dependent on SAMSUNG_USBPHY.
> >
Hi Kukjin,
On Wed, Jan 30, 2013 at 10:36 AM, Kukjin Kim wrote:
> Vivek Gautam wrote:
>>
>> 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
For some reason they didn't get replaced so far by their paravirt
equivalents, resulting in code to be run with interrupts disabled that
doesn't expect so (causing, in the observed case, a BUG_ON() to
trigger) when syscall auditing is enabled.
David (Cc-ed) came up with an identical fix, so
On Mon, Jan 28, 2013 at 03:00:57PM +0100, Florian Vaussard wrote:
> Calls to some external PWM chips can sleep. To help users,
> add pwm_can_sleep() API.
>
> Cc: Thierry Reding
> Cc: Peter Ujfalusi
> Signed-off-by: Florian Vaussard
> ---
> drivers/pwm/core.c | 12
>
On Wed, 2013-01-30 at 08:07 +, Saurav Kashyap wrote:
> I am submitting some correction patches today and this patch will be part
> of the scsi-misc submission after that set.
Thanks.
Paul Bolle
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
On Fri, Jan 25, 2013 at 11:36:53AM +, James Hogan wrote:
> Hi,
>
> On 14/01/13 10:54, James Hogan wrote:
> > Here's a new version addressing Jiri's feedback.
> >
> > Add a TTY driver for communicating over a Meta DA (Debug Adapter)
> > channel using the bios channel SWITCH operation.
> >
>
On Tue, Jan 29, 2013 at 09:49:52AM +0100, Dirkjan Bussink wrote:
> This change fixes a deadlock when the multiplexer is closed while there
> are still client side ports open.
>
> When the multiplexer is closed and there are active tty's it tries to
> close them with tty_vhangup. This has a
On Thu, Jan 10, 2013 at 04:40:19PM -0700, Toshi Kani wrote:
> +/*
> + * Hot-plug device information
> + */
Again, stop it with the "generic" hotplug term here, and everywhere
else. You are doing a very _specific_ type of hotplug devices, so spell
it out. We've worked hard to hotplug
On Thu, Jan 10, 2013 at 04:40:21PM -0700, Toshi Kani wrote:
> Added sys_hotplug.c, which is the system device hotplug framework code.
>
> shp_register_handler() allows modules to register their hotplug handlers
> to the framework. shp_submit_req() provides the interface to submit
> a hotplug or
On Thu, Jan 10, 2013 at 04:40:19PM -0700, Toshi Kani wrote:
> Added include/linux/sys_hotplug.h, which defines the system device
> hotplug framework interfaces used by the framework itself and
> handlers.
>
> The order values define the calling sequence of handlers. For add
> execute, the
On Mon, Jan 14, 2013 at 12:21:30PM -0700, Toshi Kani wrote:
> On Mon, 2013-01-14 at 20:07 +0100, Rafael J. Wysocki wrote:
> > On Monday, January 14, 2013 11:42:09 AM Toshi Kani wrote:
> > > On Mon, 2013-01-14 at 19:47 +0100, Rafael J. Wysocki wrote:
> > > > On Monday, January 14, 2013 08:53:53 AM
On Mon, Jan 14, 2013 at 12:02:04PM -0700, Toshi Kani wrote:
> On Mon, 2013-01-14 at 19:48 +0100, Rafael J. Wysocki wrote:
> > On Monday, January 14, 2013 08:33:48 AM Toshi Kani wrote:
> > > On Fri, 2013-01-11 at 22:23 +0100, Rafael J. Wysocki wrote:
> > > > On Thursday, January 10, 2013 04:40:19
On Tue, Jan 29, 2013 at 02:17:26AM +0400, Ilya Zykov wrote:
> On 24.01.2013 2:36, Karthik Manamcheri wrote:
> > When the tty input buffer is full and thereby throttled,
> > flushing/resetting the read buffer should unthrottle to allow more
> > data to be received.
> >
> > Signed-off-by: Karthik
On Mon, Jan 28, 2013 at 10:34:44PM -0500, Peter Hurley wrote:
> The unthrottle may restart the writer before the rx push
> has a chance to start emptying the rx buffer, resulting in an
> overflowed rx buffer and lost data.
>
> Perform the actual device unthrottle with the rx push instead.
>
>
On 01/30/2013 03:48 PM, Thierry Reding wrote:
> * PGP Signed by an unknown key
>
> On Wed, Jan 30, 2013 at 04:27:11PM +0900, Alex Courbot wrote:
>> On 01/30/2013 04:20 PM, Mark Zhang wrote:
> [...]
+static int panel_claa101_get_modes(struct display_entity *entity,
+
On Wed, 2013-01-30 at 13:31 +0530, Viresh Kumar wrote:
> On Wed, Jan 30, 2013 at 1:02 PM, Andy Shevchenko
> wrote:
> > We get a device from the ACPI CSRT table. During enumeration we don't
> > know what kind of the device it is. From the enumeration point of view
> > each device enumerated from
>On Mon, 2012-10-08 at 11:15 -0500, Saurav Kashyap wrote:
>> Acked-by: Saurav Kashyap
>>
>> Thanks,
>> ~Saurav
>>
>> >Compiling qla_gs.o (part of the qla2xxx module) triggers two GCC
>> >warnings:
>> >drivers/scsi/qla2xxx/qla_gs.c: In function Œqla2x00_fdmi_rhba¹:
>> >
On Sat, Jan 26, 2013 at 05:06:31PM -0500, Jake Champlin wrote:
> Fixed multiple coding style issues
>
> Signed-off-by: Jake Champlin
> ---
> drivers/staging/csr/csr_msgconv.c | 392
> --
> 1 file changed, 169 insertions(+), 223 deletions(-)
Please break
On Mon, Jan 28, 2013 at 09:38:23AM +0900, Minchan Kim wrote:
> Now zram allocates new page with GFP_KERNEL in zram I/O path
> if IO is partial. Unfortunately, It may cuase deadlock with
> reclaim path so this patch solves the problem.
>
> Cc: sta...@vger.kernel.org
> Cc: Jerome Marchand
>
On Mon, Jan 28, 2013 at 12:47:40PM +0900, Minchan Kim wrote:
> Hi Seth,
>
> On Fri, Jan 25, 2013 at 11:46:14AM -0600, Seth Jennings wrote:
> > These patches are the first 4 patches of the zswap patchset I
> > sent out previously. Some recent commits to zsmalloc and
> > zcache in staging-next
On Fri, Jan 25, 2013 at 11:46:16AM -0600, Seth Jennings wrote:
> zs_create_pool() currently takes a name argument which is
> never used in any useful way.
>
> This patch removes it.
>
> Acked-by: Nitin Gupta
> Acked-by: Minchan Kim
> Signed-off-by: Seth Jennnings
> Acked-by: Dan Magenheimer
On Wed, Jan 30, 2013 at 1:02 PM, Andy Shevchenko
wrote:
> We get a device from the ACPI CSRT table. During enumeration we don't
> know what kind of the device it is. From the enumeration point of view
> each device enumerated from CSRT is a platform device (see
> drivers/acpi/csrt.c for the
On Fri, Jan 25, 2013 at 01:54:08PM -0500, Jake Champlin wrote:
> Fixed Bracing Issue flagged by checkpatch.pl
>
> Signed-off-by: Jake Champlin
> ---
> drivers/staging/comedi/drivers/amplc_dio200.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git
On Fri, Jan 25, 2013 at 01:54:08PM -0500, Jake Champlin wrote:
Fixed Bracing Issue flagged by checkpatch.pl
Signed-off-by: Jake Champlin jake.champlin...@gmail.com
---
drivers/staging/comedi/drivers/amplc_dio200.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git
On Wed, Jan 30, 2013 at 1:02 PM, Andy Shevchenko
andriy.shevche...@linux.intel.com wrote:
We get a device from the ACPI CSRT table. During enumeration we don't
know what kind of the device it is. From the enumeration point of view
each device enumerated from CSRT is a platform device (see
On Fri, Jan 25, 2013 at 11:46:16AM -0600, Seth Jennings wrote:
zs_create_pool() currently takes a name argument which is
never used in any useful way.
This patch removes it.
Acked-by: Nitin Gupta ngu...@vflare.org
Acked-by: Minchan Kim minc...@kernel.org
Signed-off-by: Seth Jennnings
On Mon, Jan 28, 2013 at 12:47:40PM +0900, Minchan Kim wrote:
Hi Seth,
On Fri, Jan 25, 2013 at 11:46:14AM -0600, Seth Jennings wrote:
These patches are the first 4 patches of the zswap patchset I
sent out previously. Some recent commits to zsmalloc and
zcache in staging-next forced a
On Mon, Jan 28, 2013 at 09:38:23AM +0900, Minchan Kim wrote:
Now zram allocates new page with GFP_KERNEL in zram I/O path
if IO is partial. Unfortunately, It may cuase deadlock with
reclaim path so this patch solves the problem.
Cc: sta...@vger.kernel.org
Cc: Jerome Marchand
On Sat, Jan 26, 2013 at 05:06:31PM -0500, Jake Champlin wrote:
Fixed multiple coding style issues
Signed-off-by: Jake Champlin jake.champlin...@gmail.com
---
drivers/staging/csr/csr_msgconv.c | 392
--
1 file changed, 169 insertions(+), 223
On Mon, 2012-10-08 at 11:15 -0500, Saurav Kashyap wrote:
Acked-by: Saurav Kashyap saurav.kash...@qlogic.com
Thanks,
~Saurav
Compiling qla_gs.o (part of the qla2xxx module) triggers two GCC
warnings:
drivers/scsi/qla2xxx/qla_gs.c: In function Œqla2x00_fdmi_rhba¹:
On Wed, 2013-01-30 at 13:31 +0530, Viresh Kumar wrote:
On Wed, Jan 30, 2013 at 1:02 PM, Andy Shevchenko
andriy.shevche...@linux.intel.com wrote:
We get a device from the ACPI CSRT table. During enumeration we don't
know what kind of the device it is. From the enumeration point of view
On Mon, Jan 28, 2013 at 10:34:44PM -0500, Peter Hurley wrote:
The unthrottle may restart the writer before the rx push
has a chance to start emptying the rx buffer, resulting in an
overflowed rx buffer and lost data.
Perform the actual device unthrottle with the rx push instead.
501 - 600 of 1182 matches
Mail list logo
