From: Henrik Rydberg
Sent: Thursday, October 04, 2012 2:01 AM
> It seems this driver is already present in staging. Comments and
> formatting have been improved in the staging version, but that aside,
> the two versions look very similar. Why don't you submit fixes to
> that driver instead?
> On
Anthony Liguori writes:
> Rusty Russell writes:
>
>> "Michael S. Tsirkin" writes:
>>
>> There's a reason I haven't done this. I really, really dislike "my
>> implemention isn't broken" feature bits. We could have an infinite
>> number of them, for each bug in each device.
>>
>> So my plan
Kees Cook writes:
> On Thu, Sep 20, 2012 at 3:14 PM, Kees Cook wrote:
>> As part of the effort to create a stronger boundary between root and
>> kernel, Chrome OS wants to be able to enforce that kernel modules are
>> being loaded only from our read-only crypto-hash verified (dm_verity)
>> root
From: Namhyung Kim
Currently tracepoint events cannot be completed because they contain a
colon (:) character. The colon is considered as a word separator when
bash completion is done - variable COMP_WORDBREAKS contains colon - so
if a word being completed contains a colon it can be a problem.
Hi Alex,
Looks to be a preempt issue with the iommu pools code. I did find a
couple more bugs along the way too.
Anton
--
There are a number of issues in the recent IOMMU pools code:
- On a preempt kernel we might switch CPUs in the middle of building
a scatter gather list. When this
Hi Al,
Today's linux-next merge of the signal tree got conflicts in
arch/avr32/include/asm/Kbuild, arch/cris/include/asm/Kbuild,
arch/frv/include/asm/Kbuild, arch/h8300/include/asm/Kbuild,
arch/ia64/include/asm/Kbuild, arch/m32r/include/asm/Kbuild,
arch/microblaze/include/asm/Kbuild,
Hi Sekhar,
On Wed, Oct 3, 2012 at 4:08 PM, Sekhar Nori wrote:
> On 10/3/2012 12:05 PM, Prabhakar wrote:
>> From: Lad, Prabhakar
>>
>> while testing display on dm644x, for ED out-range signals
>> was observed. This patch fixes appropriate clock setting
>> for ED.
>
> Can you please clarify what
Remove the redundant target residency initialisation in
pseries_cpuidle_driver_init().
This is currently over-writing the residency time updated as part of the static
table, resulting in all the idle states having the same target
residency of 100us which is incorrect. This may result in the menu
Earlier without cpuidle framework on pseries, the native arch
idle routine comprised of both snooze and nap
states. smt_snooze_delay variable was used to delay
the idle process entry to deeper idle state like nap.
With the coming of cpuidle, this arch specific idle was replaced
by two different
smt_snooze_delay was designed to delay idle loop's nap entry
in the native idle code before it got ported over to use as part of
the cpuidle framework.
A -ve value assigned to smt_snooze_delay should result in
busy looping, in other words disabling the entry to nap state.
-
The following series consists of a bunch of fixes for
cpuidle back-end driver for ppc64 (pSeries) platform.
The series applies on 3.6-rc7 and has been tested on ppc64 pSeries
POWER7 system with snooze and nap states.
With these fixes, avg idle residency for nap on 50 percent idle system
Hi Laurent,
On Wed, Oct 3, 2012 at 7:43 PM, Laurent Pinchart
wrote:
> Hi Prabhakar,
>
> On Wednesday 03 October 2012 19:23:05 Prabhakar wrote:
>> From: Lad, Prabhakar
>>
>> V4L2_CID_TEST_PATTERN is now a standard control.
>> This patch replaces the user defined control for test
>> pattern to
On 22 September 2012 00:02, wrote:
Hi Morten,
I would try to review your patches in coming days. For now, Just
reporting a problem
which i encountered during routine build.
> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> index 490f1f0..8f0f3b9 100644
> --- a/kernel/sched/fair.c
>
Hi all,
Today's linux-next merge of the arm-soc tree got a conflict in
arch/x86/include/asm/Kbuild between commit 10b63956fce7 ("UAPI: Plumb the
UAPI Kbuilds into the user header installation and checking") from Linus'
tree and commit e7a570ff7dff ("asm-generic: Add default clkdev.h") from
the
Hi all,
Today's linux-next merge of the arm-soc tree got conflicts in
arch/cris/include/asm/Kbuild, arch/h8300/include/asm/Kbuild and
arch/m32r/include/asm/Kbuild between commit 786d35d45cc4 ("Make most arch
asm/module.h files use asm-generic/module.h") from the modules tree and
commit
Rusty Russell writes:
> Anthony Liguori writes:
>> Rusty Russell writes:
>>
>>> "Michael S. Tsirkin" writes:
>>>
Thinking about Sasha's patches, we can reduce ring usage
for virtio net small packets dramatically if we put
virtio net header inline with the data.
This can be
From: Fabio Estevam
Currently da9062_tsi does not probe and it fails as follows:
da9052 1-0048: Unable to determine device interrupts
Use the new da9052 irq functions and allow the driver to probe and operate
correctly.
Tested on mx53qsb board using 'evtest' tool.
Cc: Dmitry Torokhov
Cc:
> On Wed, Oct 03, 2012 at 05:54:08AM +0200, Arun MURTHY wrote:
> > > On Mon, Oct 01, 2012 at 07:30:38AM +0200, Arun MURTHY wrote:
> > > > > On Fri, Sep 28, 2012 at 01:35:01PM +0530, Arun Murthy wrote:
> > > > > > +#include
> > > > > > +#include
> > > > > > +#include
> > > > > > +#include
> > >
Anthony Liguori writes:
> Rusty Russell writes:
>
>> "Michael S. Tsirkin" writes:
>>
>>> Thinking about Sasha's patches, we can reduce ring usage
>>> for virtio net small packets dramatically if we put
>>> virtio net header inline with the data.
>>> This can be done for free in case guest net
Stephen Rothwell writes:
> [Lets also cc Rusty who committed the patch ...]
>
> On Wed, 03 Oct 2012 16:04:46 -0700 Randy Dunlap wrote:
>>
>> From: Randy Dunlap
>>
>> Fix printk format warning in x509_cert_parser.c:
>>
>> crypto/asymmetric_keys/x509_cert_parser.c: In function 'x509_note_OID':
From: Fabio Estevam
Currently da9062_tsi does not probe and it fails as follows:
da9052 1-0048: Unable to determine device interrupts
Use the new da9052 irq functions and allow the driver to probe and operate
correctly.
Tested on mx53qsb board using 'evtest' tool.
Cc: Dmitry Torokhov
Cc:
From: Fabio Estevam
Convert to the new da9052 interrupt functions, so that we can get rid of
irq_base references.
Cc: Grant Likely
Cc: Linus Walleij
Signed-off-by: Fabio Estevam
---
Build tested only.
drivers/gpio/gpio-da9052.c |6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
From: Fabio Estevam
Convert to the new da9052 interrupt functions, so that we can get rid of
irq_base references.
Cc: Anton Vorontsov
Signed-off-by: Fabio Estevam
---
Build tested only.
drivers/power/da9052-battery.c | 44 +++-
1 file changed, 25
From: Fabio Estevam
Use the new da9052 irq functions and allow the driver to probe successfully.
Cc: Dmitry Torokhov
Cc:
Signed-off-by: Fabio Estevam
---
drivers/input/misc/da9052_onkey.c | 22 +-
1 file changed, 5 insertions(+), 17 deletions(-)
diff --git
From: Fabio Estevam
Create a da9052-irq.c file so that it can handle interrupt related functions.
This is useful for allowing the da9052 drivers to use such functions
when dealing with da9052 interrupts.
Signed-off-by: Fabio Estevam
---
drivers/mfd/Makefile |1 +
From: Fabio Estevam
On a mx53qsb dt-kernel the da9052-core driver fails to probe as follows:
da9052 1-0048: DA9052 ADC IRQ failed ret=-22
The reason for the error was due to passing only the offset as the interrupt
number in request_threaded_irq() without da9052->irq_base.
The recommended
On Thu, Oct 04, 2012 at 02:32:40AM +0200, Laurent Pinchart wrote:
> Hi,
>
> The first patch in this series should fix the UVC gadget compilation errors in
> linux-next. The second patch should make sure I'll be notified next time a
> patch tries to break it :-)
>
> Both patches are based on
Hi Rusty,
Today's linux-next merge of the modules tree got a conflict in Makefile
between commit d183e6f570f3 ("UAPI: Move linux/version.h") from Linus'
tree and commit 91657140708d ("MODSIGN: Make mrproper should remove
generated files") from the modules tree.
I fixed it up (see below) and can
On Wed, Oct 3, 2012 at 6:48 PM, Yasuaki Ishimatsu
wrote:
> From: Wen Congyang
>
> The memory device has been ejected and powoffed, so we can call
> acpi_bus_remove() to remove the memory device from acpi bus.
>
> CC: Len Brown
> Reviewed-by: Yasuaki Ishimatsu
> Signed-off-by: Wen Congyang
>
On Thu, Oct 4, 2012 at 12:58 AM, Linus Torvalds
wrote:
> That said, there's clearly enough variation here that I think that for
> now I won't take the step to disable the udev part. I'll do the patch
> to support "direct filesystem firmware loading" using the udev default
> paths, and that
On Wed, 2012-10-03 at 20:32 -0400, Steven Rostedt wrote:
> On Wed, 2012-10-03 at 08:38 -0700, Joe Perches wrote:
> > On Wed, 2012-10-03 at 11:14 -0400, Steven Rostedt wrote:
> > > I first check
> > > the MAINTAINERS file. If the subsystem I'm working on exists there, I
> > > only email those that
UEFI variable filesystem need a new mount point, so this patch add
efivars kobject to efi_kobj for create a /sys/firmware/efi/efivars
folder.
Cc: Matt Fleming
Cc: Jeremy Kerr
Cc: Matthew Garrett
Cc: H. Peter Anvin
Signed-off-by: Lee, Chun-Yi
---
drivers/firmware/efivars.c | 11 +++
Hi Dave,
Today's linux-next merge of the drm tree got a conflict in
drivers/gpu/drm/nouveau (lots of files) between commit 760285e7e7ab
("UAPI: (Scripted) Convert #include "..." to #include in
drivers/gpu/") from Linus' tree and various commits from the drm tree.
There is a large reorganisation
Hi Dave,
After merging the drm tree, today's linux-next build (x86_64 allmodconfig)
produced these warnings:
drivers/gpu/drm/gma500/backlight.c:29:13: warning: 'do_gma_backlight_set'
defined but not used [-Wunused-function]
drivers/gpu/drm/nouveau/core/subdev/gpio/base.c: In function
Greetings,
Patch Description: Add product id in ftdi_sio.c struct table ( static
struct usb_device_id id_table_combined []) and include a define
statement in ftdi_sio_ids.h for RTSYSTEMS CT63 Radio Cable.
Output from dmesg regarding the hardware:
[ 5489.423407] usb 10-1: New USB device
David and Stephen,
I apologize for not taking the necessary steps to verify our patches
before submission. Ignorance is not an excuse... Anyways David thank you
for fixing the issue for us.
Jay-
-Original Message-
From: David Miller [mailto:da...@davemloft.net]
Sent: Wednesday, October
Hi Dave,
Today's linux-next merge of the drm tree got conflicts in
drivers/gpu/drm/i915/intel_dp.c and drivers/gpu/drm/i915/intel_drv.h
between commit 760285e7e7ab ("UAPI: (Scripted) Convert #include "..." to
#include in drivers/gpu/") from Linus' tree and commit 54d63ca6605d
("drm/i915: Move DP
From: Andrew Morton
Date: Tue, 2 Oct 2012 15:55:44 -0700
> I had a shot at integrating all this onto the pending stuff in linux-next.
> "mm: Add and use update_mmu_cache_pmd() in transparent huge page code."
> needed minor massaging in huge_memory.c. But as Andrea mentioned, we
> ran aground
(2012/10/04 1:00), Mark Wielaard wrote:
> On Wed, 2012-10-03 at 09:53 -0400, Steven Rostedt wrote:
>> On Wed, 2012-10-03 at 21:17 +0900, Masami Hiramatsu wrote:
>>> <1><9a58>: Abbrev Number: 86 (DW_TAG_subprogram)
>>> <9a59> DW_AT_external: 1
>>> <9a59> DW_AT_name:
On Wed, Oct 03, 2012 at 01:03:14PM -0700, Paul E. McKenney wrote:
> That has not proven sufficient for me in the past, RCU_FAST_NO_HZ
> being a case in point.
Taint the kernel at boot time? That'd be sufficient to force distros to
disable it.
--
Matthew Garrett | mj...@srcf.ucam.org
--
To
Hi Dave,
Today's linux-next merge of the drm tree got a conflict in
drivers/gpu/drm/gma500/psb_drv.h between commit 760285e7e7ab ("UAPI:
(Scripted) Convert #include "..." to #include in
drivers/gpu/") from Linus' tree and commit 4d46259f00c6 ("drm: gma500:
Kill the GEM glue layer") from the drm
Hi Frederic,
On Tue, 2 Oct 2012 17:54:10 +0200, Frederic Weisbecker wrote:
> On Wed, Oct 03, 2012 at 12:21:32AM +0900, Namhyung Kim wrote:
>> The '_get_comp_words_by_ref' function is available from the bash
>> completion v1.2 so that earlier version emits following warning:
>>
>> $ perf
> > > - Post the entire patch series to lkml for review (I'd like a cc please)
> >
> > Already happened, multiple people reviewed and tested.
>
> um, I would not consider "Looks ok to me from a quick look." and "I
> couldn't tell from the github view, but I assume you follow standard
> coding
From: Wen Congyang
The memory device has been ejected and powoffed, so we can call
acpi_bus_remove() to remove the memory device from acpi bus.
CC: Len Brown
Reviewed-by: Yasuaki Ishimatsu
Signed-off-by: Wen Congyang
---
drivers/acpi/acpi_memhotplug.c |3 ++-
1 file changed, 2
From: Stephen Rothwell
Date: Thu, 4 Oct 2012 11:06:15 +1000
> Actually, for me it is. I have a script that does the "use yesterday's
> version" for me. To fix (even a one liner) means bringing up an editor,
> commiting, creating the patch and then recommiting it (an implementation
> detail)
From: Wen Congyang
The function acpi_bus_remove() can remove a acpi device from acpi bus.
When a acpi device is removed, we need to call this function to remove
the acpi device from acpi bus. So export this function.
CC: Len Brown
Reviewed-by: Yasuaki Ishimatsu
Signed-off-by: Wen Congyang
The patch-set was divided from following thread's patch-set.
https://lkml.org/lkml/2012/9/5/201
If you want to know the reason, please read following thread.
https://lkml.org/lkml/2012/10/2/83
The patch exports "acpi_bus_remove()" for removing a acpi device from a
acpi bus at memory hot plug.
On Wed, Oct 3, 2012 at 6:33 PM, Ming Lei wrote:
>
> Yes, the patch will make firmware cache not working, I would like to fix
> that when I return from one trip next week.
>
> BTW, firmware cache is still needed even direct loading is taken.
I agree 100%, I'd have liked to do the caching for the
Hi Len,
Today's linux-next merge of the acpi tree got a conflict in
include/acpi/acpixf.h between commit a1ce39288e6f ("UAPI: (Scripted)
Convert #include "..." to #include in kernel system headers")
from Linus' tree and commit be030a576854 ("ACPICA: Add support for
complex _PLD buffers") from
This patch add platform data for MUIC device to initialize register
on probe() call because it should unmask interrupt mask register
and initialize some register related to MUIC device.
Signed-off-by: Chanwoo Choi
Signed-off-by: Myungjoo Ham
Signed-off-by: Kyungmin Park
---
Rusty Russell writes:
> "Michael S. Tsirkin" writes:
>
> There's a reason I haven't done this. I really, really dislike "my
> implemention isn't broken" feature bits. We could have an infinite
> number of them, for each bug in each device.
>
> So my plan was to tie this assumption to the new
On 10/03/2012 12:59 AM, Axel Lin wrote:
> This simplifies the code.
>
> Signed-off-by: Axel Lin
> ---
> drivers/extcon/extcon-max77693.c | 18 ++
> 1 file changed, 6 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/extcon/extcon-max77693.c
>
On 10/03/2012 12:30 AM, Axel Lin wrote:
> Signed-off-by: Axel Lin
> ---
> drivers/extcon/extcon-class.c |4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/extcon/extcon-class.c b/drivers/extcon/extcon-class.c
> index 946a318..337bbb4 100644
> ---
On 10/03/2012 11:23 AM, Axel Lin wrote:
> Fix below issues:
> 1. If request_threaded_irq() fails, current code does not free all requested
>irqs.
> 2. Add missing extcon_dev_unregister() in error path if failed to read
> revision
>number.
>
> Signed-off-by: Axel Lin
> ---
>
ACPI: Preparing to enter system sleep state S3
PM: Saving platform NVS memory
Disabling non-boot CPUs ...
numa_remove_cpu cpu 1 node 0: mask now 0
Broke affinity for irq 46
smpboot: CPU 1 is now offline
BUG: sleeping function called from invalid context at kernel/mutex.c:269
in_atomic(): 0,
Rusty Russell writes:
> "Michael S. Tsirkin" writes:
>
>> Thinking about Sasha's patches, we can reduce ring usage
>> for virtio net small packets dramatically if we put
>> virtio net header inline with the data.
>> This can be done for free in case guest net stack allocated
>> extra head room
"Michael S. Tsirkin" writes:
> Capacity math on ring full is wrong: we are
> looking at num_sg but that might be optimistic
> because of indirect buffer use.
>
> The implementation also penalizes fast path
> with extra memory accesses for the benefit of
> ring full condition handling which is
David Howells writes:
> Rusty Russell wrote:
>
>> Right. I think we need to use different names for generated vs supplied
>> files
>
> The problem with supplied files is people who do allyesconfig, allmodconfig
> and randconfig just to test things finding that their builds break. The
> kernel
Paolo Bonzini writes:
> Il 03/10/2012 08:44, Rusty Russell ha scritto:
>> There's a reason I haven't done this. I really, really dislike "my
>> implemention isn't broken" feature bits. We could have an infinite
>> number of them, for each bug in each device.
>
> However, this bug affects
On Monday, October 01, 2012 3:35 PM Thierry Reding wrote
>
> Make sure the duty-cycle and period passed in are not negative. This
> should eventually be made implicit by making them unsigned. While at
> it, the drivers' .config() implementations can have the equivalent
> checks removed.
>
>
Hi David,
On Wed, 03 Oct 2012 20:50:53 -0400 (EDT) David Miller
wrote:
>
> I do have a question though, it is honestly really that much easier to
> revert a whole days worth of changes (and therefore not get the code
> tested at all) than to simply add the obvious one liner?
Actually, for me
On Tue, Oct 02, 2012 at 07:41:10PM -0700, Kent Overstreet wrote:
> On Wed, Oct 03, 2012 at 11:28:25AM +1000, Dave Chinner wrote:
> > On Tue, Oct 02, 2012 at 05:20:29PM -0700, Kent Overstreet wrote:
> > > On Tue, Oct 02, 2012 at 01:41:17PM -0400, Jeff Moyer wrote:
> > > > Kent Overstreet writes:
>
On Tue, Oct 02, 2012 at 10:46:22PM -0500, Mike Christie wrote:
> On 10/02/2012 07:43 PM, Jonathan McDowell wrote:
> > Upgraded to 3.6 today on my dev box and after seeing an FC attached SAN
> > go down and come back up (due to an expected reboot) I started getting
> > the following in my logs. It
On 3 Oct 2012, Al Viro spake thusly:
> Looks sane. TBH, I'd still prefer to see udev forcibly taken over and put
> into
> usr/udev in kernel tree - I don't trust that crowd at all and the fewer
> critical userland bits they can play leverage games with, the safer we are.
>
> Al, that -><-
On Wed, Oct 3, 2012 at 7:46 AM, Daniel Santos wrote:
> On 10/03/2012 09:01 AM, Steven Rostedt wrote:
>> You don't need to use get_maintainers. It's more of a help tool to find
>> maintainers and not something that is mandatory. Not everyone that has
>> ever touched one of these files needs to be
On 10/03/2012 07:32 PM, Steven Rostedt wrote:
> On Wed, 2012-10-03 at 08:38 -0700, Joe Perches wrote:
>> On Wed, 2012-10-03 at 11:14 -0400, Steven Rostedt wrote:
>>> I first check
>>> the MAINTAINERS file. If the subsystem I'm working on exists there, I
>>> only email those that are listed there,
a cast [enabled by default]
>
> Caused by commit 8c357ebd5693 ("cxgb4: Dynamically allocate memory in
> t4_memory_rw() and get_vpd_params()"). Missing include of
> linux/vmalloc.h.
>
> I have used the net tree from next-20121003 for today.
Thanks, I'll fix this as is shown b
From: Ben Hutchings
Date: Wed, 3 Oct 2012 22:45:10 +0100
> I thought of it as being a peripheral feature (which most Solarflare
> hardware doesn't implement) so it made sense for SFC_PTP to be optional
> like SFC_MTD and so on. But I'm quite happy to use a select instead, if
> you want that to
Peter Senna Tschudin さんは書きました:
> From: Peter Senna Tschudin
>
> Convert a nonnegative error return code to a negative one, as returned
> elsewhere in the function.
>
> A simplified version of the semantic match that finds this problem is as
> follows: (http://coccinelle.lip6.fr/)
>
> //
> (
>
This change makes it so that we can avoid virt_to_phys overhead when using the
io_tlb_overflow_buffer. My original plan was to completely remove the value
and replace it with a constant but I had seen that there were recent patches
that stated this couldn't be done until all device drivers that
Currently swiotlb is the only consumer for swiotlb_bounce. Since that is the
case it doesn't make much sense to be exporting it so make it a static
function only.
In addition we can save a few more lines of code by making it so that it
accepts the DMA address as a physical address instead of a
This change makes it so that the sync functionality also uses physical
addresses. This helps to further reduce the use of virt_to_phys and
phys_to_virt functions.
Signed-off-by: Alexander Duyck
---
drivers/xen/swiotlb-xen.c |3 +--
include/linux/swiotlb.h |3 ++-
lib/swiotlb.c
This change makes it so that the unmap functionality also uses physical
addresses. This helps to further reduce the use of virt_to_phys and
phys_to_virt functions.
Signed-off-by: Alexander Duyck
---
drivers/xen/swiotlb-xen.c |4 ++--
include/linux/swiotlb.h |3 ++-
lib/swiotlb.c
This change makes it so that swiotlb_tbl_map_single will return a physical
address instead of a virtual address when called. The advantage to this once
again is that we are avoiding a number of virt_to_phys and phys_to_virt
translations by working with everything as a physical address.
One
This change makes it so that io_tlb_start contains a physical address instead
of a virtual address. The advantage to this is that we can avoid costly
translations between virtual and physical addresses when comparing the
io_tlb_start against DMA addresses.
Signed-off-by: Alexander Duyck
---
In the case of swiotlb we already have the start of the region and the number
of slabs that give us the region size. Instead of having to call
virt_to_phys on two pointers we can just take advantage of the fact that the
region is linear and just compute the end based on the start plus the size.
While working on 10Gb/s routing performance I found a significant amount of
time was being spent in the swiotlb DMA handler. Further digging found that a
significant amount of this was due to the fact that virtual to physical
address translation and calling the function that did it. It accounted
Hi Ralf,
Today's linux-next merge of the mips tree got a conflict in
arch/mips/include/asm/octeon/octeon-model.h between commit a1ce39288e6f
("UAPI: (Scripted) Convert #include "..." to #include in
kernel system headers") from the tree and commit 5cf02e5554a4 ("MIPS:
OCTEON: Add detection of
On Wed, 2012-10-03 at 08:38 -0700, Joe Perches wrote:
> On Wed, 2012-10-03 at 11:14 -0400, Steven Rostedt wrote:
> > I first check
> > the MAINTAINERS file. If the subsystem I'm working on exists there, I
> > only email those that are listed there, including any mailing lists that
> > are
Signed-off-by: Laurent Pinchart
---
MAINTAINERS |7 +++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index d919e3d..b118b23 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -7392,6 +7392,13 @@ S: Maintained
F:
Composite gadget support is now available as a library instead of being
built with each gadget. Composite drivers need to select
USB_LIBCOMPOSITE.
Signed-off-by: Laurent Pinchart
---
drivers/usb/gadget/Kconfig |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git
Hi,
The first patch in this series should fix the UVC gadget compilation errors in
linux-next. The second patch should make sure I'll be notified next time a
patch tries to break it :-)
Both patches are based on Linus' tree.
Laurent Pinchart (2):
usb: gadget: Make webcam gadget select
On 10/03/2012 01:26 PM, David Rientjes wrote:
> On Wed, 3 Oct 2012, Daniel Santos wrote:
>
>> Thanks. I've actually just reversed the patch order per Josh's
>> suggestion and added patch comments to it. I can squash them if you
>> guys prefer.
>>
> No need to be so fine-grained in your patches,
Hi,
> Yes. With that patch applied, things work for me again.
Thanks Alex, Nish. We can reproduce this on one of our Biminis, looking
into it now.
Anton
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More
ry_rw() and get_vpd_params()"). Missing include of
linux/vmalloc.h.
I have used the net tree from next-20121003 for today.
--
Cheers,
Stephen Rothwells...@canb.auug.org.au
pgpscLnyQrLjq.pgp
Description: PGP signature
Thanks a lot Guenter!
Thanks a lot Vivien also for the help.
Guillaume
- Mail original -
De: "Guenter Roeck"
À: "Vivien Didelot"
Cc: lm-sens...@lm-sensors.org, "Guillaume Roguez"
, "Jean Delvare" ,
linux-kernel@vger.kernel.org, "Steve Hardy"
Envoyé: Mercredi 3 Octobre 2012 19:37:58
On Wed, Oct 03, 2012 at 03:23:27PM -0700, Eric W. Biederman wrote:
> "Paul E. McKenney" writes:
>
> > On Wed, Oct 03, 2012 at 11:43:32AM -0700, Kees Cook wrote:
> >> On Wed, Oct 3, 2012 at 9:47 AM, Paul E. McKenney
> >> wrote:
> >> > On Wed, Oct 03, 2012 at 09:17:02AM -0700, Greg Kroah-Hartman
On Thu, Oct 4, 2012 at 3:48 AM, Al Viro wrote:
> On Wed, Oct 03, 2012 at 03:23:56PM -0700, Chris Zankel wrote:
>> Hi Linus,
>>
>> Please pull the changes for the Xtensa architecture for v3.7.
>>
>> Thanks,
>> -Chris
>
> BTW, could you do an xtensa counterpart of the stuff in
>
On Wed, 2012-10-03 at 07:47 -0400, Christoph Hellwig wrote:
> On Tue, Oct 02, 2012 at 01:16:44PM -0700, Nicholas A. Bellinger wrote:
> > * Optionally allow fd_buffered_io=1 to be enabled for people
> > * who want use the fs buffer cache as an WriteCache mechanism.
> > *
On Thu, Oct 04, 2012 at 12:23:41AM +0200, Matthias Schniedermeyer wrote:
> Personally i would have been bitten by this change, because for years i
> have used a symlink in /tmp (which has the sticky bit) to a directory
> somewhere else for historical reasons. But as i was aware of this change
>
The code in function probe_roms accesses the legacy adapter space (in
the physical address range 640k-1mb) without regard to how this range is
described in the memory map. The assumption in the code is that the
result of an access to unpopulated space is a soft fail, returning -1.
This assumption
On Wed, Oct 03, 2012 at 03:23:56PM -0700, Chris Zankel wrote:
> Hi Linus,
>
> Please pull the changes for the Xtensa architecture for v3.7.
>
> Thanks,
> -Chris
BTW, could you do an xtensa counterpart of the stuff in
Greg Kroah-Hartman writes:
> On Wed, Oct 03, 2012 at 04:03:54PM -0700, Eric W. Biederman wrote:
>>
>> Linus,
>>
>> Please pull the for-linus git tree from:
>>
>>
>> git://git.kernel.org:/pub/scm/linux/kernel/git/ebiederm/user-namespace.git
>> for-linus
>>
>>HEAD:
On Wed, Oct 03, 2012 at 04:54:08PM -0400, Vivien Didelot wrote:
> From: Guillaume Roguez
>
> The ADS7830 device is almost the same as the ADS7828,
> except that it does 8-bit sampling, instead of 12-bit.
> This patch extends the ads7828 driver to support this chip.
>
> Signed-off-by: Guillaume
On Wed, Oct 03, 2012 at 04:54:07PM -0400, Vivien Didelot wrote:
> As there is no reliable way to identify the chip, it is preferable to
> remove the detect callback, to avoid misdetection.
>
> Module parameters are not worth it here, so let's get rid of them and
> add an ads7828_platform_data
On Wed, Oct 03, 2012 at 04:33:21PM -0700, Kees Cook wrote:
> On Wed, Oct 3, 2012 at 4:29 PM, Guenter Roeck wrote:
> > On Tue, Oct 02, 2012 at 07:50:42PM -, Kees Cook wrote:
> >> This config item has not carried much meaning for a while now and is
> >> almost always enabled by default. As
On Wed, Oct 3, 2012 at 4:29 PM, Guenter Roeck wrote:
> On Tue, Oct 02, 2012 at 07:50:42PM -, Kees Cook wrote:
>> This config item has not carried much meaning for a while now and is
>> almost always enabled by default. As agreed during the Linux kernel
>> summit, it should be removed. As a
On 10/03/2012 12:30 AM, Stephen Rothwell wrote:
> Hi all,
>
> Do not add stuff destined for v3.8 to your linux-next included branches
> until after v3.7-rc1 is released.
>
> Changes since 201201002:
>
on i386:
CC drivers/mfd/syscon.o
drivers/mfd/syscon.c:94:15: error: variable
On Tue, Oct 02, 2012 at 07:50:42PM -, Kees Cook wrote:
> This config item has not carried much meaning for a while now and is
> almost always enabled by default. As agreed during the Linux kernel
> summit, it should be removed. As a first step, remove it from being
> listed, and default it to
On Wed, Oct 03, 2012 at 04:03:54PM -0700, Eric W. Biederman wrote:
>
> Linus,
>
> Please pull the for-linus git tree from:
>
>git://git.kernel.org:/pub/scm/linux/kernel/git/ebiederm/user-namespace.git
> for-linus
>
>HEAD: 702e490211b2b7e448ebe1b3a07d97ad2fc07e03 userns: Fix build of
1 - 100 of 1350 matches
Mail list logo
