This patch is to the comedi.h file that fixes up following type
of 42 warning in the file:
-Blocking comments use a trailing */ on a separate line
-Block comments use * on subsequent lines
Signed-off-by: Punit Vara
---
Usage of generic names like "uart_pins" is confusing to the reader, given
the fact that there could be more than one uart on APQ8064.
This patch adds gsbi prefix to uart pinctrl nodes so as to avoid such
confusion.
Signed-off-by: Srinivas Kandagatla
---
This patch adds rtc node for pmic8921.
Signed-off-by: Srinivas Kandagatla
---
arch/arm/boot/dts/qcom-apq8064.dtsi | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/qcom-apq8064.dtsi
b/arch/arm/boot/dts/qcom-apq8064.dtsi
index d973832..1d4fa2b 100644
---
This patch adds missing gsbi7 uart pinctrl, this is the default debug
uart on most boards.
Signed-off-by: Srinivas Kandagatla
---
arch/arm/boot/dts/qcom-apq8064.dtsi | 14 ++
1 file changed, 14 insertions(+)
diff --git a/arch/arm/boot/dts/qcom-apq8064.dtsi
This patch removes unnecessary eeprom label, which is not used
anywhere in the board file.
Signed-off-by: Srinivas Kandagatla
---
arch/arm/boot/dts/qcom-apq8064-cm-qs600.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/qcom-apq8064-cm-qs600.dts
This patch removes unnecessary eeprom label, which is not used
anywhere in the board file.
Signed-off-by: Srinivas Kandagatla
---
arch/arm/boot/dts/qcom-apq8064-ifc6410.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/qcom-apq8064-ifc6410.dts
This patch removes i2c pinctrl properties from board which which are now
mentioned in the SOC specific file. This will avoid redundant properties
across multiple board fiiles.
Signed-off-by: Srinivas Kandagatla
---
arch/arm/boot/dts/qcom-apq8064-cm-qs600.dts | 11 ---
Hi Andy,
Here are few cleanup and additions to the existing APQ8064 device tree.
Some of the patches are to do with princtrl cleanup which was always not
in the right place and some of the pinctrls were missing.
Other set of patches is to do with adding more devices like rtc rng
and pwr key for
This patch is to the comedi.h file that fixes up following type
of 42 warning in the file:
-Blocking comments use a trailing */ on a separate line
-Block comments use * on subsequent lines
Signed-off-by: Punit Vara
---
On Fri, Sep 18, 2015 at 01:56:37PM +0200, Peter Zijlstra wrote:
> +#ifndef atomic64_read_ctrl
> +static inline int atomic64_read_ctrl(atomic64_t *v)
> +{
> + int val = atomic64_read(v);
Duh
long long...
> + smp_read_barrier_depends(); /* Enforce control dependency. */
> +
On Fri, Sep 18, 2015 at 02:20:48PM +0200, LABBE Corentin wrote:
>
> I will send the modified patch series with this function name soon.
You only need to resend patches 4-7.
Thanks,
--
Email: Herbert Xu
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key:
On Fri, Sep 18, 2015 at 07:53:00PM +0800, Herbert Xu wrote:
> On Thu, Sep 10, 2015 at 03:21:39PM +0200, LABBE Corentin wrote:
> > Some driver use a modified version of sg_nents_for_len with an
> > additional parameter bool *chained for knowing if the scatterlist is
> > chained or not.
> >
> > So,
From: Nariman Poushin
Introduced by:
commit 8019ff6cfc04
("regmap: Use reg_sequence for multi_reg_write / register_patch")
Interacting with:
commit 561629755a21 ("mfd: arizona: Add support for WM8998 and WM1814")
commit 81207880cef2 ("mfd: wm5110: Add register patch for rev E and above")
On Fri, Sep 18, 2015 at 05:47:44PM +0800, Chen-Yu Tsai wrote:
> On Fri, Sep 18, 2015 at 4:48 PM, Maxime Ripard
> wrote:
> > The R8 is a new Allwinner SoC based on the A13. While both are very
> > similar, there's still a few differences. Introduce a new compatible to
> > deal with them.
> >
> >
On Fri, Sep 18, 2015 at 05:41:47PM +0800, Chen-Yu Tsai wrote:
> Hi,
>
> On Fri, Sep 18, 2015 at 4:48 PM, Maxime Ripard
> wrote:
> > The R8 is very close to the A13, but it still has a few differences,
> > notably a composite output, which the A13 lacks.
> >
> > Add a DTSI based on the A13's to
Hi Arnd,
On Fri, Sep 18, 2015 at 11:02:33AM +0200, Arnd Bergmann wrote:
> On Friday 18 September 2015 10:48:45 Maxime Ripard wrote:
> >
> > Here is a serie introducing the support for the Allwinner R8 and the
> > Nextthing's CHIP.
> >
> > Support is almost complete for the CHIP itself, the only
On 09/16/2015 04:26 PM, Mark Brown wrote:
> On Wed, Sep 16, 2015 at 03:38:09PM +0530, Vignesh R wrote:
>
>> But, I didn't get how to integrate with existing message queue. Memory
>> mapped read by-passes message queue of SPI core. Could you please
>> explain a bit more on integrating with
On Fri, Sep 18, 2015 at 04:02:21PM +0530, Sudip Mukherjee wrote:
> Fix the error path so that we can free the allocated memory on the error
> path instead of releasing them individually on each error.
>
> Signed-off-by: Sudip Mukherjee
> ---
Acked-by: Charles Keepax
Thanks,
Charles
--
To
On Fri, Sep 18, 2015 at 04:02:20PM +0530, Sudip Mukherjee wrote:
> We have requested for the firmware but we have missed releasing it both
> on success and on error path.
> While checking the code it turned out that the requested firmware is not
> even used. More over the same firmware is being
On Fri, Sep 18, 2015 at 01:50:01PM +0200, Dmitry Vyukov wrote:
> > +#ifndef atomic_read_ctrl
> > +static inline int atomic_read_ctrl(atomic_t *v)
> > +{
> > + int val = atomic_read(v);
> > + smp_read_barrier_depends(); /* Enforce control dependency. */
> > + return val;
> > +}
>
Forwading
Albino
-- Forwarded message --
From: Junio C Hamano
Date: 2015-09-17 19:16 GMT-03:00
Subject: [ANNOUNCE] Git v2.5.3
To: g...@vger.kernel.org
The latest maintenance release Git v2.5.3 is now available at
the usual places.
The tarballs are found at:
On Fri, Sep 18, 2015 at 04:02:19PM +0530, Sudip Mukherjee wrote:
> We have done regulator_bulk_enable() while booting the DSP but on the
> error exit path we have not disbled it.
>
> Signed-off-by: Sudip Mukherjee
> ---
> sound/soc/codecs/wm0010.c | 2 --
> 1 file changed, 2 deletions(-)
>
>
Linus,
The following changes since commit 6ff33f3902c3b1c5d0db6b1e2c70b6d76fba357f:
Linux 4.3-rc1 (2015-09-12 16:35:56 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus
for you to fetch changes up to
On Thu, Sep 10, 2015 at 03:21:39PM +0200, LABBE Corentin wrote:
> Some driver use a modified version of sg_nents_for_len with an
> additional parameter bool *chained for knowing if the scatterlist is
> chained or not.
>
> So, for removing duplicate code, add sg_nents_for_len2 in
>
On Fri, Sep 18, 2015 at 1:22 PM, Peter Zijlstra wrote:
> On Fri, Sep 18, 2015 at 10:28:20AM +0100, Will Deacon wrote:
>> On Fri, Sep 18, 2015 at 10:06:46AM +0100, Dmitry Vyukov wrote:
>
>> > Can we have something along the lines of:
>> >
>> > #define atomic_read_ctrl(v)
On 09/11/2015 03:27 PM, Peter Ujfalusi wrote:
> + if (irq >= 0) {
> + irq_name = devm_kasprintf(dev, GFP_KERNEL, "%s_ccint\n",
The '\n' should not be in the format string.
> + dev_name(dev));
> + ret = devm_request_irq(dev, irq,
On Fri, Sep 18, 2015 at 01:26:53PM +0200, Paolo Bonzini wrote:
> > +++ b/kernel/sched/core.c
> > @@ -2614,13 +2614,13 @@ unsigned long nr_running(void)
> >
> > /*
> > * Check if only the current task is running on the cpu.
> > + *
> > + * Caution result is subject to
On Fri, 2015-09-18 at 13:18 +0300, Mathias Nyman wrote:
> Better ask Oliver,
> Do you still have access to the HP laptop?
No I am sorry, we no longer have those laptops.
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
On Thu, Sep 17, 2015 at 9:50 AM, Dave Chinner wrote:
> On Mon, Sep 07, 2015 at 01:29:33PM +0800, Jeff Chua wrote:
>> When umount a slow device such as an SD card, the command will take a
>> while to run depending on how much data is left to write to the
>> device. Is there way to check how much
On Fri, 18 Sep 2015 13:26:53 +0200
Paolo Bonzini wrote:
>
>
> On 18/09/2015 11:27, Dominik Dingel wrote:
> > Commit 2ee507c47293 ("sched: Add function single_task_running to let a task
> > check if it is the only task running on a cpu") referenced the current
> > runqueue with the
On Fri, Sep 18, 2015 at 12:22:52PM +0100, Peter Zijlstra wrote:
> On Fri, Sep 18, 2015 at 10:28:20AM +0100, Will Deacon wrote:
> > On Fri, Sep 18, 2015 at 10:06:46AM +0100, Dmitry Vyukov wrote:
>
> > > Can we have something along the lines of:
> > >
> > > #define atomic_read_ctrl(v)
On Fri, Sep 18, 2015 at 10:28:20AM +0100, Will Deacon wrote:
> On Fri, Sep 18, 2015 at 10:06:46AM +0100, Dmitry Vyukov wrote:
> > Can we have something along the lines of:
> >
> > #define atomic_read_ctrl(v) READ_ONCE_CTRL(&(v)->counter)
>
> Funnily enough, I had this exact same discussion
On Sat, Sep 12, 2015 at 7:40 AM, Tejun Heo wrote:
> Hello,
>
> On Wed, Sep 09, 2015 at 05:49:31AM -0700, Paul Turner wrote:
>> I do not think this is a layering problem. This is more like C++:
>> there is no sane way to concurrently use all the features available,
>> however, reasonably
On 18/09/2015 11:27, Dominik Dingel wrote:
> Commit 2ee507c47293 ("sched: Add function single_task_running to let a task
> check if it is the only task running on a cpu") referenced the current
> runqueue with the smp_processor_id. When CONFIG_DEBUG_PREEMPT is enabled,
> that is only allowed if
If omap4_keypad_parse_dt() fails we returned the error code but we
missed releasing keypad_data.
Signed-off-by: Sudip Mukherjee
---
drivers/input/keyboard/omap4-keypad.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/input/keyboard/omap4-keypad.c
On Tue, 15 Sep 2015, Geliang Tang wrote:
> Fix the following 'make htmldocs' warnings:
>
> .//drivers/gpu/drm/i915/i915_gem.c:1729: warning: No description found for
> parameter 'vma'
> .//drivers/gpu/drm/i915/i915_gem.c:1729: warning: No description found for
> parameter 'vmf'
>
>
On at91sam9x5ek/at91sam9m10g45ek/sama5d3xek boards, we use the parallel
connection for ov2640. So we must set the hsync/vsync property (1 means
active high).
Otherwise, the connection would be seen as BT.656 or BT.1120.
Signed-off-by: Josh Wu
---
arch/arm/boot/dts/at91sam9m10g45ek.dts | 2 ++
On Tue, 15 Sep 2015, Geliang Tang wrote:
> Fix the following 'make htmldocs' warnings:
>
> .//drivers/gpu/drm/i915/intel_audio.c:439: warning: No description found
> for parameter 'intel_encoder'
> .//drivers/gpu/drm/i915/intel_audio.c:439: warning: Excess function
> parameter 'encoder'
On Wed, Sep 16, 2015 at 12:54:38AM +0600, Alexander Kuleshov wrote:
> The provides PFN_PHYS and PFN_DOWN macros for the
> getting page frame number and physical address of a page frame number.
> This patch replaces (pfn << PAGE_SHIFT) and (addr >> PAGE_SHIFT)
> expressions with the PFN_PHYS and
On 16/09/15 12:17, Jeff Layton wrote:
On Wed, 16 Sep 2015 10:35:49 +0100
"Suzuki K. Poulose" wrote:
From: "Suzuki K. Poulose"
...
+ write_unlock_bh(>sk_callback_lock);
+ return;
+ }
+ sock = transport->sock;
+
transport->inet = NULL;
On Wed, Sep 16, 2015 at 12:54:24AM +0600, Alexander Kuleshov wrote:
> The already provides for_each_mem_range() macro that
> iterates through memblock areas from type_a and not included in type_b.
> We can remove custom for_each_dump_mem_range() macro and use the
> for_each_mem_range() instead.
>
Hi Linus,
Please consider pulling LED subsystem fixes for v4.3-rc2.
The following changes since commit 6ff33f3902c3b1c5d0db6b1e2c70b6d76fba357f:
Linux 4.3-rc1 (2015-09-12 16:35:56 -0700)
are available in the git repository at:
On Fri, Sep 18, 2015 at 02:36:09PM +0800, Herbert Xu wrote:
>
> But yes there are ordering issues here so I've decided to make
> rhashtable use a new field for its hash instead.
>
> Note that I've dropped the acks as this patch is now substantially
> different.
v3 doesn't apply to the current
On 17/09/15 15:50, Trond Myklebust wrote:
On Thu, 2015-09-17 at 10:18 -0400, Jeff Layton wrote:
On Thu, 17 Sep 2015 09:38:33 -0400
Trond Myklebust wrote:
On Tue, Sep 15, 2015 at 2:52 PM, Jeff Layton <
jlay...@poochiereds.net> wrote:
On Tue, 15 Sep 2015 16:49:23 +0100
"Suzuki K. Poulose"
On the error path we have missed releasing the firmware.
Signed-off-by: Sudip Mukherjee
---
drivers/video/fbdev/broadsheetfb.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/video/fbdev/broadsheetfb.c
b/drivers/video/fbdev/broadsheetfb.c
index
Hi, Guennadi
On 8/30/2015 10:06 PM, Guennadi Liakhovetski wrote:
Hi Josh,
Sorry, I missed the 4.3 merge cycle, but isn't this patch a fix? Isn't it
fixing soc-camera / atmel-isi on a specific platform, where the clock name
is longer, than currently supported? Is this platform in the mainline
On 18/09/15 12:51, Mark Rutland wrote:
> On Fri, Sep 18, 2015 at 07:09:16AM +0100, Adrian Hunter wrote:
>> On 17/09/15 18:41, Mark Rutland wrote:
>>> Hi,
>>>
>>> On Wed, Sep 16, 2015 at 09:54:54PM +0100, Arnaldo Carvalho de Melo wrote:
Em Wed, Sep 16, 2015 at 06:18:49PM +0100, Mark Rutland
When a trace recorded on a 32-bit device is processed with a 64-bit
binary, the higher 32-bits of the address need to ignored
The lack of this results in the output of the 64-bit pointer
value to the trace as the 32-bit address lookup fails in find_printk.
Before:
burn-1778 [003] 548.600305:
We are returning NULL if we are not able to attach the iommu to the
domain but while returning we missed freeing info.
Signed-off-by: Sudip Mukherjee
---
drivers/iommu/intel-iommu.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/iommu/intel-iommu.c b/drivers/iommu/intel-iommu.c
From: Marc Zyngier
Date: Fri, 18 Sep 2015 11:03:12 +0100
> On Fri, 18 Sep 2015 18:22:07 +0900
> Kohji Okuno wrote:
>
>> From: Thomas Gleixner
>> Date: Fri, 18 Sep 2015 11:04:23 +0200
>> > That's weird. The flow is:
>> >
>> > interrupt()
>> > mask()
>> > ret = primary_handler()
>> > if
Hi Namhyung,
Thanks for looking into this!
On 17/09/15 16:26, Namhyung Kim wrote:
> Hi,
>
> On Thu, Sep 17, 2015 at 11:58 PM, Kapileshwar Singh
> wrote:
>> Hi Steve,
>>
>> Thanks for looking into this!
>>
>> On 17/09/15 14:11, Steven Rostedt wrote:
>>> On Thu, 17 Sep 2015 12:14:36 +0100
>>>
On Fri, Sep 18, 2015 at 12:49:07PM +0200, Christian Borntraeger wrote:
> Am 18.09.2015 um 12:41 schrieb Michael S. Tsirkin:
> > Upon TUNSETSNDBUF, macvtap reads the requested sndbuf size into
> > a local variable u.
> > commit 39ec7de7092b ("macvtap: fix uninitialized access on
> > TUNSETIFF")
Am 18.09.2015 um 12:41 schrieb Michael S. Tsirkin:
> Upon TUNSETSNDBUF, macvtap reads the requested sndbuf size into
> a local variable u.
> commit 39ec7de7092b ("macvtap: fix uninitialized access on
> TUNSETIFF") changed its type to u16 (which is the right thing to
> do for all other macvtap
In ovl_copy_up_locked(), newdentry is leaked if the function exits through
out_cleanup as this just to out after calling ovl_cleanup() - which doesn't
actually release the ref on newdentry.
The out_cleanup segment should instead exit through out2 as certainly
newdentry leaks - and possibly upper
Open the lower file with O_LARGEFILE in ovl_copy_up() if the lower file is
>= 4GiB in size.
Reported-by: Ulrich Obergfell
Signed-off-by: David Howells
---
fs/overlayfs/copy_up.c |9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/fs/overlayfs/copy_up.c
On 17 September 2015 at 14:45, Lee Jones wrote:
> Signed-off-by: Pankaj Dev
> Signed-off-by: Lee Jones
Comments addressed, Also LGTM.
Acked-by: Kieran Bingham
> ---
> drivers/char/hw_random/Kconfig | 10 +++
> drivers/char/hw_random/Makefile | 1 +
> drivers/char/hw_random/st-rng.c |
On Fri, 18 Sep 2015 11:18:42 +0200
Oleksij Rempel wrote:
> From: Oleksij Rempel
>
> Freescale iMX23/iMX28 and Alphascale ASM9260 have similar
Is it Alphascale or Alpascale? You may need to fix the patch title.
> interrupt collectors. It makes easy to reuse irq-mxs code for ASM9260.
>
The following changes since commit 997e120843e82609c8d99a9d5714e6cf91e14cbe:
virtio_balloon: do not change memory amount visible via /proc/meminfo
(2015-09-08 13:32:11 +0300)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git tags/for_linus
hi Daniel Stone:
On 2015/9/16 23:23, Daniel Stone wrote:
> Hi Xinwei,
> Thanks for this contribution! We look forward to seeing support for
> these devices.
>
> This isn't an exhaustive review, but two very high-level comments
> which should result in a lot of changes ...
>
> On 15 September
Upon TUNSETSNDBUF, macvtap reads the requested sndbuf size into
a local variable u.
commit 39ec7de7092b ("macvtap: fix uninitialized access on
TUNSETIFF") changed its type to u16 (which is the right thing to
do for all other macvtap ioctls), breaking all values > 64k.
The value of TUNSETSNDBUF
On 02/09/15 18:11, Leo Yan wrote:
> On Tue, Jul 07, 2015 at 07:24:15PM +0100, Morten Rasmussen wrote:
>> Let available compute capacity and estimated energy impact select
>> wake-up target cpu when energy-aware scheduling is enabled and the
>> system in not over-utilized (above the tipping point).
We have requested for the firmware but we have missed releasing it both
on success and on error path.
While checking the code it turned out that the requested firmware is not
even used. More over the same firmware is being loaded by
wm0010_stage2_load().
Signed-off-by: Sudip Mukherjee
---
Fix the error path so that we can free the allocated memory on the error
path instead of releasing them individually on each error.
Signed-off-by: Sudip Mukherjee
---
sound/soc/codecs/wm0010.c | 22 ++
1 file changed, 10 insertions(+), 12 deletions(-)
diff --git
We have done regulator_bulk_enable() while booting the DSP but on the
error exit path we have not disbled it.
Signed-off-by: Sudip Mukherjee
---
sound/soc/codecs/wm0010.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/sound/soc/codecs/wm0010.c b/sound/soc/codecs/wm0010.c
index
Linus,
please pull the latest x86-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-urgent-for-linus
A single regression fix for the x86 dma allocator which got wreckaged
in the merge window.
Thanks,
tglx
-->
Junichi
On 18/09/15 06:11, Jon Masters wrote:
On Sep 14, 2015, at 06:26, Daniel Thompson wrote:
This patchset provides a pseudo-NMI for arm64 kernels by reimplementing
the irqflags macros to modify the GIC PMR (the priority mask register is
accessible as a system register on GICv3 and later) rather
On Fri, Sep 18, 2015 at 09:33:36AM +0100, Charles Keepax wrote:
> On Fri, Sep 18, 2015 at 01:50:15PM +1000, Stephen Rothwell wrote:
> > It looks like that patch has been forgotten as I am still applying it
> > to the linux-next tree every day ...
> Apologies if I am a little out of my depth
On 17/09/15 07:59, Ulf Hansson wrote:
> [...]
>
+ /*
+* The caller must have CAP_SYS_RAWIO, and must be calling this on
the
+* whole block device, not on a partition. This prevents overspray
+* between sibling partitions.
+*/
On 09/18/15 12:08, Arnd Bergmann wrote:
> On Friday 18 September 2015 11:52:28 Hans Verkuil wrote:
>> On 09/18/15 11:43, Arnd Bergmann wrote:
>>> On Friday 18 September 2015 11:27:40 Hans Verkuil wrote:
Ah, OK. Got it.
I think this is dependent on the upcoming media workshop next
On Fri, 18 Sep 2015, Oleksij Rempel wrote:
> Some HW has similar functionality but different register offsets.
> Make sure we can change offsets dynamically.
You forgot to mention the other preparatory changes.
Thanks,
tglx
--
To unsubscribe from this list: send the line "unsubscribe
On Fri, 18 Sep 2015, Oleksij Rempel wrote:
'changelog' is not really a descriptive subject line for a cover
letter.
Thanks,
tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
On 17 September 2015 at 14:45, Lee Jones wrote:
> In April 2009, commit d405640 ("Driver Core: misc: add node name support
> for misc devices.") inadvertently changed the device node name from
> /dev/hw_random to /dev/hwrng. Since 6 years has passed since the change
> it seems unpractical to
On 17 September 2015 at 14:45, Lee Jones wrote:
> In April 2009, commit d405640 ("Driver Core: misc: add node name support
> for misc devices.") inadvertently changed the device node name from
> /dev/hw_random to /dev/hwrng. Since 6 years has passed since the change
> it seems unpractical to
On Fri, 18 Sep 2015 11:18:40 +0200
Oleksij Rempel wrote:
Hi Oleksij,
> v2:
> - move some parts from patch 2 to 1
> - make separate irq_chip for ICOLL and ASM9260
>
> Oleksij Rempel (2):
> ARM: irqchip: mxs: prepare driver for HW with different offsets
> ARM: irqchip: mxs: add Alpascale
On Friday 18 September 2015 11:49:50 Hans Verkuil wrote:
> *If* the conversion takes place only in v4l2-ioctl.c, then it makes sense
> have these structs + ioctls moved to v4l2-ioctl.h.
Ok.
> I noticed that v4l2-compat-ioctl32.c wasn't changed. Is that right? I have
> unfortunately no time to
On 10.09.2015 20:27, Laura Abbott wrote:
We received several reports of systems rebooting and powering on
after an attempted shutdown. Testing showed that setting
XHCI_SPURIOUS_WAKEUP quirk in addition to the XHCI_SPURIOUS_REBOOT
quirk allowed the system to shutdown as expected for Lynxpoint
On Friday 18 September 2015 11:52:28 Hans Verkuil wrote:
> On 09/18/15 11:43, Arnd Bergmann wrote:
> > On Friday 18 September 2015 11:27:40 Hans Verkuil wrote:
> >> Ah, OK. Got it.
> >>
> >> I think this is dependent on the upcoming media workshop next month. If we
> >> decide to redesign
Hi Linus,
Please pull powerpc fixes for 4.3:
The following changes since commit 7d9071a095023cd1db8fa18fa0d648dc1a5210e0:
Merge branch 'for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs (2015-09-05 20:34:28
-0700)
are available in the git repository at:
On Fri, 18 Sep 2015 18:22:07 +0900
Kohji Okuno wrote:
> From: Thomas Gleixner
> Date: Fri, 18 Sep 2015 11:04:23 +0200
> > That's weird. The flow is:
> >
> > interrupt()
> > mask()
> > ret = primary_handler()
> > if (ret == WAKE_THREAD)
> > wake_thread()
> > else
> > unmask()
>
On 15/09/18, Steve Grubb wrote:
> On Fri, 18 Sep 2015 03:52:43 -0400
> Richard Guy Briggs wrote:
>
> > A bug was introduced by "audit: try harder to send to auditd upon
> > netlink failure", caused by incomplete code and a function that
> > expects a string and does not accept a format plus
Sorry guys, some of you will get the patches twice, as Sören's name
in the header caused vger to reject all the patches.
--
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
On Fri, Sep 18, 2015 at 07:49:56PM +1000, Michael Ellerman wrote:
> On Fri, 2015-09-18 at 08:22 +0800, Boqun Feng wrote:
> > Ping ;-)
>
> Hi Boqun,
>
Hello,
> We keep track of patches in patchwork:
>
> http://patchwork.ozlabs.org/project/linuxppc-dev/list/?submitter=67102
>
Good to know
Hi Axel,
Thanks for the patch
Acked-by: Srinivas Kandagatla
I remember fixing this sometime back which was reported by static
checker reported by Dan Carpenter, I forgot to send it over to wider
audience. Thanks for reminding.
--srini
On 18/09/15 10:50, Axel Lin wrote:
It's pointless to
Add a phy_device_remove() function to complement phy_device_register(),
which undoes the effects of phy_device_register() by removing the phy
device from visibility, but not freeing it.
This allows these details to be moved out of the mdio bus code into
the phy code where this action belongs.
Validate that the phy_device passed into fixed_phy_update_state() is a
fixed-phy device before walking the list of phys for a fixed phy at the
same address.
Signed-off-by: Russell King
---
drivers/net/phy/fixed_phy.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
of_phy_find_device() increments the phy struct device refcount,
which we need to properly balance. Add code to network drivers
using this function to ensure that the struct device refcount is
correctly balanced.
Signed-off-by: Russell King
---
drivers/net/ethernet/apm/xgene/xgene_enet_hw.c
Take a refcount on the phy struct device when the phy device is attached
to a network device, and drop it after it's detached. This ensures that
a refcount is held on the phy device while the device is being used by
a network device, thereby preventing the phy_device from being
unexpectedly
Re-implement the mdiobus module refcounting to ensure that we actually
ensure that the mdiobus module code does not go away while we might call
into it.
The old scheme using bus->dev.driver was buggy, because bus->dev is a
class device which never has a struct device_driver associated with it,
bus_find_device() is defined as:
* This is similar to the bus_for_each_dev() function above, but it
* returns a reference to a device that is 'found' for later use, as
* determined by the @match callback.
and it does indeed return a reference-counted pointer to the device:
while
of_mdio_find_bus() leaks a struct device refcount, caused by using
class_find_device() and not realising that the device reference has
its refcount incremented:
* Note, you will need to drop the reference with put_device() after use.
...
while ((dev = class_dev_iter_next())) {
On 09/18/15 11:43, Arnd Bergmann wrote:
> On Friday 18 September 2015 11:27:40 Hans Verkuil wrote:
>> Ah, OK. Got it.
>>
>> I think this is dependent on the upcoming media workshop next month. If we
>> decide to redesign v4l2_buffer anyway, then we can avoid timeval completely.
>> And the only
On Fri, Sep 18, 2015 at 07:09:16AM +0100, Adrian Hunter wrote:
> On 17/09/15 18:41, Mark Rutland wrote:
> > Hi,
> >
> > On Wed, Sep 16, 2015 at 09:54:54PM +0100, Arnaldo Carvalho de Melo wrote:
> >> Em Wed, Sep 16, 2015 at 06:18:49PM +0100, Mark Rutland escreveu:
> >>> This has been observed to
It's pointless to test (cell->bit_offset || cell->bit_offset).
nvmem_shift_read_buffer_in_place() should be called when
(cell->bit_offset || cell->nbits).
Signed-off-by: Axel Lin
---
drivers/nvmem/core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/nvmem/core.c
On 09/18/15 11:26, Arnd Bergmann wrote:
> On Friday 18 September 2015 09:18:45 Hans Verkuil wrote:
>> Hi Arnd,
>>
>> Thanks once again for working on this! Unfortunately, this approach won't
>> work, see my comments below.
>>
>> BTW, I would expect to see compile errors when compiling for 32 bit.
On Fri, 2015-09-18 at 08:22 +0800, Boqun Feng wrote:
> Ping ;-)
Hi Boqun,
We keep track of patches in patchwork:
http://patchwork.ozlabs.org/project/linuxppc-dev/list/?submitter=67102
So your patch won't be forgotten.
I tend to start taking patches for next after rc2, which should come out
From: Oleksij Rempel
Freescale iMX23/iMX28 and Alphascale ASM9260 have similar
interrupt collectors. It makes easy to reuse irq-mxs code for ASM9260.
Differences between this devices are fallowing:
- different register offsets
- different count of intterupt lines per register
- ASM9260 don't
On Fri, Sep 18, 2015 at 4:48 PM, Maxime Ripard
wrote:
> The R8 is a new Allwinner SoC based on the A13. While both are very
> similar, there's still a few differences. Introduce a new compatible to
> deal with them.
>
> Signed-off-by: Maxime Ripard
> ---
> arch/arm/mach-sunxi/sunxi.c | 3 ++-
Hi,
While looking at the phy code, I identified a number of weaknesses
where refcounting on device structures was being leaked, where
modules could be removed while in-use, and where the fixed-phy could
end up having unintended consequences caused by incorrect calls to
fixed_phy_update_state().
Hi Yassin,
On Fri, Sep 18, 2015 at 10:19:55AM +1000, Yassin Jaffer wrote:
> Hi Maxime
>
> I appreciate your time and efforts .
>
> Do you need that rate to be enforced, or is it some leftover from the
> > allwinner BSP?
>
>
> I've found that clock rate works fine with the default denounce and
On Friday 18 September 2015 11:27:40 Hans Verkuil wrote:
> Ah, OK. Got it.
>
> I think this is dependent on the upcoming media workshop next month. If we
> decide to redesign v4l2_buffer anyway, then we can avoid timeval completely.
> And the only place where we would need to convert it in the
601 - 700 of 1682 matches
Mail list logo
