On Sun, Nov 4, 2012 at 11:51 PM, Greg Kroah-Hartman
wrote:
> On Sat, Nov 03, 2012 at 11:17:57PM -0700, Colin Cross wrote:
>> On Mon, Oct 29, 2012 at 2:40 PM, Greg Kroah-Hartman
>> wrote:
>> > 3.4-stable review patch. If anyone has any objections, please let me know.
>> >
>> > --
On Sat, Nov 03, 2012 at 11:17:57PM -0700, Colin Cross wrote:
> On Mon, Oct 29, 2012 at 2:40 PM, Greg Kroah-Hartman
> wrote:
> > 3.4-stable review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > From: Heiko Stuebner
> >
> > commit 308b3afb97dc342e9c4f95
On Mon, Nov 5, 2012 at 3:41 PM, Greg Kroah-Hartman
wrote:
> On Mon, Nov 05, 2012 at 03:37:31PM +0800, Zhi Yong Wu wrote:
>> HI, greg
>>
>> Some of the patchset haven't passed the check of checkpatch.pl as below:
>>
>> WARNING: line over 80 characters
>> #85: FILE: drivers/block/floppy.c:4319:
>> +
On Mon, Nov 05, 2012 at 03:37:31PM +0800, Zhi Yong Wu wrote:
> HI, greg
>
> Some of the patchset haven't passed the check of checkpatch.pl as below:
>
> WARNING: line over 80 characters
> #85: FILE: drivers/block/floppy.c:4319:
> + device_remove_file(&floppy_device[drive].dev,
This is not a good thing to assume. A vendor could have an external button,
gor example.
ebied...@xmission.com wrote:
>"H. Peter Anvin" writes:
>
>> On 11/05/2012 07:14 AM, Eric W. Biederman wrote:
>>>
>>> In any case the notion that unattended install with no user
>interaction
>>> on any uef
HI, greg
Some of the patchset haven't passed the check of checkpatch.pl as below:
WARNING: line over 80 characters
#85: FILE: drivers/block/floppy.c:4319:
+ device_remove_file(&floppy_device[drive].dev,
&dev_attr_cmos);
WARNING: line over 80 characters
#419: FILE: drivers/
On Wed, Oct 31, 2012 at 05:57:27PM +0200, Pantelis Antoniou wrote:
[...]
> diff --git a/drivers/video/backlight/pwm_bl.c
> b/drivers/video/backlight/pwm_bl.c
[...]
> @@ -20,6 +20,8 @@
> #include
> #include
> #include
> +#include
> +#include
linux/err.h is already included earlier.
Thierr
Hi Linus, thanks for the reply!
On Monday 05 November 2012 02:04:33 Linus Walleij wrote:
> On Wed, Oct 31, 2012 at 10:04 AM, Alex Courbot wrote:
> > Would anyone be opposed to having a gpio_get() function that works
> > similarly to e.g. regulator_get() and clk_get()?
>
> I understand the concep
"H. Peter Anvin" writes:
> On 11/05/2012 07:14 AM, Eric W. Biederman wrote:
>>
>> In any case the notion that unattended install with no user interaction
>> on any uefi machine in any state is complete and total rubbish. It
>> can't be done. You need power and you need boot media.
>>
>
> That
On Thu, Oct 18, 2012 at 18:56:39, Porter, Matt wrote:
...snip...
...snip...
...snip...
>
> This series adds DMA Engine support for AM33xx, which uses
> an EDMA DMAC. The EDMA DMAC has been previously supported by only
> a private API implementation (much like the situation with OMAP
> DMA) found
On 11/05/2012 07:14 AM, Eric W. Biederman wrote:
>
> In any case the notion that unattended install with no user interaction
> on any uefi machine in any state is complete and total rubbish. It
> can't be done. You need power and you need boot media.
>
That is a hugely different thing from nee
On Wed, Oct 31, 2012 at 05:57:10PM +0200, Pantelis Antoniou wrote:
> No need to hide of_pwm_request, it's useful to other in-kernel users.
Can you specify which users that might be? I'm reluctant to export
symbols which aren't used by any drivers.
> diff --git a/drivers/pwm/core.c b/drivers/pwm/c
Hi, Stephen,
On Mon, 2012-11-05 at 11:46 +1100, Stephen Rothwell wrote:
> Hi Zhang,
>
> Today's linux-next merge of the thermal tree got a conflict in
> drivers/thermal/rcar_thermal.c between commit 608f62b996c6 ("thermal:
> solve compilation errors in rcar_thermal") from Linus' tree and commit
>
First, `dev' is dereferenced in dev_to_node(dev), suggesting that it
must be non-null. Later `dev' is checked against NULL, suggesting
the opposite. This patch adds a NULL check before its use.
Signed-off-by: Xi Wang
---
mm/dmapool.c |5 -
1 file changed, 4 insertions(+), 1 deletion(-)
From: Doug Goldstein
Date: Mon, 5 Nov 2012 00:19:19 -0600
> By this argument we shouldn't ever improve any API or add new syscalls
> since we'll have to have fallback code to handle the old interfaces
> when the new ones aren't available.
It makes sense to add new APIs when existing mechanisms a
Jiri Kosina writes:
> On Fri, 2 Nov 2012, Vivek Goyal wrote:
>
>> > With secure boot enabled, then the kernel should refuse to let an
>> > unsigned kexec load new images, and kexec itself should refuse to
>> > load unsigned images.
>>
>> Yep, good in theory. Now that basically means reimplementi
I think no need to make 'happened' static as we just check 'ud->event'
feild. Maybe making this function inline would make more sense.
inline int usbip_event_happened(struct usbip_device *ud)
{
return ud->event ? 1 : 0;
}
Thanks
Harvey
On Mon, Nov 5, 2012 at 1:34 PM, Prashant Shah wrot
Hello Tanino-san,
On Wed, 31 Oct 2012 23:05:01 +0900
Mitsuhiro Tanino wrote:
> This patch introduces a function which excludes hwpoison pages
> from vmcore as a default action for makedumpfile.
>
> Signed-off-by: Mitsuhiro Tanino
Thank you for your work. I think it's good feature.
I will mer
On Sun, Nov 4, 2012 at 11:53 PM, David Miller wrote:
> From: Doug Goldstein
> Date: Sun, 4 Nov 2012 23:45:56 -0600
>
>> As Ben Greear pointed out this would allow shell scripts and other
>> scripting languages to better detect vlans. Kay pointed out that this
>> would allow better uevent filters
The dereference rport->data should come after the NULL check of rport.
Signed-off-by: Xi Wang
---
drivers/scsi/bnx2fc/bnx2fc_io.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/scsi/bnx2fc/bnx2fc_io.c b/drivers/scsi/bnx2fc/bnx2fc_io.c
index 8d4626c..eebe93c 1006
Matthew Garrett writes:
> On Sun, Nov 04, 2012 at 09:14:47AM +, James Bottomley wrote:
>
>> I've actually had more than enough experience with automated installs
>> over my career: they're either done by paying someone or using a
>> provisioning system. In either case, they provision a stati
As the Northbridge IDs are at most 16-bits, use the same type
consistently and cleanup some indexes to use smaller types.
v2: Drop unneeded changes and changes Boris will cleanup later
Signed-off-by: Daniel J Blueman
---
arch/x86/include/asm/amd_nb.h|2 +-
arch/x86/include/asm/processor
As the AMD64 last-level-cache ID is 16-bits and federated systems
eg using Numascale's NumaConnect/NumaChip can have more than 255 memory
controllers, use 16-bits to store the ID.
v2: Avoid change to intlv_en variable
v3: Drop unneeded change to index
Signed-off-by: Daniel J Blueman
---
drivers
Fix the handling of memory controller detection to index the array
of detected Northbridges, allowing memory controllers over multiple
PCI domains in federated systems eg using Numascale's NumaConnect/
NumaChip.
v4: Generate linear Northbridge ID by indexing detected Northbridges
v5: Reorder funct
Hi,
Although the ARM-based Zeus (XScale PXA270) Single board computer works
well for 3.2.x series kernels, it fails to boot from series 3.3.x. It
attempts to boot but stops at:
"Uncompressing Linux... done, booting the kernel".
This problem is also exhibited in kernel series 3.4.x, 3.5.x, 3.6.x.
Hi Henrik,
> > This patch converts to MT-B because Synaptics touch devices are
> > capable of tracking identifiable fingers
> >
> > This patch was tested on pandaboard, except input_mt_sync_frame(),
> > which is a quite new function.
>
> I am not sure how to interpret this. Is the patch untested,
From: Ajay Kumar Gupta
Device tree node for usbss on AM33XX. There are two musb
controllers on am33xx platform so have port0-mode and
port1-mode data.
[af...@ti.com: reg & interrupt property addition]
Signed-off-by: Ajay Kumar Gupta
Signed-off-by: Santhapuri, Damodar
Signed-off-by: Ravi Babu
From: Doug Goldstein
Date: Sun, 4 Nov 2012 23:45:56 -0600
> As Ben Greear pointed out this would allow shell scripts and other
> scripting languages to better detect vlans. Kay pointed out that this
> would allow better uevent filters in the future as well. So there are
> some merits to this patc
Hi all,
Changes since 20121102:
The v4l-dvb tree still had its build failure so I used the version from
next-20121026.
The thermal tree gained a conflict against Linus' tree.
The modules tree lost its build failure.
The usb tree lost its build failures.
The signal tree gained a conflict again
Fixed some coding style issues.
Signed-off-by: Kumar Amit Mehta
---
.../ethernet/qlogic/netxen/netxen_nic_ethtool.c| 86 ++--
1 file changed, 43 insertions(+), 43 deletions(-)
diff --git a/drivers/net/ethernet/qlogic/netxen/netxen_nic_ethtool.c
b/drivers/net/ethernet/qlog
On Tue, Oct 23, 2012 at 1:36 AM, David Miller wrote:
> From: Doug Goldstein
> Date: Mon, 22 Oct 2012 00:53:57 -0500
>
>> Sets the sysfs device_type to 'vlan' for udev. This makes it easier for
>> applications that query network information via udev to identify vlans
>> instead of using strrchr().
On 2012/11/1 3:44, Tejun Heo wrote:
> All ->pre_destory() implementations return 0 now, which is the only
> allowed return value. Make it return void.
>
> Signed-off-by: Tejun Heo
> Cc: Michal Hocko
> Cc: Balbir Singh
> Cc: KAMEZAWA Hiroyuki
> Cc: Vivek Goyal
Acked-by: Li Zefan
--
To unsu
On 2012/11/1 3:44, Tejun Heo wrote:
> CGRP_WAIT_ON_RMDIR is another kludge which was added to make cgroup
> destruction rollback somewhat working. cgroup_rmdir() used to drain
> CSS references and CGRP_WAIT_ON_RMDIR and the associated waitqueue and
> helpers were used to allow the task performing
On 2012/11/1 3:44, Tejun Heo wrote:
> Because ->pre_destroy() could fail and can't be called under
> cgroup_mutex, cgroup destruction did something very ugly.
>
> 1. Grab cgroup_mutex and verify it can be destroyed; fail otherwise.
>
> 2. Release cgroup_mutex and call ->pre_destroy().
>
>
On 2012/11/1 3:44, Tejun Heo wrote:
> This patch makes cgroup_create() fail if @parent is marked removed.
> This is to prepare for further updates to cgroup_rmdir() path.
>
> Note that this change isn't strictly necessary. cgroup can only be
> created via mkdir and the removed marking and dentry
On 2012/11/1 3:44, Tejun Heo wrote:
> 2ef37d3fe4 ("memcg: Simplify mem_cgroup_force_empty_list error
> handling") removed the last user of __DEPRECATED_clear_css_refs. This
> patch removes __DEPRECATED_clear_css_refs and mechanisms to support
> it.
>
> * Conditionals dependent on __DEPRECATED_cle
Hi,
> int happened = 0;
>
> - spin_lock(&ud->lock);
> if (ud->event != 0)
> happened = 1;
> - spin_unlock(&ud->lock);
>
> return happened;
I am guessing locking was intended to protect ud->event along with
happened so that (checking the value of
On 2012/11/1 3:44, Tejun Heo wrote:
> CSS_REMOVED is one of the several contortions which were necessary to
> support css reference draining on cgroup removal. All css->refcnts
> which need draining should be deactivated and verified to equal zero
> atomically w.r.t. css_tryget(). If any one isn'
checkpatch.pl throws error message for the current code. This patch fixes
this coding style issue.
Signed-off-by: Kumar Amit Mehta
---
drivers/net/ethernet/qlogic/qlge/qlge_dbg.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/drivers/net/ethernet/qlogic/ql
On Mon, Nov 05, 2012 at 12:50:26PM +0800, Harvey Yang wrote:
> From: harvey.yang
>
>
> Signed-off-by: harvey.yang
> ---
> drivers/staging/usbip/usbip_event.c |2 --
> 1 files changed, 0 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/staging/usbip/usbip_event.c
> b/drivers/staging
Hi Andrew,
Today's linux-next merge of the akpm tree got a conflict in
drivers/acpi/acpi_memhotplug.c between commits 85fcb3758c10 ("ACPI /
memory-hotplug: introduce a mutex lock to protect the list in
acpi_memory_device") and d0fbb400b6f3 ("ACPI / memory-hotplug: add memory
offline code to acpi_m
From: harvey.yang
Signed-off-by: harvey.yang
---
drivers/staging/usbip/usbip_event.c |2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/usbip/usbip_event.c
b/drivers/staging/usbip/usbip_event.c
index d332a34..668f8e0 100644
--- a/drivers/staging/usbip/us
On Sun, Nov 4, 2012 at 8:14 PM, Bob Liu wrote:
> Hmm, I attached a simple fix patch.
Reviewed-by: Michel Lespinasse
(also ran some tests with it, but I could never reproduce the original
issue anyway).
Bob, it would be easier if you had sent the original patch inline
rather than as an attachmen
On Mon, Nov 5, 2012 at 11:31 AM, Michel Lespinasse wrote:
> On Sun, Nov 4, 2012 at 6:20 PM, Bob Liu wrote:
>> The loop for each entry of vma->anon_vma_chain in validate_mm() is not
>> protected by anon_vma lock.
>> I think that may be the cause.
>>
>> Michel, What's your opinion？
>
> Good catch,
Hi Al,
Today's linux-next merge of the signal tree got a conflict in
arch/arm/kernel/process.c between commit 77a3018e38b9 ("Cortex-M3: Add
support for exception handling") from the cortex tree and commit
9e6479930021 ("arm: switch to generic fork/vfork/clone") from the signal
tree.
I fixed it up
On 2012年11月05日 09:54, Shawn Guo wrote:
On Fri, Nov 02, 2012 at 08:37:41PM +0800, yongd wrote:
I got it. So how do you think of such below partition/reorganization?
It looks fine to me for imx.
Ok. I will update like this way if we have no other issues. Thanks.
Patch-1:
For sdhci-esdhc-im
On Sun, Nov 4, 2012 at 6:20 PM, Bob Liu wrote:
> The loop for each entry of vma->anon_vma_chain in validate_mm() is not
> protected by anon_vma lock.
> I think that may be the cause.
>
> Michel, What's your opinion？
Good catch, I think that's it. Somehow it had not occured to me to
verify the che
Josh Boyer writes:
> diff --git a/Makefile b/Makefile
> index 14c93b3..7e27d51 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -722,8 +722,14 @@ export mod_strip_cmd
> ifeq ($(CONFIG_MODULE_SIG),y)
> MODSECKEY = ./signing_key.priv
> MODPUBKEY = ./signing_key.x509
> +ifeq ($(KBUILD_EXTMOD),)
> +SI
Lee Jones writes:
> drivers/virtio/virtio_mmio.c: In function ‘vm_cmdline_set’:
> drivers/virtio/virtio_mmio.c:535:4: warning: format ‘%u’ expects argument of
> type ‘unsigned int *’, but argument 4 has type ‘resource_size_t *’ [-Wformat]
>
> Cc: Rusty Russell
> Cc: virtualizat...@lists.linux-fo
Josh Boyer writes:
> On Fri, Nov 02, 2012 at 01:49:14PM +1030, Rusty Russell wrote:
>> My comment was more that this relies on eu-strip, because we always
>> sign modules on installation, so you need eu-strip to *unsign* them
>> (strip won't do it, BTW).
>
> Really? Which version of binutils are
Jan Beulich writes:
> This makes the resulting diagnostics quite a bit more useful.
>
> Signed-off-by: Jan Beulich
Nice. I'm a bit disappointed we can't just treat _Static_assert() as
void, like:
#define BUILD_BUG_ON_ZERO(e) (_Static_assert(!(e), "!(" #e ")"), 0)
> @@ -54,6 +61,15 @@ struct p
On 10/27/2012 05:52 AM, Matt Helsley wrote:
> On Thu, Oct 25, 2012 at 12:23:24PM +0200, Michael Kerrisk (man-pages) wrote:
>> Hi Pat,
>>
>>
I suppose that I have a concern that goes in the other direction. Is
there not some other solution possible that doesn't require the use of
EPOL
On 11/05/2012 03:57 AM, Zhang, Jun wrote:
> Hello, Anvin
> 1) use "memmap=exactmap", which remove all ranges include ram and non-ram
> range. So my first patch reserve the non-ram range.
> 2)don't use " memmap=exactmap ", so it reserve all ranges. But we only need
> non-ram, so we need kernel to
Hello, Anvin
1) use "memmap=exactmap", which remove all ranges include ram and non-ram
range. So my first patch reserve the non-ram range.
2)don't use " memmap=exactmap ", so it reserve all ranges. But we only need
non-ram, so we need kernel to remove RAM, just as my second patch.
Best Regards!
On Sun, Nov 4, 2012 at 11:16 AM, Julia Lawall wrote:
> I didn't change any cases where the if test contains a function call. The
> current definitions of WARN_ON seem to always evaluate the condition
> expression, but I was worried that that might not always be the case. And
> calling a function
On 11/05/2012 02:37 AM, Zhang, Jun wrote:
> Hello, Gortmaker
> I will modify my subject. Thanks!
>
> Hello, Anvin
> from our three options, I think third option is better. But in 3) option,
> there are two choose, 3.1) is like memmap=REMOVERAM, 3.2) is
> memmap=CRASHKDUMP.
> In 3.1) we maybe nee
On Sat, Nov 3, 2012 at 5:27 AM, Mingming.cao wrote:
> On Fri, 2012-11-02 at 14:38 +0800, Zhi Yong Wu wrote:
>> Here also has another question.
>>
>> How to save the file temperature among the umount to be able to
>> preserve the file tempreture after reboot?
>>
>> This above is the requirement fro
Hi Geert,
On 2012/11/04 22:20, Geert Uytterhoeven wrote:
> On Tue, Sep 25, 2012 at 8:09 AM, Damian Hobson-Garcia
> wrote:
>> are holding the device file open, the address returned to userspace is
>> DMA_ERROR_CODE.
>
> Only a small subset of the architectures
> (arm/ia64/microblaze/openrisc/powe
On Sat, Nov 3, 2012 at 4:10 AM, Darrick J. Wong wrote:
> On Fri, Nov 02, 2012 at 04:41:09PM +0800, Zheng Liu wrote:
>> On Fri, Nov 02, 2012 at 02:38:29PM +0800, Zhi Yong Wu wrote:
>> > Here also has another question.
>> >
>> > How to save the file temperature among the umount to be able to
>> > pr
On Fri, Nov 02, 2012 at 03:29:50PM +0100, Stanislav Meduna wrote:
> On 31.10.2012 22:41, Stanislav Meduna wrote:
>
> > on an embedded platform using a Freescale i.MX28 ARM processor
> > I am experiencing a strange phenomenon - the latencies reported
> > are dependent of HZ
>
> OK, the problem is
On Fri, Nov 2, 2012 at 4:41 PM, Zheng Liu wrote:
> On Fri, Nov 02, 2012 at 02:38:29PM +0800, Zhi Yong Wu wrote:
>> Here also has another question.
>>
>> How to save the file temperature among the umount to be able to
>> preserve the file tempreture after reboot?
>>
>> This above is the requirement
On Sat, Nov 3, 2012 at 11:51 AM, Sasha Levin wrote:
> Ping?
>
> On Thu, Oct 25, 2012 at 4:26 PM, Sasha Levin wrote:
>> On 10/18/2012 06:46 PM, Sasha Levin wrote:
>>> Hi all,
>>>
>>> While fuzzing with trinity inside a KVM tools (lkvm) guest, on today's
>>> linux-next kernel,
>>> I saw the follow
On Mon, 5 Nov 2012, Huang Ying wrote:
> In current runtime PM implementation, the active child count of the
> parent device may be decreased if the runtime PM of the child device
> is disabled and forbidden. For example, to unbind a PCI driver with a
> PCI device, the following code path is possi
Hello, Gortmaker
I will modify my subject. Thanks!
Hello, Anvin
from our three options, I think third option is better. But in 3) option, there
are two choose, 3.1) is like memmap=REMOVERAM, 3.2) is memmap=CRASHKDUMP.
In 3.1) we maybe need ifdef/endif within the { } of the function (like
exactma
On Fri, Nov 02, 2012 at 08:37:41PM +0800, yongd wrote:
> I got it. So how do you think of such below partition/reorganization?
>
It looks fine to me for imx.
> Patch-1:
> For sdhci-esdhc-imx.c, only add MMC_CAP_NEEDS_POLL for ESDHC_CD_NONE. With
> that
> improper logic of sdhci_add_host(), this
On Mon, 2012-11-05 at 11:46 +1100, Stephen Rothwell wrote:
> Hi Zhang,
>
> Today's linux-next merge of the thermal tree got a conflict in
> drivers/thermal/rcar_thermal.c between commit 608f62b996c6 ("thermal:
> solve compilation errors in rcar_thermal") from Linus' tree and commit
> ebbf0f11e7b4
In current runtime PM implementation, the active child count of the
parent device may be decreased if the runtime PM of the child device
is disabled and forbidden. For example, to unbind a PCI driver with a
PCI device, the following code path is possible:
pci_device_remove
pm_runtime_set_su
On Fri, Nov 02, 2012 at 10:48:21AM -0600, Shuah Khan wrote:
> On Fri, 2012-10-26 at 09:43 -0600, Shuah Khan wrote:
> > Add support for debug_dma_mapping_error() call to avoid warning from
> > debug_dma_unmap() interface when it checks for mapping error checked
> > status. Without this patch, device
Jason Wang writes:
> +struct virtnet_info {
> + u16 num_queue_pairs;/* # of RX/TX vq pairs */
> + u16 total_queue_pairs;
> +
> + struct send_queue *sq;
> + struct receive_queue *rq;
> + struct virtqueue *cvq;
> +
> + struct virtio_device *vdev;
> + struct ne
On Fri, Nov 2, 2012 at 4:07 PM, Jason Kridner wrote:
>> Take a look at arch/x86/platform/mrst/mrst.c. It's a specific example of
>> a platform which parses tables and attaches devices to the right physical
>> bus in a manner they can be reliably probed even when the device has no
>> sane autodetec
Hi Zhang,
Today's linux-next merge of the thermal tree got a conflict in
drivers/thermal/rcar_thermal.c between commit 608f62b996c6 ("thermal:
solve compilation errors in rcar_thermal") from Linus' tree and commit
ebbf0f11e7b4 ("Thermal: Pass zone parameters as argument to
tzd_register") from the
On Fri, Nov 2, 2012 at 12:32 PM, Pantelis Antoniou
wrote:
> The i2c2 alias cannot be resolved at compile time; there has to be
>
> a) A DT object format where unresolved aliases (symbols) are tracked
> b) A runtime DT linker that will resolve the alias, and will insert the
>i2c2-devices child
Hi Mauro,
On Mon, 29 Oct 2012 11:14:03 +1100 Stephen Rothwell
wrote:
>
> After merging the v4l-dvb tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/hid/hid-picolcd_cir.c: In function 'picolcd_init_cir':
> drivers/hid/hid-picolcd_cir.c:119:27: error: 'RC_TYPE_
On Fri, Nov 2, 2012 at 10:19 AM, Koen Kooi wrote:
> button@1 {
> debounce_interval = <50>;
> linux,code = <105>;
> label = "left";
> gpios = <&gpi
On So, 04 Nov 2012, Dave Airlie wrote:
> Yeah thats fine, bisecting works by going to where commits were
> originally committed, so drm-intel-next was 3.6.0-rc2 at some point
> was only merged into Linus later.
Ok, thanks, didn't know that. Have started the bisect game now,
coming back in about 1
On Fri, Nov 2, 2012 at 8:43 AM, Pantelis Antoniou
wrote:
> Assuming that we do work on a DT object format, and that the runtime
> resolution mechanism is approved,
> then I agree that this part of the capebus patches can be dropped and the
> functionality assumed by generic
> DT core.
>
> The qu
On 04/11/12 04:45, Luca Clementi wrote:
> On Fri, Nov 2, 2012 at 11:29 AM, Greg Kroah-Hartman
> wrote:
>> On Thu, Nov 01, 2012 at 11:15:52PM -0700, Luca Clementi wrote:
>>> + vfree(current_log->buffer);
>>> + kfree(current_log->misc.name);
>>> + kfree(current
On 02/11/12 17:15, Luca Clementi wrote:
> Created the module_exit for the android logger so that
> it can be loaded and unloaded as a module. Fixed
> module_init and some other minor issues.
>
> Signed-off-by: Luca Clementi
> Cc: Greg Kroah-Hartman
> Cc: Brian Swetland
> ---
> drivers/staging/
Jason Wang writes:
> This patch implement the {set|get}_channels method of ethool to allow user to
> change the number of queues dymaically when the device is running. This would
> let the user to tune the device for specific applications.
...
> + /* Only two modes were support currently */
>
Jason Wang writes:
> This addes multiqueue support to virtio_net driver. There's two mode
> supported:
> single queue pair mode and multiple queue pairs mode. An obvious
> difference compared with a physical mq card is that virtio-net reserve
> first two virtqueues when it is working in multiqueu
Sjur Brændeland writes:
> From: Sjur Brændeland
>
> This patch-set introduces a new virtio type "rproc_serial" for communicating
> with remote processors over shared memory. The driver depends on the
> the remoteproc framework. As preparation for introducing "rproc_serial"
> I've done a refactor
On 11/03/2012 08:04 PM, David Miller :
> From: Nicolas Ferre
> Date: Tue, 30 Oct 2012 12:30:28 +0100
>
>> Due to the use of common structure in at91_ether and macb drivers,
>> change the name of DMA descriptor structures in at91_ether as well:
>> dma_desc => macb_dma_desc
>>
>> Signed-off-by: Nic
On 11/04/2012 10:06 PM, Geert Uytterhoeven wrote:
> On Fri, Oct 19, 2012 at 1:28 PM, Jiri Slaby wrote:
>> + if ((quirks & MS_RDESC_3K) && *rsize == 106 &&
>> + !memcmp((char []){ 0x19, 0x00, 0x29, 0xff },
>> + &rdesc[94], 4)) {
>
> Which v
Add generic ESS vendor ID to pm_whitelist. This should fix suspend on
all Maestro-2 and Maestro-2E based PCI cards.
Tested on Terratec DMX and SF64-PCE2.
Signed-off-by: Ondrej Zary
--- a/sound/pci/es1968.c
+++ b/sound/pci/es1968.c
@@ -2655,6 +2655,8 @@ static struct ess_device_list pm_whitelist[
Namit Gupta wrote:
> API simple_strtol() and simple_strtoul() are giving incorrect result for
> string "-".
> These API's consider "-" as a '-' (negative integer) and return incorrect
> string pointer.
> The API returns pointer next to '-' character. However it should return
> starting pointer of
Hi Alexandra,
Thanks for making changes.
> This patch converts to MT-B because Synaptics touch devices are
> capable of tracking identifiable fingers
>
> This patch was tested on pandaboard, except input_mt_sync_frame(),
> which is a quite new function.
I am not sure how to interpret this. Is t
On Mon, Nov 5, 2012 at 2:59 AM, Luming Yu wrote:
>
> This patch is the first step to test some basic hardware functions like
> TSC to help people understand if there is any hardware latency as well
> as throughput problem exposed on bare metal or left behind by BIOS or
> interfered by SMI. Current
Hey,
Op 05-11-12 02:59, Luming Yu schreef:
> This patch is the first step to test some basic hardware functions like
> TSC to help people understand if there is any hardware latency as well
> as throughput problem exposed on bare metal or left behind by BIOS or
> interfered by SMI. Currently the p
On Fri, Oct 19, 2012 at 1:28 PM, Jiri Slaby wrote:
> + if ((quirks & MS_RDESC_3K) && *rsize == 106 &&
> + !memcmp((char []){ 0x19, 0x00, 0x29, 0xff },
> + &rdesc[94], 4)) {
Which version of gcc are you using?
I'm getting (m68k-linux-gnu-g
On Sun, 4 Nov 2012, Arnd Bergmann wrote:
On Sunday 04 November 2012, Julia Lawall wrote:
Hmm, I did not think that WARN() took a KERN_ERR argument, which should
really be implied here. Looking at the code, it really seems to be required
at the moment, but only 5 out of 117 callers use it this
On Sun, 2012-11-04 at 09:47 -0800, Jonathan Nieder wrote:
> Matt Fleming wrote:
>
> > --- a/drivers/platform/x86/Kconfig
> > +++ b/drivers/platform/x86/Kconfig
> > @@ -717,7 +717,7 @@ config XO15_EBOOK
> >
> > config SAMSUNG_LAPTOP
> > tristate "Samsung Laptop driver"
> > - depends on X86
On Sunday 04 November 2012, Julia Lawall wrote:
> > Hmm, I did not think that WARN() took a KERN_ERR argument, which should
> > really be implied here. Looking at the code, it really seems to be required
> > at the moment, but only 5 out of 117 callers use it this way.
> >
> > Any idea what is goi
Hi Benjamin,
> The goal of this patch is to implement in a reliable way Win 8
> multitouch protocol (to avoid quirking many devices). Thanks to the
> precision they made in the specification, I think it is feasible:
> they add the dynamic part that were missing in Win 7 spec:
> """
> When sending
If regmap_read() failed, arizona_micdet() returns IRQ_NONE
leaving &info->lock mutex locked as opposed to all other return paths.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Alexey Khoroshilov
---
drivers/extcon/extcon-arizona.c |1 +
1 file changed, 1 inse
fixed below checkpatch warning.
- WARNING: Prefer netdev_info(netdev, ... then dev_info(dev, ... then
pr_info(... to printk(KERN_INFO ...
- WARNING: Prefer netdev_dbg(netdev, ... then dev_dbg(dev, ... then
pr_debug(... to printk(KERN_DEBUG ...
- WARNING: Prefer netdev_err(netdev, ... then dev_e
fixed below checkpatch warning.
- WARNING: Prefer netdev_info(netdev, ... then dev_info(dev, ... then
pr_info(... to printk(KERN_INFO ...
Signed-off-by: YAMANE Toshiaki
---
drivers/staging/media/go7007/go7007-driver.c |5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/
Hi Corentin,
Thanks for your feedback on this. Indeed, what Olof is saying is
correct. In its current form, this driver exists to register i2c
devices on our laptops. We have one piece of information (the irq,
specifically) that cannot be added to the i2c_board_info when using
user space probing.
It looks like these patches were not a good idea, because in each case the
printk provides an error level, and WARN then provides another one.
Sorry for the noise.
julia
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.
Nobody knows? This is really obscure for an EDF patch. Making things a bit
more accessible should be a priority. I think a lot of enthusiasts would
like to have smooth control over stuff, without windows-jitter. If you can
do a robot arm, jitter-free with this, then I am very interested.
uw
On Sun, 4 Nov 2012, Arnd Bergmann wrote:
On Saturday 03 November 2012, Julia Lawall wrote:
@@ -113,10 +113,6 @@
printk(KERN_INFO a); \
touch_nmi_watchdog(); \
} while (0)
-#define eprintk(a...) do { \
- printk(KERN_ERR a); \
-
1 - 100 of 221 matches
Mail list logo
