On Sat, 24 Aug 2019 at 07:53, Hans de Goede wrote:
>
> To avoid problems like this, this commit adds a new
> gpiolib_acpi_run_edge_events_on_boot kernel commandline option which
> can be "on", "off", or "auto" (default).
>
> In auto mode the default is on and a DMI based blacklist is used,
> the
Hi Hans and everyone,
On Mon, 19 Aug 2019 at 04:59, Hans de Goede wrote:
>
> Hi Ian, et. al.,
>
> As such I guess we may need to go with the blacklist patch you suggested
> which sucks, but having these devices not boot sucks even harder.
>
> I guess this problem did not magically fix it self in
a...@vger.kernel.org
Signed-off-by: Ian W MORRISON
Reviewed-by: Hans de Goede
Reviewed-by: Andy Shevchenko
---
drivers/gpio/gpiolib-acpi.c | 33 +++--
1 file changed, 27 insertions(+), 6 deletions(-)
diff --git a/drivers/gpio/gpiolib-acpi.c b/drivers/gpio/gpiolib-acpi.
a...@vger.kernel.org
Signed-off-by: Ian W MORRISON
---
drivers/gpio/gpiolib-acpi.c | 28 +++-
1 file changed, 23 insertions(+), 5 deletions(-)
diff --git a/drivers/gpio/gpiolib-acpi.c b/drivers/gpio/gpiolib-acpi.c
index 259cf6ab969b..8d855dc9b020 100644
--- a/drivers/gpio/
a default of for these devices.
Signed-off-by: Ian W MORRISON
---
drivers/bluetooth/hci_h5.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/bluetooth/hci_h5.c b/drivers/bluetooth/hci_h5.c
index 8eede1197cd2..cce422dc1b8d 100644
--- a/drivers/bluetooth/hci_h5.c
+++ b/drivers
a default of for these devices.
Signed-off-by: Ian W MORRISON
---
drivers/bluetooth/hci_h5.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/bluetooth/hci_h5.c b/drivers/bluetooth/hci_h5.c
index 8eede1197cd2..cce422dc1b8d 100644
--- a/drivers/bluetooth/hci_h5.c
+++ b/drivers
-reviews/jtpHvZOfZ-Q).
It is important to similarly include in the mainline and stable kernels to
facilitate various distros that are now raising bug reports (for example:
https://bugs.launchpad.net/intel/+bug/1760545).
Many thanks,
Ian
On Sun, 22 Apr 2018 at 08:46, Ian W MORRISON <ianwmo
-reviews/jtpHvZOfZ-Q).
It is important to similarly include in the mainline and stable kernels to
facilitate various distros that are now raising bug reports (for example:
https://bugs.launchpad.net/intel/+bug/1760545).
Many thanks,
Ian
On Sun, 22 Apr 2018 at 08:46, Ian W MORRISON wrote:
> On
On 21 April 2018 at 11:22, Botello Ortega, Luis
wrote:
> Hi all:
>
> We tested GLK DMC 1.04 FW in last week of September 2017, using the latest
> drm-tip version for that time (4.14.0-rc2) and according to our results we
> could declare this FW as acceptable and
On 21 April 2018 at 11:22, Botello Ortega, Luis
wrote:
> Hi all:
>
> We tested GLK DMC 1.04 FW in last week of September 2017, using the latest
> drm-tip version for that time (4.14.0-rc2) and according to our results we
> could declare this FW as acceptable and healthy to be used with kernel
On 20 April 2018 at 17:50, Jani Nikula <jani.nik...@linux.intel.com> wrote:
> On Fri, 20 Apr 2018, Ian W MORRISON <ianwmorri...@gmail.com> wrote:
>> I've performed backport testing and some additional analysis as follows:
>
> What testing did you do beyond booting? Did
On 20 April 2018 at 17:50, Jani Nikula wrote:
> On Fri, 20 Apr 2018, Ian W MORRISON wrote:
>> I've performed backport testing and some additional analysis as follows:
>
> What testing did you do beyond booting? Did you run igt?
>
> BR,
> Jani.
I did some basic testin
t;From: Jani Nikula [mailto:jani.nik...@linux.intel.com]
>> >>Sent: Wednesday, April 11, 2018 5:27 AM
>> >>To: Ian W MORRISON <ianwmorri...@gmail.com>
>> >>Cc: Vivi, Rodrigo <rodrigo.v...@intel.com>; Srivatsa, Anusha
>> >><anusha.sri
On 18 April 2018 at 00:14, Joonas Lahtinen
wrote:
> Quoting Jani Nikula (2018-04-17 12:02:52)
>> On Mon, 16 Apr 2018, "Srivatsa, Anusha" wrote:
>> >>-Original Message-
>> >>From: Jani Nikula [mailto:jani.nik...@linux.intel.com]
>> >>
On 11 April 2018 at 22:27, Jani Nikula <jani.nik...@linux.intel.com> wrote:
> On Wed, 11 Apr 2018, Ian W MORRISON <ianwmorri...@gmail.com> wrote:
>>
>>
>>>
>>> NAK on indiscriminate Cc: stable. There are zero guarantees that older
>>> kern
On 11 April 2018 at 22:27, Jani Nikula wrote:
> On Wed, 11 Apr 2018, Ian W MORRISON wrote:
>>
>>
>>>
>>> NAK on indiscriminate Cc: stable. There are zero guarantees that older
>>> kernels will work with whatever firmware you throw at them.
>>&g
>
> NAK on indiscriminate Cc: stable. There are zero guarantees that older
> kernels will work with whatever firmware you throw at them.
>
I included 'Cc: stable' so the patch would get added to the v4.16 and
v4.15 kernels
which I have tested with the patch. I found that earlier kernels
didn't
>
> NAK on indiscriminate Cc: stable. There are zero guarantees that older
> kernels will work with whatever firmware you throw at them.
>
I included 'Cc: stable' so the patch would get added to the v4.16 and
v4.15 kernels
which I have tested with the patch. I found that earlier kernels
didn't
On 14 June 2017 at 00:36, Dan Carpenter wrote:
> Kernel style is to have spaces around the operators. This is staging
> code so we do all the style fixes. We don't always update older drivers
> but sometimes we do. No one is planning to change those drivers though
>
On 14 June 2017 at 00:36, Dan Carpenter wrote:
> Kernel style is to have spaces around the operators. This is staging
> code so we do all the style fixes. We don't always update older drivers
> but sometimes we do. No one is planning to change those drivers though
> so I guess the answer is no
On 12 June 2017 at 20:46, Fabian Wolff wrote:
> This patch adds spaces around the binary operators '-' and '+', which
> is the preferred style, and reformats a pointer argument declaration
> to fix a false positive "spaces preferred around that '*'" message
> reported by
On 12 June 2017 at 20:46, Fabian Wolff wrote:
> This patch adds spaces around the binary operators '-' and '+', which
> is the preferred style, and reformats a pointer argument declaration
> to fix a false positive "spaces preferred around that '*'" message
> reported by checkpatch.pl.
>
>
On 2 June 2017 at 00:48, Ian W MORRISON <ianwmorri...@gmail.com> wrote:
> On 6/1/17 5:49 PM, Ian W MORRISON wrote:
>> On 31 May 2017 at 10:53, Doug Smythies <dsmyth...@telus.net> wrote:
>>> Note Before:
>>> I might not have the address list correct, as
On 2 June 2017 at 00:48, Ian W MORRISON wrote:
> On 6/1/17 5:49 PM, Ian W MORRISON wrote:
>> On 31 May 2017 at 10:53, Doug Smythies wrote:
>>> Note Before:
>>> I might not have the address list correct, as I have re-created this
>>> e-mail from the web page ar
On 6/1/17 5:49 PM, Ian W MORRISON wrote:
> On 31 May 2017 at 10:53, Doug Smythies <dsmyth...@telus.net> wrote:
>> Note Before:
>> I might not have the address list correct, as I have re-created this
>> e-mail from the web page archive, having found the thread af
On 6/1/17 5:49 PM, Ian W MORRISON wrote:
> On 31 May 2017 at 10:53, Doug Smythies wrote:
>> Note Before:
>> I might not have the address list correct, as I have re-created this
>> e-mail from the web page archive, having found the thread after bisecting the
>> kernel.
&
On 31 May 2017 at 10:53, Doug Smythies wrote:
> Note Before:
> I might not have the address list correct, as I have re-created this
> e-mail from the web page archive, having found the thread after bisecting the
> kernel.
>
> On 2017.05.29 18:50:57 -0400 (EDT) Mikulas Patocka
On 31 May 2017 at 10:53, Doug Smythies wrote:
> Note Before:
> I might not have the address list correct, as I have re-created this
> e-mail from the web page archive, having found the thread after bisecting the
> kernel.
>
> On 2017.05.29 18:50:57 -0400 (EDT) Mikulas Patocka wrote:
>> On Sun, 28
On 9 May 2017 at 00:42, Andy Shevchenko <andy.shevche...@gmail.com> wrote:
> On Sun, May 7, 2017 at 1:04 PM, Ian W MORRISON <ianwmorri...@gmail.com> wrote:
>
> What are you trying to achieve by posting this patch over and over so often?
>
> Version 5 look pretty go
On 9 May 2017 at 00:42, Andy Shevchenko wrote:
> On Sun, May 7, 2017 at 1:04 PM, Ian W MORRISON wrote:
>
> What are you trying to achieve by posting this patch over and over so often?
>
> Version 5 look pretty good to me. Just stop posting it again and wait
> when Greg t
A re-positioned call to kfree() in
drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c
causes a segmentation error. This patch removed the kfree() call.
Fixes 6557ddfec348 ("staging: rtl8723bs: Fix various errors in
os_dep/ioctl_cfg80211.c")
Signed-off-by: Ian W Morrison <ianwmorri
A re-positioned call to kfree() in
drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c
causes a segmentation error. This patch removed the kfree() call.
Fixes 6557ddfec348 ("staging: rtl8723bs: Fix various errors in
os_dep/ioctl_cfg80211.c")
Signed-off-by: Ian W Morrison
Reviewed-b
(version 5) has tabs rather than spaces, no
wrap around, a changelog and a sign-off email.
Reviewed-by: Hans de Goede <hdego...@redhat.com>
Signed-off-by: Ian W Morrison <ianwmorri...@gmail.com>
---
drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c | 1 -
1 file changed, 1 deletion(-)
(version 5) has tabs rather than spaces, no
wrap around, a changelog and a sign-off email.
Reviewed-by: Hans de Goede
Signed-off-by: Ian W Morrison
---
drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211
(version 4) has tabs rather than spaces, no
wrap around and a changelog. The patch has received one review:
Patch looks good to me:
Reviewed-by: Hans de Goede <hdego...@redhat.com>
Signed-off-by: Ian W Morrison <linux...@linuxium.com.au>
---
drivers/staging/rtl8723bs/os_dep/ioctl_cfg8021
(version 4) has tabs rather than spaces, no
wrap around and a changelog. The patch has received one review:
Patch looks good to me:
Reviewed-by: Hans de Goede
Signed-off-by: Ian W Morrison
---
drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c | 1 -
1 file changed, 1 deletion(-)
diff --git
(version 3) has tabs rather than spaces and no wrap
around. The patch has received one review:
Patch looks good to me:
Reviewed-by: Hans de Goede <hdego...@redhat.com>
Regards,
Ian
From: Ian W Morrison <linux...@linuxium.com.au>
Date: Fri, 28 Apr 2017 02:20:38 +1000
Subject: [PATCH] stagin
(version 3) has tabs rather than spaces and no wrap
around. The patch has received one review:
Patch looks good to me:
Reviewed-by: Hans de Goede
Regards,
Ian
From: Ian W Morrison
Date: Fri, 28 Apr 2017 02:20:38 +1000
Subject: [PATCH] staging: rtl8723bs: remove a call to kfree in
os_dep
On 5/6/17 11:41 PM, Greg KH wrote:
On Sat, May 06, 2017 at 06:00:24PM +1000, Ian W MORRISON wrote:
The kernel when booted with Ubuntu 17.04 results in an unusable system
however with the following patch booting is successful and the system
is usable. The patch and kernel builds have been
On 5/6/17 11:41 PM, Greg KH wrote:
On Sat, May 06, 2017 at 06:00:24PM +1000, Ian W MORRISON wrote:
The kernel when booted with Ubuntu 17.04 results in an unusable system
however with the following patch booting is successful and the system
is usable. The patch and kernel builds have been
hen booted with Ubuntu 17.04 results in an unusable system
however with the following patch booting is successful and the system
is usable. The patch and kernel builds have been tested against on an
Intel Compute Stick (STCK1A32WFC model).
Regards,
Ian
From: Ian W Morrison <linux...@linuxium.co
results in an unusable system
however with the following patch booting is successful and the system
is usable. The patch and kernel builds have been tested against on an
Intel Compute Stick (STCK1A32WFC model).
Regards,
Ian
From: Ian W Morrison
Date: Fri, 28 Apr 2017 02:20:38 +1000
Subject: [PATCH] staging
42 matches
Mail list logo