On Sat, Sep 08, 2018 at 02:16:40PM -0700, Guenter Roeck wrote:
> On 09/07/2018 02:07 PM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.18.7 release.
> > There are 145 patches in this series, all will be posted as a response
> > to this one. If anyone has any
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 response
> > to this one. If anyone has any
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 response
> > to this one. If anyone has any
On Sun, Sep 09, 2018 at 12:56:45AM -0300, Rafael David Tinoco wrote:
> Greg,
>
> On Fri, Sep 7, 2018 at 6:41 PM Greg Kroah-Hartman
> wrote:
> >
> > 4.4-stable review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > From: Jann Horn
> >
> > commit
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 response
> > to this one. If anyone has
I am by no means a kernel expert, but Tomeu asked whether I could
review this. Generally the patch looks okay, it applied (on top of
4.18.5-gentoo), and compiled without problems.
However, running the experimental qemu branch I get a kernel bug:
BUG: unable to handle kernel NULL pointer
From: Borislav Petkov
... instead of open-coding it, in static_key_mod().
No functional changes.
Signed-off-by: Borislav Petkov
Cc: Ingo Molnar
Cc: Josh Poimboeuf
Cc: Peter Zijlstra
Cc: "Steven Rostedt (VMware)"
Cc: Jason Baron
---
kernel/jump_label.c | 2 +-
1 file changed, 1
Hi,
This patch series adds DT bindings (patch #1) and the corresponding driver
(patch #2) for the Panasonic AN30259A 3-channel LED driver. AN30259A
uses an internal clock for controlling brightness/on-off cycles, but
also supports using an external PWM/clock input. This patch series only
AN30259A is a 3-channel LED driver which uses I2C. It supports timed
operation via an internal PWM clock, and variable brightness. This
driver offers support for basic hardware-based blinking and brightness
control.
The datasheet is freely available:
Signed-off-by: Simon Shields
Acked-by: Pavel Machek
Reviewed-by: Rob Herring
---
.../bindings/leds/leds-an30259a.txt | 43 +++
1 file changed, 43 insertions(+)
create mode 100644 Documentation/devicetree/bindings/leds/leds-an30259a.txt
diff --git
Hi,
On 06-09-18 04:55, Kai-Heng Feng wrote:
Raydium touchscreen triggers interrupt storm after system-wide suspend:
[ 179.085033] i2c_hid i2c-CUST:00: i2c_hid_get_input: incomplete
report (58/65535)
According to Raydium, Windows driver does not reset the device after
system resume.
The
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 September 2018 at 19:19, Scott Branden
> > > > wrote:
> > > > >
Size of struct page might be larger than 64 bytes if debug options
enabled, or fields added for debugging intentionally. Yet an upper
limit need be added at build time to trigger an alert in case the
size is too big to boot up system, warning people to check if it's
be done on purpose in advance.
In memory KASLR, __PHYSICAL_MASK_SHIFT is taken to calculate the
initial size of the direct mapping region. This is right in the
old code where __PHYSICAL_MASK_SHIFT was equal to MAX_PHYSMEM_BITS,
46bit, and only 4-level mode was supported.
Later, in commit:
b83ce5ee91471d ("x86/mm/64: Make
Vmemmap region has different maximum size depending on paging mode.
Now its size is hardcoded as 1TB in memory KASLR, this is not
right for 5-level paging mode. It will cause overflow if vmemmap
region is randomized to be adjacent to cpu_entry_area region and
its actual size is bigger than 1TB.
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 response
> > to this one. If anyone has any
On Sun, Sep 09, 2018 at 12:56:45AM -0300, Rafael David Tinoco wrote:
> Greg,
>
> On Fri, Sep 7, 2018 at 6:41 PM Greg Kroah-Hartman
> wrote:
> >
> > 4.4-stable review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > From: Jann Horn
> >
> > commit
On Sun, Sep 09, 2018 at 10:22:27AM +0530, Naresh Kamboju wrote:
> On 8 September 2018 at 02:39, 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 response
> > to this one. If
I'm announcing the release of the 4.18.7 kernel.
All users of the 4.18 kernel series must upgrade.
The updated 4.18.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.18.y
and can be browsed at the normal kernel.org git web browser:
On Sun, Sep 09, 2018 at 11:16:33AM +0200, Greg KH wrote:
> On Sun, Sep 09, 2018 at 12:56:45AM -0300, Rafael David Tinoco wrote:
> > Greg,
> >
> > On Fri, Sep 7, 2018 at 6:41 PM Greg Kroah-Hartman
> > wrote:
> > >
> > > 4.4-stable review patch. If anyone has any objections, please let me
> > >
On Sat, Sep 08, 2018 at 09:05:53PM +0200, Miguel Ojeda wrote:
> On non-SMP configs, when only one of CONFIG_{PARAVIRT,IRQ_TIME}_ACCOUNTING
> is defined, we are declaring a variable (irq_delta or steal) which
> is not used:
>
> kernel/sched/core.c: In function ‘update_rq_clock_task’:
>
The following changes since commit 9a47249d444d344051c7c0e909fad0e88515a5c2:
random: Make crng state queryable (2018-08-02 17:33:06 -0400)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/random.git tags/for_linus
for you to fetch changes up to
syzbot has found a reproducer for 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=13af4cda40
kernel config:
Linus,
please pull the latest irq-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
irq-urgent-for-linus
A single fix to prevent allocating excessive memory in the GIC/ITS driver.
While the subject of the patch might suggest otherwise this is a real
On Wed, 2018-08-15 at 09:48 +0800, houlong wei wrote:
> On Wed, 2018-07-25 at 09:26 +0800, Houlong Wei wrote:
> > This patch adds the device node of the GCE hardware for CMDQ module.
> > [...]
Hello Matthias,
Sorry to disturb you. Are you availabe to review this patch and give
your comment?
2018-09-07 8:37 GMT+09:00 Randy Dunlap :
> From: Randy Dunlap
>
> If there is no System.map file for "make modules_install",
> scripts/depmod.sh will silently exit with success, having done
> nothing. Since this is an unexpected situation, change it to
> report a Warning for the missing file.
Hi Linus,
Please pull some Kbuild fixes.
Thanks!
The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3:
Linux 4.19-rc1 (2018-08-26 14:11:59 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git
2018-09-04 9:42 GMT+09:00 Masahiro Yamada :
> These symbols were added by commit 028f042613c3 ("kallsyms: support
> kernel symbols in Blackfin on-chip memory") for Blackfin.
>
> The Blackfin support was removed by commit 4ba66a976072 ("arch: remove
> blackfin port").
>
> Signed-off-by: Masahiro
On Wed, 2018-08-15 at 09:46 +0800, houlong wei wrote:
> On Wed, 2018-07-25 at 09:26 +0800, Houlong Wei wrote:
> > Add Mediatek CMDQ helper to create CMDQ packet and assemble GCE op code.
> >[...]
Hello Matthias,
Sorry to disturb you. Could you please review this patch and give
your comment?
Linus,
please pull the latest x86-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-urgent-for-linus
A set of fixes for x86:
- Prevent multiplication result truncation on 32bit. Introduced with the
early timestamp reworrk.
- Ensure
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.
>
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
---
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 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
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 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
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 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
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 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 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 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
syzbot has found a reproducer for the following crash on:
HEAD commit:28619527b8a7 Merge git://git.kernel.org/pub/scm/linux/kern..
git tree: bpf
console output: https://syzkaller.appspot.com/x/log.txt?x=14800f0a40
kernel config:
Linus,
please pull the latest timers-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
timers-urgent-for-linus
Two fixes for timekeeping:
- Revert to the previous kthread based update, which is unfortunately
required due to lock ordering issues.
Linus,
please pull the latest smp-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
smp-urgent-for-linus
Two fixes for the hotplug state machine code:
- Move the misplaces smb() in the hotplug thread function to the proper
place, otherwise a half
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: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 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 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
[...]
---
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
height_to_maxnodes array.
Signed-off-by: Wang Long
---
lib/radix-tree.c | 13
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 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
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
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:
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, 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 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 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 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
>
* 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,
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 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
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
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:
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
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
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
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
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"
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,
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
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
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 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
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
ests
* ltp-fs-tests
* ltp-fs_bind-tests
* ltp-fs_perms_simple-tests
* ltp-fsx-tests
* ltp-hugetlb-tests
* ltp-io-tests
* ltp-ipc-tests
* ltp-math-tests
* ltp-nptl-tests
* ltp-open-posix-tests
* ltp-pty-tests
* ltp-sched-tests
* ltp-securebits-tests
* ltp-syscalls-tests
* ltp-timers-tests
* kselftest-vsyscall-mode-native
* kselftest-vsyscall-mode-none
Summary
---
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 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,
Latch2 pins control a number of on-board devices, namely LCD, NAND,
MODEM and CODEC. Those pins used to be initialized with safe values
from init_machine before that operation was:
1) moved to late_initcall in preparation for conversion of latch2 to
GPIO device - see commit f7519d8c8290 ("ARM:
Another week, another rc.
Things look fairly normal. The diffstat shows some unusual patterns,
but that's partly due to some late nds32 updates and nilfs2 got the
copyright messages converted to SPDX, and that just shows up like a
sore thumb in the diffstat.
But other than odd details like
On Sun, Sep 09, 2018 at 11:46:20AM -0700, Bart Van Assche wrote:
> On Sun, 2018-09-09 at 20:58 +0800, Ming Lei wrote:
> > Now percpu_ref_reinit() can only be done on one percpu refcounter
> > when it drops zero. And the limit shouldn't be so strict, and it
> > is quite straightforward that
LGTM
Reviewed-by: tang.junhui.li...@gmail.com
zhong jiang 于2018年9月8日周六 下午9:41写道：
>
> debugfs_remove_recursive has taken IS_ERR_OR_NULL into account. So just
> remove the condition check before debugfs_remove_recursive.
>
> Signed-off-by: zhong jiang
> ---
> drivers/md/bcache/debug.c | 3 +--
>
On Thu, Sep 06, 2018 at 04:46:58PM -0700, Stefan Agner wrote:
> The pinctrl properties on the IOMUXC node get overwritten by the
> carrier board level device tree, hence the pinctrl_reset_moci
> pinctrl does not get applied.
>
> Associate the pinctrl_reset_moci pinctrl with the PCIe node where
>
On Fri, Aug 31, 2018 at 03:53:12PM +0800, Anson Huang wrote:
> i.MX6 SoCs have MMDC ipg clock for registers access, to make
> sure MMDC registers access successfully, add optional clock
> enable for MMDC driver.
>
> Signed-off-by: Anson Huang
Applied this one, thanks.
Convert modem related GPIO setup from integer space to GPIO descriptors.
Also, restore original initialization order of the MODEM device and its
related GPIO pins.
Cleanup of MODEM relaated regulator setup is postponed while waiting for
upcoming conversion of fixed regulator API to GPIO
On Fri, 2018-09-07 at 17:01 +0200, Thomas Gleixner wrote:
> Avoid the extra variable and gotos by splitting the function into the
> actual algorithm and a callable function which contains the lock
> protection.
>
> Rename it to should_split_large_page() while at it so the return values make
>
Don't request MODEM IRQ GPIO by its global number in
ams_delta_modem_init(). Instead, obtain its GPIO descriptor
and assign related IRQ to the MODEM. Do that from
omap_gpio_deps_init(), where the chip is already looked up. Then, in
ams_delta_modem_init(), just check for the IRQ number having
Amstrad Delta MODEM device used to be initialized at arch_initcall
before it was once moved to late_initcall by commit f7519d8c8290 ("ARM:
OMAP1: ams-delta: register latch dependent devices later"). The purpose
of that change was to postpone initialization of devices which depended
on latch2 pins
LGTM
Reviewed-by: tang.junhui.li...@gmail.com
zhong jiang 于2018年9月8日周六 下午9:08写道：
>
> debugfs_remove has taken the IS_ERR_OR_NULL into account. Just
> remove the unnecessary condition.
>
> Signed-off-by: zhong jiang
> ---
> drivers/md/bcache/super.c | 3 +--
> 1 file changed, 1 insertion(+), 2
On Tue, Aug 28, 2018 at 04:34:04PM -0700, Randy Dunlap wrote:
> From: Randy Dunlap
>
> Since this header is in "include/uapi/linux/", apparently people
> want to use it in userspace programs -- even in C++ ones.
> However, the header uses a C++ reserved keyword ("private"),
> so change that to
There might be a possible memory leak in drivers/platform/x86/dell-smbios-wmi.c
In the `run_smbios_call' function, the buffer created via ACPI_ALLOCATE_BUFFER
within the output object is not freed properly.
Generally, this buffer should be freed using:
kfree(output.pointer);
But it hasn't
On Sunday 09 September 2018 01:11 AM, Grygorii Strashko wrote:
>
>
> On 09/06/2018 09:16 AM, Keerthy wrote:
>>
>>
>> On Wednesday 05 September 2018 04:07 PM, Linus Walleij wrote:
>>> On Mon, Sep 3, 2018 at 7:40 AM Keerthy wrote:
On Saturday 01 September 2018 12:43 AM, Andrew F. Davis
On 9/7/18 2:40 PM, Jan H. Schönherr wrote:
> Add a new command line argument cosched_max_level=, which allows
> enabling coscheduling at boot. The number corresponds to the scheduling
> domain up to which coscheduling can later be enabled for cgroups.
>
> For example, to enable coscheduling of
1 - 100 of 268 matches
Mail list logo
