4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Arnaldo Carvalho de Melo
commit ecf1e2253ea79c6204f4d6a5e756e8fb4aed5a7e upstream.
Instead of the one when another syscall takes place while another is being
processed (in another CPU, but we s
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
commit f0e8faa7a5e894b0fc99d24be1b18685a92ea466 upstream.
This function clearly never worked and always returns true,
as pointed out by gcc-7:
arch/arm/mach-ux500/pm.c: In functi
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Saeed Mahameed
commit 6fa26208206c406fa529cd73f7ae6bf4181e270b upstream.
Report the correct speed in the port attributes when using a 56Gbps
ethernet link. Without this change the field is inc
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Dave Martin
commit aeb1f39d814b2e21e5e5706a48834bfd553d0059 upstream.
This patch adds an explicit __reserved[] field to user_fpsimd_state
to replace what was previously unnamed padding.
This e
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Jack Morgenstein
commit befcabcd530e4ffb6f016638f693b7d94986d2ba upstream.
If OpenSM runs over a ConnectX-3, and there are ConnectX-4 or Connect-IB
VFs active on the network, the OpenSM will re
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Madhavan Srinivasan
commit df21d2fa733035e4d414379960f94b2516b41296 upstream.
Test uses PMC2 to count the event. But PMC1 is being initialized.
Patch to fix it.
Fixes: 3752e453f6ba ('selftests
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Leon Romanovsky
commit aa6aae38f7fb2c030f326a6dd10b58fff1851dfa upstream.
The failure in ib_cache_setup_one function during
ib_register_device will leave leaked allocated memory.
Fixes: 03db3a
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Nicolas Iooss
commit 7ec03e60ef81c19b5d3a46dd070ee966774b860f upstream.
Function ite_set_carrier_params() uses variable use_demodulator after
having initialized it to false in some if branches,
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Jiri Olsa
commit 2bd42f3aaa53ebe78b9be6f898b7945dd61f9773 upstream.
There might be systems where MAP_32BIT is not defined, like some some
RHEL7 powerpc versions.
Signed-off-by: Jiri Olsa
Cc:
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Eran Ben Elisha
commit 1f22e454df2eb99ba6b7ace3f594f6805cdf5cbc upstream.
According to the firmware spec, FLOW_STEERING_IB_UC_QP_RANGE command is
supported only if dmfs_ipoib bit is set.
If it
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Eran Ben Elisha
commit 1f22e454df2eb99ba6b7ace3f594f6805cdf5cbc upstream.
According to the firmware spec, FLOW_STEERING_IB_UC_QP_RANGE command is
supported only if dmfs_ipoib bit is set.
If it
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Jack Morgenstein
commit c482af646d0809a8d5e1b7f4398cce3592589b98 upstream.
For non-special QPs, the port value becomes non-zero only at the
RESET-to-INIT transition. If the QP has not undergone
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Kamal Heib
commit 0b59970e7d96edcb3c7f651d9d48e1a59af3c3b0 upstream.
Remove the warning print of "can't use of GFP_NOIO" to avoid prints in
each QP creation when devices aren't supporting IB_QP
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Sriharsha Basavapatna
commit ce1ca7d2d140a1f4aaffd297ac487f246963dd2f upstream.
In rdma_read_chunk_frmr() when ib_post_send() fails, the error code path
invokes ib_dma_unmap_sg() to unmap the s
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Dave Martin
commit 9a17b876b573441bfb3387ad55d98bf7184daf9d upstream.
Ensure that if userspace supplies insufficient data to
PTRACE_SETREGSET to fill all the registers, the thread's old
registe
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit 7a546af50eb78ab99840903083231eb635c8a566 upstream.
Make sure to check for short control transfers in order to avoid parsing
uninitialised buffer data and leaking it to user
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Stefan Schmidt
commit 05a974efa4bdf6e2a150e3f27dc6fcf0a9ad5655 upstream.
>From 4.9 we should really avoid using the stack here as this will not be DMA
able on various platforms. This changes th
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Gu Zheng
commit 497de07d89c1410d76a15bec2bb41f24a2a89f31 upstream.
This change was missed the tmpfs modification in In CVE-2016-7097
commit 073931017b49 ("posix_acl: Clear SGID bit when setting
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Steven Rostedt
commit 8329e818f14926a6040df86b2668568bde342ebf upstream.
Matt Fleming reported seeing crashes when enabling and disabling
function profiling which uses function graph tracer. La
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Bjorn Helgaas
commit 89e9f7bcd8744ea25fcf0ac671b8d72c10d7d790 upstream.
Martin reported that the Supermicro X8DTH-i/6/iF/6F advertises incorrect
host bridge windows via _CRS:
pci_root PNP0A0
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Vladimir Zapolskiy
commit af92305e567b7f4c9cf48b9e46c1f48ec9ffb1fb upstream.
On i.MX31 AVIC interrupt controller base address is at 0x6800.
The problem was shadowed by the AVIC driver, whi
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit 6d104af38b570d37aa32a5803b04c354f8ed513d upstream.
Not all platforms support DMA to the stack, and specifically since v4.9
this is no longer supported on x86 with VMAP_STACK
On Mon, Jan 23, 2017 at 06:24:24PM -0800, Stephen Boyd wrote:
> When the address is invalid, we print out the address that's
> in info.addr, but that member of info hasn't been assigned yet.
> It's assigned in the line after we check the address. This causes
> the print to show something like
>
>
On Mon, 23 Jan 2017, Linus Torvalds wrote:
> For all I know, there may be some security reason why we really don't
> want the automatic helpers, even if they can be convenient.
>
> Also, you can just enable them with a kernel command line or a sysctl,
> so it's not like you can't get the old beha
This patch split alloc_fresh_huge_page_node into 2 parts:
- fast path without __GFP_REPEAT flag
- slow path with __GFP_REPEAT flag
Thus, if there is a server with uneven numa memory layout:
available: 7 nodes (0-6)
node 0 cpus: 0 1 2 3 4 5 6 7
node 0 size: 6603 MB
node 0 free: 91 MB
node 1 cpus:
n
Currently there is no hard limitation for kswapd retry times if no progress
is made. Then kswapd will take 100% for a long time.
In my test, I tried to allocate 4000 hugepages by:
echo 4000 > /proc/sys/vm/nr_hugepages
Then,kswapd will take 100% cpu for a long time.
The numa layout is:
available:
If there is a server with uneven numa memory layout:
available: 7 nodes (0-6)
node 0 cpus: 0 1 2 3 4 5 6 7
node 0 size: 6603 MB
node 0 free: 91 MB
node 1 cpus:
node 1 size: 12527 MB
node 1 free: 157 MB
node 2 cpus:
node 2 size: 15087 MB
node 2 free: 189 MB
node 3 cpus:
node 3 size: 16111 MB
node 3
When there is no reclaimable pages in the zone, even the zone is
not balanced, we let kswapd go sleeping. That is prepare_kswapd_sleep
will return true in this case.
Signed-off-by: Jia He
---
mm/vmscan.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/mm/vmscan.c b/mm/vmsca
On Tue, Jan 24, 2017 at 8:32 AM, Oliver Neukum wrote:
> Am Montag, den 23.01.2017, 19:36 +0100 schrieb Lukáš Lalinský:
>> I have uploaded both captures here -
>> https://gist.github.com/lalinsky/83148a827d5cd43e79e377d8e1b5ed0d
>
> Indeed it is does not set a configuration. Either the capture
> is
On Tue 2017-01-24 15:06:39, Zhang Rui wrote:
> On Mon, Jan 23, 2017 at 03:49:12PM -0800, Guenter Roeck wrote:
> > On Tue, Jan 24, 2017 at 12:26:54AM +0100, Pavel Machek wrote:
> > > Hi!
> > >
> > > > > >I'll try to revert it on the top of v4.10-rc5 now... and yes, it
> > > > > >fixes
> > > > > >t
Hi!
> > > > >I'll try to revert it on the top of v4.10-rc5 now... and yes, it fixes
> > > > >the issue.
> > > > >
> > > > >Any idea what went wrong and how to fix that?
> > > > >
> > > > >Anyway as we are at -rc5 and this is warning fix that caused a
> > > > >regression on different hardware... it
Am Montag, den 23.01.2017, 19:36 +0100 schrieb Lukáš Lalinský:
> On Sat, Jan 21, 2017 at 10:08 AM, Greg Kroah-Hartman
> wrote:
> >
> > Always use scripts/get_maintainer.pl to determine who to send
> > patches
> > to, and what mailing list. You forgot linux-usb@vger, which I've
> > now
> > added.
Kevin Hilman writes:
> Hello,
>
> On Wed, Oct 26, 2016 at 12:41 PM, Robert Jarzmik
> wrote:
>> As the power supply framework provides a way to store and retrieve
>> private supply data, use it.
>>
>> In the process, change the platform data for wm97xx_battery from a
>> container of a single str
On 20 January 2017 at 21:08, Arnd Bergmann wrote:
> I got this new build error on today's linux-next
>
> drivers/mmc/host/s3cmci.h:69:24: error: field 'pio_tasklet' has incomplete
> type
> struct tasklet_struct pio_tasklet;
> drivers/mmc/host/s3cmci.c: In function 's3cmci_enable_irq':
> drivers
Hi brian,
On 01/24/2017 10:31 AM, Brian Norris wrote:
Hi Jeffy,
On Fri, Jan 20, 2017 at 09:52:08PM +0800, Jeffy Chen wrote:
[ 39.044329] do not call blocking ops when !TASK_RUNNING; state=1 set
at [] hidp_session_thread+0x110/0x568 [hidp]
...
[ 40.159664] Call trace:
[ 40.162122] [] __mi
On Mon, Jan 23, 2017 at 03:49:12PM -0800, Guenter Roeck wrote:
> On Tue, Jan 24, 2017 at 12:26:54AM +0100, Pavel Machek wrote:
> > Hi!
> >
> > > > >I'll try to revert it on the top of v4.10-rc5 now... and yes, it fixes
> > > > >the issue.
> > > > >
> > > > >Any idea what went wrong and how to fix
Am 23.01.2017 um 16:24 schrieb Jonathan Corbet :
> On Mon, 23 Jan 2017 15:14:51 +
> Matthew Wilcox wrote:
>
>>> I maintain my own stack of "linuxdoc" with a python version
>>> of the kernel-doc script (hosted on github). It uses the same
>>> regexes as the perl version (using a python rewri
On Wednesday 14 December 2016 01:06 PM, Ingo Molnar wrote:
> * Alexis Berlemont wrote:
>
>> Hi Masami,
>>
>> Many thanks for your mail.
>>
>> Here is another patch set which tries to fix the points you mentioned:
>>
>> * Skip the arguments containing a constant ($123);
>> * Review the code in c
Commit a389fcfd2cb5 ("Drivers: hv: vmbus: Fix signaling logic in
hv_need_to_signal_on_read()")
added the proper mb(), but removed the test "prev_write_sz < pending_sz"
when making the signal decision.
As a result, the guest can signal the host unnecessarily,
and then the host can throttle the gu
On Mon, Jan 23, 2017 at 5:27 AM, Arnaldo Carvalho de Melo
wrote:
> Em Sun, Jan 22, 2017 at 02:51:25PM -0800, Alexei Starovoitov escreveu:
>> On Sat, Jan 21, 2017 at 07:51:43AM +0300, Dan Carpenter wrote:
>> > max_key is a value in the 0-63 range, so on 32 bit systems the shift
>> > could wrap.
>>
Hi Stephen,
Sorry I did not get to v1 and v2 in a timely manner.
On 01/23/17 12:48, Stephen Boyd wrote:
> Platforms like 96boards have a standardized connector/expansion
> slot that exposes signals like GPIOs to expansion boards in an
> SoC agnostic way. We'd like the DT overlays for the expansi
Hi Lee,
On Mon, Jan 23, 2017 at 4:12 AM, Lee Jones wrote:
> Arm, IIO and PWM Maintainers,
>
> Enjoy!
>
> The following changes since commit 7ce7d89f48834cefece7804d38fc5d85382edf77:
>
> Linux 4.10-rc1 (2016-12-25 16:13:08 -0800)
>
> are available in the git repository at:
>
> git://git.kernel
There are some special ISA/LPC devices that work on a specific I/O range where
it is not correct to specify a 'ranges' property in DTS parent node as cpu
addresses translated from DTS node are only for memory space on some
architectures, such as Arm64. Without the parent 'ranges' property, current
Low-pin-count interface is integrated into some SoCs. The accesses to those
peripherals under LPC make use of I/O ports rather than the memory mapped I/O.
To drive these devices, this patch introduces a method named indirect-IO.
In this method the in/out() accessor in include/asm-generic/io.h will
This patch supports the IPMI-bt device attached to the Low-Pin-Count interface
implemented on Hisilicon Hip06/Hip07 SoC.
---
| LPC host|
| |
---
|
After indirect-IO is introduced, system must can assigned indirect-IO devices
with logical I/O ranges which are different from those for PCI I/O devices.
Otherwise, I/O accessors can't identify whether the I/O port is for memory
mapped I/O or indirect-IO.
As current helper, pci_register_io_range(),
The low-pin-count(LPC) interface of Hip06/Hip07 accesses the peripherals in
I/O port addresses. This patch implements the LPC host controller driver which
perform the I/O operations on the underlying hardware.
We don't want to touch those existing peripherals' driver, such as ipmi-bt. So
this drive
The patch update the _CRS of LPC children with the system logical I/O resource
after the translation from LPC-local I/O. Then the ACPI platform device
enumeration for LPC can apply the right I/O resource to request the system I/O
space.
Signed-off-by: zhichang.yuan
---
drivers/bus/hisi_lpc.c |
On 2017년 01월 24일 12:51, MyungJoo Ham wrote:
>> The devfreq using passive governor is not able to change the governor.
>> So, the user can not change the governor through 'available_governor' sysfs
>> entry. Also, the devfreq which don't use the passive governor is not able to
>> change to 'passive'
On 01/23/2017 05:50 PM, Arnd Bergmann wrote:
The of_node member in struct drm_bridge is hidden when CONFIG_OF
is disabled, causing a build error:
drivers/gpu/drm/bridge/dw-hdmi.c: In function '__dw_hdmi_probe':
drivers/gpu/drm/bridge/dw-hdmi.c:2063:14: error: 'struct drm_bridge' has no
member
Hi Linus,
v2 simply fixes an issue identified by the kbuild test robot. v1 is available
at: https://lkml.org/lkml/2017/1/23/12
This short series resolves a TODO comment in the Aspeed GPIO driver regarding
banks Y, Z, AA, AB and AC by implementing their support. It's a little involved
given some o
This is less straight-forward than one would hope, as some banks only
have 4 pins rather than 8, others are output only, yet more (W and
X, already supported) are input-only, and in the case of the g4 SoC bank
AC doesn't exist.
Add some structs to describe the varying properties of different banks
From: Joel Stanley
The Aspeed SoCs have more GPIOs than can be represented with A-Z. The
documentation uses two letter names such as AA and AB, so make the names
a three-character array in the bank struct to accommodate this.
Signed-off-by: Joel Stanley
Signed-off-by: Andrew Jeffery
---
drive
On Tue, 2017-01-24 at 10:32 +0800, Chen-Yu Tsai wrote:
> Hi everyone,
Hi!
Thanks for working on that!
You might want to bump the copyright year starting from patch 5.
[...]
Päikest,
Priit Laes
Hi, Bibby:
On Tue, 2017-01-24 at 13:10 +0800, Bibby Hsieh wrote:
> Current Mediatek DRM driver does not support interlaced mode, and
> will hang if such resolution is used: Filter those to prevent
> kernel hangs, until the DRM driver is fixed properly.
>
> Signed-off-by: Bibby Hsieh
Acked-by: C
Hi all,
Changes since 20170123:
The net-next tree gained a conflict against the net tree.
The drm tree gained a build failure so I used the version from
next-20170123.
The mfd tree gained a conflict against the arm-soc tree.
The kselftest tree gained a conflict against the net-next tree.
Non
On Mon, Jan 23, 2017 at 08:44:53PM +0100, Paolo Bonzini wrote:
> If you just implement getclock64 the PTP_SYS_OFFSET output:
>
> device clock | |sample2| |sample4| |sample6| ...
> -
> realtime clock |sample1| |sa
Hi, Bibby:
On Tue, 2017-01-24 at 12:40 +0800, Bibby Hsieh wrote:
> MT8173 overlay can support UYVY and YUYV format,
> we add the format in DRM driver.
>
> Signed-off-by: Bibby Hsieh
> Reviewed-by: Daniel Kurtz
Acked-by: CK Hu
> ---
> drivers/gpu/drm/mediatek/mtk_disp_ovl.c | 7 +++
> d
In a TPM2, sessions can be globally exhausted once there are
TPM_PT_ACTIVE_SESSION_MAX of them (even if they're all context saved).
The Strategy for handling this is to keep a global count of all the
sessions along with their creation time. Then if we see the TPM run
out of sessions (via the TPM_R
commit 4a9d4b024a31 ("switch fput to task_work_add") implements a
schedule_work() for completing fput(), but did not guarantee calling
__fput() after unpacking initramfs. Because of this, there is a
possibility that during boot a driver can see ETXTBSY when it tries
to load a binary from initramfs
sessions are different from transient objects in that their handles
may not be virtualized (because they're used for some hmac
calculations). Additionally when a session is context saved, a
vestigial memory remains in the TPM and if it is also flushed, that
will be lost and the session context wil
These two patches are easily separated. The first does session
handling. This incarnation uses TPM_RC_REFERENCE_H0 errors from
context save or load to signal when a session has been flushed (so it
no longer does tracking or flush emulation). The second patch does
management for session exhaustio
Give me a link to hoke up with u
On 1/23/17, mutizwaro...@gmail.com wrote:
> Asian_Girls_Looking_for_Serious_Dating
>
>
> GO_HERE
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> '-unsub-' [image]
Hi, YT:
On Mon, 2017-01-23 at 19:05 +0800, YT Shen wrote:
> This patch update enable/disable flow of DSI module.
> Original flow works on there is a bridge chip: DSI -> bridge -> panel.
> In this case: DSI -> panel, the DSI sub driver flow should be updated.
> We need to initialize DSI first so th
Here, If ioremap_nocache will fail. It will return NULL.
Kernel can run into a NULL-pointer dereference.
This error check will avoid NULL pointer dereference.
Signed-off-by: Arvind Yadav
---
sound/pci/ymfpci/ymfpci_main.c | 4
1 file changed, 4 insertions(+)
diff --git a/sound/pci/ymfpci/y
On Mon, Jan 23, 2017 at 09:06:20PM -0200, Marcelo Tosatti wrote:
> Can you please describe what problem exists with this scheme?
This new kernel code exists just because chrony doesn't implement the
PRECISE ioctl. Instead of adding new "fake" modes, just teach chrony
about the better method.
I p
On Tue, 2017-01-24 at 05:18 +, Valo, Kalle wrote:
> Joe Perches writes:
>
> > On Mon, 2017-01-23 at 15:04 +, Srinivas Kandagatla wrote:
> > > use dma_zalloc_coherent() instead of dma_alloc_coherent and memset().
> >
> > []
> > > diff --git a/drivers/net/wireless/ath/ath10k/pci.c
> > > b
Hello Peter, Mikulas
just came across this patch https://lkml.org/lkml/2016/5/17/440
Peter, are you still planning to merge it? or is there something
that made you change your mind?
-ss
Joe Perches writes:
> On Mon, 2017-01-23 at 15:04 +, Srinivas Kandagatla wrote:
>> use dma_zalloc_coherent() instead of dma_alloc_coherent and memset().
> []
>> diff --git a/drivers/net/wireless/ath/ath10k/pci.c
>> b/drivers/net/wireless/ath/ath10k/pci.c
> []
>> @@ -896,7 +896,7 @@ static in
On Mon, Jan 23, 2017 at 06:38:42PM -0800, Dave Hansen wrote:
> On 01/23/2017 06:09 PM, Kevin Hao wrote:
> > On Mon, Jan 23, 2017 at 06:01:10PM -0800, Dave Hansen wrote:
> >> On 01/23/2017 05:50 PM, Kevin Hao wrote:
> >>> According to the ISA manual, XSAVES also set the XCOMP_BV[62:0]. My code
> >>
Hi Mark
On 24 January 2017 at 02:54, Mark Rutland wrote:
> Hi,
>
> On Wed, Jan 18, 2017 at 09:25:24PM +0800, fu@linaro.org wrote:
>> From: Fu Wei
>>
>> This patchset:
>> (1)Preparation for adding GTDT support in arm_arch_timer:
>> 1. Clean up printk() usage
>> 2. Rename t
Current Mediatek DRM driver does not support interlaced mode, and
will hang if such resolution is used: Filter those to prevent
kernel hangs, until the DRM driver is fixed properly.
Signed-off-by: Bibby Hsieh
---
drivers/gpu/drm/mediatek/mtk_hdmi.c | 2 ++
1 file changed, 2 insertions(+)
diff -
Hi Ingo,
On 01/22/2017 05:31 PM, Ingo Molnar wrote:
> * Lu Baolu wrote:
>
>> xHCI debug capability (DbC) is an optional but standalone
>> functionality provided by an xHCI host controller. Software
>> learns this capability by walking through the extended
>> capability list of the host. xHCI spec
Hi Shuah,
Today's linux-next merge of the kselftest tree got a conflict in:
tools/testing/selftests/bpf/Makefile
between commit:
4d3381f5a322 ("bpf: Add tests for the lpm trie map")
from the net-next tree and commit:
88baa78d1f31 ("selftests: remove duplicated all and clean target")
fr
Hi Ingo,
On 01/22/2017 05:04 PM, Ingo Molnar wrote:
> * Lu Baolu wrote:
>
+static void xdbc_runtime_delay(unsigned long count)
+{
+ udelay(count);
+}
+static void (*xdbc_delay)(unsigned long) = xdbc_early_delay;
>>> Is this udelay() complication really necessary? udelay(
MT8173 overlay can support UYVY and YUYV format,
we add the format in DRM driver.
Signed-off-by: Bibby Hsieh
Reviewed-by: Daniel Kurtz
---
drivers/gpu/drm/mediatek/mtk_disp_ovl.c | 7 +++
drivers/gpu/drm/mediatek/mtk_drm_plane.c | 2 ++
2 files changed, 9 insertions(+)
diff --git a/driver
Hello,
Applied to f2fs.git.
Thanks,
On 01/24, Masanari Iida wrote:
> This patch fix a typo in f2fs.txt
>
> Signed-off-by: Masanari Iida
> ---
> Documentation/filesystems/f2fs.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/filesystems/f2fs.txt
> b/
Hi Chao,
On 01/22, Chao Yu wrote:
> In scenario of intensively node allocation, free nids will be ran out
> soon, then it needs to stop to load free nids by traversing NAT blocks,
> in worse case, if NAT blocks does not be cached in memory, it generates
> IOs which slows down our foreground operat
It looks like bnep_session has same pattern as the issue reported in
old rfcomm:
while (1) {
set_current_state(TASK_INTERRUPTIBLE);
if (condition)
break;
// may call might_sleep here
schedule();
It looks like cmtp_session has same pattern as the issue reported in
old rfcomm:
while (1) {
set_current_state(TASK_INTERRUPTIBLE);
if (condition)
break;
// may call might_sleep here
schedule();
It looks like hidp_session_thread has same pattern as the issue reported in
old rfcomm:
while (1) {
set_current_state(TASK_INTERRUPTIBLE);
if (condition)
break;
// may call might_sleep here
schedule();
> The devfreq using passive governor is not able to change the governor.
> So, the user can not change the governor through 'available_governor' sysfs
> entry. Also, the devfreq which don't use the passive governor is not able to
> change to 'passive' governor on the fly.
Another thoughts on the c
This patch fix a typo in f2fs.txt
Signed-off-by: Masanari Iida
---
Documentation/filesystems/f2fs.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/filesystems/f2fs.txt
b/Documentation/filesystems/f2fs.txt
index d99faced79cb..0ab33d4c8406 100644
--- a/Documen
> This patch just adds the simple log to show the PPMU device's registration
> during the kernel booting.
>
> Signed-off-by: Chanwoo Choi
> ---
> drivers/devfreq/event/exynos-ppmu.c | 3 +++
> 1 file changed, 3 insertions(+)
>
Applied in for-next
> This patch fixes the wrong description of governor_userspace.c
> and removes the unneeded blank line.
>
> Signed-off-by: Chanwoo Choi
> ---
Applied in for-next
> The _remove_devfreq() releases the all resources of the devfreq
> device. This function is only called in the devfreq_dev_release().
> For that reason, the devfreq core doesn't need to leave the
> _remove_devfreq() separately. This patch releases the all
> resources in the devfreq_dev_release() a
> Until now, the trans_stat information of passive devfreq is not updated.
> This patch updates the trans_stat information after setting the target
> frequency of passive devfreq device.
Acked-by: MyungJoo Ham
>
> Fixes: 996133119f57 ("PM / devfreq: Add new passive governor")
> Cc: sta...@vger.
> Yeah, we did have this same conversation awhile back, didn't we?
>
> Back then, did I think to ask if this could be minimized or even prevented
> by adding memory barriers appropriately? ;-)
>
> Thanx, Paul
Yes, it can be fixed by adding a
We may be able to see invalid Broadcom tags when the hardware and drivers are
misconfigured, or just while exercising the error path. Instead of flooding
the console with messages, flat out drop the packet.
Signed-off-by: Florian Fainelli
---
net/dsa/tag_brcm.c | 3 ++-
1 file changed, 2 inserti
These are part of the vc4 display pipeline.
Signed-off-by: Eric Anholt
---
.../devicetree/bindings/display/brcm,bcm-vc4.txt | 35 ++
1 file changed, 35 insertions(+)
diff --git a/Documentation/devicetree/bindings/display/brcm,bcm-vc4.txt
b/Documentation/devicetree/binding
The DSI0 and DSI1 blocks on the 2835 are related hardware blocks.
Some registers move around, and the featureset is slightly different,
as DSI1 (the 4-lane DSI) is a later version of the hardware block.
This driver doesn't yet enable DSI0, since we don't have any hardware
to test against, but it do
This is a resend from a month ago of just two of the patches (several
are accepted at this point) from the DSI series, hoping to collect an
ack from DT. Ccing the clock folks as well, since this ends up being
a clock provider.
Eric Anholt (2):
dt-bindings: Document the VC4 DSI module nodes.
d
On Tue, Jan 24, 2017 at 9:35 AM, Bibby Hsieh wrote:
>
> Hi, Daniel,
>
> Thanks for your comment.
>
> On Tue, 2017-01-03 at 14:27 +0800, Daniel Kurtz wrote:
> > On Fri, Dec 30, 2016 at 2:26 PM, Bibby Hsieh
> > wrote:
> > >
> > > MT8173 overlay can support UYVY and YUYV format,
> > > we add the fo
On Mon, Jan 23, 2017 at 07:12:03PM +1100, Michael Ellerman wrote:
> "Paul E. McKenney" writes:
>
> > On Sat, Jan 14, 2017 at 11:54:17AM -0800, Paul E. McKenney wrote:
> >> On Sat, Jan 14, 2017 at 10:35:50AM +0100, Ingo Molnar wrote:
> >> > * Paul E. McKenney wrote:
> >
> > [ . . . ]
> >
> >> > >
On Mon, Jan 23, 2017 at 01:50:32PM -0800, Linus Torvalds wrote:
> On Mon, Jan 23, 2017 at 7:05 AM, Michael S. Tsirkin wrote:
> >
> > virtio, vhost: fixes, cleanups
>
> Was there a reason why you sent this twice?
>
> Or was this *supposed* to be the ARM DMA fix pull request? Because it wasn't.
>
On 01/23/2017 08:49 PM, John Keeping wrote:
Hi Chris,
On Mon, 23 Jan 2017 09:38:54 +0800, Chris Zhong wrote:
On 01/22/2017 12:31 AM, John Keeping wrote:
The multiplication ratio for the PLL is required to be even due to the
use of a "by 2 pre-scaler". Currently we are likely to end up with
Hi all,
Today's linux-next merge of the mfd tree got a conflict in:
arch/arm/boot/dts/stm32f429.dtsi
between commits:
3604ef9c8154 ("ARM: dts: stm32: Add ADC support to stm32f429")
dd3feb755a4a ("ARM: dts: stm32: Add RTC support for STM32F429 MCU")
from the arm-soc tree and commit:
90
The dw-mipi-dsi of rk3399 is almost the same as rk3288, the rk3399 has
additional phy config clock.
Signed-off-by: Chris Zhong
Acked-by: Rob Herring
---
Changes in v4: None
Changes in v3: None
.../devicetree/bindings/display/rockchip/dw_mipi_dsi_rockchip.txt | 4 +++-
1 file changed, 3 in
Signed-off-by: Chris Zhong
Acked-by: Rob Herring
---
Changes in v4: None
Changes in v3: None
.../devicetree/bindings/display/rockchip/dw_mipi_dsi_rockchip.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git
a/Documentation/devicetree/bindings/display/rockchip/dw_mipi_dsi_rockchip.tx
Reference the power domain incase dw-mipi power down when
in use.
Signed-off-by: Chris Zhong
Reviewed-by: Sean Paul
---
Changes in v4: None
Changes in v3: None
drivers/gpu/drm/rockchip/dw-mipi-dsi.c | 16
1 file changed, 16 insertions(+)
diff --git a/drivers/gpu/drm/rockchip
1 - 100 of 823 matches
Mail list logo
