Ping?
On Fri, Dec 21, 2012 at 1:59 PM, Sasha Levin wrote:
> Switch hugemem to use the new hashtable implementation. This reduces the
> amount of generic unrelated code in the hugemem.
>
> This also removes the dymanic allocation of the hash table. The upside is that
> we save a pointer dereferenc
All drivers which use this subdevice use also the control framework.
The v4l2_subdev_core_ops operations {query/g_/s_}ctrl are useless because
device drivers will inherit controls from this subdevice.
Signed-off-by: Federico Vaga
---
drivers/media/i2c/adv7180.c | 3 ---
1 file modificato, 3 rimo
This patch re-write the driver and use the videobuf2
interface instead of the old videobuf. Moreover, it uses also
the control framework which allows the driver to inherit
controls from its subdevice (ADV7180)
Signed-off-by: Federico Vaga
Acked-by: Giancarlo Asnaghi
---
drivers/media/pci/sta2x1
This is useful when you need to specify specific GFP flags during memory
allocation (e.g. GFP_DMA).
Signed-off-by: Federico Vaga
---
drivers/media/v4l2-core/videobuf2-dma-contig.c | 7 ++-
include/media/videobuf2-dma-contig.h | 5 +
2 file modificati, 7 inserzioni(+), 5 rimozio
On Sun, 2013-01-06 at 17:44 +0100, Willy Tarreau wrote:
> On Sun, Jan 06, 2013 at 08:39:53AM -0800, Eric Dumazet wrote:
> > Hmm, I'll have to check if this really can be reverted without hurting
> > vmsplice() again.
>
> Looking at the code I've been wondering whether we shouldn't transform
> the
> I have more information about DMA on the board that I'm using; probably, I
> can make dma-contig work with my device.
Ok, the driver STA2X11 now works with a patched dma-contig allocator. So, my
streaming allocator it is not mandatory.
I based my work on the previous work made by Windriver, b
On Sun, 2013-01-06 at 16:51 +0100, Willy Tarreau wrote:
> Hi Eric,
>
> Oh sorry, I didn't really want to pollute the list with links and configs,
> especially during the initial report with various combined issues :-(
>
> The client is my old "inject" tool, available here :
>
> http://git.
On Sun, Jan 06, 2013 at 08:39:53AM -0800, Eric Dumazet wrote:
> Hmm, I'll have to check if this really can be reverted without hurting
> vmsplice() again.
Looking at the code I've been wondering whether we shouldn't transform
the condition to perform the push if we can't push more segments, but
I
On Sat, 2013-01-05 at 09:13 +0100, Mike Galbraith wrote:
> I still have a 2.6-rt problem I need to find time to squabble with, but
> maybe I'll soonish see if what you did plus what I did combined works
> out on that 4x10 core box where current is _so_ unbelievably horrible.
> Heck, it can't get a
OK, now that sys_execve() unification has settled down, let's get back
to this one. The real problem is what you are doing with bprm->filename
and bprm->interp; blind use of ->d_name is completely wrong.
For what it's worth, how should it work for e.g. shell scripts? That's
the main user of bprm
This patch series add the channel wise pause control on dma driver and then
add support for Tegra114 SoCs.
The orginal change was in single patch and based on review comment, trying to
split
the change to have more meaningful changelog matches with actual code change.
Laxman Dewangan (2):
dma
NVIDIA's some SoCs like Tegra114 support the channel wise pause control
inplace of global pause which pauses all DMA channels. When SoCs support
the channel wise pause control then it uses the global pause for clock
gating for register access as well as all DMA channel pause. Hence DMA
registers ar
NVIDIA's Tegra114 has APB DMA controller which has 32 dma channels
and support support channel wise pause control.
Add support for Tegra114 which uses the channel wise pause control
hardware feature.
Signed-off-by: Laxman Dewangan
---
drivers/dma/tegra20-apb-dma.c | 11 +++
1 files ch
On Sun, Jan 06, 2013 at 07:55:53PM +0800, Hillf Danton wrote:
> On Sat, Jan 5, 2013 at 11:22 PM, Dave Jones wrote:
> > I have no idea what happened here, but this is the first time I've seen
> > this one.
> > This was running a tree pulled yesterday afternoon.
> >
> Would you please try th
On Sun, Jan 06 2013, Simon Jeons wrote:
>> >write(1, "1\n", 2) = 3
>> Here it tells it.
> On Sun, 2013-01-06 at 08:48 +, Liu Hui-R64343 wrote:
> Why this value trouble you?
Because write() is supposed to return the number of bytes successfully
written.
--
Best regard
On Sunday 06 January 2013 08:07 PM, Vinod Koul wrote:
On Sat, Jan 05, 2013 at 05:36:08PM +0530, Laxman Dewangan wrote:
NVIDIA's Tegra114 has APB DMA controller which supports channel wise
pause control. The global pause is used for clock gating and hence
DMA registers are not accessible if DMAs
Hi Eric,
On Sun, Jan 06, 2013 at 06:59:02AM -0800, Eric Dumazet wrote:
> On Sun, 2013-01-06 at 10:24 +0100, Willy Tarreau wrote:
>
> > It does not change anything to the tests above unfortunately. It did not
> > even stabilize the unstable runs.
> >
> > I'll check if I can spot the original comm
On Sun, Jan 06, 2013 at 07:48:49AM -0800, Guenter Roeck wrote:
> Commit b9d6ba94 (vfs: add a retry_estale helper function to handle retries
> on ESTALE) intruduced the use of ESTALE in namei.h. Since namei.h does not
> include errno.h, this results in the following build error for callers/users
> w
Commit b9d6ba94 (vfs: add a retry_estale helper function to handle retries
on ESTALE) intruduced the use of ESTALE in namei.h. Since namei.h does not
include errno.h, this results in the following build error for callers/users
which do not include errno.h directly.
include/linux/namei.h:114:19: er
On Sat, Jan 05, 2013 at 05:36:08PM +0530, Laxman Dewangan wrote:
> NVIDIA's Tegra114 has APB DMA controller which supports channel wise
> pause control. The global pause is used for clock gating and hence
> DMA registers are not accessible if DMAs are globally disabled.
>
> Add support for use of
On Sun, 2013-01-06 at 10:24 +0100, Willy Tarreau wrote:
> It does not change anything to the tests above unfortunately. It did not
> even stabilize the unstable runs.
>
> I'll check if I can spot the original commit which caused the regression
> for MTUs that are not n*4096+52.
Since you don't p
On 01/06/2013 08:21 AM, Denis Efremov wrote:
> The symbol of_fixed_clk_setup is exported and annotated __init.
> This looks like section mismatch.
> Fix this by removing the __init annotation of of_fixed_clk_setup.
>
> Signed-off-by: Denis Efremov
Mike should take this.
Acked-by: Rob Herring
The symbol of_fixed_clk_setup is exported and annotated __init.
This looks like section mismatch.
Fix this by removing the __init annotation of of_fixed_clk_setup.
Signed-off-by: Denis Efremov
---
drivers/clk/clk-fixed-rate.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a
On Sun, Jan 06, 2013 at 03:18:38PM +0800, Jason Wang wrote:
> Polling errors were ignored by vhost/vhost_net, this may lead to crash when
> trying to remove vhost from waitqueue when after the polling is failed. Solve
> this problem by:
>
> - checking the poll->wqh before trying to remove from wai
2013/1/5 Francois Romieu :
> Can you check if things improve with v3.8-rc2 after removing :
>
> 1. 9ecb9aabaf634677c77af467f4e3028b09d7bcda
>r8169: workaround for missing extended GigaMAC registers
> 2. d64ec841517a25f6d468bde9f67e5b4cffdc67c7
>r8169: enable internal ASPM and clock request
Hi Viro,
Em Sat, 15 Dec 2012 20:38:29 +
Al Viro escreveu:
> On Sat, Dec 15, 2012 at 08:12:37PM +, Al Viro wrote:
> > Walking rbtree while it's modified is a Bad Idea(tm); besides,
> > the result of find_vma() can be freed just as it's getting returned
> > to caller. Fortunately, it'
Am 05.01.2013 12:42, schrieb Alexander Holler:
The console functions are using spinlocks while calling fb-driver ops
but udlfb waits for a semaphore in many ops. This results in the BUG
"scheduling while atomic". One of those call flows is e.g.
vt_console_print() (spinlock printing_lock)
I see the following error, using the .config inline, below.
arch/m68k/mm/init.c: In function 'print_memmap':
arch/m68k/mm/init.c:139:2: error: 'KMAP_START' undeclared (first use in this
function)
arch/m68k/mm/init.c:139:2: note: each undeclared identifier is reported only
once for each function
On 2013/1/5 5:50, Bjorn Helgaas wrote:
> [+to Yijing, +cc Kenji]
>
> On Fri, Jan 4, 2013 at 1:01 PM, Bjorn Helgaas wrote:
>> On Thu, Jan 3, 2013 at 8:41 AM, Jiang Liu wrote:
>>> Hi Daniel,
>>> It seems like an issue caused by recursive PCIe HPC.
>>> Could you please help to try the patch
Mel Gorman wrote:
> Using a 3.7.1 or 3.8-rc2 kernel, can you reproduce the problem and then
> answer the following questions please?
This is on my main machine running 3.8-rc2
> 1. What are the contents of /proc/vmstat at the time it is stuck?
===> /proc/vmstat <===
nr_free_pages 40305
nr_inact
On Sun, Jan 06, 2013 at 11:25:25AM +0100, Willy Tarreau wrote:
> OK good news here, the performance drop on the myri was caused by a
> problem between the keyboard and the chair. After the reboot series,
> I forgot to reload the firmware so the driver used the less efficient
> firmware from the NIC
Hi Dave
On Sat, Jan 5, 2013 at 11:22 PM, Dave Jones wrote:
> I have no idea what happened here, but this is the first time I've seen this
> one.
> This was running a tree pulled yesterday afternoon.
>
> BUG: unable to handle kernel paging request at 880100201000
> IP: [] copy_page_rep+0x5/0x
On Sun, Jan 06, 2013 at 12:46:58PM +0100, Romain Francoise wrote:
> Willy Tarreau writes:
>
> > That makes me think that I should try 3.8-rc2 since LRO was removed
> > there :-/
>
> Better yet, find a way to automate these tests so they can run continually
> against net-next and find problems ea
On 01/03/2013 09:40 AM, Jiri Kosina wrote:
> On Sat, 15 Dec 2012, Alexander Holler wrote:
>
>> These are Usage IDs for the attributes year, month, day,
>> hour, minute and second, needed to read HID time sensors.
>>
>> Signed-off-by: Alexander Holler
>
> Signed-off-by: Jiri Kosina
Added to togr
On 01/03/2013 09:41 AM, Jiri Kosina wrote:
> On Sat, 15 Dec 2012, Alexander Holler wrote:
>
>> The stuff in hid-sensor-attributes.h is needed by every piece which
>> uses hid-sensor-hub and merging it into hid-sensor-hub.h makes it accessible
>> from outside the iio subdirectory.
>>
>> Signed-off-
On 01/04/2013 01:10 PM, Alexander Holler wrote:
> Am 04.01.2013 10:18, schrieb Jiri Kosina:
>> On Thu, 3 Jan 2013, Andrew Morton wrote:
>>
This driver makes the time from HID sensors (hubs) which are offering
such available like any other RTC does.
>
>>> Looks OK to me. It sounds like J
On 01/03/2013 09:42 AM, Jiri Kosina wrote:
> On Sat, 15 Dec 2012, Alexander Holler wrote:
>
>> The structure with common attributes for hid-sensors isn't specific
>> to the iio-subsystem, so rename it to hid_sensor_common.
>>
>> Signed-off-by: Alexander Holler
>
> Acked-by: Jiri Kosina
Added to
Willy Tarreau writes:
> That makes me think that I should try 3.8-rc2 since LRO was removed
> there :-/
Better yet, find a way to automate these tests so they can run continually
against net-next and find problems early...
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel
Hi David
Από το iPhone μου
6 Ιαν 2013, 5:58, ο/η David Gibson έγραψε:
> On Fri, Jan 04, 2013 at 09:16:08PM +0200, Pantelis Antoniou wrote:
>> After fixing the is_printable bug the test suite fails.
>> Fix it with this patch
>>
>> Signed-off-by: Pantelis Antoniou
>
> Rather than just removing
On 01/03/2013 06:28 AM, Kim, Milo wrote:
> Use 'dev' of iio device in a kernel message rather than i2c client device
> node.
>
> Signed-off-by: Milo(Woogyom) Kim
added to togreg branch of iio.git
Thanks
> ---
> drivers/iio/adc/lp8788_adc.c |2 +-
> 1 file changed, 1 insertion(+), 1 deletio
On 01/03/2013 06:28 AM, Kim, Milo wrote:
> The lp8788-adc is a platform driver of lp8788-mfd.
> The platform device is allocated when mfd_add_devices() is called
> in lp8788-mfd.
> On the other hand, 'lp->dev' is the i2c client device.
>
> Therefore, this 'platform_device' is a proper parent
Commit 85ff6acb075a484780b3d763fdf41596d8fc0970 (xen/granttable: Grant
tables V2 implementation) changed the GREFS_PER_GRANT_FRAME macro from
a constant to a conditional expression. The expression depends on
grant_table_version being appropriately set. Unfortunately, at init
time grant_table_versio
Tegra KBC driver have the default key mapping for 16x8 configuration.
The key mapping can be provided through platform data or through DT
and the mapping varies from platform to platform, hence this default
mapping is not so useful. Remove the default mapping to reduce the code
lines of the driver.
The NVIDIA's Tegra KBC has maximum 24 pins to make matrix keypad.
Any pin can be configured as row or column. The maximum column pin
can be 8 and maximum row pin can be 16.
Remove the assumption that all first 16 pins will be used as row
and remaining as columns and Add the property for configurin
Use devm_* for memory, clock, irq, input device allocation. This reduces
code for freeing these resources.
Signed-off-by: Laxman Dewangan
---
Changes from V1: None
Changes from V2:
- remove the error checks changes from original.
- return -EBUSY when reg mapping fail.
- remove unregister_input_d
This patch series:
- fix build warning,
- use devm_* for allocation,
- make column/rows configuration through DT and
- remove the rarely used key mapping table.
Changes from V1:
- renames the rows and pins property array.
- nit cleanups.
Changes from V2:
- remove the error checks changes fr
Fix the following build warning when building driver with CONFIG_PM_SLEEP
not selected.
tegra-kbc.c:360:13: warning: 'tegra_kbc_set_keypress_interrupt' defined but not
used [-Wunused-function]
Signed-off-by: Laxman Dewangan
---
Changes from V1, V2 and V3:
None
drivers/input/keyboard/t
On Sunday 06 January 2013 04:48 AM, Dmitry Torokhov wrote:
On Sat, Jan 05, 2013 at 04:50:58PM +0530, Laxman Dewangan wrote:
HI Dmitry,
Thanks for quick review.
I will take care of your comment in next version. Some have my answer.
On Saturday 05 January 2013 01:36 PM, Dmitry Torokhov wrote:
In preempt case current arch_local_irq_restore() from
preempt_schedule_irq() may enable hard interrupt but we really
should disable interrupts when we return from the interrupt,
and so that we don't get interrupted after loading SRR0/1.
Signed-off-by: Tiejun Chen
---
arch/powerpc/kernel/entry_64
Signed-off-by: Kusanagi Kouichi
---
fs/namespace.c | 17 -
1 file changed, 8 insertions(+), 9 deletions(-)
diff --git a/fs/namespace.c b/fs/namespace.c
index 55605c5..467ca80 100644
--- a/fs/namespace.c
+++ b/fs/namespace.c
@@ -71,15 +71,14 @@ static int mnt_alloc_id(struct mou
On Sun, Jan 06, 2013 at 10:24:35AM +0100, Willy Tarreau wrote:
> But before that I'll try to find the recent one causing the myri10ge to
> slow down, it should take less time to bisect.
OK good news here, the performance drop on the myri was caused by a
problem between the keyboard and the chair.
> -Original Message-
> From: Bryan Wu [mailto:coolo...@gmail.com]
> Sent: Saturday, January 05, 2013 3:46 AM
> To: Kim, Milo
> Cc: linux-l...@vger.kernel.org; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH 00/33] leds: cleanup LP5521/5523 LED driver
>
> On Thu, Dec 20, 2012 at 4:17 PM,
Hi Varun,
On Thu, Jan 03, 2013 at 05:21:09AM +, Sethi Varun-B16395 wrote:
> It's been a while since I submitted this patch. I have tried to
> address your comments regarding the subwindow attribute. I would
> really appreciate if I can get some feedback on this patch.
I have some ideas in min
On Fri, Jan 04, 2013 at 07:21:34PM +1100, Alexey Kardashevskiy wrote:
> On 16/12/12 22:20, Joerg Roedel wrote:
> >Please resend the patch when the merge-window is closed.
>
> is it closed now? not sure I entirely understand what window you
> kept in mind :)
Yes, it is closed now :-) The merge-wi
Hi Jonathan.
> The section mismatch warning can be easy to miss during the kernel build
> process. Allow it to be marked as fatal to be easily caught and prevent
> bugs from slipping in.
>
> Signed-off-by: Jonathan Kliegman
Another way to make them much more visible would be to make
the warnin
On 2013/1/4 5:44, Tejun Heo wrote:
> Hello, guys.
>
> This is the second take of "drop cpuset->stack_list and ->parent"
> patchset. Other than being rebased on top of v3.8-rc2 + "cpuset:
> decouple cpuset locking from cgroup core, take#2", nothing really has
> changed.
>
> The original patchset
On Sat, Jan 05, 2013 at 11:35:24PM -0800, Eric Dumazet wrote:
> On Sun, 2013-01-06 at 03:52 +0100, Willy Tarreau wrote:
>
> > OK so I observed no change with this patch, either on the loopback
> > data rate at >16kB MTU, or on the myri. I'm keeping it at hand for
> > experimentation anyway.
> >
>
>-Original Message-
>From: Simon Jeons [mailto:simon.je...@gmail.com]
>Sent: Sunday, January 06, 2013 5:20 PM
>To: Liu Hui-R64343
>Cc: Wanpeng Li; linux-kernel@vger.kernel.org; mgor...@suse.de;
>a...@linux-foundation.org; r...@redhat.com; minc...@kernel.org;
>kamezawa.hir...@jp.fujitsu.com;
On Sun, 2013-01-06 at 08:48 +, Liu Hui-R64343 wrote:
> >-Original Message-
> >From: Wanpeng Li [mailto:liw...@linux.vnet.ibm.com]
> >Sent: Sunday, January 06, 2013 4:46 PM
> >To: Liu Hui-R64343
> >Cc: linux-kernel@vger.kernel.org; mgor...@suse.de; akpm@linux-
> >foundation.org; r...@red
Compiling vexpress client drivers as module results in error messages such as
ERROR: "__vexpress_config_func_get" [drivers/hwmon/vexpress.ko] undefined!
ERROR: "vexpress_config_func_put" [drivers/hwmon/vexpress.ko] undefined!
This is because the global functions in drivers/mfd/vexpress-config.c a
Hi Shawn,
On Thu, Dec 20, 2012 at 06:33:11PM -0800, Shawn Nematbakhsh wrote:
> On resume from suspend there is a possibility for multi-byte scancodes
> to be handled incorrectly. atkbd_reconnect disables the processing of
> scancodes in software by calling atkbd_disable, but the keyboard may
> sti
On Fri, Jan 04, 2013 at 10:50:41PM +0900, Akinobu Mita wrote:
> 2013/1/4 Antonio Quartulli :
> > On Thu, Jan 03, 2013 at 09:19:15PM +0900, Akinobu Mita wrote:
> >> Use more preferable function name which implies using a pseudo-random
> >> number generator.
> >>
> >> Signed-off-by: Akinobu Mita
> >
>-Original Message-
>From: Wanpeng Li [mailto:liw...@linux.vnet.ibm.com]
>Sent: Sunday, January 06, 2013 4:46 PM
>To: Liu Hui-R64343
>Cc: linux-kernel@vger.kernel.org; mgor...@suse.de; akpm@linux-
>foundation.org; r...@redhat.com; minc...@kernel.org;
>kamezawa.hir...@jp.fujitsu.com; linux..
From: Julia Lawall
devm_kzalloc should not be followed by kfree, as this results in a double
free. The problem was found using the following semantic match
(http://coccinelle.lip6.fr/):
//
@@
expression x,e;
@@
x = devm_kzalloc(...)
... when != x = e
?-kfree(x,...);
//
Furthermore, in the r
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() and pm_runtime_autosuspend().
When pick a request:
If device is resuming/suspe
On Sat, 5 Jan 2013, Anton Vorontsov wrote:
On Sat, Dec 08, 2012 at 06:16:35PM +0100, Julia Lawall wrote:
From: Julia Lawall
devm_request_threaded_irq requests and irq that is freed when a driver
detaches. This patch uses devm_request_threaded_irq for irqs that are
requested in the probe fu
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, return -EBUSY.
Otherwise set q->r
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 request to quiesce for the device.
[aaron...@intel.com: Do
In August 2010, Jens and Alan discussed about "Runtime PM and the block
layer". http://marc.info/?t=12825910841&r=1&w=2
And then Alan has given a detailed implementation guide:
http://marc.info/?l=linux-scsi&m=133727953625963&w=2
To test:
# ls -l /sys/block/sda
/sys/devices/pci:00/:00:
From: Lin Ming
Add a flag REQ_PM to identify the request is PM related.
As an example, modify scsi code to use this flag.
Signed-off-by: Lin Ming
Signed-off-by: Aaron Lu
---
drivers/scsi/scsi_lib.c| 9 -
drivers/scsi/sd.c | 9 +
include/linux/blk_types.h | 2 +
> +static void schedule_cpuset_propagate_hotplug(struct cpuset *cs)
> +{
> + /*
> + * Pin @cs. The refcnt will be released when the work item
> + * finishes executing.
> + */
> + if (!css_tryget(&cs->css))
> + return;
> +
> + /*
> + * Queue @cs->empty_cp
On 2013/1/4 5:35, Tejun Heo wrote:
> Hello, guys.
>
> This is the second attempt at decoupling cpuset locking from cgroup
> core. Changes from the last take[L] are
>
> * cpuset-drop-async_rebuild_sched_domains.patch moved from 0007 to
> 0009. This reordering makes cpu hotplug handling async f
>-Original Message-
>From: Wanpeng Li [mailto:liw...@linux.vnet.ibm.com]
>Sent: Sunday, January 06, 2013 4:00 PM
>To: Liu Hui-R64343
>Cc: linux-kernel@vger.kernel.org; mgor...@suse.de; akpm@linux-
>foundation.org; r...@redhat.com; minc...@kernel.org;
>kamezawa.hir...@jp.fujitsu.com; linux..
201 - 273 of 273 matches
Mail list logo