Hi Stefan, Daniel,
On Mon, Sep 04, 2017 at 02:52:13PM +0800, Leo Yan wrote:
> After applied Stefan Wahren patch ("ARM: cpuidle: Avoid memleak if init
> fail") there have no memleak issue, but the code is not consistent to
> handle initialization failure between driver registration and device
> reg
On Fri, Sep 01, 2017 at 11:35:40PM +0100, André Przywara wrote:
> On 01/09/17 07:04, Maxime Ripard wrote:
> > On Fri, Sep 01, 2017 at 01:31:35AM +0100, Andre Przywara wrote:
> >> Hi,
> >>
> >> On 31/08/17 00:36, Stefan Brüns wrote:
> >>> The A64 SoC has the same dma engine as the H3 (sun8i), with a
On Mon, Sep 04, 2017 at 12:23:09AM +0100, André Przywara wrote:
> On 03/09/17 23:40, Stefan Brüns wrote:
> > The H83T uses a compatible string different from the A23, but requires
>
> A83T
>
> > the same clock autogating register setting.
> >
> > The H3 also requires setting the clock auto
Hello Guenter
Thank you again for reviewing my patches!
It was the first time for me :-) to add something to the kernel.
+- vref-supply
+ The external reference in microvolt for this device is set to this
value.
+ If it does not exists the reference will be set to 330uV
(3.3V).
s/exis
2017-09-04 2:54 GMT+02:00 Mauro Carvalho Chehab :
> Em Sun, 3 Sep 2017 22:05:23 +0200
> Honza Petrouš escreveu:
>
>> 1) #define CA_SET_DESCR _IOW('o', 134, ca_descr_t)
>>
>>
>> CA_SET_DESCR is used for feeding descrambler device
>> with correct key
Linus,
Please pull the latest perf-core-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf-core-for-linus
# HEAD: 1b2f76d77a277bb70d38ad0991ed7f16bbc115a9 Merge tag
'perf-core-for-mingo-4.14-20170829' of
git://git.kernel.org/pub/scm/linux/kernel/git/a
Hi,
I haven't heard anything about this driver. I'm trying to interpret if
the silence is because there is something fundamentally wrong with the
driver or is it because it doesn't use any of the mailbox
infrastructure it is being ignored.
Either way I'm happy to address the problems - in the eve
Linus,
Please pull the latest ras-core-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git ras-core-for-linus
# HEAD: 9662d43f523dfc0dc242ec29c2921c43898d6ae5 x86/mce/AMD: Allow any CPU
to initialize the smca_banks array
A single change fixing SMCA bank ini
On 08/24/2017 10:04 AM, Oleksandr Andrushchenko wrote:
Hello,
On 08/24/2017 07:38 AM, Takashi Sakamoto wrote:
On Aug 23 2017 23:51, Oleksandr Grytsov wrote:
Hi,
Thank you for detailed explanation.
We understand that emulated interrupt on the frontend side is
completely not
acceptable and d
On 08/31/2017 12:24 PM, Joe Lawrence wrote:
Hi Joao,
Hi Joe and Josh,
Thanks for the quick feedback, I'll be looking forward for your comments
once you have the change to dig deeper :). I'll apply all typo-fixes,
add klpclean to the PHONY targets and change the quiet_cmd invocation as
sug
Linus,
Please pull the latest sched-core-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
sched-core-for-linus
# HEAD: bbdacdfed2f5fa50a2cc9f500a36e05990a0837d sched/debug: Optimize
sched_domain sysctl generation
The main changes in this cycle were:
-
Hey,
I recently tried enabling the bfq scheduler by booting with
scsi_mod.use_blk_mq=1 and selecting the scheduler using the following
/etc/udev/rules.d/60-scheduler.rules:
ACTION=="add|change", KERNEL=="sd[a-z]", ATTR{queue/scheduler}="bfq"
I’m using an INTEL SSDSC2BP48 disk.
The system boots
On Fri, Sep 01, 2017 at 11:51:53PM +0100, David Howells wrote:
> Peter Zijlstra wrote:
>
> > if (obj) {
> > /* use obj */
> > refcount_dec(&obj->refs); /* should never hit 0 */
> > }
>
> You've missed a bit: We need to tell the gc to run when we reduce the refcount
> to 1:
>
Hi,
On Fri, Sep 01, 2017 at 11:48:38PM +0200, Hans de Goede wrote:
> The Intel cherrytrail xhci controller has an extended cap mmio-range
> which contains registers to control the muxing to the xhci (host mode)
> or the dwc3 (device mode) and vbus-detection for the otg usb-phy.
>
> Having a mux d
On Sat, Sep 02, 2017 at 08:33:03AM +0800, Ethan Zhao wrote:
> Yep, that is the first place I considered to set the limit, but that would
> break KABI ?
nah..
Hi Dan,
After merging the nvdimm tree, today's linux-next build (i386 defconfig)
failed like this:
drivers/dax/super.c:64:20: error: redefinition of 'fs_dax_get_by_bdev'
struct dax_device *fs_dax_get_by_bdev(struct block_device *bdev)
^
In file included from drivers/dax/super
On 03/09/17 23:12, Stafford Horne wrote:
> On Fri, Sep 01, 2017 at 06:25:01PM +0100, Marc Zyngier wrote:
>> On 01/09/17 02:24, Stafford Horne wrote:
>>> On Thu, Aug 31, 2017 at 10:28:01AM +0100, Marc Zyngier wrote:
On 30/08/17 22:58, Stafford Horne wrote:
> From: Stefan Kristiansson
[...
On Fri, Sep 01, 2017 at 04:36:25PM +0300, Ville Syrjälä wrote:
> On Fri, Sep 01, 2017 at 04:07:16PM +0900, Hoegeun Kwon wrote:
> > If scanout started, we should reduce etime by delta_ns. But delta_ns
> > is negative if scanout has not started. If delta_ns is negative,
> > subtraction of delta_ns fr
Hi Divagar,
On Mon, Sep 04, 2017 at 12:10:45PM +0530, Divagar Mohandass wrote:
> Currently the device is kept in D0, there is an opportunity
> to save power by enabling runtime pm.
>
> Device can be daisy chained from PMIC and we can't rely on I2C core
> for auto resume/suspend. Driver will decid
Peter,
On 2017/9/4 15:32, Peter Zijlstra wrote:
On Sat, Sep 02, 2017 at 08:33:03AM +0800, Ethan Zhao wrote:
Yep, that is the first place I considered to set the limit, but that would
break KABI ?
nah..
V4 sent, please ignore v2 & v3.
Thanks,
Ethan
On Mon, Sep 04, 2017 at 12:40:56AM +0200, Stefan Brüns wrote:
> Preparatory patch: If the same compatible is used for different SoCs which
> have a common register layout, but different number of channels, the
> channel count can no longer be stored in the config. Store it in the
> device structure
Linus,
please pull the latest timers-core-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
timers-core-for-linus
A rather small update for the time(r) subsystem:
- A new clocksource driver IMX-TPM
- Minor fixes to the alarmtimer facility
- Device tree
On Sat, Sep 02, 2017 at 02:57:32PM +0800, Ethan Zhao wrote:
> diff --git a/kernel/sysctl.c b/kernel/sysctl.c
> index 6648fbb..609bed2 100644
> --- a/kernel/sysctl.c
> +++ b/kernel/sysctl.c
> @@ -367,7 +367,7 @@ static int sysrq_sysctl_handler(struct ctl_table *table,
> int write,
> .
Hi Dietmar,
Removing cpu effificiency table looks good to me. Nevertheless, i have
some comments below for this patch.
On 30 August 2017 at 16:41, Dietmar Eggemann wrote:
> Remove the 'cpu_efficiency/clock-frequency dt property' based solution
> to set cpu capacity which was only working for Cor
On Mon, 28 Aug 2017, Andrey Smirnov wrote:
> Add Device Tree bindings for RAVE Supervisory Processor, an MCU
> implementing varoius bits of housekeeping functionality (watchdoging,
> backlight control, LED control, etc) on RAVE family of products by
> Zodiac Inflight Innovations.
>
> Cc: cphe...@
Linus,
Please pull the latest x86-asm-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-asm-for-linus
# HEAD: dd88a0a0c8615417fe6b4285769b5b772de87279 objtool: Handle GCC stack
pointer adjustment bug
The main highlights for this cycle are:
- Introdu
Peter,
On 2017/9/4 15:49, Peter Zijlstra wrote:
On Sat, Sep 02, 2017 at 02:57:32PM +0800, Ethan Zhao wrote:
diff --git a/kernel/sysctl.c b/kernel/sysctl.c
index 6648fbb..609bed2 100644
--- a/kernel/sysctl.c
+++ b/kernel/sysctl.c
@@ -367,7 +367,7 @@ static int sysrq_sysctl_handler(struct ctl_ta
On Sun, Sep 03, 2017 at 08:59:35AM +0200, Mike Galbraith wrote:
>
> [ 126.626908] Unregister pv shared memory for cpu 1
> [ 126.631041]
> [ 126.631269] ==
> [ 126.632442] WARNING: possible circular locking dependency detected
> [ 126.633599
On Tue, 29 Aug 2017, Guenter Roeck wrote:
> On 08/29/2017 07:19 AM, Sebastian Reichel wrote:
> > Hi Guenter,
> >
> > On Tue, Aug 29, 2017 at 06:34:39AM -0700, Guenter Roeck wrote:
> > > On 08/29/2017 05:51 AM, Sebastian Reichel wrote:
> > > > Hi Lee,
> > > >
> > > > I noticed, that you did not y
On Sun, Sep 03, 2017 at 01:50:51AM -0700, Joel Fernandes wrote:
> Critical section trace events can be used for tracing the start and
> end of a critical section which can be used by a trace viewer like
> systrace to graphically view the start and end of a critical section and
> correlate them with
Linus,
please pull the latest smp-hotplug-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
smp-hotplug-for-linus
A single fix to handle the removal of the first dynamic CPU hotplug state
correctly.
Thanks,
tglx
-->
Ethan Barnes (1)
Linus,
Please pull the latest x86-boot-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-boot-for-linus
# HEAD: 0982adc746736a313dac9cb8cc936ca51ca3741a x86/boot/KASLR: Work around
firmware bugs by excluding EFI_BOOT_SERVICES_* and EFI_LOADER_* from KA
On Mon, Sep 04, 2017 at 12:40:53AM +0200, Stefan Brüns wrote:
> For the H3, the burst lengths field offsets in the channel configuration
> register differs from earlier SoC generations.
>
> Using the A31 register macros actually configured the H3 controller
> do to bursts of length 1 always, which
在 2017/9/1 5:17, Daniel Lezcano 写道:
Hi Kevin,
On 29/08/2017 10:17, Tao Wang wrote:
From: Tao Wang
This patch adds the support for thermal sensor of Hi3660 SoC.
for the Hi3660 SoC thermal sensor.
this will register sensors for thermal framework and use device
tree to bind cooling devic
On Mon, Sep 04, 2017 at 12:40:55AM +0200, Stefan Brüns wrote:
> The H3 supports bursts lengths of 1, 4, 8 and 16 transfers, each with
> a width of 1, 2, 4 or 8 bytes.
>
> The register value for the the width is log2-encoded, change the
> conversion function to provide the correct value for width =
Linus,
Please pull the latest x86-build-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-build-for-linus
# HEAD: 9e8730b178a2472fca3123e909d6e69cc8127778 x86/build: Use cc-option to
validate stack alignment parameter
More Clang support related fixes.
On Sat, 02 Sep 2017 15:58:05 -0700, Joe Perches wrote:
> On Sat, 2017-09-02 at 23:03 +0200, Jean Delvare wrote:
> > Oh, btw, is there any purpose in listing a number in front of each
> > type?
>
> Not really. I did that because I wanted a header
> and because I had no idea how many of those typ
Hi Philipp,
On Fri, Sep 01, 2017 at 06:30:00PM +0200, Philipp Rossak wrote:
> From: Philipp Rossak
>
> The WiFi side of the AP6212 WiFi/BT combo module is connected to
> mmc1. There are also GPIOs for enable and interrupts.
>
> Enable WiFi on this board by enabling mmc1 and adding the power
> s
On Sat, Sep 02, 2017 at 03:01:57PM +0800, icen...@aosc.io wrote:
> 在 2017-09-02 00:30，Philipp Rossak 写道：
> > From: Philipp Rossak
> >
> > The WiFi side of the AP6212 WiFi/BT combo module is connected to
> > mmc1. There are also GPIOs for enable and interrupts.
> >
> > Enable WiFi on this board b
Linus,
Please pull the latest x86-cpu-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-cpu-for-linus
# HEAD: aac64f7de999d5a7fff55f49434fdd87df919829 x86/cpu/amd: Hide unused
legacy_fixup_core_id() function
AMD F17h related updates.
Thanks,
Hi Philipp,
On Fri, Sep 01, 2017 at 06:30:01PM +0200, Philipp Rossak wrote:
> From: Philipp Rossak
>
> * vqmmc is in this case not needed
> * no need for pincontrol nodes when the pin is set to a GPIO
>
> Signed-off-by: Philipp Rossak
> ---
> arch/arm/boot/dts/sun8i-h3-bananapi-m2-plus.dts |
Linus,
Please pull the latest x86-debug-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-debug-for-linus
# HEAD: 4f167201edda7cd7525cc7f23944731ef5dd99a8 x86/numa_emulation:
Recalculate numa_nodes_parsed from emulated nodes
Various fixes to the NUMA
Drop the header and numbering of types. This format was confusing as
it suggested one could pass the number instead of the type name,
however it did not actually work, and numbering wasn't stable anyway.
Signed-off-by: Jean Delvare
Cc: Andy Whitcroft
Cc: Joe Perches
---
scripts/checkpatch.pl |
Linus,
Please pull the latest x86-microcode-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-microcode-for-linus
# HEAD: aa78c1ccfab6018289bc2bfd0092d516d0a49ec5 x86/microcode/intel:
Improve microcode patches saving flow
Update documentation, improv
On Fri, 1 Sep 2017, Dmitry Torokhov wrote:
> Jiri, there are some unwanted interactions between hid-multitouch and
> this driver, please hold off applying it (if you were considering it).
I have been on vacation for past 14 days, so I didn't even make it to
reviewing it ... ignoring it for now,
在 2017/9/1 5:13, Daniel Lezcano 写道:
On 29/08/2017 10:17, Tao Wang wrote:
From: Tao Wang
Bind thermal sensor driver for Hi3660.
The description is a bit light :)
All right
Signed-off-by: Tao Wang
Signed-off-by: Leo Yan
---
arch/arm64/boot/dts/hisilicon/hi3660.dtsi| 14 +
On Thu, Aug 31, 2017 at 03:42:57PM +0100, Mel Gorman wrote:
> On Thu, Aug 31, 2017 at 08:46:28AM +0200, Paolo Valente wrote:
> > [SECOND TAKE, with just the name of one of the tester fixed]
> >
> > Hi,
> > while testing the read-write unfairness issues reported by Mel, I
> > found BFQ failing to g
On 03/09/17 10:38, Nicolas Iooss wrote:
> Commit d162809f85b4 ("xen/x86: Do not call xen_init_time_ops() until
> shared_info is initialized") moved xen_init_time_ops() from __init to
> __ref without updating xen-ops.h accordingly. Fix this.
>
> Fixes: d162809f85b4 ("xen/x86: Do not call xen_init_t
Hi Rafael, Baoquan, and Chao,
At 09/04/2017 10:26 AM, Baoquan He wrote:
On 09/04/17 at 12:55am, Rafael J. Wysocki wrote:
On Sunday, September 3, 2017 4:31:23 PM CEST Chao Fan wrote:
KASLR should choose the memory region of immovable node to extract kernel.
So get ACPI SRAT table and store the
Salut,
On 04/09/17 08:04, Maxime Ripard wrote:
> On Fri, Sep 01, 2017 at 11:35:40PM +0100, André Przywara wrote:
>> On 01/09/17 07:04, Maxime Ripard wrote:
>>> On Fri, Sep 01, 2017 at 01:31:35AM +0100, Andre Przywara wrote:
Hi,
On 31/08/17 00:36, Stefan Brüns wrote:
> The A64 So
This driver has been available on https://github.com/iksaif/thinkpad-wmi for
a few year and is already deployed on large fleets of thinkpad laptops.
The WMI interface is documented here:
http://download.lenovo.com/ibmdl/pub/pc/pccbbs/thinkcentre_pdf/hrdeploy_en.pdf
It mostly focused on changing B
From: Michal Hocko
Memory offlining can fail just too eagerly under a heavy memory pressure.
[ 5410.336792] page:ea22a646bd00 count:255 mapcount:252
mapping:88ff926c9f38 index:0x3
[ 5410.336809] flags: 0x9855fe40010048(uptodate|active|mappedtodisk)
[ 5410.336811] page dumped because: is
Hi,
while testing memory hotplug on a large 4TB machine we have noticed that
memory offlining is just too eager to fail. The primary reason is that
the retry logic is just too easy to give up. We have 4 ways out of the
offline
- we have a permanent failure (isolation or memory notifiers fai
From: Michal Hocko
We have a hardcoded 120s timeout after which the memory offline fails
basically since the hot remove has been introduced. This is essentially
a policy implemented in the kernel. Moreover there is no way to adjust
the timeout and so we are sometimes facing memory offline failure
Hi Antony,
On Fri, Sep 01, 2017 at 12:53:13PM +0200, Antony Antony wrote:
> > > +&emac {
> > > + pinctrl-names = "default";
> > > + pinctrl-0 = <&emac_rgmii_pins>;
> > > + phy-supply = <®_gmac_3v3>;
> > > + phy-handle = <&ext_rgmii_phy>;
> > > + phy-mode = "rgmii";
> > > + status = "okay";
> > > +
On 04.09.2017 04:35, Kyeongdon Kim wrote:
Thanks for your reply,
But I couldn't find "NR_FRAGMENT_PAGES" in linux-next.git .. is that vmstat
counter? or others?
I mean rather than adding bunch vmstat counters for operations it might be
worth to add page counter which will show current amount
On Friday 01 September 2017 08:37 PM, Adam Ford wrote:
> At the request of Sekhar Nori from TI, this is a follow-up to
This can be:
Suggested-by: Sekhar Nori
> pending ("ARM: dts: da850-evm: add serial and ethernet aliases")
Any patch dependency references need to go below the tear line ("---"
在 2017-08-22 13:23，Icenowy Zheng 写道：
The compatible string for Allwinner V3s SoC used to be missing.
Add it to the binding document.
Fixes: b074fede01c0 ("arm: sunxi: add support for V3s SoC")
Signed-off-by: Icenowy Zheng
Maxime, Chen-Yu, ping.
Could you queue this patchset to 4.15?
---
The commit 7b2d0dbac489 ("x86/mm/pkeys: Pass VMA down in to fault signal
generation code") pass down a vma pointer to the error path, but that is
done once the mmap_sem is released when calling mm_fault_error() from
__do_page_fault().
This is dangerous as the pointed vma structure is no more safe
In collect_md mode, if the tun dev is down, it still can call
ip_tunnel_rcv to receive on packets, and the rx statistics increase
improperly.
Fixes: 2e15ea390e6f ("ip_gre: Add support to collect tunnel metadata.")
Cc: Pravin B Shelar
Signed-off-by: Haishuang Yan
---
Change since v3:
* Increme
In collect_md mode, if the tun dev is down, it still can call
__ip6_tnl_rcv to receive on packets, and the rx statistics increase
improperly.
Fixes: 8d79266bc48c ("ip6_tunnel: add collect_md mode to IPv6 tunnels")
Cc: Alexei Starovoitov
Signed-off-by: Haishuang Yan
---
Change since v3:
* Incr
On 09/04/17 at 04:17pm, Dou Liyang wrote:
> With "movable_node=1024M" option in cmdline, KASLR will can't access
> the node3 memory.
So you have extended the movable_node option from no value specified to
adding a limit value, then why don't you go one step further to extend
it as movable_node=xxx
This code is no longer used, the logging function was changed by commit
fbca164776e4 ("net: stmmac: Use the right logging function in
stmmac_mdio_register").
It was previously showing information about the type of the IRQ, if it's
polled, ignored or a normal interrupt. As we don't want information
Linus,
Please pull the latest x86-spinlocks-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-spinlocks-for-linus
# HEAD: c455fd9235b6bd2802db86109cfa0ec105992f68 x86/nmi: Use raw lock
Convert an NMI lock to raw.
Thanks,
Ingo
-
Hi Ralf and Martin,
On 09/03/2017 11:14 PM, Martin Blumenstingl wrote:
> Hi Hauke, Hi Ralf,
>
> On Sun, Sep 3, 2017 at 6:13 PM, Stephen Rothwell
> wrote:
>> Hi all,
>>
>> Commits
>>
>> bb19a5e5205b MIPS: lantiq: Remove the arch/mips/lantiq/xway/reset.c
>> implementation
>> f6a4de1654c9 MIPS: l
Linus,
Please pull the latest x86-syscall-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-syscall-for-linus
# HEAD: cf7de27ab35172a9240f079477cae3146a182998 arm64/syscalls: Check
address limit on user-mode return
Improve the security of set_fs(): w
Hi Baoquan,
At 09/04/2017 04:39 PM, Baoquan He wrote:
On 09/04/17 at 04:17pm, Dou Liyang wrote:
With "movable_node=1024M" option in cmdline, KASLR will can't access
the node3 memory.
So you have extended the movable_node option from no value specified to
adding a limit value, then why don't y
From: Huang Ying
When developing code to bootup some APs (Application CPUs)
asynchronously, the following kernel panic is encountered. After
checking the code, it is found that the IRQ descriptor may be NULL
during CPU hotplug. So I added corresponding NULL pointer checking to
fix this. And it
Hi all,
After merging the powerpc tree, today's linux-next build (powerpc
allyesconfig) produced this warning:
WARNING: vmlinux.o(.text+0xa7cb8): Section mismatch in reference from the
function .xive_spapr_init() to the function .init.text:.xive_core_init()
The function .xive_spapr_init() refere
On Sun, 27 Aug 2017, Pierre-Hugues Husson wrote:
> Extend the driver to support Ricoh RC5T619.
> Support the additional regulators and slightly different voltage ranges.
>
> Signed-off-by: Pierre-Hugues Husson
> ---
> drivers/regulator/Kconfig | 4 ++--
> drivers/regulator/rn5t618-
> Il giorno 04 set 2017, alle ore 10:14, Mel Gorman
> ha scritto:
>
> On Thu, Aug 31, 2017 at 03:42:57PM +0100, Mel Gorman wrote:
>> On Thu, Aug 31, 2017 at 08:46:28AM +0200, Paolo Valente wrote:
>>> [SECOND TAKE, with just the name of one of the tester fixed]
>>>
>>> Hi,
>>> while testing the
Hi Andrew,
After merging the akpm-current tree, today's linux-next build (x86_64
allmodconfig) failed like this:
/home/sfr/next/next/mm/hmm.c:202:2: error: unknown field 'invalidate_page'
specified in initializer
.invalidate_page = hmm_invalidate_page,
^
/home/sfr/next/next/mm/hmm.c:202:21:
> If you want to use an existing ID for an eeprom for a different size,
> there is no way to override it currently.
Can you give an example for that?
signature.asc
Description: PGP signature
On 2017/9/4 16:21, Michal Hocko wrote:
> From: Michal Hocko
>
> We have a hardcoded 120s timeout after which the memory offline fails
> basically since the hot remove has been introduced. This is essentially
> a policy implemented in the kernel. Moreover there is no way to adjust
> the timeout a
On Mon 04-09-17 16:58:30, Xishi Qiu wrote:
> On 2017/9/4 16:21, Michal Hocko wrote:
>
> > From: Michal Hocko
> >
> > We have a hardcoded 120s timeout after which the memory offline fails
> > basically since the hot remove has been introduced. This is essentially
> > a policy implemented in the k
Hi,
Another two weeks, another ping. Is everything allright with Dmitry?
-- Sebastian
On Mon, Aug 21, 2017 at 12:03:51PM +0200, Sebastian Reichel wrote:
> Hi,
>
> ping?
>
> -- Sebastian
>
> On Tue, Jul 25, 2017 at 03:56:56PM +0200, Sebastian Reichel wrote:
> > Hi Dmitry,
> >
> > Gentle ping
From: Colin Ian King
Don't populate the array seq on the stack, instead make it static.
Makes the object code smaller by over 170 bytes:
Before:
textdata bss dec hex filename
132273232 0 16459404b drivers/input/joystick/adi.o
After:
textdata bss
On Mon, Sep 04, 2017 at 04:39:14PM +0800, Baoquan He wrote:
>On 09/04/17 at 04:17pm, Dou Liyang wrote:
>> With "movable_node=1024M" option in cmdline, KASLR will can't access
>> the node3 memory.
>
>So you have extended the movable_node option from no value specified to
>adding a limit value, then
Em Mon, 4 Sep 2017 09:12:49 +0200
Honza Petrouš escreveu:
> 2017-09-04 2:54 GMT+02:00 Mauro Carvalho Chehab :
> > Em Sun, 3 Sep 2017 22:05:23 +0200
> > Honza Petrouš escreveu:
> >
> >> 1) #define CA_SET_DESCR _IOW('o', 134, ca_descr_t)
> >>
> >
On Mon, Sep 4, 2017 at 4:14 PM, Mel Gorman wrote:
> On Thu, Aug 31, 2017 at 03:42:57PM +0100, Mel Gorman wrote:
>> On Thu, Aug 31, 2017 at 08:46:28AM +0200, Paolo Valente wrote:
>> > [SECOND TAKE, with just the name of one of the tester fixed]
>> >
>> > Hi,
>> > while testing the read-write unfair
Hi all,
Changes since 20170901:
The s390 tree gained a conflict against Linus' tree.
The block tree gained a conflict against Linus' tree.
The tip tree gained a conflict against the mips tree.
The usb tree gained a conflict against the mips tree.
The nvdimm tree gained a build failure for whi
On 2017/9/4 17:01, Michal Hocko wrote:
> On Mon 04-09-17 16:58:30, Xishi Qiu wrote:
>> On 2017/9/4 16:21, Michal Hocko wrote:
>>
>>> From: Michal Hocko
>>>
>>> We have a hardcoded 120s timeout after which the memory offline fails
>>> basically since the hot remove has been introduced. This is ess
Attempt to untangle the ordering in blk-mq. The patch introducing the
single smp_mb__before_atomic() is obviously broken in that it doesn't
clearly specify a pairing barrier and an obtained guarantee.
The comment is further misleading in that it hints that the
deadline store and the COMPLETE stor
Linus,
Please pull the latest locking-core-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
locking-core-for-linus
# HEAD: d82fed75294229abc9d757f08a4817febae6c4f4 locking/lockdep/selftests:
Fix mixed read-write ABBA tests
NOTE: this tree depends on you
On Mon 04-09-17 17:05:15, Xishi Qiu wrote:
> On 2017/9/4 17:01, Michal Hocko wrote:
>
> > On Mon 04-09-17 16:58:30, Xishi Qiu wrote:
> >> On 2017/9/4 16:21, Michal Hocko wrote:
> >>
> >>> From: Michal Hocko
> >>>
> >>> We have a hardcoded 120s timeout after which the memory offline fails
> >>> ba
On 29-08-17, 14:03, Greg Kroah-Hartman wrote:
> Who couldn't reach an agreement?
Rob Herring (DT Maintainer) didn't like the first set of bindings and wasn't
convinced that we need any new bindings for this purpose to begin with.
> So you gave up and decided to make a
> whole bunch of kernel code
On 04/09/2017 02:58, Leo Yan wrote:
> On Sat, Sep 02, 2017 at 10:34:34AM +0200, Daniel Lezcano wrote:
>> On 02/09/2017 04:54, Leo Yan wrote:
>>> On Wed, Aug 30, 2017 at 10:47:32AM +0200, Daniel Lezcano wrote:
The TEMP0_CFG configuration register contains different field to set up the
temp
On Mon, Sep 04, 2017 at 03:51:32PM +1000, Stephen Rothwell wrote:
> Hi Greg,
>
> Today's linux-next merge of the usb tree got a conflict in:
>
> drivers/phy/Makefile
>
> between commit:
>
> 0ab3aa747f26 ("phy: Add an USB PHY driver for the Lantiq SoCs using the RCU
> module")
>
> from the
Hi Stephen,
On 2017/9/1 21:28, Stephen Boyd wrote:
> On 09/01, Wei Xu wrote:
>> Hi Stephen,
>>
>> On 2017/9/1 2:32, Stephen Boyd wrote:
>>> On 08/29, Leo Yan wrote:
From: Dmitry Shmidt
This patch is to add watchdog binding for Hi6220 on Hikey board.
Signed-off-by: Dmitry
On Mon, 4 Sep 2017, Huang, Ying wrote:
> diff --git a/kernel/irq/cpuhotplug.c b/kernel/irq/cpuhotplug.c
> index 638eb9c83d9f..af9029625271 100644
> --- a/kernel/irq/cpuhotplug.c
ry> +++ b/kernel/irq/cpuhotplug.c
> @@ -129,10 +129,13 @@ void irq_migrate_all_off_this_cpu(void)
> struct irq_desc
Linus,
Please pull the latest x86-mm-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-mm-for-linus
# HEAD: 9e52fc2b50de3a1c08b44f94c610fbe998c0031a x86/mm: Enable RCU based
page table freeing (CONFIG_HAVE_RCU_TABLE_FREE=y)
[ NOTE: this tree depends o
From: Colin Ian King
Trivial fix to spelling mistake in dev_dbg message
Signed-off-by: Colin Ian King
---
drivers/clk/clk-hsdk-pll.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/clk/clk-hsdk-pll.c b/drivers/clk/clk-hsdk-pll.c
index bbf237173b37..c4ee280f454d
On Mon, Sep 04, 2017 at 11:15:47AM +0200, Viresh Kumar wrote:
> On 29-08-17, 14:03, Greg Kroah-Hartman wrote:
> > Who couldn't reach an agreement?
>
> Rob Herring (DT Maintainer) didn't like the first set of bindings and wasn't
> convinced that we need any new bindings for this purpose to begin wi
2017-09-04 11:06 GMT+02:00 Mauro Carvalho Chehab :
> Em Mon, 4 Sep 2017 09:12:49 +0200
> Honza Petrouš escreveu:
>
>> 2017-09-04 2:54 GMT+02:00 Mauro Carvalho Chehab :
>> > Em Sun, 3 Sep 2017 22:05:23 +0200
>> > Honza Petrouš escreveu:
>> >
>> >> 1) #define CA_SET_DESCR _IOW('o', 134, ca_des
Linus,
please pull the latest x86-apic-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-apic-for-linus
NOTE: this tree depends on you having merged x86-asm-for-linus first. If that
could not be merged then please disregard this pull request.
This update
Add core pll node (core_clk) to manage cpu frequency.
core_clk node represents pll itself.
input_clk node represents clock signal source (basically xtal)
which comes to pll input.
Signed-off-by: Eugeniy Paltsev
---
arch/arc/boot/dts/hsdk.dts | 11 +--
arch/arc/configs/hsdk_defconfig
Sorry for delayed response...
On Tue, Aug 29, 2017 at 7:39 PM, Konrad Rzeszutek Wilk
wrote:
> On Tue, Aug 29, 2017 at 09:34:46AM +0530, Anup Patel wrote:
>> This patch adds Broadcom FlexRM low-level reset for
>> VFIO platform.
>>
>
> Is there an document that explains and /or details the various
By default, it is assumed that the UTMI clock is generated from a 12 MHz
reference clock (MAINCK). If it's not the case, the FREQ field of the
SFR_UTMICKTRIM has to be updated to generate the UTMI clock in the
proper way.
The UTMI clock has a fixed rate of 480 MHz. In fact, there is no
multiplier
Hello Lin,
Sorry for this late answer.
I'm not maintainer, just a contributor... but as some update seems
strange for me, so i prefer to highlight it to clarify them.
On 08/17/2017 04:24 AM, Lin Huang wrote:
> From: huang lin
>
> on some board use enable pin to control dmic start and stop,
> so
Hi Steve,
On Fri, Sep 01, 2017 at 06:33:11PM -0400, Steven Rostedt wrote:
> Recently kmemleak discovered a bug in my code where an allocated
> trampoline for a ftrace function tracer wasn't freed due to an exit
> path. The thing is, kmemleak was able to catch this 100% when it was
> triggered by o
1 - 100 of 533 matches
Mail list logo
