Hi Stephen,
On jeu., juin 15 2017, Stephen Rothwell wrote:
> Hi all,
>
> I noticed that commit
>
> c6f4e66bd0f4 ("arm64: marvell: dts: add xmdio nodes for 7k/8k")
>
> has no Signed-off-by for its comitter.
Thanks for the warning, I fix it right now.
Gregory
>
> --
> Cheers,
> Stephen Ro
Implement an arch-speicfic watchdog rather than use the perf-based
hardlockup detector.
The new watchdog takes the soft-NMI directly, rather than going
through perf. Perf interrupts are to be made maskable in future, so
that would prevent the perf detector from working in those regions.
Additiona
Split SOFTLOCKUP_DETECTOR from LOCKUP_DETECTOR, and split
HARDLOCKUP_DETECTOR_PERF from HARDLOCKUP_DETECTOR.
LOCKUP_DETECTOR implies the general boot, sysctl, and programming
interfaces for the lockup detectors.
An architecture that wants to use a hard lockup detector must define
HAVE_HARDLOCKUP_
Signed-off-by: Nicholas Piggin
---
include/linux/nmi.h | 3 ---
1 file changed, 3 deletions(-)
diff --git a/include/linux/nmi.h b/include/linux/nmi.h
index aa3cd0878270..5e2e57536d98 100644
--- a/include/linux/nmi.h
+++ b/include/linux/nmi.h
@@ -12,9 +12,6 @@ extern void touch_softlockup_watchdo
Colin Ian King wrote:
> Trivial fix to spelling mistake in ath6kl_dbg debug message
>
> Signed-off-by: Colin Ian King
> Reviewed-by: Steve deRosier
> Signed-off-by: Kalle Valo
Patch applied to ath-next branch of ath.git, thanks.
fe611d047e45 ath6kl: fix spelling mistake: "Indicat" -> "Indic
After reconfiguring watchdog sysctls etc., architecture specific
watchdogs may not get all their parameters updated.
watchdog_reconfigure() can be implemented to pull the new values
in and set the arch NMI watchdog.
Signed-off-by: Nicholas Piggin
---
kernel/watchdog.c | 29 +
For architectures that define HAVE_NMI_WATCHDOG, instead of having
them provide the complete touch_nmi_watchdog() function, just have
them provide arch_touch_nmi_watchdog().
This gives the generic code more flexibility in implementing this
function, and arch implementations don't miss out on touch
This is the latest series to make the hardlockup watchdog more
easily replaceable by arch code. The last patch provides some
justification for why we want to do this (existing sparc watchdog
is another that could benefit).
Since last time, we tidied up the Kconfig approach so it was not
so jumbled
This patchset adds driver support for UFS for Hi3660 SoC. It is verified on
HiKey960 board
In v2
The dts ufs node patch,
v2-0003-arm64-dts-Add-ufs-dts-node-for-Hisilicon-Hi3660-S.patch,
is dependent on the patch below:
>From Guodong Xu
https://www.spinics.net/lists/arm-kernel/msg588232.html
B
This enable configs for Hi3660 UFS driver.
Reviewed-by: Chen Feng
Signed-off-by: Zhangfei Gao
Signed-off-by: Chen Jun
Signed-off-by: Guodong Xu
---
arch/arm64/configs/defconfig | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
i
add hi3660 ufs driver code
Signed-off-by: Geng Jianfeng
Signed-off-by: Bu Tao
Signed-off-by: Zang Leigang
Signed-off-by: Yu Jianfeng
---
drivers/scsi/ufs/Kconfig | 8 +
drivers/scsi/ufs/Makefile | 1 +
drivers/scsi/ufs/ufs-hi3660.c | 727 ++
arm64: dts: add ufs node for hi3660
Signed-off-by: Bu Tao
---
arch/arm64/boot/dts/hisilicon/hi3660-hikey960.dts | 9 +
arch/arm64/boot/dts/hisilicon/hi3660.dtsi | 19 +++
2 files changed, 28 insertions(+)
diff --git a/arch/arm64/boot/dts/hisilicon/hi3660-hikey96
add ufs node document for hi3660
Signed-off-by: Bu Tao
---
.../devicetree/bindings/ufs/hi3660-ufs.txt | 58 ++
1 file changed, 58 insertions(+)
create mode 100644 Documentation/devicetree/bindings/ufs/hi3660-ufs.txt
diff --git a/Documentation/devicetree/bindings/ufs
Partitions in HiKey960 are formatted as f2fs and squashfs.
f2fs is for userdata; squashfs is for system. Both partitions are required
by Android.
Signed-off-by: Zhangfei Gao
Signed-off-by: Chen Jun
Signed-off-by: Guodong Xu
---
arch/arm64/configs/defconfig | 8
1 file changed, 8 inser
Andi,
On Thu, Jun 15, 2017 at 4:18 PM, Andi Kleen wrote:
>> Looking at this approach, the user interface is straightforward,
>> implementation in the x86 code is a bit more hairy because of the way
>> the branch_stack is captured, via the cpuc->lbr_entries. If you assume
>> that SKID_IP cannot be
On 15/06/17 20:55, Kim Phillips wrote:
>
> Signed-off-by: Kim Phillips
Looks like defines for sampling support that got mixed in with earlier
patches. We can always put them back when we need them, so:
Acked-by: Adrian Hunter
> ---
> tools/perf/arch/x86/util/intel-bts.c | 4
> tools/pe
Thomas,
can you take a look at the generic patches as they are the required
base for the block work?
On Fri, Jun 16, 2017 at 03:54:30PM +1000, NeilBrown wrote:
> Hi Jens,
> I didn't hear back ... have you had a chance to look?
> In case it helps, you can pull the full set, based on a recent Linus tree,
> from
> git://neil.brown.name/linux bioset
>
> or I can resend the patches if you lik
From: Velibor Markovski
Add compatible string for the ARM CCN-502 interconnect
Signed-off-by: Velibor Markovski
Acked-by: Mark Rutland
Signed-off-by: Scott Branden
---
drivers/bus/arm-ccn.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/bus/arm-ccn.c b/drivers/bus/arm-ccn.c
inde
From: Velibor Markovski
Add CCN-502 to the list of supported devices by ARM CCN PMU driver.
Signed-off-by: Velibor Markovski
Acked-by: Mark Rutland
Signed-off-by: Scott Branden
---
Documentation/devicetree/bindings/arm/ccn.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation
Add compatible string for ARM CCN-502 interconnect.
CCN-502 interconnect is already compatible with the
existing ARM CCN driver, which supports CCN-504.
Velibor Markovski (2):
dt-bindings: arm-ccn: Add bindings info for CCN-502 compatible string
bus: arm-ccn: Enable stats for CCN-502 intercon
On Friday 09 June 2017 01:34 AM, Rafał Miłecki wrote:
> From: Rafał Miłecki
>
> As explained in the commit 9200c6f177638 ("Revert "phy: Add USB3 PHY support
> for Broadcom NSP SoC"") this module should be modified to use MDIO bus as
> this is how PHY is really attached.
>
> This should allow r
Hi Rafal,
On Friday 16 June 2017 11:41 AM, Rafał Miłecki wrote:
> On 16 June 2017 at 08:04, Kishon Vijay Abraham I wrote:
>> On Thursday 11 May 2017 09:59 PM, Florian Fainelli wrote:
>>> On 05/11/2017 06:29 AM, Rafał Miłecki wrote:
@@ -297,6 +371,28 @@ static struct platform_driver bcm_ns_us
On Thu, Jun 15, 2017 at 02:05:21PM -0600, Logan Gunthorpe wrote:
> Presently, the order of the char devices listed in /proc/devices is not
> entirely sequential. If a char device has a major number greater than
> CHRDEV_MAJOR_HASH_SIZE (255), it will be ordered as if its major were
> module 255. Fo
Hi all,
Changes since 20170615:
Dropped tree: uuid (difficult merge conflict)
The clk tree gained a conflict against the reset tree.
The drm-tegra tree gained a conflict against the drm tree.
The kspp (was akpm) tree still had its build failure for which I reverted
a commit.
The sound-asoc
Hi Linus,
Here is one mmc fix intended for v4.12 rc6. It's based on v4.12-rc5.
Details are as usual found in the signed tag. Please pull this in!
Kind regards
Ulf Hansson
The following changes since commit 32c1431eea4881a6b17bd7c639315010aeefa452:
Linux 4.12-rc5 (2017-06-11 16:48:20 -0700)
On Thu, Jun 15, 2017 at 05:40:49PM -0700, Guenter Roeck wrote:
> On 06/15/2017 10:54 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.11.6 release.
> > There are 13 patches in this series, all will be posted as a response
> > to this one. If anyone has any i
On Fri 2017-06-16 01:07:00, Sakari Ailus wrote:
> On Wed, Jun 14, 2017 at 09:41:29PM +0200, Pavel Machek wrote:
> > diff --git a/drivers/media/platform/omap3isp/isp.c
> > b/drivers/media/platform/omap3isp/isp.c
> > index 4ca3fc9..b80debf 100644
> > --- a/drivers/media/platform/omap3isp/isp.c
> > +
On Thu, Jun 15, 2017 at 04:25:07PM -0600, Shuah Khan wrote:
> On 06/15/2017 11:54 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.11.6 release.
> > There are 13 patches in this series, all will be posted as a response
> > to this one. If anyone has any issu
On Mon, 15 May 2017 17:04:44 +0200, Milian Wolff wrote:
commit 1982ad48fc82c284a5cc55697a012d3357e84d01
Author: Milian Wolff
Date: Wed May 24 15:21:25 2017 +0900
> --- a/tools/perf/util/unwind-libdw.c
> +++ b/tools/perf/util/unwind-libdw.c
> @@ -168,12 +168,16 @@ frame_callback(Dwfl_Frame *sta
On 16 June 2017 at 08:04, Kishon Vijay Abraham I wrote:
> On Thursday 11 May 2017 09:59 PM, Florian Fainelli wrote:
>> On 05/11/2017 06:29 AM, Rafał Miłecki wrote:
>>> @@ -297,6 +371,28 @@ static struct platform_driver bcm_ns_usb3_driver = {
>>> .of_match_table = bcm_ns_usb3_id_table,
The uuid-types tree in uuid.git is immutable, please work on top
of that for ACPI - in fact ACPI was on the of trees we explicitly did this
for. So don't sneak any acpi bits in through the arm64 tree.
Hi Rafal,
On Thursday 11 May 2017 09:59 PM, Florian Fainelli wrote:
> On 05/11/2017 06:29 AM, Rafał Miłecki wrote:
>> From: Rafał Miłecki
>>
>> As USB 3.0 PHY is attached to the MDIO bus this module should provide a
>> MDIO driver and use a proper bus layer. This is a proper (cleaner)
>> solution
On 06/15/2017 11:24 PM, Eric Anholt wrote:
ERR_PTR() needs a negative errno argument.
Thanks, I'll queue it to drm-misc-next-fixes once it's opened.
Archit
Signed-off-by: Eric Anholt
---
drivers/gpu/drm/bridge/panel.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a
On Monday 12 June 2017 01:42 PM, Tony Lindgren wrote:
> Commit 8ae904e3c236 ("phy: cpcap-usb: Add CPCAP PMIC USB support")
> is missing return statement as noted by Colin Ian King
> . If the optional pins are not configured,
> we just want to return early and not attempt to configure the pins.
>
On Thu, May 11 2017, NeilBrown wrote:
> On Tue, May 02 2017, NeilBrown wrote:
>
>> This is a revision of my series of patches working
>> towards removing the bioset work queues.
>
> Hi Jens,
> could I get some feed-back about your thoughts on this series?
> Will you apply it? When? Do I need t
On Thursday 08 June 2017 05:01 PM, Srinath Mannam wrote:
> This patchset extends the Broadcom SATA PHY driver to add
> support for Stingray SATA PHY.
>
> All patches are based on linux-phy/next
>
> Changes since v1:
> - Rebased patchset on linux-phy/next
>
merged, thanks!
-Kishon
> Srinath
On 06/16/2017 02:11 AM, Eric Anholt wrote:
If the panel-bridge is being set up after the drm_mode_config_reset(),
then the connector's state would never get initialized, and we'd
dereference the NULL in the hotplug path. We also need to register
the connector, so that userspace can get at it.
2017-06-13 22:45 GMT+09:00 Masahiro Yamada :
> Introduce some macros and helpers to avoid magic numbers and
> rename macros/functions for clarification.
>
> - We see '| 2' in several places. This means Data Cycle in MAP11 mode.
> The Denali User's Guide says bit[1:0] of MAP11 is like follows:
>
Hi,
> From: linux-acpi-ow...@vger.kernel.org
> [mailto:linux-acpi-ow...@vger.kernel.org] On Behalf Of Peter
> Hutterer
> Subject: Re: [systemd-devel] [WIP PATCH 0/4] Rework the unreliable LID switch
> exported by ACPI
>
> On Thu, Jun 15, 2017 at 07:33:58AM +, Zheng, Lv wrote:
> > Hi, Peter
From: Suniel Mahesh
le16_to_cpu() accepts argument of type __le16 and cpu_to_le16()
returns an argument of type __le16. This patch fixes:
(a) the type of the variable that end's up getting return from
cpu_to_le16().
(b) the member types of struct hfa384x_host_scan_request_data,
struct hfa
With older kernels, printf.sh and bitmap.sh fail because they can't find
the respective test modules they are looking for.
Add the skip portion on missing the respective test_XXX module. Error out
the same way as prime_numbers.sh.
Signed-off-by: Sumit Semwal
---
tools/testing/selftests/lib/bitm
Hi all,
Today's linux-next merge of the uuid tree got conflicts in:
drivers/acpi/apei/ghes.c
include/uapi/linux/uuid.h
between commits:
f4dccde3f9b9 ("ras: acpi/apei: cper: add support for generic data v3
structure")
476e4940c251 ("ras: acpi / apei: generate trace event for unrecognize
Ravi Bangoria writes:
> When a kthread makes a call_usermodehelper() call the steps are:
> a. allocates current->mm
> b. load_elf_binary()
> c. populates current->thread.regs
>
> While doing this, interrupts are not disabled. If there is a perf
> interrupt in the middle of this process (i.e. s
Stephen Rothwell writes:
> After merging the wireless-drivers tree, today's linux-next build
> (x86_64 allmodconfig) produced this warning:
>
> drivers/net/wireless/broadcom/brcm80211/brcmfmac/usb.c: In function
> 'brcmf_usb_probe_phase2':
> drivers/net/wireless/broadcom/brcm80211/brcmfmac/usb.c:
When a filesystem is mounted from a loop device, writes are
throttled by balance_dirty_pages() twice: once when writing
to the filesystem and once when the loop_handle_cmd() writes
to the backing file. This double-throttling can trigger
positive feedback loops that create significant delays. The
Hi Jens,
one of these is a resend of a patch I sent a while back.
The other is new - loop closes files differently from close()
and in a way that can confuse NFS.
Thanks,
NeilBrown
---
NeilBrown (2):
loop: use filp_close() rather than fput()
loop: Add PF_LESS_THROTTLE to block/loo
When a loop device is being shutdown the backing file is
closed with fput(). This is different from how close(2)
closes files - it uses filp_close().
The difference is important for filesystems which provide a ->flush
file operation such as NFS. NFS assumes a flush will always
be called on last
Le 15/06/2017 à 19:20, Mark Brown a écrit :
The patch
ASoC: rockchip: Fix an error handling in 'rockchip_i2s_probe'
has been applied to the asoc tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-
Add MediaTek PCIe driver maintainer entry.
Signed-off-by: Ryder Lee
---
MAINTAINERS | 8
1 file changed, 8 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index f7d568b..736648e 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -9957,6 +9957,14 @@ S: Supported
F: Documentat
In preparation for splitting fujitsu-laptop into two separate modules, I
prepared two more cleanup series to minimize the amount of code being
moved around. This first series contains all patches that touch ACPI in
some way, which is why I am CCing linux-acpi as per Rafael's previous
advice.
This
Calling acpi_bus_update_power() for ACPI devices FUJ02B1 and FUJ02E3 is
pointless as they are not power manageable (neither _PS0 nor _PR0 is
defined for any of them), which causes their power state to be inherited
from their parent devices. Given the ACPI paths of these two devices
(\_SB.PCI0.LPCB
In the case of brightness-related FUJ02B1 ACPI device, initializing the
input device associated with it identically as acpi-video initializes
its input device makes sense. However, using the same data for the
input device associated with the FUJ02E3 ACPI device makes little sense,
because the latt
All ACPI device notify callbacks are invoked using acpi_os_execute(),
which causes the supplied callback to be queued to a static workqueue
which always executes on CPU 0. This means that there is no possibility
for any ACPI device notify callback to be concurrently executed on
multiple CPUs, whic
Do not check whether the pointer passed to ACPI add callbacks is NULL as
it is earlier dereferenced anyway in the bus-level probe callback,
acpi_device_probe().
Do not check the value of acpi_disabled in fujitsu_init(), because it is
already done by acpi_bus_register_driver(), which is the first f
acpi_ns_initialize_devices(), which is called during system-wide ACPI
initialization, already detects and calls all _INI methods belonging to
objects present in ACPI tables. There is no need to call these methods
again every time the module is loaded because they only initialize
status flags and h
Using a dedicated Kconfig option for enabling debugging means the user
may be forced to recompile their kernel in order to gather debugging
information, which is inconvenient. Replace custom debugging
infrastructure with standard logging functions, taking advantage of
dynamic debug. Replace a pr_
No formatting is needed when setting ACPI device name and class, so
switch to using strcpy() for this purpose.
Signed-off-by: Michał Kępień
---
drivers/platform/x86/fujitsu-laptop.c | 9 -
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/drivers/platform/x86/fujitsu-laptop.c
On Thu, Jun 15, 2017 at 8:05 PM, Andy Lutomirski wrote:
> On Thu, Jun 15, 2017 at 7:17 PM, H.J. Lu wrote:
>> On Thu, Jun 15, 2017 at 4:28 PM, Andy Lutomirski wrote:
>>> On Thu, Jun 15, 2017 at 4:11 PM, H.J. Lu wrote:
On Thu, Jun 15, 2017 at 3:45 PM, Andy Lutomirski wrote:
> On Thu, Ju
Hi Alexander,
On 16 June 2017 at 04:35, Alexander Alemayhu wrote:
> On Thu, Jun 15, 2017 at 11:26:53PM +0530, Sumit Semwal wrote:
>>
>> 4. bpf tests: These seem to have build failures in mainline as well -
>> I also tried to build kselftest-next, but a simple 'make -C
>> tools/testing/selftests/b
Works like a charm with Milian's patch.
Acked-by: Ravi Bangoria
Note:
I still see very minor differences between libunwind and libdw. Also, second
last
function gets repeated two times in every callchain but it can be fixed later
on.
Otherwise all looks good!
Thanks,
-Ravi
On Thursday 15 Jun
On Mon, May 15, 2017 at 10:58:24AM +0200, Michal Hocko wrote:
>From: Michal Hocko
>
>The current memory hotplug implementation relies on having all the
>struct pages associate with a zone/node during the physical hotplug phase
>(arch_add_memory->__add_pages->__add_section->__add_zone). In the vast
Hi Linus,
This is the main fixes pull for 4.12-rc6, all pretty normal for this
stage, nothing really stands out. The mxsfb one is probably the
largest and it's for a black screen boot problem.
Dave.
The following changes since commit 32c1431eea4881a6b17bd7c639315010aeefa452:
Linux 4.12-rc5 (2
Tetsuo Handa wrote:
> and clarify in your patch that there is no possibility
> of waiting for direct/indirect memory allocation inside free_pgtables(),
> in addition to fixing the bug above.
Oops, this part was wrong, for __oom_reap_task_mm() will give up after
waiting for one second because down_
Thanks, Wei.
On Fri, Jun 16, 2017 at 3:55 AM, Wei Xu wrote:
> Hi Guodong,
>
> On 2017/6/8 23:08, Guodong Xu wrote:
>> From: Wang Xiaoyin
>>
>> add device node for hi6421 pmic core and hi6421v530
>> voltage regulator,include LDO(1,3,9,11,15,16)
>>
>> Signed-off-by: Wang Xiaoyin
>> Signed-off-by:
Hi all,
On Fri, 16 Jun 2017 11:13:35 +1000 Stephen Rothwell
wrote:
>
> On Fri, 16 Jun 2017 10:57:22 +1000 Michael Ellerman
> wrote:
> >
> > "Rowand, Frank" writes:
> >
> > > On Thursday, June 15, 2017 2:25 AM, Abdul Haleem
> > > [mailto:abdha...@linux.vnet.ibm.com] wrote:
> > >>
> >
On Fri, 2017-06-16 at 12:13 +1000, NeilBrown wrote:
> On Thu, Jun 15 2017, Andrew Morton wrote:
>
> > On Wed, 07 Jun 2017 12:08:38 +1000 NeilBrown wrote:
> >
> > >
> > > If a positive status is passed with the AUTOFS_DEV_IOCTL_FAIL
> > > ioctl, autofs4_d_automount() will return
> > > ERR_PTR
Hi Kees,
On Thu, 15 Jun 2017 20:20:47 -0700 Kees Cook wrote:
>
> I'm so confused -- isn't this in next? All the build tests I did were
> against yesterday's -next which includes this from what I can see...
It is in next, but gets merged after the kspp tree ... so, this is when
inter-tree depende
David Miller [mailto:da...@davemloft.net]
> Sent: Wednesday, June 14, 2017 1:02 AM
> > v2:
> > For #1, replace GFP_KERNEL with GFP_NOIO for usb_submit_urb().
> >
> > v1:
> > Improve the flow about runtime suspend/resume and make the code
> > easy to read.
>
> Series applied.
Excuse me. I don't se
Hi all,
Today's linux-next merge of the tip tree got a conflict in:
drivers/acpi/apei/ghes.c
between commit:
d0189b2eef2e ("acpi: apei: handle SEA notification type for ARMv8")
from the arm64 tree and commit:
7bf130e4a065 ("ACPI/APEI: Handle GSIV and GPIO notification types")
from the
On Thu, Jun 15, 2017 at 7:51 PM, Daniel Micay wrote:
> On Fri, 2017-06-16 at 11:30 +1000, Stephen Rothwell wrote:
>> Hi Kees,
>>
>> After merging the kspp tree, today's linux-next build (x86_64
>> allmodconfig) failed like this:
>>
>> In file included from include/linux/bitmap.h:8:0,
>>
On Thu, Jun 15, 2017 at 04:10:17PM +0800, Wei Wang wrote:
> On 06/14/2017 01:56 AM, Michael S. Tsirkin wrote:
> > On Fri, Jun 09, 2017 at 06:41:38PM +0800, Wei Wang wrote:
> > > Add a new feature, VIRTIO_BALLOON_F_PAGE_CHUNKS, which enables
> > > the transfer of the ballooned (i.e. inflated/deflate
Hi Steven & Sebastian,
If there are no more comments, could you like to give reviewed-by? :)
Regards
Alex
On 05/25/2017 01:26 PM, Alex Shi wrote:
> The rt-mutex-design documents didn't gotten meaningful update from its
> first version. Even after owner's pending bit was removed in commit
> 8161
It's a serious bug which cause arm/arm64 rt boot failed.
Anyone like to give a glance?
Thanks
Alex
On 06/14/2017 09:22 PM, Alex Shi wrote:
> This is a quick fix for a bug as 'scheduling while atomic' or
> 'scheduling from the idle thread' on arm/arm64.
>
> On arm/arm64, rwlock cpu_pm_notifier_lo
On Fri, Jun 16, 2017 at 09:07:57AM +0800, Boqun Feng wrote:
> On Thu, Jun 15, 2017 at 10:56:29AM -0700, Paul E. McKenney wrote:
> [...]
> > > >
> > > > FWLIW, I agree. There was a smb_mb() in RT-linux's equivalent of
> > > > swait_activate().
> > > >
> > > > https://www.spinics.net/lists/linux-r
On Thu, Jun 15, 2017 at 10:12 PM, Alan Stern wrote:
> On Thu, 15 Jun 2017, Kai-Heng Feng wrote:
>
>> On Wed, Jun 14, 2017 at 1:28 AM, Bjorn Helgaas wrote:
>> >
>> > The lspci output [1] shows:
>> >
>> > 00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI
>> > Controller (re
On Thu, Jun 15, 2017 at 7:17 PM, H.J. Lu wrote:
> On Thu, Jun 15, 2017 at 4:28 PM, Andy Lutomirski wrote:
>> On Thu, Jun 15, 2017 at 4:11 PM, H.J. Lu wrote:
>>> On Thu, Jun 15, 2017 at 3:45 PM, Andy Lutomirski wrote:
On Thu, Jun 15, 2017 at 3:40 PM, H.J. Lu wrote:
> On Thu, Jun 15, 20
Hello,
On Thu, Jun 15, 2017 at 05:52:24PM +0300, Kirill A. Shutemov wrote:
> This patch uses modifed pmdp_invalidate(), that return previous value of pmd,
> to transfer dirty and accessed bits.
>
> Signed-off-by: Kirill A. Shutemov
> ---
> fs/proc/task_mmu.c | 8
> mm/huge_memory.c
> https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/ in the
> 4.13/scsi-queue and for-next branches. I think that's why Kees didn't
> include it but I get he needs to add that.
s/get/guess/
Or is that repo supposed to get pulled into next?
On Fri, 2017-06-16 at 11:30 +1000, Stephen Rothwell wrote:
> Hi Kees,
>
> After merging the kspp tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> In file included from include/linux/bitmap.h:8:0,
> from include/linux/cpumask.h:11,
> fr
Thanks Naveen,
On Thursday 15 June 2017 08:57 PM, Naveen N. Rao wrote:
> Hmm... are you sure it's the same issue? The above commit only went into
> v4.7, which means we weren't able to use --call-graph=dwarf till v4.7.
Yes sorry. It's from v4.7 onwards.
-Ravi
On Thu, Jun 15, 2017 at 4:37 PM, Dave Hansen wrote:
> On 06/15/2017 03:18 PM, Andy Lutomirski wrote:
>>> As you pointed out, if you are using XSAVEC's compaction features by
>>> leaving bits unset in the requested feature bitmap registers, you have
>>> no idea how much data XSAVEC will write, unle
Hi Matt,
[auto build test WARNING on security/next]
[also build test WARNING on v4.12-rc5 next-20170615]
[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/Matt-Brown/Add-Trusted-Path-Execution-as
Signed-off-by: Fengguang Wu
---
tpe_lsm.c |8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/security/tpe/tpe_lsm.c b/security/tpe/tpe_lsm.c
index fda811a..77d2498 100644
--- a/security/tpe/tpe_lsm.c
+++ b/security/tpe/tpe_lsm.c
@@ -42,7 +42,7 @@ static int tpe_strict
Hi Richard,
2017-06-15 17:36 GMT+09:00 Richard Genoud :
> Since commit fcc8487d477a ("uapi: export all headers under uapi
> directories") fakechroot make bindeb-pkg fails, mismatching files for
> directories:
> touch: cannot touch 'usr/include/video/uvesafb.h/.install': Not a
> directory
>
> This
On Thu, Jun 15, 2017 at 4:28 PM, Andy Lutomirski wrote:
> On Thu, Jun 15, 2017 at 4:11 PM, H.J. Lu wrote:
>> On Thu, Jun 15, 2017 at 3:45 PM, Andy Lutomirski wrote:
>>> On Thu, Jun 15, 2017 at 3:40 PM, H.J. Lu wrote:
On Thu, Jun 15, 2017 at 3:18 PM, Andy Lutomirski wrote:
> On Thu, Ju
On Thu, Jun 15 2017, Andrew Morton wrote:
> On Wed, 07 Jun 2017 12:08:38 +1000 NeilBrown wrote:
>
>>
>> If a positive status is passed with the AUTOFS_DEV_IOCTL_FAIL
>> ioctl, autofs4_d_automount() will return
>>ERR_PTR(status)
>> with that status to follow_automount(), which will then
>> de
unction)
err = -ENOMEM;
^
Caused by commit
c3a3d3c41b74 ("ASoC: rockchip: Fix an error handling in 'rockchip_i2s_probe'")
I have used the sound-asoc tree from next-20170615 for today.
--
Cheers,
Stephen Rothwell
On Thu, 2017-06-15 at 18:49 -0700, Jay Vosburgh wrote:
> Joe Perches wrote:
>
> > On Thu, 2017-06-15 at 19:14 +0100, Michael J Dilmore wrote:
> > > Multiple netdev_info messages clutter kernel output. Also add netdev_dbg
> > > for packets per slave.
> >
> > []
> > > diff --git a/drivers/net/bon
On (06/15/17 17:31), Petr Mladek wrote:
[..]
> > diff --git a/include/linux/console.h b/include/linux/console.h
> > index b8920a031a3e..a2525e0d7605 100644
> > --- a/include/linux/console.h
> > +++ b/include/linux/console.h
> > @@ -127,7 +127,7 @@ static inline int con_debug_leave(void)
> > */
>
On (06/15/17 16:54), Petr Mladek wrote:
> On Wed 2017-06-14 18:11:28, Sergey Senozhatsky wrote:
> > On (06/13/17 14:54), Petr Mladek wrote:
> >
> > > This patch modifies the code that enables the configured consoles.
> > > It sets the CON_CONSDEV flag also when we register the first
> > > console.
On Mon, 5 Jun 2017, Florian Fainelli wrote:
> Out of the many MIPS platforms only 3 appear to be actually using an
> I8042 keyboard controller: SGI, JAZZ and LOOGSON64, remove
> ARCH_MIGHT_HAVE_PC_SERIO from the top-level MIPS Kconfig symbol and move
> it down to those platforms that need it.
Ho
Joe Perches wrote:
>On Thu, 2017-06-15 at 19:14 +0100, Michael J Dilmore wrote:
>> Multiple netdev_info messages clutter kernel output. Also add netdev_dbg for
>> packets per slave.
>[]
>> diff --git a/drivers/net/bonding/bond_options.c
>> b/drivers/net/bonding/bond_options.c
>[]
>> @@ -9,6 +9,
The "all_var" looks like a variable, but is actually a macro.
Use IS_ENABLED(CONFIG_KALLSYMS_ALL) for clarification.
Signed-off-by: Masahiro Yamada
---
kernel/kallsyms.c | 10 ++
1 file changed, 2 insertions(+), 8 deletions(-)
diff --git a/kernel/kallsyms.c b/kernel/kallsyms.c
index 6a
On 06/15/17 17:06, Benjamin Herrenschmidt wrote:
> On Fri, 2017-06-09 at 22:47 -0700, frowand.l...@gmail.com wrote:
>> From: Frank Rowand
>>
>> Remove "phandle" and "linux,phandle" properties from the internal
>> device tree. The phandle will still be in the struct device_node
>> phandle field.
>
Hi Kees,
After merging the kspp tree, today's linux-next build (x86_64
allmodconfig) failed like this:
In file included from include/linux/bitmap.h:8:0,
from include/linux/cpumask.h:11,
from arch/x86/include/asm/cpumask.h:4,
from arch/x86/include
Hi Kees,
On Thu, 15 Jun 2017 17:35:43 -0700 Kees Cook wrote:
>
> Sounds good. I've added ARCH_HAS_FORTIFY_SOURCE to the patch (and noted it).
And that just made it in time for today's linux-next. I have removed
the patches from Andrew's tree.
--
Cheers,
Stephen Rothwell
Hi Michael,
On Fri, 16 Jun 2017 10:57:22 +1000 Michael Ellerman wrote:
>
> "Rowand, Frank" writes:
>
> > On Thursday, June 15, 2017 2:25 AM, Abdul Haleem
> > [mailto:abdha...@linux.vnet.ibm.com] wrote:
> >>
> >> On Thu, 2017-06-15 at 11:30 +0530, Abdul Haleem wrote:
> >>>
> >>> linux-next
On 2017/6/13 5:28, Alexander Duyck wrote:
> On Mon, Jun 12, 2017 at 4:05 AM, Ding Tianhong
> wrote:
...
>> /**
>> + * pcie_clear_relaxed_ordering - clear PCI Express relaxed ordering bit
>> + * @dev: PCI device to query
>> + *
>> + * If possible clear relaxed ordering
>> + */
>> +int pcie_clea
Hi Thierry,
Today's linux-next merge of the drm-tegra tree got a conflict in:
Documentation/gpu/index.rst
between commit:
bed41005e617 ("drm/pl111: Initial drm/kms driver for pl111")
from the drm tree and commit:
fa6d095eb23a ("drm/tegra: Add driver documentation")
from the drm-tegra t
1 - 100 of 999 matches
Mail list logo
