This patch fixes following compiler warning:
drivers/staging/rtl8192u/ieee80211/ieee80211_rx.c: In function
‘RxReorderIndicatePacket’:
drivers/staging/rtl8192u/ieee80211/ieee80211_rx.c:758:1: warning: the
frame size of 1064 bytes is larger than 1024 bytes
[-Wframe-larger-than=]
It replaces the
Hi Maxime,
On Wed, 16 Dec 2015 11:47:36 +0100
Maxime Ripard wrote:
> > Because SUN4I_CODEC_AC_MIC_PHONE_CAL is sun7i-specific.
>
> Yet, you're using it in both cases (A10 vs A20).
Yes. I'm trying to keep complexity and duplication down.
I figured it wouldn't be bad to have unused registers in
On 16 December 2015 at 22:41, Nish Aravamudan wrote:
> Hi Daniel,
>
> On Wed, Dec 16, 2015 at 1:43 AM, Daniel Baluta
> wrote:
>> On Tue, Dec 15, 2015 at 9:19 PM, Nish Aravamudan
>> wrote:
>>> So, I apologize in advance for this relatively vague report, but I'm fairly
>>> sure
>>> the Yoga 900
On Wed, Dec 16, 2015 at 08:55:45PM +, Okash Khawaja wrote:
> Compiling drivers/staging/rtl8192u/ gives following compiler warning:
>
> drivers/staging/rtl8192u/ieee80211/ieee80211_rx.c: In function
> ‘RxReorderIndicatePacket’:
> drivers/staging/rtl8192u/ieee80211/ieee80211_rx.c:758:1:
On 12/16/2015 11:17 PM, Richard Weinberger wrote:
Am 16.12.2015 um 21:59 schrieb Vegard Nossum:
An inverted return value check in hostfs_mknod() caused the function
to return success after handling it as an error (and cleaning up).
[...]
Applied! :-)
BTW: How did you create this patch? I
Am 16.12.2015 um 21:59 schrieb Vegard Nossum:
> An inverted return value check in hostfs_mknod() caused the function
> to return success after handling it as an error (and cleaning up).
>
> It resulted in the following segfault when trying to bind() a named
> unix socket:
>
> Pid: 198, comm:
On Thu, Dec 10, 2015 at 08:55:27AM -0800, Suravee Suthikulpanit wrote:
> This patch introduces pci_msi_register_fwnode_provider() for irqchip
> to register a callback, to provide a way to determine appropriate MSI
> domain for a pci device.
>
> It also introduces
Compiling drivers/staging/rtl8192u/ gives following compiler warning:
drivers/staging/rtl8192u/ieee80211/ieee80211_rx.c: In function
‘RxReorderIndicatePacket’:
drivers/staging/rtl8192u/ieee80211/ieee80211_rx.c:758:1: warning: the
frame size of 1064 bytes is larger than 1024 bytes
On Thu, Dec 10, 2015 at 08:55:29AM -0800, Suravee Suthikulpanit wrote:
> This patch replaces the struct device_node with struct fwnode_handle
> since this structure is common between DT and ACPI.
>
> It also refactors gicv2m_init_one() to prepare for ACPI support.
> The only functional change is
When testing liburcu on a 3.18 Linux kernel, 2-core MIPS (cpu model :
Ingenic JZRISC V4.15 FPU V0.0), we notice that a blocked sys_futex
FUTEX_WAIT returns -1, errno=ENOSYS when interrupted by a SA_RESTART
signal handler. This spurious ENOSYS behavior causes hangs in liburcu
0.9.x. Running a MIPS
On 12/16/15, Jeff Merkey wrote:
> On 12/16/15, Jeff Merkey wrote:
>> Setting the (trap flag | resume flag) inside of an nmi handler results
>> in a hard lockup while setting the resume flag works fine.
>>
>> The watchdog detector fails to detect the lockup. I am currently
>> examining the trap
On 03/12/2015 at 14:41:21 -0500, Akshay Bhat wrote :
> This driver supports the following functions:
> - reading and setting time
> - alarms when connected to an IRQ
> - reading and clearing the voltage low flags
>
> Datasheet:
>
> From: Marcelo Tosatti [mailto:mtosa...@redhat.com]
> Sent: Wednesday, November 18, 2015 1:27 PM
> To: Yu, Fenghua
> Cc: H Peter Anvin ; Ingo Molnar ;
> Thomas Gleixner ; Peter Zijlstra
> ; linux-kernel ; x86
> ; Vikas Shivappa
> Subject: Re: [PATCH V15 11/11] x86,cgroup/intel_rdt : Add a
On 16/12/2015 20:15, Alex Williamson wrote:
> The consumers would be, for instance, Intel PI + the threaded handler
> added in this series. These run independently, the PI bypass simply
> makes the interrupt disappear from the host when it catches it, but if
> the vCPU isn't running in the
On Wed, 2015-12-16 at 19:17 +0100, Borislav Petkov wrote:
> On Wed, Dec 16, 2015 at 09:52:37AM -0800, Dan Williams wrote:
> > It's possible that as far as the resource table is concerned the
> > resource type might just be "reserved". It may not be until after a
> > driver loads that we discover
On Thu, Dec 03, 2015 at 03:35:22PM +0200, Stanimir Varbanov wrote:
> From: Stanimir Varbanov
>
> The PCIe driver reuse the Designware common code for host
> and MSI initialization, and also program the Qualcomm
> application specific registers.
>
> Signed-off-by: Stanimir Varbanov
>
He is stepping into native_safe_halt() when this bug occurs (processor
has halted). I am starting to wonder is this is a linux bug or intel
bug. I am starting to lean towards intel bug possibly. I will go and
review intels documentation about what happens when a processor has
been halted, is
Hi Daniel,
On Wed, Dec 16, 2015 at 1:43 AM, Daniel Baluta wrote:
> On Tue, Dec 15, 2015 at 9:19 PM, Nish Aravamudan
> wrote:
>> So, I apologize in advance for this relatively vague report, but I'm fairly
>> sure
>> the Yoga 900 has an accelerometer amongst other sensors (ambient light?)
>>
On Wed, Dec 16, 2015 at 1:31 AM, Crt Mori wrote:
> Hi,
> So you were using 4.4-rc5 before and it worked, but after applying a
> patch it stopped?
Sorry, I should have explained it better. Without the patchset
referred to in my original e-mail, the touchpad simply doesn't work.
However, I do have
On 12/16/2015 8:58 AM, Felipe Balbi wrote:
>
> Hi,
>
> changbin...@intel.com writes:
>> From: "Du, Changbin"
>>
>> To stop an out endpoint, software should set sets the Global OUT NAK,
>> but not the Global Non-periodic IN NAK. This driver bug leads the out-ep
>> failed be in disabled state
Am Mittwoch, 16. Dezember 2015, 16:27:18 schrieb Caesar Wang:
> From: Yakir Yang
>
> ACLK_VIO is the noc bus clock for display module, display cann't
> read data from ddr without this clock enabled.
>
> Due to it shouldn't belong to any driver, but we need it enabled,
> so just mark it as the
Hi Linus, please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm libnvdimm-fixes
...to receive:
1/ 2 bug fixes for misuse of PAGE_MASK in scatterlist and dma-debug.
These are tagged for -stable. The scatterlist impact is potentially
corrupted dma addresses on HIGHMEM
> > +/*
> > + * Check whether we can use a group for top down.
> > + * Without a group may get bad results due to multiplexing.
> > + */
>
> That is not because you have a counter used by the NMI that
> you cannot group. If HT is off you have plenty of counters to
> do this.
Such a heuristic
On Wed, 2015-12-16 at 19:20 +, Haiyang Zhang wrote:
> > -Original Message-
> > From: Eric Dumazet [mailto:eric.duma...@gmail.com]
> > Sent: Wednesday, December 16, 2015 12:08 PM
> >
> > This looks very very wrong to me.
> >
> > How many times this is called per second, for the 'one
On Wed, Dec 16, 2015 at 01:05:20PM -0800, Randy Dunlap wrote:
> On 12/15/15 21:43, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20151215:
> >
> > The drm-misc tree gained a conflict against Linus' tree.
> >
> > The i2c tree gained a build failure for which I applied a patch.
> >
>
Hi Stan,
On Tue, Dec 15, 2015 at 10:24:07AM +0200, Stanimir Varbanov wrote:
> On 12/03/2015 03:35 PM, Stanimir Varbanov wrote:
> > From: Stanimir Varbanov
> >
> > The PCIe driver reuse the Designware common code for host
> > and MSI initialization, and also program the Qualcomm
> > application
On Wed, Dec 16, 2015 at 12:22 PM, Cong Wang wrote:
> Hmm, we should exclude the raw socket case, something like the
> following, but I am not sure if the check is too strict or not, also
> not sure if we should return an error for this raw socket case.
>
> diff --git a/net/core/sock.c
On 12/15/15 21:43, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20151215:
>
> The drm-misc tree gained a conflict against Linus' tree.
>
> The i2c tree gained a build failure for which I applied a patch.
>
> The gpio tree gained a build failure so I used the version from
>
An inverted return value check in hostfs_mknod() caused the function
to return success after handling it as an error (and cleaning up).
It resulted in the following segfault when trying to bind() a named
unix socket:
Pid: 198, comm: a.out Not tainted 4.4.0-rc4
RIP: 0033:[<61077df6>]
On Wed, Nov 25, 2015 at 02:27:37PM -0800, Stephen Boyd wrote:
> The #size-cells for the pmics are 0, but we specify a size in the
> reg property so that MPP and GPIO modules can figure out how many
> pins there are. Now that we've done that by counting irqs, we can
> remove the size elements in
On 12/16/2015 3:13 AM, Will Deacon wrote:
On Tue, Dec 15, 2015 at 04:18:08PM -0800, Yang Shi wrote:
The kernel just send out a SIGTRAP signal when handling ptrace breakpoint in
debug exception, so it sounds safe to have interrupt enabled if it is not
disabled by the parent process.
Is this
On Wed, Nov 25, 2015 at 02:27:36PM -0800, Stephen Boyd wrote:
> The #size-cells for the pmics are 0, but we specify a size in the
> reg property so that MPP and GPIO modules can figure out how many
> pins there are. Now that we've done that by counting irqs, we can
> remove the size elements in
On 15.12.2015 15:57, Jisheng Zhang wrote:
> Commit ac82d1277215 ("arm64: perf: add Cortex-A53 support") adds the
> cortex A53 PMU support, thus instead of using the generic armv8-pmuv3
> compatibility use the more specific Cortex A53 compatibility.
>
> Signed-off-by: Jisheng Zhang
> ---
> Since
I tested this patch and gave some hints to Jader when it first appeared
on the libfuse mailing list some months ago.
Signed-off-by: Luca Risolia
Jader H. Silva wrote:
Implement cuse mmap using shmem to provide the actual memory maps.
Pages must be read/written using fuse's NOTIFY_RETRIEVE
Hi,
On 16/12/2015 at 18:14:06 +0100, Thierry Reding wrote :
> Also, please use "drm/panel: " as the prefix (instead of "drm: panel: ")
> to make it easier for me to pick up things. I was about to send out a
> pull request for drm/panel when I noticed that there was this patch. The
> v4 wasn't Cc:
On 12/15/15 21:43, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20151215:
>
> The drm-misc tree gained a conflict against Linus' tree.
>
> The i2c tree gained a build failure for which I applied a patch.
>
> The gpio tree gained a build failure so I used the version from
>
On Wed, Dec 16, 2015 at 11:34 AM, Dmitry Vyukov wrote:
> BUG: KASAN: slab-out-of-bounds in sock_setsockopt+0x1284/0x13d0 at
> addr 88006563ec10
> Read of size 4 by task syzkaller_execu/4755
> =
> BUG RAWv6 (Not
On Fri, 2015-12-11 at 16:53 +0800, Yongji Xie wrote:
> Current vfio-pci implementation disallows to mmap MSI-X table in
> case that user get to touch this directly.
>
> However, EEH mechanism could ensure that a given pci device
> can only shoot the MSIs assigned for its PE and guest kernel also
With b3ca9b02b00704053a38bfe4c31dbbb9c13595d0, the AF_UNIX SOCK_STREAM
receive code was changed from using mutex_lock(>readlock) to
mutex_lock_interruptible(>readlock) to prevent signals from being
delayed for an indefinite time if a thread sleeping on the mutex
happened to be selected for
Remi Pommarel writes:
> On Mon, Dec 07, 2015 at 08:09:47PM -0800, Eric Anholt wrote:
>> Stefan Wahren writes:
>>
>> > Hi Remi,
>> >
>> > Am 07.12.2015 um 19:17 schrieb Remi Pommarel:
>> >> Hi Stefan,
>> >>
>> >> On Sun, Dec 06, 2015 at 10:16:25PM +0100, Stefan Wahren wrote:
>> >>> Hi Remi,
>>
On Fri, 2015-12-11 at 16:53 +0800, Yongji Xie wrote:
> Current vfio-pci implementation disallows to mmap
> sub-page(size < PAGE_SIZE) MMIO BARs because these BARs' mmio page
> may be shared with other BARs.
>
> But we should allow to mmap these sub-page MMIO BARs if all MMIO BARs
> are page
Hi Jader,
[auto build test WARNING on v4.4-rc5]
[cannot apply to next-20151216]
url:
https://github.com/0day-ci/linux/commits/Jader-H-Silva/fuse-implement-cuse-mmap/20151217-034148
config: i386-tinyconfig (attached as .config)
reproduce:
# save the attached .config to linux build
> -Original Message-
> From: Eric Dumazet [mailto:eric.duma...@gmail.com]
> Sent: Wednesday, December 16, 2015 12:08 PM
>
> This looks very very wrong to me.
>
> How many times this is called per second, for the 'one flow' case ?
>
> Don't you use TSO in this driver ?
>
> What about
Em Wed, Dec 16, 2015 at 09:37:18AM +0800, Wangnan (F) escreveu:
>
>
> On 2015/12/15 20:36, Jiri Olsa wrote:
> >On Mon, Dec 14, 2015 at 10:39:11AM +, Wang Nan wrote:
> >
> >SNIP
> >
> >>@@ -137,12 +138,15 @@ void machine__exit(struct machine *machine)
> >> void machine__delete(struct machine
On Thu, 2015-12-03 at 10:22 -0800, Yunhong Jiang wrote:
> For VFIO device with MSI interrupt type, it's possible to handle the
> interrupt on hard interrupt context without invoking the interrupt
> thread. Handling the interrupt on hard interrupt context reduce the
> interrupt latency.
>
>
On Thu, 2015-12-03 at 10:22 -0800, Yunhong Jiang wrote:
> Extend the irq_bypass manager to support runtime consumers. A runtime
> irq_bypass consumer can handle interrupt when an interrupt triggered. A
> runtime consumer has it's handle_irq() function set and passing a
> irq_context for the irq
Hello,
The following program triggers heap-out-of-bounds access in sock_setsockopt:
// autogenerated by syzkaller (http://github.com/google/syzkaller)
#include
#include
#include
#include
#include
#include
#include
#define SOF_TIMESTAMPING_OPT_ID (1<<7)
int main()
{
int fd =
Em Tue, Dec 15, 2015 at 05:10:46PM +0530, Naveen N. Rao escreveu:
> On 2015/12/15 08:51AM, Wang Nan wrote:
> > From: "Naveen N. Rao"
> >
> > perf build is currently (v4.4-rc5) broken on powerpc:
> >
> > bpf.c:28:4: error: #error __NR_bpf not defined. libbpf does not support
> > your arch.
> >
Implement cuse mmap using shmem to provide the actual memory maps.
Pages must be read/written using fuse's NOTIFY_RETRIEVE and NOTIFY_STORE api.
Signed-off-by: Jader H. Silva
---
fs/fuse/cuse.c| 459 +-
fs/fuse/dev.c | 163
On Wed, Dec 16, 2015 at 10:42 AM, Ian Abbott wrote:
> On 12/12/15 17:09, Moritz König wrote:
>>
>> This patch makes plx9080.h use kernel types.
>>
>> Signed-off-by: Moritz König
>> Signed-off-by: Fabian Lang
>> ---
>> drivers/staging/comedi/drivers/plx9080.h | 2 +-
>> 1 file changed, 1
On 12/15/15 21:43, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20151215:
>
on i386, when CONFIG_PM_SLEEP is not enabled:
../drivers/gpu/drm/vc4/vc4_v3d.c: In function 'vc4_v3d_set_power':
../drivers/gpu/drm/vc4/vc4_v3d.c:157:29: error: called object is not a function
or function
The patch
regulator: tps65917/palmas: Add bypass ops for LDOs with bypass capability
has been applied to the regulator tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually
On 12/02/15 10:29, Hugh Dickins wrote:
> On Mon, 23 Nov 2015, Dmitry Vyukov wrote:
>> On Mon, Nov 9, 2015 at 9:55 AM, Dmitry Vyukov wrote:
[snip]
>>> triggers WARNING in shmem_evict_inode:
>>>
>>> [ cut here ]
>>> WARNING: CPU: 0 PID: 10442 at mm/shmem.c:625
On Wednesday 16 December 2015 17:19:05 Catalin Marinas wrote:
> On Wed, Dec 16, 2015 at 04:58:20PM +, Catalin Marinas wrote:
> > On Wed, Dec 16, 2015 at 04:54:34PM +0100, Arnd Bergmann wrote:
> > > On Wednesday 16 December 2015 00:42:35 Yury Norov wrote:
> > > >
> > > > #ifdef CONFIG_COMPAT
On Tue, Dec 15, 2015 at 08:54:15PM +0800, Chen Feng wrote:
> +config REGULATOR_HI655X
> + tristate "Hisilicon HI655X PMIC regulators support"
> + depends on ARCH_HISI
> + depends on MFD_HI655X_PMIC && OF
> + help
> + This driver provides support for the voltage regulators of
On Wed, Dec 16, 2015 at 05:27:48PM +0530, Archit Taneja wrote:
> On 12/16/2015 02:45 PM, Boris Brezillon wrote:
> >On Wed, 19 Aug 2015 10:19:03 +0530
> >Archit Taneja wrote:
> >>+ return mtd_device_parse_register(mtd, NULL, , NULL, 0);
> >
> > return mtd_device_parse_register(mtd, NULL,
On Wed, Dec 16, 2015 at 10:57:52AM -0800, Dan Williams wrote:
> Aside from "System RAM" checks I don't think any of these strcmp
> usages are in fast paths.
Sure, 0.1% slowdown here, 0.2% slowdown there... this is how you get a
bloated kernel.
In addition to that, using strings to identify
On Wed, 2015-12-16 at 18:56 +0100, Paolo Bonzini wrote:
> Alex,
>
> can you take a look at the extension to the irq bypass interface in
> patch 2? I'm not sure I understand what is the case where you have
> multiple consumers for the same token.
The consumers would be, for instance, Intel PI +
+++ Miroslav Benes [16/12/15 13:59 +0100]:
On Wed, 16 Dec 2015, Jessica Yu wrote:
+++ Jessica Yu [09/12/15 14:10 -0500]:
> +++ Josh Poimboeuf [08/12/15 12:38 -0600]:
> >
> > There was a lot of discussion for v1, so I'm not sure, but I thought we
> > ended up deciding to get rid of the
On Wednesday 16 December 2015 19:31:30 Gregory CLEMENT wrote:
> diff --git a/drivers/net/ethernet/cadence/macb.c
> b/drivers/net/ethernet/cadence/macb.c
> index 88c1e1a..35661aa 100644
> --- a/drivers/net/ethernet/cadence/macb.c
> +++ b/drivers/net/ethernet/cadence/macb.c
> @@ -28,6 +28,7 @@
>
Hi Richard,
On mer., déc. 16 2015, Richard Cochran wrote:
> On Wed, Dec 16, 2015 at 07:31:30PM +0100, Gregory CLEMENT wrote:
>> +Optional properties for PHY child node:
>> +- reset-gpios : Should specify the gpio for phy reset
>
> reset-gpios plural or reset-gpio singular?
The bindings name
On Wed, Dec 16, 2015 at 07:31:30PM +0100, Gregory CLEMENT wrote:
> +Optional properties for PHY child node:
> +- reset-gpios : Should specify the gpio for phy reset
reset-gpios plural or reset-gpio singular?
> +
> Examples:
>
> macb0: ethernet@fffc4000 {
> @@ -29,4 +32,8 @@ Examples:
>
During testing, I discovered that __generic_file_splice_read() returns
0 (EOF) when aops->readpage fails with AOP_TRUNCATED_PAGE on the first
page of a single/multi-page splice read operation. This EOF return code
causes the userspace test to (correctly) report a zero-length read error
when it was
On Tue, Dec 15, 2015 at 5:38 PM, Daniel Mentz wrote:
> dma-debug uses struct dma_debug_entry to keep track of dma coherent
> memory allocation requests. The virtual address is converted into a pfn
> and an offset. Previously, the offset was calculated using an incorrect
> bit mask. As a result,
On Tue, Dec 15, 2015 at 9:58 PM, David Miller wrote:
> From: Dmitry Vyukov
> Date: Tue, 15 Dec 2015 21:55:37 +0100
>
>> I've seen a kernel address at least in pptp_bind,
>
> We're not talking about pptp_bind.
>
> We're talking about llcp_{,raw}_sock_bind().
>
> If your hex dump doesn't show it,
On Wed, Dec 16, 2015 at 10:17 AM, Borislav Petkov wrote:
> On Wed, Dec 16, 2015 at 09:52:37AM -0800, Dan Williams wrote:
[..]
> Now, imagine you have to do this pretty often. Which is faster: a
> strcmp() or an int comparison...?
Aside from "System RAM" checks I don't think any of these strcmp
On Wednesday, December 16, 2015 09:13:35 AM Alexander Duyck wrote:
> On Wed, Dec 16, 2015 at 9:01 AM, Hannes Reinecke wrote:
> > On Wednesday, December 16, 2015 08:52:10 AM Alexander Duyck wrote:
> >> On Wed, Dec 16, 2015 at 2:49 AM, Hannes Reinecke wrote:
> >> > + if (header[0] ==
On Wed, Dec 16, 2015 at 01:54:20PM +, Måns Rullgård wrote:
> Mark Brown writes:
> > I need the patch in a form I can apply.
> I assumed your email client had some way of displaying the message I
> replied to. Guess I was wrong.
My workflow for reviewing and applying patches is based
On 12/16/2015 09:34 PM, Sergei Shtylyov wrote:
To avoid performance overhead when using skb_flow_dissect_flow_keys(),
we switch to the simple parsers to get the IP and port numbers.
Performance comparison: throughput (Gbps):
Number of connections, before patch, after patch
18.56
On 12/12/15 17:09, Moritz König wrote:
This patch makes plx9080.h use kernel types.
Signed-off-by: Moritz König
Signed-off-by: Fabian Lang
---
drivers/staging/comedi/drivers/plx9080.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On 12/16/15, Jeff Merkey wrote:
> Setting the (trap flag | resume flag) inside of an nmi handler results
> in a hard lockup while setting the resume flag works fine.
>
> The watchdog detector fails to detect the lockup. I am currently
> examining the trap gate and interrupt gate setup on Linux
On 12/12/15 17:09, Moritz König wrote:
This patch adds spaces around binary operators in plx9080.h.
Signed-off-by: Moritz König
Signed-off-by: Fabian Lang
---
drivers/staging/comedi/drivers/plx9080.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On 12/12/15 17:09, Moritz König wrote:
This patch fixes the format of comments in plx9080.h.
Signed-off-by: Moritz König
Signed-off-by: Fabian Lang
---
drivers/staging/comedi/drivers/plx9080.h | 132 ++-
1 file changed, 95 insertions(+), 37 deletions(-)
diff
On Wed, Dec 16, 2015 at 1:56 PM, Jan Kara wrote:
> On Mon 07-12-15 11:27:07, Dmitry Vyukov wrote:
>> Hello,
>>
>> While running syzkaller fuzzer on commit
>> 31ade3b83e1821da5fbb2f11b5b3d4ab2ec39db8, I've hit the following UBSAN
>> warning. I think it can lead to an unexpected active wait loop,
We might make bad memory allocations if we get (e.g.) -ENOSYS from
of_clk_get_parent_count().
Noticed by Coverity.
Fixes: f66541ba02d5 ("clk: gpio: Get parent clk names in of_gpio_clk_setup()")
Signed-off-by: Brian Norris
Cc: Jyri Sarha
Cc: Sergej Sawazki
Cc: Stephen Boyd
---
Sorry, I
Hello.
On 12/16/2015 09:03 PM, Haiyang Zhang wrote:
To avoid performance overhead when using skb_flow_dissect_flow_keys(),
we switch to the simple parsers to get the IP and port numbers.
Performance comparison: throughput (Gbps):
Number of connections, before patch, after patch
1
On 12/12/15 22:26, Masanari Iida wrote:
> This patch fix spelling typos found in printk and Kconfig.
>
> Signed-off-by: Masanari Iida
> ---
> drivers/atm/firestream.c| 2 +-
> drivers/crypto/nx/nx-842.c | 2 +-
>
With device tree it is no more possible to reset the PHY at board
level. Furthermore, doing in the driver allow to power down the PHY when
the network interface is no more used.
This reset can't be done at the PHY driver level. The PHY must be able to
answer to the mii bus scan to let the kernel
Reported by Coverity.
Fixes: f66541ba02d5 ("clk: gpio: Get parent clk names in of_gpio_clk_setup()")
Signed-off-by: Brian Norris
Cc: Jyri Sarha
Cc: Sergej Sawazki
Cc: Stephen Boyd
---
drivers/clk/clk-gpio.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Bhuvanchandra DV
commit 6219f432ec037317a77c40910da12a626c34af1c upstream.
Calculate ADCR_VTEMP25 using VTEMP25 at VREFH_ADC 3V3. Existing
calculations consider the typical values
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Corey Minyard
commit 0cfec916e86d881e209de4b4ae9959a6271e6660 upstream.
The timer and thread were not being started for internal messages,
so in interrupt mode if something hung the
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Vladimir Zapolskiy
commit 01bb70ae0b98d266fa3e860482c7ce22fa482a6e upstream.
If common clock framework is configured, the driver generates a warning,
which is fixed by this change:
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Lars-Peter Clausen
commit 785171fd6cd7dcd7ada5a733b6a2d44ec566c3a0 upstream.
While the datasheet for the AD7785 lists 0xXB as the product ID the actual
product ID is 0xX3.
Fix the
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Lars-Peter Clausen
commit 5dcbe97bedd6ba4b0f574a96cc2e293d26f3d857 upstream.
The ad5629/ad5669 are the I2C variant of the ad5628/ad5668, which has a SPI
interface. They are mostly
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Chris Lesiak
commit 0d2f6fd3ffd5e7a447233a57112246bc00064752 upstream.
The Silicon Labs Si7013, Si7020, and Si7021 family of I2C humidity and
temperature sensors deliver 16 bit data
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: David Woodhouse
commit 1bcb49e663f88bccee35b8688e6a3da2bea31fd4 upstream.
The Honeywell HGI80 is a wireless interface to the evohome connected
thermostat. It uses a TI 3410
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Jani Nikula
commit 1b9448b071caa7d10bb2569fabe3020a2c25ae59 upstream.
Unsurprisingly macbooks have backlights, just the VBT doesn't seem to
know it in this case.
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Imre Deak
commit fd0fe6acf1dd88aabfbf383f7e4c16315387a7b7 upstream.
After Damien's D3 fix I started to get runtime suspend residency for the
first time and that revealed a breakage
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: =?UTF-8?q?Petr=20=C5=A0tetiar?=
commit 9d5b5ed796d7afd7e8d2ac4b4fb77c6a49463f4b upstream.
It seems like this device has same vendor and product IDs as G2K
devices, but it has
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Aleksander Morgado
commit e07af133c3e2716db25e3e1e1d9f10c2088e9c1a upstream.
Also known as Verizon U620L.
The device is modeswitched from 1410:9020 to 1410:9022 by selecting the
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Alex Deucher
commit 24dd2f64c5a877392925202321c7c2c46c2b0ddf upstream.
Avoids spew on resume for systems where sysfs may
fail even on init.
bug:
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Thomas Betker
commit a57f8dac46fbac5ab0e31aef1a98b3f6eb30c079 upstream.
The scaling factor for VREFN is 3.0/4096 (not 1.0/4096), just as for
VREFP. This is not immediately obvious
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: =?UTF-8?q?Michel=20D=C3=A4nzer?=
commit 96ea47c0ec8c012509116bee8c57414281428fc4 upstream.
They reportedly cause random GPU hangs.
Bugzilla:
Setting the (trap flag | resume flag) inside of an nmi handler results
in a hard lockup while setting the resume flag works fine.
The watchdog detector fails to detect the lockup. I am currently
examining the trap gate and interrupt gate setup on Linux and if
anyone has any ideas it would be
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: =?UTF-8?q?Bj=C3=B8rn=20Mork?=
commit 59536da34513c594af2a6fd35ba65ea45b6960a1 upstream.
The DEVICE_HWI type was added under the faulty assumption that Huawei
devices based on
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Tadeusz Struk
commit 176155dac13f528e0a58c14dc322623219365d91 upstream.
Bugfix - don't dereference userspace pointer.
Signed-off-by: Tadeusz Struk
Signed-off-by: Herbert Xu
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Mathias Nyman
commit dad67d5f3d0efe01d38c6cebcb6698280e51927b upstream.
Clear device initiated resume variables once device is fully up and running
in U0 state.
Resume needs to be
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Ben McCauley
commit b9e51b2b1fda19143f48d182ed7a2943f21e1ae4 upstream.
In some SoCs, dwc3 is implemented as a USB2.0 only
core, meaning that it can't ever achieve SuperSpeed.
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Rajmohan Mani
commit a5964396190d0c40dd549c23848c282fffa5d1f2 upstream.
Existing Intel xHCI controllers require a delay of 1 mS,
after setting the CMD_RESET bit in command register,
On Wed, Dec 16, 2015 at 09:52:37AM -0800, Dan Williams wrote:
> It's possible that as far as the resource table is concerned the
> resource type might just be "reserved". It may not be until after a
> driver loads that we discover the memory range type. The identifying
> string is driver
301 - 400 of 1744 matches
Mail list logo
