On 09/04/2017 10:21 AM, Michal Hocko wrote:
> 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|a
From: David Woodhouse
Date: Fri, 08 Sep 2017 18:23:22 +0100
> I don't know that anyone's ever tried saying "show me the chapter and
> verse of the documentation"
Do you know why I brought this up? Because the person I am replying
to told me that the syscall documentation should have suggested t
On 09/04/2017 10:21 AM, 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 timeo
Thanks for the comments. Replies inline.
On Fri, Sep 8, 2017 at 2:34 AM, Dan Carpenter wrote:
> On Thu, Sep 07, 2017 at 06:22:13PM -0700, Badhri Jagan Sridharan wrote:
>> +static int tcpm_validate_caps(struct tcpm_port *port, const u32 *pdo,
>> + unsigned int nr_pdo)
>>
On 09/08/2017 10:14 AM, Eugeniy Paltsev wrote:
On Wed, 2017-09-06 at 12:54 -0700, Vineet Gupta wrote:
On 09/06/2017 11:21 AM, Eugeniy Paltsev wrote:
DW ethernet controller on AXS10x hangs sometimes after SW reset, so
add temporary quirk to reset DW ethernet controller IP core.
This quirk can be
On Fri, Sep 8, 2017 at 2:45 AM, Greg Kroah-Hartman
wrote:
> On Thu, Sep 07, 2017 at 06:22:13PM -0700, Badhri Jagan Sridharan wrote:
>> The source and sink caps should follow the following rules.
>> This patch validates whether the src_caps/snk_caps adheres
>> to it.
>>
>> 6.4.1 Capabilities Messag
This is a port on kernel 4.13 of the work done by Peter Zijlstra to
handle page fault without holding the mm semaphore [1].
The idea is to try to handle user space page faults without holding the
mmap_sem. This should allow better concurrency for massively threaded
process since the page fault han
From: Peter Zijlstra
One of the side effects of speculating on faults (without holding
mmap_sem) is that we can race with free_pgtables() and therefore we
cannot assume the page-tables will stick around.
Remove the reliance on the pte pointer.
Signed-off-by: Peter Zijlstra (Intel)
---
mm/memo
On Thu, Sep 07, 2017 at 04:37:43PM +0800, Wei-Ning Huang wrote:
> From: Wei-Ning Huang
>
> Add Google hammer HID driver. This driver allow us to control hammer
> keyboard backlights and support future features. Since current hid-core
> logic does not allow us to specify different USB interface f
On Fri, Sep 8, 2017 at 1:25 PM, Linus Torvalds
wrote:
> On Fri, Sep 8, 2017 at 12:09 AM, Christoph Hellwig wrote:
>>
>> But yes, for the init-time integrity_read_file this is incorrect.
>> It never tripped up, and I explicitly added the lockdep annotations
>> so that anything would show up, and i
> -Original Message-
> From: Pavel Machek [mailto:pa...@ucw.cz]
> Sent: Friday, September 08, 2017 2:26 AM
> To: Tristram Ha - C24268
> Cc: and...@lunn.ch; muva...@gmail.com; nathan.leigh.con...@gmail.com;
> vivien.dide...@savoirfairelinux.com; f.faine...@gmail.com;
> net...@vger.kernel.org
Hi Liam,
I finally continues testing on OpenPandora.
> Am 31.08.2017 um 22:19 schrieb Liam Breck :
>
> Hi,
>
> This may be a fix that allows >0 input from DT, but won't try to
> program the register since the first 3 fields aren't compatible:
>
> ... bq27500_dm_regs[] = {
> ...
> [bq27xxx_dm_d
Hi,
On Fri, Sep 8, 2017 at 4:18 AM, Daniel Thompson
wrote:
> On 07/09/17 19:04, Doug Anderson wrote:
>> I'd agree that I don't think we should land Enric's series as-is.
>> ...but I think something has been missing from the discussion so far:
>> the fact that the backlight driver doesn't necessar
On Friday 08 September 2017 19:38:37 H. Nikolaus Schaller wrote:
> and here is the result:
>
> > root@letux:~# dmesg|fgrep bq27
> > [ 10.391235] bq27xxx_battery_setup
> > [ 10.391265] bq27xxx_battery_setup: dm_regs=bf0520e0
> > [ 10.393798] (NULL device *): hwmon: 'bq27500-1-0' is not a vali
Makes code more concise and readable
Signed-off-by: Harsha Sharma
---
Change in v2:
-Change in subject
-Change in log message
drivers/staging/typec/tcpm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/typec/tcpm.c b/drivers/staging/typec/tcpm.c
index 630
Maybe "Rewrite comparison to NULL pointer" in the subject to include what
was done, not just code was touched.
On Fri, 8 Sep 2017, Harsha Sharma wrote:
> Makes code more concise and readable
Makes -> Make. Commit logs should be written in the imperative, like you
are telling someone what to do.
From: Benson Leung
usbhid->intf->needs_remote_wakeup is set when a device is opened, and is
cleared when a device is closed.
In usbhid_open, usb_autopm_get_interface is called before setting the
needs_remote_wakeup flag, and usb_autopm_put_interface is called after
hid_start_in. However, when th
> Am 08.09.2017 um 19:40 schrieb Pali Rohár :
>
> On Friday 08 September 2017 19:38:37 H. Nikolaus Schaller wrote:
>> and here is the result:
>>
>>> root@letux:~# dmesg|fgrep bq27
>>> [ 10.391235] bq27xxx_battery_setup
>>> [ 10.391265] bq27xxx_battery_setup: dm_regs=bf0520e0
>>> [ 10.39379
On 08/09/2017 19:32, Laurent Dufour wrote:
> This is a port on kernel 4.13 of the work done by Peter Zijlstra to
> handle page fault without holding the mm semaphore [1].
Sorry for the noise, I got trouble sending the whole series through this
email. I will try again.
Cheers,
Laurent.
On Fri, Sep 8, 2017 at 2:36 AM, Dan Carpenter wrote:
> On Thu, Sep 07, 2017 at 06:22:14PM -0700, Badhri Jagan Sridharan wrote:
>> diff --git a/drivers/staging/typec/tcpm.c b/drivers/staging/typec/tcpm.c
>> index 58a2c279f7d1..df0986d9f756 100644
>> --- a/drivers/staging/typec/tcpm.c
>> +++ b/drive
On Tue, Sep 05, 2017 at 10:15:45AM -0400, Steven Rostedt wrote:
> On Mon, 4 Sep 2017 11:09:05 +0100
> Catalin Marinas wrote:
> > On Fri, Sep 01, 2017 at 06:33:11PM -0400, Steven Rostedt wrote:
> > > Now I was thinking that it may be due to the fact that the trampoline
> > > is allocated with modul
On 09/08/2017 05:02 PM, Colin King wrote:
From: Colin Ian King
The assignment of net via call sock_net will dereference sk. This
is performed before a sanity null check on sk, so there could be
a potential null dereference on the sock_net call if sk is null.
Fix this by assigning net after th
On Fri, Sep 08, 2017 at 01:46:30PM +0200, Pablo Neira Ayuso wrote:
> On Wed, Aug 30, 2017 at 05:18:04PM +0530, Arvind Yadav wrote:
> > rhashtable_params are not supposed to change at runtime. All
> > Functions rhashtable_* working with const rhashtable_params
> > provided by . So mark the non-const
Hi Linus,
We have a bigger set of updates for ARC this time (mostly because some couldn't
make last release bus). Please pull.
Thx,
-Vineet
--->
The following changes since commit cc4a41fe5541a73019a864883297bd5043aa6d98:
Linux 4.13-rc7 (2017-08-27 17:20:40 -0700)
are available in the
Make code more concise and readable
Signed-off-by: Harsha Sharma
---
Change in v3:
-Change in subject and log message
Change in v2:
-Change in subject
-Change in log message
drivers/staging/typec/tcpm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/type
I checked. __pmd() works.
BTW, my sparc32 fix was added in linux-next on August 11th
and __pmd() is there, too. This means __pmd() + my fix has survived
for almost a month in linux-next. It should be good.
--
Best Regards
Yan Zi
On 7 Sep 2017, at 23:43, Stephen Rothwell wrote:
> Hi all,
>
> On
Hello, Shaohua.
On Fri, Sep 08, 2017 at 10:07:15AM -0700, Shaohua Li wrote:
> > The fact that we're forwarding explicitly in loop still bothers me a
> > bit. Can you please elaborate why we don't want to do this
> > generically through aio?
>
> I think we must forward in loop, because each cmd c
> -Original Message-
> From: Pavel Machek [mailto:pa...@ucw.cz]
> Sent: Friday, September 08, 2017 2:19 AM
> To: Tristram Ha - C24268
> Cc: and...@lunn.ch; muva...@gmail.com; nathan.leigh.con...@gmail.com;
> vivien.dide...@savoirfairelinux.com; f.faine...@gmail.com;
> net...@vger.kernel.org
From: Adrian Salido
The buffer allocation is not currently accounting for an extra byte for
the report id. This can cause an out of bounds access in function
i2c_hid_set_or_send_report() with reportID > 15.
Signed-off-by: Guenter Roeck
Signed-off-by: Dmitry Torokhov
---
drivers/hid/i2c-hid/i2
Add pm-domains property which is required for 66AK2Gx. Also document 66AK2G
unique clocks property usage.
Signed-off-by: Franklin S Cooper Jr
Acked-by: Rob Herring
Acked-by: Sekhar Nori
---
Documentation/devicetree/bindings/i2c/i2c-davinci.txt | 12
1 file changed, 12 insertions(+
>> Hi Greg,
>>
>> Could you please apply it for 4.4-stable.
>> This fixes https://nvd.nist.gov/vuln/detail/CVE-2017-9985
>
> This vulnerability is just non-issue. You can't get it working
> practically; it requires a modified hardware of the decade old ISA
> sound card, and yet the system has to
66AK2G has I2C instances that are not apart of the ALWAYS_ON power domain
like other Keystone 2 SoCs and OMAPL138. Therefore, pm_runtime
is required to insure the power domain used by the specific I2C instance is
properly turned on along with its functional clock.
Signed-off-by: Franklin S Cooper
Add I2C support to 66AK2G. Primary requirement is to add PM
Runtime support to the driver.
This has been tested on following platforms by performing simple i2c test
such as i2c detect and reading on board i2c devices:
K2G GP evm
OMAPL138
K2L GP EVM
and boot tested on:
K2E GP EVM
K2HK GP EVM
Vers
On Thu, Sep 07, 2017 at 11:26:47PM +0200, Ingo Molnar wrote:
>
> * Eric Biggers wrote:
>
> > On Thu, Sep 07, 2017 at 09:15:34AM +0200, Ingo Molnar wrote:
> > >
> > > * Eric Biggers wrote:
> > >
> > > > Thanks for fixing these! I don't have time to review these in detail,
> > > > but I ran
>
Thank you !! :)
- Taeung
On 09/08/2017 11:36 PM, Arnaldo Carvalho de Melo wrote:
Em Thu, Sep 07, 2017 at 12:18:56PM +0900, Taeung Song escreveu:
When there isn't a config file (e.g. ~/.perfconfig)
or it has nothing, the config set wasn't created.
If the config set not exists, a config file c
On Fri, Sep 8, 2017 at 10:22 AM, Linus Torvalds
wrote:
>
> Of course, I only did a "make allmodconfig" to test the MODVERSIONS
> case, I didn't actually install the modules. Is that error perhaps
> only detected at install time?
Oh, I take that back. I just got a ton of warnings with my
allmodcon
Hi Arnaldo,
Now that the metrics patchkit has been merged, the actual JSON
metrics for Intel CPUs can be merged. Please pull this version.
It includes Skylake Server support and was rebased.
Thanks,
-Andi
The following changes since commit 1b2f76d77a277bb70d38ad0991ed7f16bbc115a9:
Merge tag
This message and any attachments may contain confidential information from
Cypress or its subsidiaries. If it has been received in error, please advise
the sender and immediately delete this message.
>From 891fe3887b53d2bad35d3f94c845ecb89ab58509 Mon Sep 17 00:00:00 2001
From: Jeffrey Chu
Dat
This is a port on kernel 4.13 of the work done by Peter Zijlstra to
handle page fault without holding the mm semaphore [1].
The idea is to try to handle user space page faults without holding the
mmap_sem. This should allow better concurrency for massively threaded
process since the page fault han
From: Peter Zijlstra
When speculating faults (without holding mmap_sem) we need to validate
that the vma against which we loaded pages is still valid when we're
ready to install the new PTE.
Therefore, replace the pte_offset_map_lock() calls that (re)take the
PTL with pte_map_lock() which can fa
On Fri, 8 Sep 2017, Harsha Sharma wrote:
> Make code more concise and readable
>
> Signed-off-by: Harsha Sharma
Acked-by: Julia Lawall
> ---
> Change in v3:
> -Change in subject and log message
> Change in v2:
> -Change in subject
> -Change in log message
> drivers/staging/typec/tcpm.c |
The speculative page fault handler which is run without holding the
mmap_sem is calling lru_cache_add_active_or_unevictable() but the vm_flags
is not guaranteed to remain constant.
Introducing __lru_cache_add_active_or_unevictable() which has the vma flags
value parameter instead of the vma pointer
The speculative page fault handler must be protected against anon_vma
changes. This is because page_add_new_anon_rmap() is called during the
speculative path.
In addition, don't try speculative page fault if the VMA don't have an
anon_vma structure allocated because its allocation should be
protec
From: Peter Zijlstra
Try a speculative fault before acquiring mmap_sem, if it returns with
VM_FAULT_RETRY continue with the mmap_sem acquisition and do the
traditional fault.
Signed-off-by: Peter Zijlstra (Intel)
[Clearing of FAULT_FLAG_ALLOW_RETRY is now done in
handle_speculative_fault()]
[
Colin King writes:
> From: Colin Ian King
>
> The current error handling on devm_kzalloc failures performs a non-null
> check on connector. Thss check is redundant because connector is null
> at that failure point. With this check removed, we may as well make
> the failure path into a trivial -
Add a new software event to count succeeded speculative page faults.
Signed-off-by: Laurent Dufour
---
include/uapi/linux/perf_event.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/uapi/linux/perf_event.h b/include/uapi/linux/perf_event.h
index 140ae638cfd6..101e509ee39b 100644
---
The current maybe_mkwrite() is getting passed the pointer to the vma
structure to fetch the vm_flags field.
When dealing with the speculative page fault handler, it will be better to
rely on the cached vm_flags value stored in the vm_fault structure.
This patch introduce a __maybe_mkwrite() servi
From: Peter Zijlstra
Provide infrastructure to do a speculative fault (not holding
mmap_sem).
The not holding of mmap_sem means we can race against VMA
change/removal and page-table destruction. We use the SRCU VMA freeing
to keep the VMA around. We use the VMA seqcount to detect change
(includi
When handling speculative page fault, the vma->vm_flags and
vma->vm_page_prot fields are read once the page table lock is released. So
there is no more guarantee that these fields would not change in our back.
They will be saved in the vm_fault structure before the VMA is checked for
changes.
This
There is a deadlock when a CPU is doing a speculative page fault and
another one is calling do_unmap().
The deadlock occurred because the speculative path try to spinlock the
pte while the interrupt are disabled. When the other CPU in the
unmap's path has locked the pte then is waiting for all the
Add support for the new speculative faults event.
Signed-off-by: Laurent Dufour
---
tools/include/uapi/linux/perf_event.h | 1 +
tools/perf/util/evsel.c | 1 +
tools/perf/util/parse-events.c| 4
tools/perf/util/parse-events.l| 1 +
tools/perf/util/python.c
This patch enable the speculative page fault on the PowerPC
architecture.
This will try a speculative page fault without holding the mmap_sem,
if it returns with VM_FAULT_RETRY, the mmap_sem is acquired and the
traditional page fault processing is done.
Support is only provide for BOOK3S_64 curre
When dealing with speculative page fault handler, we may race with VMA
being split or merged. In this case the vma->vm_start and vm->vm_end
fields may not match the address the page fault is occurring.
This can only happens when the VMA is split but in that case, the
anon_vma pointer of the new VM
This patch a set of new trace events to collect the speculative page fault
event failures.
Signed-off-by: Laurent Dufour
---
include/trace/events/pagefault.h | 87
mm/memory.c | 59 ++-
2 files changed, 135 ins
Em Tue, Sep 05, 2017 at 01:37:08PM -0700, Andi Kleen escreveu:
> On Tue, Sep 05, 2017 at 05:07:09PM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Tue, Sep 05, 2017 at 12:52:35PM -0700, Andi Kleen escreveu:
> > > > > I'll check.
> > > >
> > > > Ok, I couldn't reproduce it anymore, after you check t
When dealing with the speculative fault path we should use the VMA's field
cached value stored in the vm_fault structure.
Currently vm_normal_page() is using the pointer to the VMA to fetch the
vm_flags value. This patch provides a new __vm_normal_page() which is
receiving the vm_flags flags value
Hi,
please pull the following btrfs branch to 4.14. The changes range through all
types: cleanups, core chagnes, sanity checks, fixes, other user visible
changes, detailed list below.
Merging notes: there's a minor conflict with the blk_status_t fix that went to
4.13-rc7 while this pull is on top
Please pull nfsd changes for 4.14 from
git://linux-nfs.org/~bfields/linux.git tags/nfsd-4.14
More RDMA work and some op-structure constification from Chuck Lever,
and a small cleanup to our xdr encoding.
--b.
Chuck Lever (9):
sunrpc: Const-ify instances of struct svc_xprt_ops
nfs
migrate_misplaced_page() is only called during the page fault handling so
it's better to pass the pointer to the struct vm_fault instead of the vma.
This way during the speculative page fault path the saved vma->vm_flags
could be used.
Signed-off-by: Laurent Dufour
---
include/linux/migrate.h |
From: Peter Zijlstra
Wrap the VMA modifications (vma_adjust/unmap_page_range) with sequence
counts such that we can easily test if a VMA is changed.
The unmap_page_range() one allows us to make assumptions about
page-tables; when we find the seqcount hasn't changed we can assume
page-tables are
Em Fri, Sep 08, 2017 at 10:46:20AM +0200, Jiri Olsa escreveu:
> Do not carry the perf.data file descriptor into
> the workload process and close it when perf
> executes the workload.
Fails in some systems with:
util/data.c: In function 'open_file_write':
util/data.c:99: error: 'O_CLOEXEC' undecla
When handling page fault without holding the mmap_sem the fetch of the
pte lock pointer and the locking will have to be done while ensuring
that the VMA is not touched in our back.
So move the fetch and locking operations in a dedicated function.
Signed-off-by: Laurent Dufour
---
mm/memory.c |
The VMA sequence count has been introduced to allow fast detection of
VMA modification when running a page fault handler without holding
the mmap_sem.
This patch provides protection against the VMA modification done in :
- madvise()
- mremap()
- mpol_rebind_policy()
From: Peter Zijlstra
Manage the VMAs with SRCU such that we can do a lockless VMA lookup.
We put the fput(vma->vm_file) in the SRCU callback, this keeps files
valid during speculative faults, this is possible due to the delayed
fput work by Al Viro -- do we need srcu_barrier() in unmount
somepla
From: Peter Zijlstra
One of the side effects of speculating on faults (without holding
mmap_sem) is that we can race with free_pgtables() and therefore we
cannot assume the page-tables will stick around.
Remove the reliance on the pte pointer.
Signed-off-by: Peter Zijlstra (Intel)
---
mm/memo
On Fri, 8 Sep 2017 20:18:29 +0300
Georgi Djakov wrote:
> diff --git a/include/trace/events/interconnect.h
> b/include/trace/events/interconnect.h
> new file mode 100644
> index ..c4a72163873c
> --- /dev/null
> +++ b/include/trace/events/interconnect.h
> @@ -0,0 +1,45 @@
> +#undef TR
On Tue, Nov 22, 2016 at 2:27 PM, Brian Norris wrote:
> On Tue, Nov 22, 2016 at 03:00:47AM -0800, Eduardo Valentin wrote:
>> On Tue, Nov 22, 2016 at 03:52:25PM +0800, Zhang Rui wrote:
>> > On Fri, 2016-11-18 at 21:30 -0800, Brian Norris wrote:
>> > > On Fri, Nov 18, 2016 at 07:41:59PM -0800, Eduard
>OK, so that's really just another variant of the existing problem we have with
>certain PCI root complexes with restrictive inbound windows.
>The appropriate way to handle that is to reserve the unusable areas of the
>IOVA space up-front.
> Since the support for the ACPI equivalent of "dma-range
Hi Xie XiuQi,
(Sorry a few versions of this went past before I caught up with it)
On 07/09/17 08:45, Xie XiuQi wrote:
> With ARM v8.2 RAS Extension, SEA are usually triggered when memory errors
> are consumed. In some cases, if the error address is in a clean page or a
> read-only page, there is
Hi gengdongjiu,
On 04/09/17 12:43, gengdongjiu wrote:
> On 2017/9/1 1:50, James Morse wrote:
>> On 28/08/17 11:38, Dongjiu Geng wrote:
>>> In current code logic, the two functions ghes_sea_add() and
>>> ghes_sea_remove() are only called when CONFIG_ACPI_APEI_SEA
>>> is defined. If not, it will ret
Add I2C DT nodes for 66AK2G. Also enable I2C0 in K2G EVM which is needed
to access the I2C EEPROM.
Version 2 changes:
No real changes. Split patches into their own patchset
Murali Karicheri (1):
ARM: dts: keystone-k2g-evm: Add I2C EEPROM DT entry
Vitaly Andrianov (1):
ARM: dts: keystone-k2g
From: Vitaly Andrianov
Add nodes for the various I2C instances.
Signed-off-by: Vitaly Andrianov
Signed-off-by: Franklin S Cooper Jr
Reviewed-by: Grygorii Strashko
---
arch/arm/boot/dts/keystone-k2g.dtsi | 36
1 file changed, 36 insertions(+)
diff --git a
From: Murali Karicheri
K2G EVM has an onboard I2C EEPROM connected to I2C0. This patch adds
the necessary DT entry for the AT24CM01 EEPROM.
Signed-off-by: Murali Karicheri
Signed-off-by: Franklin S Cooper Jr
---
arch/arm/boot/dts/keystone-k2g-evm.dts | 19 +++
1 file changed,
On 09/08/2017 07:18 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.12.12 release.
> There are 43 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses s
On 08.09.2017 19:25, Luck, Tony wrote:
> On Fri, Sep 08, 2017 at 03:18:30PM +0900, Sergey Senozhatsky wrote:
>> if the addr is not in kernel .text, then try dereferencing it and check
>> if the dereferenced addr is in kernel .text.
>
> If it really is a function pointer, then we know that it is sa
> > > @@ -0,0 +1,2066 @@
> > > +/*
> > > + * Microchip KSZ8795 switch driver
> > > + *
> > > + * Copyright (C) 2017 Microchip Technology Inc.
> > > + * Tristram Ha
> > > + *
> > > + * Permission to use, copy, modify, and/or distribute this software for
> > > any
> > > + * purpose with or wi
On 09/08/2017 07:19 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.49 release.
> There are 32 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses sh
On Fri, 8 Sep 2017 18:45:20 +0100
Catalin Marinas wrote:
> > Hmm, could this also be what causes the miss of catching the lingering
> > ftrace trampoline?
>
> Not sure (not without some additional support in kmemleak to help track
> down the source of false negatives; I'm on a long flight to L
This driver works for jz4740 & jz4780
Suggested-by: Maarten ter Huurne
Signed-off-by: Mathieu Malaterre
---
drivers/watchdog/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/watchdog/Kconfig b/drivers/watchdog/Kconfig
index c722cbfdc7e6..ca200d1f310a 100644
--
The jz4740-watchdog driver supports both jz4740 & jz4780.
Signed-off-by: Mathieu Malaterre
---
arch/mips/boot/dts/ingenic/jz4780.dtsi | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/mips/boot/dts/ingenic/jz4780.dtsi
b/arch/mips/boot/dts/ingenic/jz4780.dtsi
index 4853ef67b3ab..33d7
> > > > @@ -0,0 +1,2066 @@
> > > > +/*
> > > > + * Microchip KSZ8795 switch driver
> > > > + *
> > > > + * Copyright (C) 2017 Microchip Technology Inc.
> > > > + * Tristram Ha
> > > > + *
> > > > + * Permission to use, copy, modify, and/or distribute this software for
> any
> > > > + * purpose
Update the Ci20's defconfig to enable the JZ4740's watchdog driver.
Signed-off-by: Mathieu Malaterre
---
arch/mips/configs/ci20_defconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/mips/configs/ci20_defconfig b/arch/mips/configs/ci20_defconfig
index b42cfa7865f9..459b21e6278d 100
> Sorry about the formatting. It seems my e-mail system needs to be checked
> to make sure it does not auto-format the contents again.
I've never seen issues like this with git send-email. Please use
it. Email problems generally happen with the client, not the
backend. What client did you use to
> -Original Message-
> From: Andrew Lunn [mailto:and...@lunn.ch]
> Sent: Friday, September 08, 2017 7:12 AM
> To: Maxim Uvarov
> Cc: Tristram Ha - C24268; Pavel Machek; Nathan Conrad; Vivien Didelot; Florian
> Fainelli; netdev; linux-kernel@vger.kernel.org; Woojung Huh - C21699
> Subject: R
On Fri, Sep 8, 2017 at 11:01 AM, Linus Torvalds
wrote:
>
> It doesn't seem to happen for every exported symbol, though. Odd.
Fascinating.
Picking one file at random that shows this, I did net/ceph/mon_client.c.
The version file that gets generated for that looks like this:
__crc_ceph_monc_want
DW sdio controller has external ciu clock devider controlled via
register in SDIO IP. Due to its unexpected default value
(it should devide by 1 but it devides by 8)
SDIO IP uses wrong ciu clock and works unstable (see STAR 9001204800)
So add temporary fix and change clock frequency from 1
Add USB nodes to 66AK2G dtsi. Also enable the two USB nodes that are on
the K2G EVM.
Roger Quadros (1):
ARM: dts: k2g-evm: Enable USB 0 and 1
Vitaly Andrianov (1):
ARM: dts: k2g: Add USB instances
arch/arm/boot/dts/keystone-k2g-evm.dts | 26
arch/arm/boot/dts/keystone-k2g.d
From: Vitaly Andrianov
Add nodes for both USB instances supported by 66AK2G.
Signed-off-by: Franklin S Cooper Jr
---
arch/arm/boot/dts/keystone-k2g.dtsi | 56 +
1 file changed, 56 insertions(+)
diff --git a/arch/arm/boot/dts/keystone-k2g.dtsi
b/arch/arm/bo
From: Roger Quadros
Enable USB 0 which will be used as a host port and USB 1 which will be
used in peripheral mode.
Signed-off-by: Roger Quadros
Signed-off-by: Murali Karicheri
Signed-off-by: Franklin S Cooper Jr
---
arch/arm/boot/dts/keystone-k2g-evm.dts | 26 ++
1 f
On 09/08/2017 11:40 AM, tristram...@microchip.com wrote:
>> -Original Message-
>> From: Andrew Lunn [mailto:and...@lunn.ch]
>> Sent: Friday, September 08, 2017 7:12 AM
>> To: Maxim Uvarov
>> Cc: Tristram Ha - C24268; Pavel Machek; Nathan Conrad; Vivien Didelot;
>> Florian
>> Fainelli; netd
On Fri, 2017-09-08 at 10:21 -0700, Cong Wang wrote:
> (Cc'ing netdev)
>
> On Fri, Sep 8, 2017 at 5:59 AM, Shankara Pailoor wrote:
> > Hi,
> >
> > I found a warning while fuzzing with Syzkaller on linux 4.13-rc7 on
> > x86_64. The full stack trace is below:
> >
> > WARNING: CPU: 2 PID: 4277 at lib
On 09/07/2017 02:11 PM, tristram...@microchip.com wrote:
> From: Tristram Ha
>
> Add other KSZ switches support so that patch check does not complain.
>
> Signed-off-by: Tristram Ha
> ---
> Documentation/devicetree/bindings/net/dsa/ksz.txt | 117
> --
> 1 file changed, 62
On Tue, 5 Sep 2017 16:57:43 -0500
Tom Zanussi wrote:
> The existing code only allows for one space before and after the 'if'
> specifying the filter for a hist trigger. Add code to make that more
> permissive as far as whitespace goes.
>
> Signed-off-by: Tom Zanussi
> ---
> kernel/trace/trac
On 09/08/2017 06:02 AM, Kunihiko Hayashi wrote:
> From: Jassi Brar
>
> Add RTL8201F phy-id and the related functions to the driver.
>
> The original patch is as follows:
> https://patchwork.kernel.org/patch/2538341/
>
> Signed-off-by: Jongsung Kim
> Signed-off-by: Jassi Brar
> Signed-off-by:
On Fri, Sep 08, 2017 at 09:39:29AM -0700, Stephen Hemminger wrote:
> The Linus policy on Kconfig is that the default should be no
> for all new devices. I.e the user rebuild a new kernel from an
> old config should not by default get a larger kernel.
That might make sense for new config, but RC_CO
On 09/08/2017 06:02 AM, Kunihiko Hayashi wrote:
> DT bindings for the AVE ethernet controller found on Socionext's
> UniPhier platforms.
>
> Signed-off-by: Kunihiko Hayashi
> Signed-off-by: Jassi Brar
> ---
> .../bindings/net/socionext,uniphier-ave4.txt | 44
> ++
> 1
Hello,
On Fri, Sep 08, 2017 at 10:26:45AM -0700, David Miller wrote:
> From: David Woodhouse
> Date: Fri, 08 Sep 2017 18:23:22 +0100
>
> > I don't know that anyone's ever tried saying "show me the chapter and
> > verse of the documentation"
>
> Do you know why I brought this up? Because the pe
On 09/08/2017 11:42 AM, Eugeniy Paltsev wrote:
DW sdio controller has external ciu clock devider controlled via
register in SDIO IP. Due to its unexpected default value
(it should devide by 1 but it devides by 8)
SDIO IP uses wrong ciu clock and works unstable (see STAR 9001204800)
So add tempor
2017-09-08 21:48 GMT+03:00 Florian Fainelli :
> On 09/07/2017 02:11 PM, tristram...@microchip.com wrote:
>> From: Tristram Ha
>>
>> Add other KSZ switches support so that patch check does not complain.
>>
>> Signed-off-by: Tristram Ha
>> ---
>> Documentation/devicetree/bindings/net/dsa/ksz.txt |
> > So i would suggest one driver supporting all the different devices.
>
> There will be 5 drivers to support these devices:
>
> ksz9477.c - KSZ9893/KSZ9897/KSZ9567/KSZ9566/KSZ9477
> ksz8795.c - KSZ8795/KSZ8795/KSZ8765
> ksz8895.c - KSZ8895/KSZ8864
> ksz8863.c - KSZ8863/KSZ8873
> ksz8463.c - KSZ
501 - 600 of 795 matches
Mail list logo
