0) and
802.15.4 interfaces (such as lowpan0) as they both use the same 6lowpan
sources for compression and decompression.
Signed-off-by: Michael Scott
---
net/6lowpan/iphc.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/net/6lowpan/iphc.c b/net/6lowpan/iphc.c
index 6b1042e21656..52fad5dad9f7
han() know when a new lowpan_btle_dev is passed
in so that it only performs the delay work initialization when needed.
Signed-off-by: Michael Scott
---
net/bluetooth/6lowpan.c | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/net/bluetooth/6lowpan.c b/net/blueto
spend/resume was called. So, this generates a
"use after free" issue that was noticed while running kernel tests
with KASAN debug enabled.
Let's eliminate the status field entirely as we can use the channel
tx_credits to indicate whether we should return EAGAIN when handling
packets.
Si
son
- Data was then adjusted per QCOM MSM8994v2 documentation for Top Level
Multiplexing
- Bindings documentation was based on qcom,msm8996-pinctrl.txt by
Joonwoo Park and then modified for msm8994
content
Signed-off-by: Michael Scott
Tested-by: Jeremy McNicoll
Acked-by: Bjorn Andersson
A
On 11/02/2016 11:36 AM, Stephen Boyd wrote:
On 11/01, Michael Scott wrote:
On 11/01/2016 04:53 PM, Stephen Boyd wrote:
On 10/31, Michael Scott wrote:
+
+static const struct msm_pingroup msm8994_groups[] = {
+ PINGROUP(0, blsp_spi1, blsp_uart1, blsp_uim1, NA, NA, NA, NA, NA, NA
On 11/01/2016 04:53 PM, Stephen Boyd wrote:
On 10/31, Michael Scott wrote:
+
+static const struct msm_pingroup msm8994_groups[] = {
+ PINGROUP(0, blsp_spi1, blsp_uart1, blsp_uim1, NA, NA, NA, NA, NA, NA,
+NA, NA),
I see an hdmi_rcv group here after blsp_uim1. Please
ndersson
- Data was then adjusted per QCOM MSM8994 documentation for Top Level
Multiplexing
- Bindings documentation was based on qcom,msm8996-pinctrl.txt by
Joonwoo Park and then modified for msm8994
content
Signed-off-by: Michael Scott
Tested-by: Jeremy McNicoll
Acked-by: Bjorn Ande
ndersson
- Data was then adjusted per QCOM MSM8994 documentation for Top Level
Multiplexing
- Bindings documentation was based on qcom,msm8996-pinctrl.txt by
Joonwoo Park and then modified for msm8994 content
Signed-off-by: Michael Scott
Tested-by: Jeremy McNicoll
Acked-by: Bjorn Andersson
A
On 10/31/2016 08:45 AM, Hashcode wrote:
From: Michael Scott
Initial pinctrl driver for QCOM msm8994 platforms.
In order to continue the initial board support for QCOM msm8994/msm8992
presented in patches from Jeremy McNicoll , let's put
a proper pinctrl driver in place.
Currently, t
Resending: The mailing lists bounced due me being silly and replying on
my phone.
Please reply to this email instead of the last one.
On 10/29/2016 01:27 AM, Linus Walleij wrote:
On Thu, Oct 27, 2016 at 1:32 AM, Michael Scott wrote:
Initial pinctrl driver for QCOM msm8994 platforms.
In
ndersson
- Data was then adjusted per QCOM MSM8994 documentation for Top Level
Multiplexing
- Bindings documentation was based on qcom,msm8996-pinctrl.txt by
Joonwoo Park and then modified for msm8994 content
Signed-off-by: Michael Scott
---
V1 -> V2: fixed missing FUNCTION(nav_pps) and
When running checkpatch.pl on a new pinctrl driver in
drivers/pinctrl/qcom, I noticed a warning about creating
a new maintainer. The drivers/pinctrl/qcom folder doesn't have
anyone assigned in the MAINTAINERS file.
Let's assign it to ARM/QUALCOMM SUPPORT.
Signed-off-by: Mic
ndersson
- Data was then adjusted per QCOM MSM8994 documentation for Top Level
Multiplexing
- Bindings documentation was based on qcom,msm8996-pinctrl.txt by
Joonwoo Park and then modified for msm8994 content
Signed-off-by: Michael Scott
---
.../bindings/pinctrl/qcom,msm8994-pinctrl.txt
the
new_value in the constraints list would be duplicated.
Signed-off-by: Michael Scott
---
kernel/power/qos.c | 6 --
1 file changed, 6 deletions(-)
diff --git a/kernel/power/qos.c b/kernel/power/qos.c
index 25cf89b..8703fc7 100644
--- a/kernel/power/qos.c
+++ b/kernel/power/qos.c
@@ -369,12 +36
14 matches
Mail list logo
