On Wed 26-07-17 17:06:59, Jerome Glisse wrote:
[...]
> This does not seems to be an opt-in change ie if i am reading patch 3
> correctly if an altmap is not provided to __add_pages() you fallback
> to allocating from begining of zone. This will not work with HMM ie
> device private memory. So at ve
On Wed 26-07-17 15:25:03, Andrew Morton wrote:
> On Wed, 26 Jul 2017 14:19:52 +0200 Michal Hocko wrote:
>
> > > > Please note that this code has been removed by
> > > > http://lkml.kernel.org/r/20170721143915.14161-2-mho...@kernel.org. It
> > > > will get to linux-next as soon as Andrew releases
On Thu 27-07-17 11:30:50, Wenwei Tao wrote:
> 2017-07-26 21:44 GMT+08:00 Michal Hocko :
> > On Wed 26-07-17 21:07:42, Wenwei Tao wrote:
[...]
> >> I think there is a css double put in mem_cgroup_iter. Under reclaim,
> >> we call mem_cgroup_iter the first time with prev == NULL, and we get
> >> last
Good point, so patches 1/5 and 2/5 should be swapped around.
Mikko
On 27.07.2017 09:47, kbuild test robot wrote:
Hi Mikko,
[auto build test ERROR on tegra/for-next]
[also build test ERROR on v4.13-rc2 next-20170726]
[if your patch is applied to the wrong git tree, please drop us a note to
This patch add the spdif dt node for rk322x SoCs.
Signed-off-by: Sugar Zhang
---
arch/arm/boot/dts/rk322x.dtsi | 20
1 file changed, 20 insertions(+)
diff --git a/arch/arm/boot/dts/rk322x.dtsi b/arch/arm/boot/dts/rk322x.dtsi
index f3e4ffd..b3b80e1 100644
--- a/arch/arm/boo
On Wed 26-07-17 18:29:12, Andrea Arcangeli wrote:
> On Wed, Jul 26, 2017 at 07:45:57AM +0200, Michal Hocko wrote:
> > On Tue 25-07-17 21:19:52, Andrea Arcangeli wrote:
> > > On Tue, Jul 25, 2017 at 06:04:00PM +0200, Michal Hocko wrote:
> > > > - down_write(&mm->mmap_sem);
> > > > + if (
Hi Heiko,
Thank you for the quick reply. I will remove the gerrit Change-Ids in my
v2 patches.
Thanks again,
Rocky
在 2017/7/27 14:36, Heiko Stübner 写道:
Hi Rocky,
Am Dienstag, 25. Juli 2017, 17:09:44 CEST schrieb Rocky Hao:
attempt to new compatible for thermal founding on RK3328 SoC.
Chang
Hi Mikko,
[auto build test ERROR on tegra/for-next]
[also build test ERROR on v4.13-rc2 next-20170726]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Mikko-Perttunen/arm64-tegra-Add-BPMP
This adds support the AHCI-compliant Serial ATA controller present
on MediaTek SoCs.
Signed-off-by: Ryder Lee
---
drivers/ata/Kconfig| 10 +++
drivers/ata/Makefile | 1 +
drivers/ata/ahci_mtk.c | 196 +
3 files changed, 207 insertions(+)
Hi,
This patch series add support for AHCI compatible SATA controller, and it is
compliant with the ahci 1.3 and sata 3.0 specification. This driver is slightly
different than ahci_platform.c (eg. reset control, subsystem setting).
Ryder Lee (2):
ata: mediatek: add support for MediaTek SATA con
Add DT bindings for the onboard SATA controller present on the MediaTek
SoCs.
Signed-off-by: Ryder Lee
---
Documentation/devicetree/bindings/ata/ahci-mtk.txt | 48 ++
1 file changed, 48 insertions(+)
create mode 100644 Documentation/devicetree/bindings/ata/ahci-mtk.txt
diff
Hi Rocky,
Am Dienstag, 25. Juli 2017, 17:09:44 CEST schrieb Rocky Hao:
> attempt to new compatible for thermal founding on RK3328 SoC.
>
> Change-Id: Ie6f6d7b4e545891a0035851a923c0412f584140c
> Signed-off-by: Rocky Hao
generally looks good but you should not have gerrit Change-Ids in patches
fo
Hi Thierry,
[auto build test WARNING on linuxtv-media/master]
[also build test WARNING on v4.13-rc2 next-20170726]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Thierry-Escande/v4l2-Add
On Wed 26-07-17 18:39:28, Andrea Arcangeli wrote:
> On Wed, Jul 26, 2017 at 07:45:33AM +0200, Michal Hocko wrote:
> > Yes, exit_aio is the only blocking call I know of currently. But I would
> > like this to be as robust as possible and so I do not want to rely on
> > the current implementation. Th
Signed-off-by: Vivek Gautam
---
arch/arm64/boot/dts/qcom/pmi8994.dtsi | 17 +
1 file changed, 17 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/pmi8994.dtsi
b/arch/arm64/boot/dts/qcom/pmi8994.dtsi
index d3879a4e8076..3b04ca63c31e 100644
--- a/arch/arm64/boot/dts/qcom/pmi899
Function dmi_matches can me made a bit faster:
* The documented purpose of dmi_initialized is to catch too early
calls to dmi_check_system(). I'm not fully convinced it justifies
slowing down the initialization of all systems out there, but at
least the check should not have been moved from
Update the bindings doc and driver for pmi8994-gpio devices.
Signed-off-by: Vivek Gautam
---
- Have been using this patch-set on db820c [1] for extcon with
usb controller. The usb controller uses one of these gpios
for usb-id/vbus detection.
[1] https://github.com/boddob/linux/tree/for-qcom
Hi Baoquan,
At 07/27/2017 02:08 PM, b...@redhat.com wrote:
On 07/26/17 at 08:19pm, Dou Liyang wrote:
Hi Baoquan,
There are two places where we used DMAR table in Linux:
1) In detect_intel_iommu() in ACPI early stage:
...
status = acpi_get_table(ACPI_SIG_DMAR, 0, &dmar_tbl);
if (dmar_tbl
In the non-cooperative userfaultfd case, the process exit may race with
outstanding mcopy_atomic called by the uffd monitor. Returning -ENOSPC
instead of -EINVAL when mm is already gone will allow uffd monitor to
distinguish this case from other error conditions.
Cc: sta...@vger.kernel.org
Fixes
On Wed, 26 Jul 2017 15:45:52 -0600
Shuah Khan wrote:
> On 07/26/2017 03:25 PM, Steven Rostedt wrote:
> > On Mon, 24 Jul 2017 09:39:25 -0600
> > Shuah Khan wrote:
> >
> >
> >>> Masami Hiramatsu (5):
> >>> selftests: ftrace: Do not failure if there is unsupported tests
> >>> selftest
Hi Viresh,
On Wed, Jul 26, 2017 at 10:46 PM, Viresh Kumar wrote:
> On 26-07-17, 22:14, Joel Fernandes (Google) wrote:
>> Also one more comment about this usecase:
>>
>> You mentioned in our discussion at [2] sometime back, about the
>> question of initial utilization,
>>
>> "We don't have any su
On Wed, Jul 26, 2017 at 10:50 PM, Viresh Kumar wrote:
> On 26-07-17, 22:34, Joel Fernandes (Google) wrote:
>> On Wed, Jul 26, 2017 at 2:22 AM, Viresh Kumar
>> wrote:
>> > @@ -221,7 +226,7 @@ static void sugov_update_single(struct
>> > update_util_data *hook, u64 time,
>> > sugov_set_iow
On Wed, 26 Jul 2017, Stefan Berger wrote:
> cap_inode_need_killpriv returns 1 if security.capability exists and
> has a value and inode_killpriv() is required, 0 otherwise. Fix the
> description of the return value to reflect this.
>
> Signed-off-by: Stefan Berger
> ---
> security/commoncap.c |
On 07/26/17 at 08:19pm, Dou Liyang wrote:
> Hi Baoquan,
> > > There are two places where we used DMAR table in Linux:
> > >
> > > 1) In detect_intel_iommu() in ACPI early stage:
> > >
> > > ...
> > > status = acpi_get_table(ACPI_SIG_DMAR, 0, &dmar_tbl);
> > >
> > > if (dmar_tbl) {
> > > ac
On 27/07/17 02:56, Colin King wrote:
From: Colin Ian King
strrchr can potentially return a null so the following strlen on the
null pointer can cause a null dereference. Add a check to see if
the string postfix is not null before calling strlen.
Detected by CoverityScan, CID#1452039 ("Derefere
Hi Kees,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.13-rc2 next-20170726]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Kees-Cook/fortify-Use-WARN-instead-of-BUG-for
On Wed, Jul 26, 2017 at 08:57:03PM +0200, Rafael J. Wysocki wrote:
> > Should I apply this or will Tony do that?
>
> So am I suppsed to drop this?
Well, as suggested in another mail, I think it'll be best if Tony and I
put ourselves as reviewers for the APEI crap and you still collect it.
Unless
Hi all,
Does somebody have the *Thinkpad x121e (AMD E-450 APU)*?
I need to do an regression test for a patchset[1].
This test is simple, but really special and only be reproduced in
Thinkpad x121e. I have tested it in Thinkpad s430, Lenovo M4340 and
Lenovo M4300. Unfortunately, I failed.
I did
On Wed, Jul 26, 2017 at 10:48:24AM +0200, Borislav Petkov wrote:
> EDAC: Add edac_pr_err/info macros
> ACPI/GHES: Add an EDAC notifier chain
> EDAC, ghes: Make it a proper module
Pushed here:
https://git.kernel.org/pub/scm/linux/kernel/git/bp/bp.git/log/?h=ghes
--
Regards/Gruss,
Boris
On 26-07-17, 22:34, Joel Fernandes (Google) wrote:
> On Wed, Jul 26, 2017 at 2:22 AM, Viresh Kumar wrote:
> > @@ -221,7 +226,7 @@ static void sugov_update_single(struct update_util_data
> > *hook, u64 time,
> > sugov_set_iowait_boost(sg_cpu, time, flags);
> > sg_cpu->last_update =
On Thu, Jul 27, 2017 at 10:29 AM, Jassi Brar wrote:
> On Thu, Jul 27, 2017 at 9:25 AM, Anup Patel wrote:
>> On Tue, Jul 25, 2017 at 9:37 PM, Jassi Brar wrote:
>>> On Tue, Jul 25, 2017 at 11:11 AM, Anup Patel
>>> wrote:
On Mon, Jul 24, 2017 at 10:06 PM, Jassi Brar
wrote:
> On Mo
On Wed, Jul 26, 2017 at 2:22 AM, Viresh Kumar wrote:
> This patch updates the schedutil governor to process cpufreq utilization
> update hooks called for remote CPUs where the remote CPU is managed by
> the cpufreq policy of the local CPU.
>
> Based on initial work from Steve Muckle.
>
> Signed-of
On 26-07-17, 22:14, Joel Fernandes (Google) wrote:
> I think you dropped [1] in your cover-letter. May be you meant to add
> it at the end of the cover letter?
>
> I noticed from your v2 that its:
> https://pastebin.com/7LkMSRxE
Yeah, I missed it. Thanks :)
> Also one more comment about this use
Hi all,
Changes since 20170726:
Non-merge commits (relative to Linus' tree): 2581
2620 files changed, 92132 insertions(+), 46797 deletions(-)
I have created today's linux-next tree at
git://git.kernel.o
Hi Roberto,
[auto build test WARNING on integrity/next]
[also build test WARNING on v4.13-rc2 next-20170726]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Roberto-Sassu/ima-measure-digest
On 2017/7/27 5:43, Jaegeuk Kim wrote:
> On 07/26, Chao Yu wrote:
>> On 2017/7/26 9:29, Jaegeuk Kim wrote:
>>> This patch exposes what features are supported by current f2fs build to
>>> sysfs
>>> entry.
>>>
>>> Signed-off-by: Jaegeuk Kim
>>
>> Reviewed-by: Chao Yu
>>
>> Minor thing, can you exch
Hi Viresh,
On Wed, Jul 26, 2017 at 2:22 AM, Viresh Kumar wrote:
> We do not call cpufreq callbacks from scheduler core for remote
> (non-local) CPUs currently. But there are cases where such remote
> callbacks are useful, specially in the case of shared cpufreq policies.
>
> This patch updates th
On Wed, Jul 26, 2017 at 07:24:59PM +, Kani, Toshimitsu wrote:
> Using sb_edac does not change the fact that it is FF. I do not think
> you'd see normal CEs on your box.
I guess we should add some blurb to EDAC to say that on FF systems,
error counts are unreliable or even non-existent.
--
R
On Wed, Jul 26, 2017 at 01:33:53PM -0500, Alan Tull wrote:
> On Sun, Jun 25, 2017 at 8:52 PM, Wu Hao wrote:
>
> Hi Hao,
>
> > This patch adds region_id to fpga_image_info data structure, it
> > allows driver to pass region id information to fpga-mgr via
> > fpga_image_info for fpga reconfigurati
Hi Roberto,
[auto build test ERROR on integrity/next]
[also build test ERROR on v4.13-rc2 next-20170726]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Roberto-Sassu/ima-measure-digest-lists
Introducing USB charger type and state definition can help
to support USB charging which will be added in USB phy core.
Signed-off-by: Baolin Wang
---
include/uapi/linux/usb/charger.h | 31 +++
1 file changed, 31 insertions(+)
create mode 100644 include/uapi/linux/
This patch introduces the usb charger support based on usb phy that
makes an enhancement to a power driver. The basic conception of the
usb charger is that, when one usb charger is added or removed by
reporting from the extcon device state change, the usb charger will
report to power user to set th
Integrate with the newly added USB charger interface to limit the current
we draw from the USB input based on the input device configuration
identified by the USB stack, allowing us to charge more quickly from high
current inputs without drawing more current than specified from others.
Signed-off-
Hi Viresh,
On Wed, Jul 26, 2017 at 2:22 AM, Viresh Kumar wrote:
>
> With Android UI and benchmarks the latency of cpufreq response to
> certain scheduling events can become very critical. Currently, callbacks
> into schedutil are only made from the scheduler if the target CPU of the
> event is t
Currently the Linux kernel does not provide any standard integration of this
feature that integrates the USB subsystem with the system power regulation
provided by PMICs meaning that either vendors must add this in their kernels
or USB gadget devices based on Linux (such as mobile phones) may not b
On Wed, Jul 26, 2017 at 02:02:42PM -0700, David Daney wrote:
> Also, if a given configuration disables CONFIG_EDAC there is some hackery
> needed to get the perf portion of the driver included.
Yes, and we don't do performance counters in EDAC.
So you could add a small memory controller driver wh
Hi,
On Thursday 27 July 2017 12:27 AM, Krzysztof Kozlowski wrote:
s3c2412_i2s_probe() might fail so driver has to revert work done by
s3c_i2sv2_probe() (clock enabling). Missing doing this would lead to
clock enable in-balance.
Signed-off-by: Krzysztof Kozlowski
---
Please, kindly test on
The UCL E-Mail Virus Protection System has been triggered by a message you sent.
One or more of the original e-mail attachments have been removed and replaced
with this message.
* The attachment may have contained a virus or malware
* The attachment may have an extension of a type unacceptable f
Hi Jens,
I'm seeing the lockdep warning below on shutdown on a Power8 machine
using IPR.
If I'm reading it right it looks like the spin_lock() (non-irq) in
blk_mq_sched_insert_request() is the immediate cause.
Looking at blk_mq_requeue_work() (the caller), it is doing
spin_lock_irqsave(). So is
On 26-07-17, 23:19, Amitoj Kaur Chawla wrote:
> Unnecessary platform_set_drvdata() has been removed since the driver
> core clears the driver data to NULL after device release or on
> probe failure. There is no need to manually clear the device
> driver data to NULL.
>
> The Coccinelle semantic pa
Hi Roberto,
[auto build test WARNING on integrity/next]
[also build test WARNING on v4.13-rc2 next-20170726]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Roberto-Sassu/ima-measure-digest
Add binding documentation for Allwinner V3s CSI.
Signed-off-by: Yong Deng
---
.../devicetree/bindings/media/sun6i-csi.txt| 49 ++
1 file changed, 49 insertions(+)
create mode 100644 Documentation/devicetree/bindings/media/sun6i-csi.txt
diff --git a/Documentation/dev
Allwinner V3s SoC have two CSI module. CSI0 is used for MIPI interface
and CSI1 is used for parallel interface. This is not documented in
datasheet but by testing and guess.
This patch implement a v4l2 framework driver for it.
Currently, the driver only support the parallel interface. MIPI-CSI2,
Signed-off-by: Yong Deng
---
MAINTAINERS | 8
1 file changed, 8 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 9826a91..b91fa27 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -3686,6 +3686,14 @@ M: Jaya Kumar
S: Maintained
F: sound/pci/cs5535audio/
+CSI DRI
Hi,
On Thursday 27 July 2017 12:42 AM, Krzysztof Kozlowski wrote:
On Thu, Jul 27, 2017 at 12:28:52AM +0530, Arvind Yadav wrote:
-Use devm_clk_get() to make cleanup paths more simple.
-clk_prepare_enable() can fail here and we must check its return value.
-Add s3c_i2sv2_remove cleanup function
Sorry for resend the patch. Delivering to somebody in cc has failed at
last time.
This patchset add initial support for Allwinner V3s CSI.
Allwinner V3s SoC have two CSI module. CSI0 is used for MIPI interface
and CSI1 is used for parallel interface. This is not documented in
datasheet but by tes
On Wed, Jul 26, 2017 at 05:29:11PM -0500, Alan Tull wrote:
> On Wed, Jul 26, 2017 at 9:20 AM, Alan Tull wrote:
> > On Wed, Jul 26, 2017 at 4:50 AM, Wu Hao wrote:
> >> On Tue, Jul 25, 2017 at 04:32:10PM -0500, Alan Tull wrote:
> >>> On Sat, Apr 1, 2017 at 7:18 AM, Wu Hao wrote:
> >>>
> >>> Hi Hao
On Wed, Jul 26, 2017 at 10:45 PM, Vinod Koul wrote:
> On Wed, Jul 26, 2017 at 11:06:42AM +0530, Anup Patel wrote:
>> This patch breaks sba_process_deferred_requests() into two parts
>> sba_process_received_request() and _sba_process_pending_requests()
>> for readability.
>>
>> In addition,
>
> tha
On Thu, Jul 27, 2017 at 9:25 AM, Anup Patel wrote:
> On Tue, Jul 25, 2017 at 9:37 PM, Jassi Brar wrote:
>> On Tue, Jul 25, 2017 at 11:11 AM, Anup Patel wrote:
>>> On Mon, Jul 24, 2017 at 10:06 PM, Jassi Brar
>>> wrote:
On Mon, Jul 24, 2017 at 9:26 AM, Anup Patel
wrote:
> Hi Jas
On Wed, Jul 26, 2017 at 10:40 PM, Vinod Koul wrote:
> On Wed, Jul 26, 2017 at 11:06:40AM +0530, Anup Patel wrote:
>> We should peek mbox channels when we are left with no free
>> sba_requests in sba_alloc_request()
>
> and why is the world should we do that, how does that help??
When setting up R
On Wed, Jul 26, 2017 at 10:39 PM, Vinod Koul wrote:
> On Wed, Jul 26, 2017 at 11:06:39AM +0530, Anup Patel wrote:
>> This patch improves memory allocation in SBA RAID driver in
>> following ways:
>> 1. Simplify struct sba_request to reduce memory consumption
>
> what is the simplification?? You ne
On Wed, Jul 26, 2017 at 10:33 PM, Vinod Koul wrote:
> On Wed, Jul 26, 2017 at 11:06:38AM +0530, Anup Patel wrote:
>> This patchset does various improvments to Broadcom SBA-RAID
>> driver and also adds SBA-RAID DT nodes for Stingray SOC.
>>
>> The patches are based on "[PATCH v2 0/7] FlexRM driver
On Tue, Jul 25, 2017 at 9:37 PM, Jassi Brar wrote:
> On Tue, Jul 25, 2017 at 11:11 AM, Anup Patel wrote:
>> On Mon, Jul 24, 2017 at 10:06 PM, Jassi Brar
>> wrote:
>>> On Mon, Jul 24, 2017 at 9:26 AM, Anup Patel wrote:
Hi Jassi,
Sorry for the delayed response...
On Fri,
This patchset add initial support for Allwinner V3s CSI.
Allwinner V3s SoC have two CSI module. CSI0 is used for MIPI interface
and CSI1 is used for parallel interface. This is not documented in
datasheet but by testing and guess.
This patchset implement a v4l2 framework driver and add a binding
Add binding documentation for Allwinner V3s CSI.
Signed-off-by: Yong Deng
---
.../devicetree/bindings/media/sun6i-csi.txt| 49 ++
1 file changed, 49 insertions(+)
create mode 100644 Documentation/devicetree/bindings/media/sun6i-csi.txt
diff --git a/Documentation/dev
Allwinner V3s SoC have two CSI module. CSI0 is used for MIPI interface
and CSI1 is used for parallel interface. This is not documented in
datasheet but by testing and guess.
This patch implement a v4l2 framework driver for it.
Currently, the driver only support the parallel interface. MIPI-CSI2,
On 26-07-17, 00:42, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> The ->get callback in the intel_pstate structure was mostly there
> for the scaling_cur_freq sysfs attribute to work, but after commit
> f8475cef9008 (x86: use common aperfmperf_khz_on_cpu() to calculate
> KHz using APERF/
On 27-07-17, 02:05, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> Add a description of the cpuinfo_cur_freq policy attribute in sysfs
> to the cpufreq documentation under Documentation/admin-guide/pm/ as
> it is missing after commit 2a0e49279850 (cpufreq: User/admin
> documentation updat
On Thu, 2017-07-27 at 10:58 +0800, honghui.zh...@mediatek.com wrote:
> From: Ryder Lee
>
> Add support for MediaTek new generation controller and update related
> properities.
>
> Signed-off-by: Ryder Lee
> Signed-off-by: Honghui Zhang
> ---
> .../devicetree/bindings/pci/mediatek-pcie.txt
On Thu, 2017-07-27 at 10:58 +0800, honghui.zh...@mediatek.com wrote:
> From: Ryder Lee
>
> Add support for MediaTek new generation controller and update related
> properities.
>
> Signed-off-by: Ryder Lee
> Signed-off-by: Honghui Zhang
> ---
> .../devicetree/bindings/pci/mediatek-pcie.txt
2017-07-26 21:44 GMT+08:00 Michal Hocko :
> On Wed 26-07-17 21:07:42, Wenwei Tao wrote:
>> From: Wenwei Tao
>>
>> By removing the child cgroup while the parent cgroup is
>> under reclaim, we could trigger the following kernel panic
>> on kernel 3.10:
>>
On 26-07-17, 14:00, Saravana Kannan wrote:
> No, the alternative is to pass it on to the CPU freq driver and let it
> decide what it wants to do. That's the whole point if having a CPU freq
> driver -- so that the generic code doesn't need to care about HW specific
> details. Which is the point I w
On Thu, 2017-07-27 at 11:19 +0800, Honghui Zhang wrote:
> On Thu, 2017-07-27 at 10:58 +0800, honghui.zh...@mediatek.com wrote:
> > From: Ryder Lee
> >
> > Introduce a structure "mtk_pcie_soc" to abstract the differences between
> > controller generations, and the .startup() hook is used to encaps
On 26-07-17, 19:42, Rafael J. Wysocki wrote:
> On Wednesday, July 26, 2017 02:52:32 PM Viresh Kumar wrote:
> > + /* Don't allow remote callbacks */
> > + if (smp_processor_id() != data->cpu)
> > + return;
>
> You can do this check against cpu->cpu, however.
>
> > + /* Don't allow
This reverts commit 809ecb9bca6a9424ccd392d67e368160f8b76c92. Since it
was reported to break vhost_net. We want to cache used event and use
it to check for notification. The assumption was that guest won't move
the event idx back, but this could happen in fact when 16 bit index
wraps around after 6
On Thu, 2017-07-27 at 10:58 +0800, honghui.zh...@mediatek.com wrote:
> From: Ryder Lee
>
> Introduce a structure "mtk_pcie_soc" to abstract the differences between
> controller generations, and the .startup() hook is used to encapsulate
> some SoC-dependent related setting. In doing so, the commo
Unnecessary platform_set_drvdata() has been removed since the driver
core clears the driver data to NULL after device release or on
probe failure. There is no need to manually clear the device
driver data to NULL.
The Coccinelle semantic patch used to make this change is as follows:
//
@@
struct p
On 07/26/2017 06:34 AM, Punit Agrawal wrote:
> Michal Hocko writes:
>
>> On Wed 26-07-17 14:33:57, Michal Hocko wrote:
>>> On Wed 26-07-17 13:11:46, Punit Agrawal wrote:
>> [...]
I've been running tests from mce-test suite and libhugetlbfs for similar
changes we did on arm64. There coul
From: Ryder Lee
Add support for MediaTek new generation controller and update related
properities.
Signed-off-by: Ryder Lee
Signed-off-by: Honghui Zhang
---
.../devicetree/bindings/pci/mediatek-pcie.txt | 168 -
1 file changed, 161 insertions(+), 7 deletions(-)
diff
Henrique,
I like your suggestion, thanks!
BTW. let's discuss (and patch) turbostat on linux-pm, rather than on lkml.
thanks,
-Len
On Tue, Jul 25, 2017 at 11:59 AM, Henrique de Moraes Holschuh
wrote:
> On Tue, 25 Jul 2017, Prarit Bhargava wrote:
>> A common way of determining if the system is
Hi Prarit,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.13-rc2]
[cannot apply to next-20170726]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Prarit-Bhargava/printk
From: Ryder Lee
This is a transitional patch. We currently use platfarm_get_resource() for
retrieving the IOMEM resources, but there might be some chips don't have
subsys/shared registers part, which depends on platform design, and these
will be introduced in further patches.
Switch this functio
From: Ryder Lee
Add support for MediaTek new generation controller and update related
properities.
Signed-off-by: Ryder Lee
Signed-off-by: Honghui Zhang
---
.../devicetree/bindings/pci/mediatek-pcie.txt | 168 -
1 file changed, 161 insertions(+), 7 deletions(-)
diff
From: Ryder Lee
Add support for new Gen2 controller which has two root ports and shares
the probing flow with legacy controller. Currently this IP block can be
found on MT7622/MT2712.
Signed-off-by: Ryder Lee
Signed-off-by: Honghui Zhang
---
drivers/pci/host/Kconfig | 5 +-
drivers/
From: Ryder Lee
In order to accommodate other SoC generations, this patch updates filename
to make it more generic, regroups specific properties by SoCs, and removes
redundant descriptions.
Signed-off-by: Ryder Lee
---
...{mediatek,mt7623-pcie.txt => mediatek-pcie.txt} | 29 +++
From: Ryder Lee
Introduce a structure "mtk_pcie_soc" to abstract the differences between
controller generations, and the .startup() hook is used to encapsulate
some SoC-dependent related setting. In doing so, the common code which
will be reused by future chips.
In addition, we change the approa
From: Honghui Zhang
MediaTek's PCIe host controller has two generation HWs, the new
generation HW has two root ports, it shares most probing flow with the
legacy controller. But the read/write config space logical is different
from the lagacy controller.
This patchset abstract the common probing
Hi, Jay,
Sorry for the mistake in last mail, the ovp is 462, and the reserved is 235.
I check the code and have not found problems with p.max_search yet.
Just forget the this patch, since there is still 870 segments below, so
it should
not be the assumed case of this patch.
By the way, I have
Hi,
On 26 July 2017 at 20:08, Sebastian Reichel
wrote:
> Hi,
>
> On Wed, Jul 26, 2017 at 11:05:25AM +0800, Baolin Wang wrote:
>> On 25 July 2017 at 17:59, Sebastian Reichel
>> wrote:
>> > On Tue, Jul 25, 2017 at 04:00:01PM +0800, Baolin Wang wrote:
>> >> Integrate with the newly added USB charge
Hi Michael,
At 07/27/2017 10:21 AM, Michael Ellerman wrote:
Dou Liyang writes:
Commit a7be6e5a7f8d ("mm: drop useless local parameters of
__register_one_node()") removes the last user of parent_node().
The parent_node() macro in POWERPC platform is unnecessary.
Remove it for cleanup.
Repor
2017-07-24 22:20 GMT+08:00 Paolo Bonzini :
> There are three issues in nested_vmx_check_exception:
>
> 1) it is not taking PFEC_MATCH/PFEC_MASK into account, as reported
> by Wanpeng Li;
>
> 2) it should rebuild the interruption info and exit qualification fields
> from scratch, as reported by Jim
On 07/27/2017 01:02 AM, Michael S. Tsirkin wrote:
On Wed, Jul 26, 2017 at 11:48:41AM +0800, Wei Wang wrote:
On 07/23/2017 09:45 AM, Michael S. Tsirkin wrote:
On Fri, Jul 14, 2017 at 03:12:43PM +0800, Wei Wang wrote:
On 07/14/2017 04:19 AM, Michael S. Tsirkin wrote:
On Thu, Jul 13, 2017 at 03:
On Wed, Jul 26, 2017 at 10:27:05PM -0400, Stefan Berger wrote:
> cap_inode_need_killpriv returns 1 if security.capability exists and
> has a value and inode_killpriv() is required, 0 otherwise. Fix the
> description of the return value to reflect this.
>
> Signed-off-by: Stefan Berger
Thanks, St
From: Liwei Song
This is a follow up to commit f712c71f7b2b ("ACPI, APEI: Fixup common
access width firmware bug") fix the following firmware bug:
[Firmware Bug]: APEI: Invalid bit width + offset in GAR [0xb2/16/0/1/1]
This is due to an 8-bit access width is specified for a 16-bit register,
Rea
On Wed, Jul 26, 2017 at 02:02:42PM -0700, David Daney wrote:
> On 07/26/2017 01:08 PM, Greg KH wrote:
> > On Wed, Jul 26, 2017 at 01:02:38PM -0700, David Daney wrote:
> > > On 07/26/2017 10:33 AM, Greg KH wrote:
> > > > On Wed, Jul 26, 2017 at 06:30:49PM +0200, Borislav Petkov wrote:
> > > > > On W
cap_inode_need_killpriv returns 1 if security.capability exists and
has a value and inode_killpriv() is required, 0 otherwise. Fix the
description of the return value to reflect this.
Signed-off-by: Stefan Berger
---
security/commoncap.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-
xhci_disable_slot() is a helper for disabling a slot when a device
goes away or recovers from error situations. Currently, it returns
success when it sees a dead host. This is not the right way to go.
It should return error and let the invoker know that disable slot
command was failed due to a dead
If xhci_disable_slot() returns success, a disable slot command
trb was queued in the command ring. The command completion
handler will free the virtual device data structure associated
with the slot. On the other hand, when xhci_disable_slot()
returns error, the invokers should take the responsibil
xhci_disable_slot() allows the invoker to pass a command pointer
as paramenter. Otherwise, it will allocate one. This will cause
memory leak when a command structure was allocated inside of this
function while queuing command trb fails. Another problem comes up
when the invoker passed a command poi
Xhci driver handles USB transaction errors on transfer events,
but transaction errors are possible on address device command
completion events as well.
The xHCI specification (section 4.6.5) says: A USB Transaction
Error Completion Code for an Address Device Command may be due
to a Stall response
1 - 100 of 968 matches
Mail list logo
