Do we really need a new source file just to call swiotlb_init? And
if we do that file should have a SPDX header these days.
Otherwise looks fine:
Reviewed-by: Christoph Hellwig
Hi Baolin,
On Wed, Nov 7, 2018 at 6:43 AM Baolin Wang wrote:
> We will meet below issue due to mutex_lock() is called in interrupt context.
> The mutex lock is used to protect the pattern trigger data, but before
> changing
> new pattern trigger data (pattern values or repeat value) by users,
Do we really need a new source file just to call swiotlb_init? And
if we do that file should have a SPDX header these days.
Otherwise looks fine:
Reviewed-by: Christoph Hellwig
Hi Baolin,
On Wed, Nov 7, 2018 at 6:43 AM Baolin Wang wrote:
> We will meet below issue due to mutex_lock() is called in interrupt context.
> The mutex lock is used to protect the pattern trigger data, but before
> changing
> new pattern trigger data (pattern values or repeat value) by users,
On Wed, Nov 07, 2018 at 12:08:23AM +, Maciej W. Rozycki wrote:
> The Broadcom SiByte BCM1250, BCM1125H and BCM1125 SOCs have an onchip
> 32-bit PCI host bridge, and the two former SOCs also have an onchip HT
> host bridge. The HT host bridge, where present, appears in the PCI
>
On Wed, Nov 07, 2018 at 12:08:23AM +, Maciej W. Rozycki wrote:
> The Broadcom SiByte BCM1250, BCM1125H and BCM1125 SOCs have an onchip
> 32-bit PCI host bridge, and the two former SOCs also have an onchip HT
> host bridge. The HT host bridge, where present, appears in the PCI
>
On Wed, 2018-11-07 at 08:35 +0100, Michal Hocko wrote:
> On Wed 07-11-18 07:35:18, Balbir Singh wrote:
> > The check seems to be quite aggressive and in a loop that iterates
> > pages, but has nothing to do with the page, did you mean to make
> > the check
> >
> > zone_idx(page_zone(page)) ==
On Wed, 2018-11-07 at 08:35 +0100, Michal Hocko wrote:
> On Wed 07-11-18 07:35:18, Balbir Singh wrote:
> > The check seems to be quite aggressive and in a loop that iterates
> > pages, but has nothing to do with the page, did you mean to make
> > the check
> >
> > zone_idx(page_zone(page)) ==
syzbot has found a reproducer for the following crash on:
HEAD commit:d881de30d29e Add linux-next specific files for 20181107
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=169e982540
kernel config:
syzbot has found a reproducer for the following crash on:
HEAD commit:d881de30d29e Add linux-next specific files for 20181107
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=169e982540
kernel config:
On Wed 07-11-18 08:35:48, Michal Hocko wrote:
> On Wed 07-11-18 07:35:18, Balbir Singh wrote:
> > On Tue, Nov 06, 2018 at 10:55:24AM +0100, Michal Hocko wrote:
> > > From: Michal Hocko
> > >
> > > Page state checks are racy. Under a heavy memory workload (e.g. stress
> > > -m 200 -t 2h) it is
On Wed 07-11-18 08:35:48, Michal Hocko wrote:
> On Wed 07-11-18 07:35:18, Balbir Singh wrote:
> > On Tue, Nov 06, 2018 at 10:55:24AM +0100, Michal Hocko wrote:
> > > From: Michal Hocko
> > >
> > > Page state checks are racy. Under a heavy memory workload (e.g. stress
> > > -m 200 -t 2h) it is
On Wed 07-11-18 07:35:18, Balbir Singh wrote:
> On Tue, Nov 06, 2018 at 10:55:24AM +0100, Michal Hocko wrote:
> > From: Michal Hocko
> >
> > Page state checks are racy. Under a heavy memory workload (e.g. stress
> > -m 200 -t 2h) it is quite easy to hit a race window when the page is
> >
On Wed 07-11-18 07:35:18, Balbir Singh wrote:
> On Tue, Nov 06, 2018 at 10:55:24AM +0100, Michal Hocko wrote:
> > From: Michal Hocko
> >
> > Page state checks are racy. Under a heavy memory workload (e.g. stress
> > -m 200 -t 2h) it is quite easy to hit a race window when the page is
> >
Hi Boris and Geert
On Tue, Nov 6, 2018 at 11:34 PM Boris Brezillon
wrote:
>
> On Tue, 6 Nov 2018 23:19:14 +0100
> Geert Uytterhoeven wrote:
>
> > Hi Boris,
> >
> > On Tue, Nov 6, 2018 at 10:58 PM Boris Brezillon
> > wrote:
> > > On Tue, 6 Nov 2018 22:44:16 +0100
> > > Geert Uytterhoeven
Hi Boris and Geert
On Tue, Nov 6, 2018 at 11:34 PM Boris Brezillon
wrote:
>
> On Tue, 6 Nov 2018 23:19:14 +0100
> Geert Uytterhoeven wrote:
>
> > Hi Boris,
> >
> > On Tue, Nov 6, 2018 at 10:58 PM Boris Brezillon
> > wrote:
> > > On Tue, 6 Nov 2018 22:44:16 +0100
> > > Geert Uytterhoeven
Add the HXT vendor ID to pci_ids.h and use it in quirks. As the
design of HXT SD4800 ACS feature is the same as QCOM QDF2xxx,
pci_quirk_qcom_rp_acs() is reused for SD4800 quirk.
cc: Joey Zheng
Reviewed-by: Sinan Kaya
Signed-off-by: Shunyong Yang
---
v2:
Add Reviewed-by: Sinan Kaya.
v1:
Add the HXT vendor ID to pci_ids.h and use it in quirks. As the
design of HXT SD4800 ACS feature is the same as QCOM QDF2xxx,
pci_quirk_qcom_rp_acs() is reused for SD4800 quirk.
cc: Joey Zheng
Reviewed-by: Sinan Kaya
Signed-off-by: Shunyong Yang
---
v2:
Add Reviewed-by: Sinan Kaya.
v1:
The HXT SD4800 PCI controller does not set the Command Completed
bit unless writes to the Slot Command register change "Control"
bits.
This patch adds SD4800 to the quirk.
Cc: Joey Zheng
Signed-off-by: Shunyong Yang
diff --git a/drivers/pci/hotplug/pciehp_hpc.c
The HXT SD4800 PCI controller does not set the Command Completed
bit unless writes to the Slot Command register change "Control"
bits.
This patch adds SD4800 to the quirk.
Cc: Joey Zheng
Signed-off-by: Shunyong Yang
diff --git a/drivers/pci/hotplug/pciehp_hpc.c
Hi Jacek,
On 7 November 2018 at 06:07, Jacek Anaszewski
wrote:
> Switch to using generic LED support for composing LED class
> device name.
>
> Signed-off-by: Jacek Anaszewski
> Cc: Xiaotong Lu
> Cc: Baolin Wang
Thanks for simplifying the code, it can work well for SC27XX LED.
Tested-by:
Hi Jacek,
On 7 November 2018 at 06:07, Jacek Anaszewski
wrote:
> Switch to using generic LED support for composing LED class
> device name.
>
> Signed-off-by: Jacek Anaszewski
> Cc: Xiaotong Lu
> Cc: Baolin Wang
Thanks for simplifying the code, it can work well for SC27XX LED.
Tested-by:
Hi Jacek,
On 7 November 2018 at 06:07, Jacek Anaszewski
wrote:
> Add public led_compose_name() API for composing LED class device
> name basing on fwnode_handle data. The function composes device name
> according to either a new pattern or the legacy
> pattern. The decision on using the
>
Hi Jacek,
On 7 November 2018 at 06:07, Jacek Anaszewski
wrote:
> Add public led_compose_name() API for composing LED class device
> name basing on fwnode_handle data. The function composes device name
> according to either a new pattern or the legacy
> pattern. The decision on using the
>
This fixes the following warning:
kernel/cgroup/cpuset.c: In function ‘cpuset_cancel_attach’:
kernel/cgroup/cpuset.c:1501:17: warning: variable ‘cs’ set but not used
[-Wunused-but-set-variable]
struct cpuset *cs;
^
Signed-off-by: Yi Wang
---
kernel/cgroup/cpuset.c | 2 --
1
This fixes the following warning:
kernel/cgroup/cpuset.c: In function ‘cpuset_cancel_attach’:
kernel/cgroup/cpuset.c:1501:17: warning: variable ‘cs’ set but not used
[-Wunused-but-set-variable]
struct cpuset *cs;
^
Signed-off-by: Yi Wang
---
kernel/cgroup/cpuset.c | 2 --
1
Use git commit description style 'commit <12+ chars of sha1>
("")' in the comments.
Signed-off-by: Peng Hao
---
arch/arm64/kernel/sys32.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm64/kernel/sys32.c b/arch/arm64/kernel/sys32.c
index 0f8bcb7..8317a5a 100644
Use git commit description style 'commit <12+ chars of sha1>
("")' in the comments.
Signed-off-by: Peng Hao
---
arch/arm64/kernel/sys32.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm64/kernel/sys32.c b/arch/arm64/kernel/sys32.c
index 0f8bcb7..8317a5a 100644
This updates dt-binding documentation for MT7629 SoC
Signed-off-by: Ryder Lee
---
Documentation/devicetree/bindings/watchdog/mtk-wdt.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/watchdog/mtk-wdt.txt
This updates bindings for MT7629 RNG driver.
Signed-off-by: Ryder Lee
---
Documentation/devicetree/bindings/rng/mtk-rng.txt | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/rng/mtk-rng.txt
This updates dt-binding documentation for MT7629 SoC
Signed-off-by: Ryder Lee
---
Documentation/devicetree/bindings/watchdog/mtk-wdt.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/watchdog/mtk-wdt.txt
This updates bindings for MT7629 RNG driver.
Signed-off-by: Ryder Lee
---
Documentation/devicetree/bindings/rng/mtk-rng.txt | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/rng/mtk-rng.txt
Hi Nylon,
Nylon Chen 於 2018年11月7日 週三 下午1:32寫道：
>
> The "fpu_dp" should be added to hwcap_str table to make sure the cpu features
> displayed correctly.
>
> Signed-off-by: Nylon Chen
> ---
> arch/nds32/kernel/setup.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git
Hi Nylon,
Nylon Chen 於 2018年11月7日 週三 下午1:32寫道：
>
> The "fpu_dp" should be added to hwcap_str table to make sure the cpu features
> displayed correctly.
>
> Signed-off-by: Nylon Chen
> ---
> arch/nds32/kernel/setup.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git
On 06.11.2018 11:43, Arun KS wrote:
On 2018-11-06 14:07, Konstantin Khlebnikov wrote:
On 06.11.2018 11:30, Arun KS wrote:
On 2018-11-06 13:47, Konstantin Khlebnikov wrote:
On 06.11.2018 8:38, Arun KS wrote:
Any comments?
Looks good.
Except unclear motivation behind this change.
This should
On 06.11.2018 11:43, Arun KS wrote:
On 2018-11-06 14:07, Konstantin Khlebnikov wrote:
On 06.11.2018 11:30, Arun KS wrote:
On 2018-11-06 13:47, Konstantin Khlebnikov wrote:
On 06.11.2018 8:38, Arun KS wrote:
Any comments?
Looks good.
Except unclear motivation behind this change.
This should
Hi Jacek,
On 7 November 2018 at 06:07, Jacek Anaszewski
wrote:
> Replace of_led_classdev_register() with led_classdev_register_ext(), which
> accepts easily extendable struct led_init_data, instead of the fixed
> struct device_node argument. The latter can be now passed in a fwnode
> property of
Hi Jacek,
On 7 November 2018 at 06:07, Jacek Anaszewski
wrote:
> Replace of_led_classdev_register() with led_classdev_register_ext(), which
> accepts easily extendable struct led_init_data, instead of the fixed
> struct device_node argument. The latter can be now passed in a fwnode
> property of
Thanks Srinivas for the fix.
On 11/6/2018 5:08 PM, Srinivas Kandagatla wrote:
For some reason the dapm widgets are incorrectly defined from the start,
Not sure how we ended up with such thing. Fix them now!
Without this fix the backend dais are always powered up even if there
is no active
Thanks Srinivas for the fix.
On 11/6/2018 5:08 PM, Srinivas Kandagatla wrote:
For some reason the dapm widgets are incorrectly defined from the start,
Not sure how we ended up with such thing. Fix them now!
Without this fix the backend dais are always powered up even if there
is no active
On 2018-11-07 02:17, Andy Lutomirski wrote:
On Tue, Nov 6, 2018 at 4:02 PM Sean Christopherson
wrote:
/*
* EEXIT or EENTER faulted. In the latter case, %RAX already holds some
* fault indicator, e.g. -EFAULT.
*/
eexit_or_eenter_fault:
ret
But userspace wants to know whether it
On 2018-11-07 02:17, Andy Lutomirski wrote:
On Tue, Nov 6, 2018 at 4:02 PM Sean Christopherson
wrote:
/*
* EEXIT or EENTER faulted. In the latter case, %RAX already holds some
* fault indicator, e.g. -EFAULT.
*/
eexit_or_eenter_fault:
ret
But userspace wants to know whether it
On 11/6/18 12:41 PM, Dave Chinner wrote:
> On Tue, Nov 06, 2018 at 12:00:06PM +0100, Jan Kara wrote:
>> On Tue 06-11-18 13:47:15, Dave Chinner wrote:
>>> On Mon, Nov 05, 2018 at 04:26:04PM -0800, John Hubbard wrote:
On 11/5/18 1:54 AM, Jan Kara wrote:
> Hmm, have you tried larger buffer
On 11/6/18 12:41 PM, Dave Chinner wrote:
> On Tue, Nov 06, 2018 at 12:00:06PM +0100, Jan Kara wrote:
>> On Tue 06-11-18 13:47:15, Dave Chinner wrote:
>>> On Mon, Nov 05, 2018 at 04:26:04PM -0800, John Hubbard wrote:
On 11/5/18 1:54 AM, Jan Kara wrote:
> Hmm, have you tried larger buffer
On 11/7/18 12:15 AM, Andrew Morton wrote:
> On Tue, 6 Nov 2018 14:20:53 +0200 Alexey Skidanov
> wrote:
>
>> On success, gen_pool_first_fit_align() returns the bit number such that
>> chunk_start_addr + (bit << order) is properly aligned. On failure,
>> the bitmap size parameter is returned.
On 11/7/18 12:15 AM, Andrew Morton wrote:
> On Tue, 6 Nov 2018 14:20:53 +0200 Alexey Skidanov
> wrote:
>
>> On success, gen_pool_first_fit_align() returns the bit number such that
>> chunk_start_addr + (bit << order) is properly aligned. On failure,
>> the bitmap size parameter is returned.
On 2018-11-07 01:38, Michal Hocko wrote:
On Tue 06-11-18 21:01:29, Arun KS wrote:
On 2018-11-06 19:36, Michal Hocko wrote:
> On Tue 06-11-18 11:33:13, Arun KS wrote:
> > When free pages are done with higher order, time spend on
> > coalescing pages by buddy allocator can be reduced. With
> >
On 2018-11-07 01:38, Michal Hocko wrote:
On Tue 06-11-18 21:01:29, Arun KS wrote:
On 2018-11-06 19:36, Michal Hocko wrote:
> On Tue 06-11-18 11:33:13, Arun KS wrote:
> > When free pages are done with higher order, time spend on
> > coalescing pages by buddy allocator can be reduced. With
> >
On 2018-11-07 05:52, Andrew Morton wrote:
On Fri, 26 Oct 2018 16:30:58 +0530 Arun KS
wrote:
This series convert totalram_pages, totalhigh_pages and
zone->managed_pages to atomic variables.
The whole point appears to be removal of managed_page_count_lock, yes?
Why? What is the value of
On 2018-11-07 05:52, Andrew Morton wrote:
On Fri, 26 Oct 2018 16:30:58 +0530 Arun KS
wrote:
This series convert totalram_pages, totalhigh_pages and
zone->managed_pages to atomic variables.
The whole point appears to be removal of managed_page_count_lock, yes?
Why? What is the value of
On 11/7/18 12:11 AM, Andrew Morton wrote:
> On Tue, 6 Nov 2018 14:20:53 +0200 Alexey Skidanov
> wrote:
>
>> On success, gen_pool_first_fit_align() returns the bit number such that
>> chunk_start_addr + (bit << order) is properly aligned. On failure,
>> the bitmap size parameter is returned.
On 11/7/18 12:11 AM, Andrew Morton wrote:
> On Tue, 6 Nov 2018 14:20:53 +0200 Alexey Skidanov
> wrote:
>
>> On success, gen_pool_first_fit_align() returns the bit number such that
>> chunk_start_addr + (bit << order) is properly aligned. On failure,
>> the bitmap size parameter is returned.
On 11/06/2018 08:31 PM, Roberto Sassu wrote:
This patch removes the hard-coded limit of the active_banks array size.
The hard-coded limit in static array active_banks[] represents the
maximum possible banks.
A TPM might have three banks, but only one bank may be active.
To confirm my
On 11/06/2018 08:31 PM, Roberto Sassu wrote:
This patch removes the hard-coded limit of the active_banks array size.
The hard-coded limit in static array active_banks[] represents the
maximum possible banks.
A TPM might have three banks, but only one bank may be active.
To confirm my
Hi Vitaly:
Thanks for your review.
On 11/6/2018 11:50 PM, Vitaly Kuznetsov wrote:
ltyker...@gmail.com writes:
From: Lan Tianyu
This patch is to initialize ept_pointer to INVALID_PAGE and check it
before flushing ept tlb. If ept_pointer is invalidated, bypass the flush
request.
Hi Vitaly:
Thanks for your review.
On 11/6/2018 11:50 PM, Vitaly Kuznetsov wrote:
ltyker...@gmail.com writes:
From: Lan Tianyu
This patch is to initialize ept_pointer to INVALID_PAGE and check it
before flushing ept tlb. If ept_pointer is invalidated, bypass the flush
request.
On Sun, Oct 28, 2018 at 11:24 PM Amit Kucheria wrote:
>
> On Thu, Oct 25, 2018 at 9:38 PM Andy Gross wrote:
> >
> > On Thu, Oct 25, 2018 at 10:55:32AM +0530, Amit Kucheria wrote:
> >
> >
> >
> > > Andy,
> > >
> > > While you acked the tsens thermal DT patches[1] so they could go
> > > through
On Sun, Oct 28, 2018 at 11:24 PM Amit Kucheria wrote:
>
> On Thu, Oct 25, 2018 at 9:38 PM Andy Gross wrote:
> >
> > On Thu, Oct 25, 2018 at 10:55:32AM +0530, Amit Kucheria wrote:
> >
> >
> >
> > > Andy,
> > >
> > > While you acked the tsens thermal DT patches[1] so they could go
> > > through
From: Jiri Olsa
Date: Tue, 6 Nov 2018 21:42:55 +0100
> I pushed that fix in perf/fixes branch, but I'm still occasionaly
> hitting the namespace crash.. working on it ;-)
Jiri, how can this new scheme work without setting copy_on_queue
for the queued_events we use here?
I don't see
From: Jiri Olsa
Date: Tue, 6 Nov 2018 21:42:55 +0100
> I pushed that fix in perf/fixes branch, but I'm still occasionaly
> hitting the namespace crash.. working on it ;-)
Jiri, how can this new scheme work without setting copy_on_queue
for the queued_events we use here?
I don't see
Hi,
Since 37c8a5fafa3bb7dcdd51774be353be6cb2912b86 [kbuild: consolidate
Devicetree dtb build rules], the target bindeb-pkg no longer installs
DTBs in the .deb package.
Thanks,
Nuno
Hi,
Since 37c8a5fafa3bb7dcdd51774be353be6cb2912b86 [kbuild: consolidate
Devicetree dtb build rules], the target bindeb-pkg no longer installs
DTBs in the .deb package.
Thanks,
Nuno
There was a special path in handle_userfault() in the past that we'll
return a VM_FAULT_NOPAGE when we detected non-fatal signals when waiting
for userfault handling. We did that by reacquiring the mmap_sem before
returning. However that brings a risk in that the vmas might have
changed when we
There was a special path in handle_userfault() in the past that we'll
return a VM_FAULT_NOPAGE when we detected non-fatal signals when waiting
for userfault handling. We did that by reacquiring the mmap_sem before
returning. However that brings a risk in that the vmas might have
changed when we
This is the gup counterpart of the change that allows the VM_FAULT_RETRY
to happen for more than once.
Signed-off-by: Peter Xu
---
mm/gup.c | 17 +
1 file changed, 13 insertions(+), 4 deletions(-)
diff --git a/mm/gup.c b/mm/gup.c
index 6faff46cd409..8a0e7f9bd29a 100644
---
This is the gup counterpart of the change that allows the VM_FAULT_RETRY
to happen for more than once.
Signed-off-by: Peter Xu
---
mm/gup.c | 17 +
1 file changed, 13 insertions(+), 4 deletions(-)
diff --git a/mm/gup.c b/mm/gup.c
index 6faff46cd409..8a0e7f9bd29a 100644
---
(sorry I got the cc list messed up; am sending another one with no
change but only to fix the cc list)
This is an RFC series as cleanup and enhancements to current page
fault logic. The whole idea comes from the discussion between Andrea
and Linus on the bug reported by syzbot here:
The idea comes from a discussion between Linus and Andrea [1].
Before this patch we only allow a page fault to retry once. We achieved
this by clearing the FAULT_FLAG_ALLOW_RETRY flag when doing
handle_mm_fault() the second time. This was majorly used to avoid
unexpected starvation of the
There's plenty of places around __get_user_pages() that has a parameter
"nonblocking" which does not really mean that "it won't block" (because
it can really block) but instead it shows whether the mmap_sem is
released by up_read() during the page fault handling mostly when
VM_FAULT_RETRY is
(sorry I got the cc list messed up; am sending another one with no
change but only to fix the cc list)
This is an RFC series as cleanup and enhancements to current page
fault logic. The whole idea comes from the discussion between Andrea
and Linus on the bug reported by syzbot here:
The idea comes from a discussion between Linus and Andrea [1].
Before this patch we only allow a page fault to retry once. We achieved
this by clearing the FAULT_FLAG_ALLOW_RETRY flag when doing
handle_mm_fault() the second time. This was majorly used to avoid
unexpected starvation of the
There's plenty of places around __get_user_pages() that has a parameter
"nonblocking" which does not really mean that "it won't block" (because
it can really block) but instead it shows whether the mmap_sem is
released by up_read() during the page fault handling mostly when
VM_FAULT_RETRY is
We will meet below issue due to mutex_lock() is called in interrupt context.
The mutex lock is used to protect the pattern trigger data, but before changing
new pattern trigger data (pattern values or repeat value) by users, we always
cancel the timer firstly to clear previous patterns'
We will meet below issue due to mutex_lock() is called in interrupt context.
The mutex lock is used to protect the pattern trigger data, but before changing
new pattern trigger data (pattern values or repeat value) by users, we always
cancel the timer firstly to clear previous patterns'
From: Hou Zhiqiang
Removed the wrong compatible string "snps,dw-pcie", in case
match incorrect driver.
Signed-off-by: Hou Zhiqiang
---
V3:
- Reworded the subject.
arch/arm64/boot/dts/freescale/fsl-ls1012a.dtsi | 2 +-
arch/arm64/boot/dts/freescale/fsl-ls1043a.dtsi | 6 +++---
From: Hou Zhiqiang
Removed the wrong compatible string "snps,dw-pcie", in case
match incorrect driver.
Signed-off-by: Hou Zhiqiang
---
V3:
- Reworded the subject.
arch/arm64/boot/dts/freescale/fsl-ls1012a.dtsi | 2 +-
arch/arm64/boot/dts/freescale/fsl-ls1043a.dtsi | 6 +++---
From: Hou Zhiqiang
Removed the compatible string "snps,dw-pcie", it is for the reference
platform driver for PCI RC IP Protoyping Kits based on the ARC SDP,
so it is not suitable for all platform with designware PCIe controller,
and platform vendors have themselves' drivers.
The compatible
From: Hou Zhiqiang
Removed the wrong compatible string "snps,dw-pcie", in case
match incorrect driver.
Signed-off-by: Hou Zhiqiang
---
V3:
- Reworded the subject.
arch/arm/boot/dts/ls1021a.dtsi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
From: Hou Zhiqiang
Removed the compatible string "snps,dw-pcie" from FSL layerscape-pci compatible
string list.
Hou Zhiqiang (4):
dt-bindings: pci: layerscape-pci: add compatible strings
"fsl,ls1043a-pcie"
dt-bindings: pci: layerscape-pci: removed compatible string
"snps,dw-pcie"
From: Hou Zhiqiang
Removed the compatible string "snps,dw-pcie", it is for the reference
platform driver for PCI RC IP Protoyping Kits based on the ARC SDP,
so it is not suitable for all platform with designware PCIe controller,
and platform vendors have themselves' drivers.
The compatible
From: Hou Zhiqiang
Removed the wrong compatible string "snps,dw-pcie", in case
match incorrect driver.
Signed-off-by: Hou Zhiqiang
---
V3:
- Reworded the subject.
arch/arm/boot/dts/ls1021a.dtsi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
From: Hou Zhiqiang
Removed the compatible string "snps,dw-pcie" from FSL layerscape-pci compatible
string list.
Hou Zhiqiang (4):
dt-bindings: pci: layerscape-pci: add compatible strings
"fsl,ls1043a-pcie"
dt-bindings: pci: layerscape-pci: removed compatible string
"snps,dw-pcie"
From: Hou Zhiqiang
The PCIe compatible string for LS1043A was lost, so add it.
Signed-off-by: Hou Zhiqiang
Reviewed-by: Rob Herring
---
V3:
- no change
Documentation/devicetree/bindings/pci/layerscape-pci.txt | 1 +
1 file changed, 1 insertion(+)
diff --git
From: Hou Zhiqiang
The PCIe compatible string for LS1043A was lost, so add it.
Signed-off-by: Hou Zhiqiang
Reviewed-by: Rob Herring
---
V3:
- no change
Documentation/devicetree/bindings/pci/layerscape-pci.txt | 1 +
1 file changed, 1 insertion(+)
diff --git
The "fpu_dp" should be added to hwcap_str table to make sure the cpu features
displayed correctly.
Signed-off-by: Nylon Chen
---
arch/nds32/kernel/setup.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/nds32/kernel/setup.c b/arch/nds32/kernel/setup.c
index eacc79024879..e39274a21481
We add a config for user to enable or disable this feature.
It can be used to control the hardware prefetch function.
Signed-off-by: Nylon Chen
---
arch/nds32/Kconfig.cpu| 7 +++
arch/nds32/include/asm/bitfield.h | 6 ++
arch/nds32/kernel/head.S | 2 +-
The "fpu_dp" should be added to hwcap_str table to make sure the cpu features
displayed correctly.
Signed-off-by: Nylon Chen
---
arch/nds32/kernel/setup.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/nds32/kernel/setup.c b/arch/nds32/kernel/setup.c
index eacc79024879..e39274a21481
We add a config for user to enable or disable this feature.
It can be used to control the hardware prefetch function.
Signed-off-by: Nylon Chen
---
arch/nds32/Kconfig.cpu| 7 +++
arch/nds32/include/asm/bitfield.h | 6 ++
arch/nds32/kernel/head.S | 2 +-
Hello,
syzbot found the following crash on:
HEAD commit:d881de30d29e Add linux-next specific files for 20181107
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1103882b40
kernel config: https://syzkaller.appspot.com/x/.config?x=caa433e1c8778437
Hello,
syzbot found the following crash on:
HEAD commit:d881de30d29e Add linux-next specific files for 20181107
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1103882b40
kernel config: https://syzkaller.appspot.com/x/.config?x=caa433e1c8778437
Current imx7d-sdb.dts has some incorrect settings about
Rev-A and Rev-B boards, some of the settings are based on
Rev-A board but some are based on Rev-B board, clean up it
by adding i.MX7D SDB Rev-A board support, make default
imx7d-sdb.dts for Rev-B board as usual, and introduce
Current imx7d-sdb.dts has some incorrect settings about
Rev-A and Rev-B boards, some of the settings are based on
Rev-A board but some are based on Rev-B board, clean up it
by adding i.MX7D SDB Rev-A board support, make default
imx7d-sdb.dts for Rev-B board as usual, and introduce
From: Hou Zhiqiang
The order of parameters is not correct when invoking the outbound
window disable routine.
Fixes: commit 4a2745d760fac ("PCI: layerscape: Disable outbound
windows configured by bootloader").
Cc: sta...@vger.kernel.org
Signed-off-by: Hou Zhiqiang
---
V2:
- Tagged this patch
From: Hou Zhiqiang
The order of parameters is not correct when invoking the outbound
window disable routine.
Fixes: commit 4a2745d760fac ("PCI: layerscape: Disable outbound
windows configured by bootloader").
Cc: sta...@vger.kernel.org
Signed-off-by: Hou Zhiqiang
---
V2:
- Tagged this patch
Hello,
syzbot found the following crash on:
HEAD commit:d881de30d29e Add linux-next specific files for 20181107
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=14aa485d40
kernel config: https://syzkaller.appspot.com/x/.config?x=caa433e1c8778437
Hello,
syzbot found the following crash on:
HEAD commit:d881de30d29e Add linux-next specific files for 20181107
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=14aa485d40
kernel config: https://syzkaller.appspot.com/x/.config?x=caa433e1c8778437
Hello,
syzbot found the following crash on:
HEAD commit:d881de30d29e Add linux-next specific files for 20181107
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=16e42f5b40
kernel config: https://syzkaller.appspot.com/x/.config?x=caa433e1c8778437
Hello,
syzbot found the following crash on:
HEAD commit:d881de30d29e Add linux-next specific files for 20181107
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=10ae982540
kernel config: https://syzkaller.appspot.com/x/.config?x=caa433e1c8778437
Hello,
syzbot found the following crash on:
HEAD commit:d881de30d29e Add linux-next specific files for 20181107
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=16e42f5b40
kernel config: https://syzkaller.appspot.com/x/.config?x=caa433e1c8778437
Hello,
syzbot found the following crash on:
HEAD commit:d881de30d29e Add linux-next specific files for 20181107
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=10ae982540
kernel config: https://syzkaller.appspot.com/x/.config?x=caa433e1c8778437
1 - 100 of 1544 matches
Mail list logo
