On Wed, Sep 05, 2018 at 03:46:12PM +0800, Anson Huang wrote:
> Add i.MX6QDL SabreAuto board's gpio keys support, there
> are 5 gpio keys on base board:
>
> SW3: KEY_HOME;
> SW4: KEY_BACK;
> SW5: KEY_PROGRAM;
> SW6: KEY_VOLUMEUP;
> SW7: KEY_VOLUMEDOWN;
>
> Signed-off-by: Anson Huang
Applied,
On Wed, Sep 05, 2018 at 03:46:12PM +0800, Anson Huang wrote:
> Add i.MX6QDL SabreAuto board's gpio keys support, there
> are 5 gpio keys on base board:
>
> SW3: KEY_HOME;
> SW4: KEY_BACK;
> SW5: KEY_PROGRAM;
> SW6: KEY_VOLUMEUP;
> SW7: KEY_VOLUMEDOWN;
>
> Signed-off-by: Anson Huang
Applied,
On Wed, Sep 05, 2018 at 04:10:29PM +0800, Anson Huang wrote:
> Add egalax touch screen support on i2c2 bus.
>
> Signed-off-by: Anson Huang
Applied, thanks.
On Wed, Sep 05, 2018 at 04:10:29PM +0800, Anson Huang wrote:
> Add egalax touch screen support on i2c2 bus.
>
> Signed-off-by: Anson Huang
Applied, thanks.
Attn:
I am Mr. Salim Zaid, citizen and Principal assurance
manager in one of reputable banks in Europe. Mr. Mohammed Raji a
staff of Saudi Kayan Petrochemical Company got in touch with me on an
investment which was placed under our banks management some years ago.I
would respectfully request that
Attn:
I am Mr. Salim Zaid, citizen and Principal assurance
manager in one of reputable banks in Europe. Mr. Mohammed Raji a
staff of Saudi Kayan Petrochemical Company got in touch with me on an
investment which was placed under our banks management some years ago.I
would respectfully request that
Andreas Noever has let it be known off-list already a while ago that he
currently cannot spare as much time for Thunderbolt development as he'd
like. As a result the driver's development has become dominated by
Intel.
I would like to step up as co-maintainer to provide additional checks
and
Hi!
I do have some oopses, but they seem to be different on each
boot. IIRC message was "scheduling?...on offline CPU?".
Any ideas? Does it work for you?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky,
Hi!
I do have some oopses, but they seem to be different on each
boot. IIRC message was "scheduling?...on offline CPU?".
Any ideas? Does it work for you?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky,
Andreas Noever has let it be known off-list already a while ago that he
currently cannot spare as much time for Thunderbolt development as he'd
like. As a result the driver's development has become dominated by
Intel.
I would like to step up as co-maintainer to provide additional checks
and
macOS correlates PCI devices with Thunderbolt ports and stores their
device paths in each other's I/O Registry entry:
IOThunderboltPort@7 {
"PCI Device" = 4
"PCI Function" = 0
"PCI Path" =
"IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PEG1@1,1/IOPP/UPSB@0/IOPP/DSB2@4"
macOS correlates PCI devices with Thunderbolt ports and stores their
device paths in each other's I/O Registry entry:
IOThunderboltPort@7 {
"PCI Device" = 4
"PCI Function" = 0
"PCI Path" =
"IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PEG1@1,1/IOPP/UPSB@0/IOPP/DSB2@4"
The code for ICM-controlled tunnel management stores a pointer to the
upstream port in struct icm. We're going to need it in the code for
OS-controlled tunnel management as well, so move the pointer to
struct tb which is shared by both tunnel management methods.
Searching for the upstream port
The code for ICM-controlled tunnel management stores a pointer to the
upstream port in struct icm. We're going to need it in the code for
OS-controlled tunnel management as well, so move the pointer to
struct tb which is shared by both tunnel management methods.
Searching for the upstream port
The port numbers of PCIe adapters on a CIO switch and the slot numbers
of their corresponding PCI devices don't necessarily match up in
ascending order.
E.g. Light Ridge in host mode (MacBookPro9,1) mixes them up like this:
switch port 7 == pci slot 4 (PCIe downstream port)
switch port 8 == pci
The port numbers of PCIe adapters on a CIO switch and the slot numbers
of their corresponding PCI devices don't necessarily match up in
ascending order.
E.g. Light Ridge in host mode (MacBookPro9,1) mixes them up like this:
switch port 7 == pci slot 4 (PCIe downstream port)
switch port 8 == pci
If a PCIe downstream adapter is marked disabled in the DROM, that port
is ineligible for tunnel establishment, so skip over it when searching
for an unused port.
Signed-off-by: Lukas Wunner
---
drivers/thunderbolt/tb.c | 2 ++
1 file changed, 2 insertions(+)
diff --git
If a PCIe downstream adapter is marked disabled in the DROM, that port
is ineligible for tunnel establishment, so skip over it when searching
for an unused port.
Signed-off-by: Lukas Wunner
---
drivers/thunderbolt/tb.c | 2 ++
1 file changed, 2 insertions(+)
diff --git
Thunderbolt material for v4.20, comprising:
* A fix to skip disabled ports on tunnel establishment. I am not aware
that this has caused breakage in the real world so far, so no need to
apply to v4.19 or backport to stable.
* Obtain PCI slot number from DROM and use it to correlate PCI
Thunderbolt material for v4.20, comprising:
* A fix to skip disabled ports on tunnel establishment. I am not aware
that this has caused breakage in the real world so far, so no need to
apply to v4.19 or backport to stable.
* Obtain PCI slot number from DROM and use it to correlate PCI
On 09/09/2018 11:03 AM, Greg Kroah-Hartman wrote:
On Sun, Sep 09, 2018 at 08:54:41AM -0700, Guenter Roeck wrote:
On 09/09/2018 01:55 AM, Greg Kroah-Hartman wrote:
On Sat, Sep 08, 2018 at 02:14:53PM -0700, Guenter Roeck wrote:
On 09/07/2018 02:09 PM, Greg Kroah-Hartman wrote:
This is the
On 09/09/2018 11:03 AM, Greg Kroah-Hartman wrote:
On Sun, Sep 09, 2018 at 08:54:41AM -0700, Guenter Roeck wrote:
On 09/09/2018 01:55 AM, Greg Kroah-Hartman wrote:
On Sat, Sep 08, 2018 at 02:14:53PM -0700, Guenter Roeck wrote:
On 09/07/2018 02:09 PM, Greg Kroah-Hartman wrote:
This is the
The IRQ work is added before the struct rtc is allocated and registered,
but this struct is used in the IRQ handler. This may lead to a NULL pointer
dereference.
Switch to devm_rtc_allocate_device/rtc_register_device to allocate the rtc
before calling menelaus_add_irq_work.
Also, this solves a
The IRQ work is added before the struct rtc is allocated and registered,
but this struct is used in the IRQ handler. This may lead to a NULL pointer
dereference.
Switch to devm_rtc_allocate_device/rtc_register_device to allocate the rtc
before calling menelaus_add_irq_work.
Also, this solves a
The IRQ is requested before the struct rtc is allocated and registered, but
this struct is used in the IRQ handler. This may lead to a NULL pointer
dereference.
Switch to devm_rtc_allocate_device/rtc_register_device to allocate the rtc
before requesting the IRQ.
Signed-off-by: Alexandre Belloni
The IRQ is requested before the struct rtc is allocated and registered, but
this struct is used in the IRQ handler. This may lead to a NULL pointer
dereference.
Switch to devm_rtc_allocate_device/rtc_register_device to allocate the rtc
before requesting the IRQ.
Cc: Eddie Huang
Cc: Sean Wang
The IRQ is requested before the struct rtc is allocated and registered, but
this struct is used in the IRQ handler. This may lead to a NULL pointer
dereference.
Switch to devm_rtc_allocate_device/rtc_register_device to allocate the rtc
before requesting the IRQ.
Signed-off-by: Alexandre Belloni
The IRQ is requested before the struct rtc is allocated and registered, but
this struct is used in the IRQ handler. This may lead to a NULL pointer
dereference.
Switch to devm_rtc_allocate_device/rtc_register_device to allocate the rtc
before requesting the IRQ.
Cc: Eddie Huang
Cc: Sean Wang
Switch to devm_rtc_allocate_device to simplify the erro and driver removal
paths.
Cc: Linus Walleij
Signed-off-by: Alexandre Belloni
---
drivers/rtc/rtc-pl031.c | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/drivers/rtc/rtc-pl031.c
Switch to devm_rtc_allocate_device to simplify the erro and driver removal
paths.
Cc: Linus Walleij
Signed-off-by: Alexandre Belloni
---
drivers/rtc/rtc-pl031.c | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/drivers/rtc/rtc-pl031.c
On Mon, Aug 13, 2018 at 7:40 PM Rishabh Bhatnagar wrote:
>
> From: Rishabh Bhatnagar
>
> Drivers that are registered at an initcall level may have to
> wait until late_init before the probe deferral mechanism can
> retry their probe functions. It is possible that their
> dependencies were
On Mon, Aug 13, 2018 at 7:40 PM Rishabh Bhatnagar wrote:
>
> From: Rishabh Bhatnagar
>
> Drivers that are registered at an initcall level may have to
> wait until late_init before the probe deferral mechanism can
> retry their probe functions. It is possible that their
> dependencies were
On Fri, Sep 7, 2018 at 5:29 PM Quentin Perret wrote:
>
> On Friday 07 Sep 2018 at 10:52:01 (+0200), Rafael J. Wysocki wrote:
> > On Thursday, September 6, 2018 4:38:44 PM CEST Quentin Perret wrote:
> > > Hi Rafael,
> > >
> > > On Thursday 06 Sep 2018 at 11:18:55 (+0200), Rafael J. Wysocki wrote:
On Fri, Sep 7, 2018 at 5:29 PM Quentin Perret wrote:
>
> On Friday 07 Sep 2018 at 10:52:01 (+0200), Rafael J. Wysocki wrote:
> > On Thursday, September 6, 2018 4:38:44 PM CEST Quentin Perret wrote:
> > > Hi Rafael,
> > >
> > > On Thursday 06 Sep 2018 at 11:18:55 (+0200), Rafael J. Wysocki wrote:
On Fri, 31 Aug 2018, Andy Lutomirski wrote:
> (Hi, Florian!)
>
> On Fri, Aug 31, 2018 at 6:59 PM, Matt Rickard wrote:
> > Process clock_gettime(CLOCK_TAI) in vDSO.
> > This makes the call about as fast as CLOCK_REALTIME and CLOCK_MONOTONIC:
> >
> > nanoseconds
> > before after clockname
> >
On Fri, 31 Aug 2018, Andy Lutomirski wrote:
> (Hi, Florian!)
>
> On Fri, Aug 31, 2018 at 6:59 PM, Matt Rickard wrote:
> > Process clock_gettime(CLOCK_TAI) in vDSO.
> > This makes the call about as fast as CLOCK_REALTIME and CLOCK_MONOTONIC:
> >
> > nanoseconds
> > before after clockname
> >
On Fri, Sep 7, 2018 at 10:09 PM Fieah Lim wrote:
>
> There's no magic inside, let's just make it more intuitive.
Again, please fix the changelog. It is not useful as is.
> Signed-off-by: Fieah Lim
> ---
> drivers/cpuidle/governors/ladder.c | 2 +-
> drivers/cpuidle/governors/menu.c | 2
On Fri, Sep 7, 2018 at 10:09 PM Fieah Lim wrote:
>
> There's no magic inside, let's just make it more intuitive.
Again, please fix the changelog. It is not useful as is.
> Signed-off-by: Fieah Lim
> ---
> drivers/cpuidle/governors/ladder.c | 2 +-
> drivers/cpuidle/governors/menu.c | 2
On Fri, Sep 7, 2018 at 8:55 PM Fieah Lim wrote:
>
> ktime_us_delta() is not that cheap on some platform,
> and I think this is also the right thing to do.
> While at it, fix some coding style as well.
>
> Signed-off-by: Fieah Lim
> ---
> drivers/cpuidle/cpuidle.c | 17 -
> 1
On Fri, Sep 7, 2018 at 8:55 PM Fieah Lim wrote:
>
> ktime_us_delta() is not that cheap on some platform,
> and I think this is also the right thing to do.
> While at it, fix some coding style as well.
>
> Signed-off-by: Fieah Lim
> ---
> drivers/cpuidle/cpuidle.c | 17 -
> 1
On Fri, Sep 7, 2018 at 8:55 PM Fieah Lim wrote:
>
> ktime_us_delta() is not that cheap on some platform,
> and I think this is also the right thing to do.
> While at it, fix some coding style as well.
>
> Signed-off-by: Fieah Lim
Fix your changelog at least to say that you optimize the code
On Fri, Sep 7, 2018 at 8:55 PM Fieah Lim wrote:
>
> ktime_us_delta() is not that cheap on some platform,
> and I think this is also the right thing to do.
> While at it, fix some coding style as well.
>
> Signed-off-by: Fieah Lim
Fix your changelog at least to say that you optimize the code
* Arnaldo Carvalho de Melo wrote:
> Hi Ingo,
>
> Please consider pulling,
>
> - Arnaldo
>
> Test results at the end of this message, as usual.
>
> The following changes since commit 66e5db4a1ccc64f278653bc69dc406d184dc750a:
>
> Merge tag 'perf-core-for-mingo-4.19-20180820' of
>
* Arnaldo Carvalho de Melo wrote:
> Hi Ingo,
>
> Please consider pulling,
>
> - Arnaldo
>
> Test results at the end of this message, as usual.
>
> The following changes since commit 66e5db4a1ccc64f278653bc69dc406d184dc750a:
>
> Merge tag 'perf-core-for-mingo-4.19-20180820' of
>
Hello,
I am Mr. Emeka Ezela, the head of International remittance Department, United
Bank for Africa (UBA) I have a business deal i would like to propose to you.
If you are interested to know more, kindly contact me on my private emails
(emekaez...@mail.com) for more details.
Regards,
Hello,
I am Mr. Emeka Ezela, the head of International remittance Department, United
Bank for Africa (UBA) I have a business deal i would like to propose to you.
If you are interested to know more, kindly contact me on my private emails
(emekaez...@mail.com) for more details.
Regards,
Hi Olof,
On Sat, Sep 8, 2018 at 6:18 PM, Olof Johansson wrote:
> Hi,
>
> On Fri, Aug 3, 2018 at 10:53 AM, Jolly Shah wrote:
>> From: Rajan Vaja
>>
>> Add ZynqMP firmware IOCTL API to control and configure
>> devices like PLLs, SD, Gem, etc.
>>
>> Signed-off-by: Rajan Vaja
>> Signed-off-by:
Hi Olof,
On Sat, Sep 8, 2018 at 6:18 PM, Olof Johansson wrote:
> Hi,
>
> On Fri, Aug 3, 2018 at 10:53 AM, Jolly Shah wrote:
>> From: Rajan Vaja
>>
>> Add ZynqMP firmware IOCTL API to control and configure
>> devices like PLLs, SD, Gem, etc.
>>
>> Signed-off-by: Rajan Vaja
>> Signed-off-by:
I would be inclined to blame FUSE for this problem.
On Sun, Sep 09, 2018 at 11:41:02AM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:f8f65382c98a Merge tag 'for-linus' of git://git.kernel.org..
> git tree: upstream
> console output:
I would be inclined to blame FUSE for this problem.
On Sun, Sep 09, 2018 at 11:41:02AM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:f8f65382c98a Merge tag 'for-linus' of git://git.kernel.org..
> git tree: upstream
> console output:
Charles Keepax writes:
> On Tue, Sep 04, 2018 at 07:35:05PM +0100, Colin King wrote:
>> From: Colin Ian King
>>
>> In the case where IS_BUILTIN(CONFIG_AC97_BUS)) is not true, the
>> wm97xx_driver driver is being unregistered even it has not been
>> previously registered. Fix this by only
Charles Keepax writes:
> On Tue, Sep 04, 2018 at 07:35:05PM +0100, Colin King wrote:
>> From: Colin Ian King
>>
>> In the case where IS_BUILTIN(CONFIG_AC97_BUS)) is not true, the
>> wm97xx_driver driver is being unregistered even it has not been
>> previously registered. Fix this by only
On Sun, Sep 09, 2018 at 09:21:00PM +0800, Wang Long wrote:
> if i == 0, height_to_maxnodes[i] = 0,
> if i >= 1, height_to_maxnodes[i] = height_to_maxnodes[i-1]
> + __maxindex(i-1) + 1.
>
> so delete height_to_maxindex and optimize the calculation of
>
On Sun, Sep 09, 2018 at 09:21:00PM +0800, Wang Long wrote:
> if i == 0, height_to_maxnodes[i] = 0,
> if i >= 1, height_to_maxnodes[i] = height_to_maxnodes[i-1]
> + __maxindex(i-1) + 1.
>
> so delete height_to_maxindex and optimize the calculation of
>
On Tue, Aug 28, 2018 at 6:53 AM, Patrick Bellasi
wrote:
> Utilization clamping requires to map each different clamp value
> into one of the available clamp groups used by the scheduler's fast-path
> to account for RUNNABLE tasks. Thus, each time a TG's clamp value
> sysfs attribute is updated
On Tue, Aug 28, 2018 at 6:53 AM, Patrick Bellasi
wrote:
> Utilization clamping requires to map each different clamp value
> into one of the available clamp groups used by the scheduler's fast-path
> to account for RUNNABLE tasks. Thus, each time a TG's clamp value
> sysfs attribute is updated
Hello,
syzbot found the following crash on:
HEAD commit:f8f65382c98a Merge tag 'for-linus' of git://git.kernel.org..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=113260ae40
kernel config: https://syzkaller.appspot.com/x/.config?x=8f59875069d721b6
Hello,
syzbot found the following crash on:
HEAD commit:f8f65382c98a Merge tag 'for-linus' of git://git.kernel.org..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=113260ae40
kernel config: https://syzkaller.appspot.com/x/.config?x=8f59875069d721b6
On Sun, Sep 09, 2018 at 06:33:06AM -0700, Guenter Roeck wrote:
> On 09/09/2018 01:55 AM, Greg Kroah-Hartman wrote:
> > On Sat, Sep 08, 2018 at 02:14:53PM -0700, Guenter Roeck wrote:
> > > On 09/07/2018 02:09 PM, Greg Kroah-Hartman wrote:
> > > > This is the start of the stable review cycle for the
On Sun, Sep 09, 2018 at 06:33:06AM -0700, Guenter Roeck wrote:
> On 09/09/2018 01:55 AM, Greg Kroah-Hartman wrote:
> > On Sat, Sep 08, 2018 at 02:14:53PM -0700, Guenter Roeck wrote:
> > > On 09/07/2018 02:09 PM, Greg Kroah-Hartman wrote:
> > > > This is the start of the stable review cycle for the
On Sun, Sep 09, 2018 at 08:54:41AM -0700, Guenter Roeck wrote:
> On 09/09/2018 01:55 AM, Greg Kroah-Hartman wrote:
> > On Sat, Sep 08, 2018 at 02:14:53PM -0700, Guenter Roeck wrote:
> > > On 09/07/2018 02:09 PM, Greg Kroah-Hartman wrote:
> > > > This is the start of the stable review cycle for the
On Sun, Sep 09, 2018 at 08:54:41AM -0700, Guenter Roeck wrote:
> On 09/09/2018 01:55 AM, Greg Kroah-Hartman wrote:
> > On Sat, Sep 08, 2018 at 02:14:53PM -0700, Guenter Roeck wrote:
> > > On 09/07/2018 02:09 PM, Greg Kroah-Hartman wrote:
> > > > This is the start of the stable review cycle for the
On 09/09/2018 09:46 AM, Ben Hutchings wrote:
On Tue, 2018-08-14 at 19:18 +0200, Greg Kroah-Hartman wrote:
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Andi Kleen
commit 958f79b9ee55dfaf00c8106ed1c22a2919e0028b upstream
[...]
---
On 09/09/2018 09:46 AM, Ben Hutchings wrote:
On Tue, 2018-08-14 at 19:18 +0200, Greg Kroah-Hartman wrote:
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Andi Kleen
commit 958f79b9ee55dfaf00c8106ed1c22a2919e0028b upstream
[...]
---
On Sun, Sep 9, 2018 at 6:45 PM, Borislav Petkov wrote:
> On Sun, Sep 09, 2018 at 06:36:01PM +0200, Miguel Ojeda wrote:
>> No, you get a different warning depending on whether you have enabled
>> CONFIG_PARAVIRT_TIME_ACCOUNTING or CONFIG_IRQ_TIME_ACCOUNTING.
>
> Ok.
>
> Still, adding
On Sun, Sep 9, 2018 at 6:45 PM, Borislav Petkov wrote:
> On Sun, Sep 09, 2018 at 06:36:01PM +0200, Miguel Ojeda wrote:
>> No, you get a different warning depending on whether you have enabled
>> CONFIG_PARAVIRT_TIME_ACCOUNTING or CONFIG_IRQ_TIME_ACCOUNTING.
>
> Ok.
>
> Still, adding
On Tue, 2018-08-14 at 19:18 +0200, Greg Kroah-Hartman wrote:
> 4.4-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Andi Kleen
>
> commit 958f79b9ee55dfaf00c8106ed1c22a2919e0028b upstream
[...]
> --- a/arch/x86/include/asm/pgtable.h
> +++
On Tue, 2018-08-14 at 19:18 +0200, Greg Kroah-Hartman wrote:
> 4.4-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Andi Kleen
>
> commit 958f79b9ee55dfaf00c8106ed1c22a2919e0028b upstream
[...]
> --- a/arch/x86/include/asm/pgtable.h
> +++
On Mon, Jun 4, 2018 at 7:31 AM, syzbot
wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:325e14f97e0c Merge branch 'fixes' of git://git.kernel.org/..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=166329d780
> kernel config:
On Mon, Jun 4, 2018 at 7:31 AM, syzbot
wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:325e14f97e0c Merge branch 'fixes' of git://git.kernel.org/..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=166329d780
> kernel config:
On Sun, Sep 09, 2018 at 06:36:01PM +0200, Miguel Ojeda wrote:
> No, you get a different warning depending on whether you have enabled
> CONFIG_PARAVIRT_TIME_ACCOUNTING or CONFIG_IRQ_TIME_ACCOUNTING.
Ok.
Still, adding __maybe_unused to both (or writing it before the name,
whatever works!) and
On Sun, Sep 09, 2018 at 06:36:01PM +0200, Miguel Ojeda wrote:
> No, you get a different warning depending on whether you have enabled
> CONFIG_PARAVIRT_TIME_ACCOUNTING or CONFIG_IRQ_TIME_ACCOUNTING.
Ok.
Still, adding __maybe_unused to both (or writing it before the name,
whatever works!) and
Hi Borislav,
On Sun, Sep 9, 2018 at 6:06 PM, Borislav Petkov wrote:
> On Sun, Sep 09, 2018 at 04:48:19PM +0200, Miguel Ojeda wrote:
>> Indeed. But note that the attribute needs to be written before the
>> variable name so that it applies to both variables (or write it twice)
>
> It warns only
Hi Borislav,
On Sun, Sep 9, 2018 at 6:06 PM, Borislav Petkov wrote:
> On Sun, Sep 09, 2018 at 04:48:19PM +0200, Miguel Ojeda wrote:
>> Indeed. But note that the attribute needs to be written before the
>> variable name so that it applies to both variables (or write it twice)
>
> It warns only
On Sun, Sep 09, 2018 at 04:48:19PM +0200, Miguel Ojeda wrote:
> Indeed. But note that the attribute needs to be written before the
> variable name so that it applies to both variables (or write it twice)
It warns only about 'steal' - not the other one.
> Also, if we go that route, I would simply
On Sun, Sep 09, 2018 at 04:48:19PM +0200, Miguel Ojeda wrote:
> Indeed. But note that the attribute needs to be written before the
> variable name so that it applies to both variables (or write it twice)
It warns only about 'steal' - not the other one.
> Also, if we go that route, I would simply
On 09/09/2018 01:43 AM, Greg Kroah-Hartman wrote:
On Sat, Sep 08, 2018 at 02:16:02PM -0700, Guenter Roeck wrote:
On 09/07/2018 02:08 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.14.69 release.
There are 89 patches in this series, all will be posted as a
On 9 September 2018 at 13:07, Catalin Marinas wrote:
> On Wed, Sep 05, 2018 at 11:04:36AM -0700, Scott Branden wrote:
>> On 18-09-05 11:00 AM, Grant Likely wrote:
>> > On Wed, Sep 5, 2018 at 6:27 PM Scott Branden
>> > wrote:
>> > > On 18-09-05 02:40 AM, Ard Biesheuvel wrote:
>> > > > On 4
On 09/09/2018 01:43 AM, Greg Kroah-Hartman wrote:
On Sat, Sep 08, 2018 at 02:16:02PM -0700, Guenter Roeck wrote:
On 09/07/2018 02:08 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.14.69 release.
There are 89 patches in this series, all will be posted as a
On 9 September 2018 at 13:07, Catalin Marinas wrote:
> On Wed, Sep 05, 2018 at 11:04:36AM -0700, Scott Branden wrote:
>> On 18-09-05 11:00 AM, Grant Likely wrote:
>> > On Wed, Sep 5, 2018 at 6:27 PM Scott Branden
>> > wrote:
>> > > On 18-09-05 02:40 AM, Ard Biesheuvel wrote:
>> > > > On 4
On 09/09/2018 01:55 AM, Greg Kroah-Hartman wrote:
On Sat, Sep 08, 2018 at 02:14:53PM -0700, Guenter Roeck wrote:
On 09/07/2018 02:09 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.9.126 release.
There are 63 patches in this series, all will be posted as a
On 09/09/2018 01:55 AM, Greg Kroah-Hartman wrote:
On Sat, Sep 08, 2018 at 02:14:53PM -0700, Guenter Roeck wrote:
On 09/07/2018 02:09 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.9.126 release.
There are 63 patches in this series, all will be posted as a
On 09/09/2018 02:01 AM, Greg Kroah-Hartman wrote:
On Sat, Sep 08, 2018 at 02:13:48PM -0700, Guenter Roeck wrote:
On 09/07/2018 02:09 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.4.155 release.
There are 47 patches in this series, all will be posted as a
On 09/09/2018 02:01 AM, Greg Kroah-Hartman wrote:
On Sat, Sep 08, 2018 at 02:13:48PM -0700, Guenter Roeck wrote:
On 09/07/2018 02:09 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.4.155 release.
There are 47 patches in this series, all will be posted as a
On 09/09/2018 02:28 AM, Greg Kroah-Hartman wrote:
On Sat, Sep 08, 2018 at 02:12:54PM -0700, Guenter Roeck wrote:
On 09/07/2018 02:10 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.18.122 release.
There are 29 patches in this series, all will be posted as a
On 09/09/2018 02:28 AM, Greg Kroah-Hartman wrote:
On Sat, Sep 08, 2018 at 02:12:54PM -0700, Guenter Roeck wrote:
On 09/07/2018 02:10 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.18.122 release.
There are 29 patches in this series, all will be posted as a
All other uses of "asm goto" go through asm_volatile_goto
(including the arm version of the same file). For consistency,
use it here as well.
Cc: Nick Desaulniers
Cc: Catalin Marinas
Cc: Will Deacon
Cc: linux-arm-ker...@lists.infradead.org
Signed-off-by: Miguel Ojeda
---
All other uses of "asm goto" go through asm_volatile_goto
(including the arm version of the same file). For consistency,
use it here as well.
Cc: Nick Desaulniers
Cc: Catalin Marinas
Cc: Will Deacon
Cc: linux-arm-ker...@lists.infradead.org
Signed-off-by: Miguel Ojeda
---
Hi Nick,
On Sat, Sep 8, 2018 at 12:21 AM, Nick Desaulniers
wrote:
> The comment above asm_volatile_goto mentions working around a GCC bug,
> and links to a bug report that claims this has been fixed in newer
> versions of GCC. Testing shows that this was resolved in GCC 4.8.2.
>
Hi Nick,
On Sat, Sep 8, 2018 at 12:21 AM, Nick Desaulniers
wrote:
> The comment above asm_volatile_goto mentions working around a GCC bug,
> and links to a bug report that claims this has been fixed in newer
> versions of GCC. Testing shows that this was resolved in GCC 4.8.2.
>
On Sun, Sep 9, 2018 at 11:36 AM, Borislav Petkov wrote:
>
> Alternatively, if you don't want to let the crazy ifdeffery in that
> function grow even more, you can simply do:
>
> ---
> diff --git a/kernel/sched/core.c b/kernel/sched/core.c
> index 625bc9897f62..1728743360d4 100644
> ---
On Sun, Sep 9, 2018 at 11:36 AM, Borislav Petkov wrote:
>
> Alternatively, if you don't want to let the crazy ifdeffery in that
> function grow even more, you can simply do:
>
> ---
> diff --git a/kernel/sched/core.c b/kernel/sched/core.c
> index 625bc9897f62..1728743360d4 100644
> ---
Hi Taniya,
How much have you stressed this driver?
I tried it on top of an integration branch based on 4.19-rc2 that we
maintain[1] and was able to get the board to reboot fairly easily with
just a few "yes > /dev/null &" instances running in the background.
I even tried with interconnect
Hi Taniya,
How much have you stressed this driver?
I tried it on top of an integration branch based on 4.19-rc2 that we
maintain[1] and was able to get the board to reboot fairly easily with
just a few "yes > /dev/null &" instances running in the background.
I even tried with interconnect
Hi Peter and Srikar,
thanks a lot for the information and for the patches to test!
> I have bounced the 5 patches to you, (one of the 6 has not been applied by
> Peter) so I have skipped that.
> They can also be fetched from
>
Hi Peter and Srikar,
thanks a lot for the information and for the patches to test!
> I have bounced the 5 patches to you, (one of the 6 has not been applied by
> Peter) so I have skipped that.
> They can also be fetched from
>
On 9 September 2018 at 04:19, Jacek Anaszewski
wrote:
> Hi Bjorn,
>
> On 09/08/2018 07:02 AM, Bjorn Andersson wrote:
>> On Tue 04 Sep 04:01 PDT 2018, Baolin Wang wrote:
>>
>>> diff --git a/Documentation/ABI/testing/sysfs-class-led-trigger-pattern
>>>
On 9 September 2018 at 04:19, Jacek Anaszewski
wrote:
> Hi Bjorn,
>
> On 09/08/2018 07:02 AM, Bjorn Andersson wrote:
>> On Tue 04 Sep 04:01 PDT 2018, Baolin Wang wrote:
>>
>>> diff --git a/Documentation/ABI/testing/sysfs-class-led-trigger-pattern
>>>
On 09/09/2018 01:55 AM, Greg Kroah-Hartman wrote:
On Sat, Sep 08, 2018 at 02:14:53PM -0700, Guenter Roeck wrote:
On 09/07/2018 02:09 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.9.126 release.
There are 63 patches in this series, all will be posted as a
On 09/09/2018 01:55 AM, Greg Kroah-Hartman wrote:
On Sat, Sep 08, 2018 at 02:14:53PM -0700, Guenter Roeck wrote:
On 09/07/2018 02:09 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.9.126 release.
There are 63 patches in this series, all will be posted as a
101 - 200 of 268 matches
Mail list logo
