Hi Kishon,
On Wed, Aug 30, 2017 at 11:01:56AM +0530, Kishon Vijay Abraham I wrote:
>
> I think we should just select the mode that a particular lane has been
> configured here instead of populating all the modes. But I think that doesn't
> make sense since the mode is set by the consumer and the
Hi Kishon,
On Wed, Aug 30, 2017 at 10:49:13AM +0530, Kishon Vijay Abraham I wrote:
> On Monday 28 August 2017 08:27 PM, Antoine Tenart wrote:
> > +
> > +static int mvebu_comphy_set_mode_sgmii(struct phy *phy, enum phy_mode mode)
>
> the mode need not be passed as argument here since this function
On Wed, Aug 30, 2017 at 11:37:21AM +0800, kernel test robot wrote:
> [0.004000]
> -
> [0.004000] BUG: -1 unexpected failures (out of 262) - debugging
> disabled! |
> [0.004000]
> ---
On Wed, Aug 30, 2017 at 10:53:39AM +0900, Byungchul Park wrote:
> On Tue, Aug 29, 2017 at 08:57:27PM +0200, Peter Zijlstra wrote:
> > On Sat, Aug 26, 2017 at 12:49:26AM +0900, Byungchul Park wrote:
> > > > However, how would it distinguish things like flushing another work
> > >
> > > I think it m
On 08/30/2017 07:47 AM, Arvind Yadav wrote:
vmw_fence_ops are not supposed to change at runtime. Functions
"dma_fence_init" working with const vmw_fence_ops provided
by . So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/gpu/drm/vmwgfx/vmwgfx_fence.c | 2 +-
1 f
gt;> url:
>> https://github.com/0day-ci/linux/commits/Greg-Kroah-Hartman/irda-move-it-to-drivers-staging-so-we-can-delete-it/20170829-090816
>>
>> in testcase: trinity
>> with following parameters:
>>
>> runtime: 300s
>>
>> test-description:
Jens,
any thoughts about this?
On Mon, Aug 14, 2017 at 11:27 AM, Oleksandr Natalenko
wrote:
> Setting I/O scheduler via kernel command line is not flexible enough
> anymore. Different schedulers might be desirable for different types
> of devices (SSDs and HDDs, for instance). Moreover, setting
Am 30.08.2017 um 01:54 schrieb Jérôme Glisse:
Call to mmu_notifier_invalidate_page() are replaced by call to
mmu_notifier_invalidate_range() and thus call are bracketed by
call to mmu_notifier_invalidate_range_start()/end()
Remove now useless invalidate_page callback.
Signed-off-by: Jérôme Glis
changes in v4:
Removed unnessesary "()" around expression in rule 4.
changes in v3:
Removed unnessesary rule 4 conditions pointed by Julia.
changes in v2:
Following the suggestion from Julia the first rule is split into
2. The output does not differ that much between these two versions,
but rule
atomic_as_refcounter.cocci script allows detecting
cases when refcount_t type and API should be used
instead of atomic_t.
Signed-off-by: Elena Reshetova
---
scripts/coccinelle/api/atomic_as_refcounter.cocci | 131 ++
1 file changed, 131 insertions(+)
create mode 100644 scrip
Hello.
Addressing your questions below.
Can't reproduce even with putting dmcypt on raid10 after applying my
patch.
Just a side note, that dm-crypt is not necessary here — I am able to
trigger hang with RAID10 and LVM only.
BTW, could you share us which blk-mq scheduler you are using on s
On Tue, Aug 29, 2017 at 07:54:39PM -0400, Jérôme Glisse wrote:
> Call to mmu_notifier_invalidate_page() are replaced by call to
> mmu_notifier_invalidate_range() and thus call are bracketed by
> call to mmu_notifier_invalidate_range_start()/end()
>
> Remove now useless invalidate_page callback.
>
>
On Wed, Aug 30, 2017 at 07:19:30AM +1000, Benjamin Herrenschmidt wrote:
> On Tue, 2017-08-29 at 13:27 +0200, Peter Zijlstra wrote:
> > mpe helped me out and explained that is the PWC hint to TBLIE.
> >
> > So, you set need_flush_all when you unhook pud/pmd/pte which you then
> > use to set PWC. So
Hi,
On (08/30/17 14:43), Byungchul Park wrote:
[..]
> > notably slower than earlier 4.13 linux-next. (e.g. scrolling in vim
> > is irritatingly slow)
>
> To Ingo,
>
> I cannot decide if we have to roll back CONFIG_LOCKDEP_CROSSRELEASE
> dependency on CONFIG_PROVE_LOCKING in Kconfig. With them en
Greg-Kroah-Hartman/irda-move-it-to-drivers-staging-so-we-can-delete-it/20170829-090816
>
> in testcase: trinity
> with following parameters:
>
> runtime: 300s
>
> test-description: Trinity is a linux system call fuzz tester.
> test-url: http://codemonkey.org.uk/proj
On Tue, Aug 29, 2017 at 05:46:57PM -0700, Sherry Yang wrote:
> Use helper functions buffer_next and buffer_prev instead
> of list_entry to get the next and previous buffers.
>
> Signed-off-by: Sherry Yang
> ---
> drivers/android/binder_alloc.c | 24 +++-
> 1 file changed, 15
Hi all,
There will be no linux-next release today, sorry.
--
Cheers,
Stephen Rothwell
Add handling of IPV6_PKTOPTIONS to dccp_v6_do_rcv() in net/dccp/ipv6.c, similar
to the handling in net/ipv6/tcp_ipv6.c
Signed-off-by: Andrii Vladyka diff --git a/net/dccp/ipv6.c b/net/dccp/ipv6.c
index 1b58eac..fdff10b 100644
--- a/net/dccp/ipv6.c
+++ b/net/dccp/ipv6.c
@@ -16,6 +16,7 @@
#include
FYI, we noticed the following commit:
commit: 66d98e78e44ccb969cb3196995759d200e64b49b ("irda: move net/irda/ to
drivers/staging/irda/net/")
url:
https://github.com/0day-ci/linux/commits/Greg-Kroah-Hartman/irda-move-it-to-drivers-staging-so-we-can-delete-it/20170829-090816
in testcas
On Mon, Aug 28, 2017 at 10:41 AM, Peter Zijlstra wrote:
> On Fri, Aug 25, 2017 at 12:11:31AM +0200, Uladzislau Rezki (Sony) wrote:
>> From: Uladzislau Rezki
>>
>> As a first step this patch makes cfs_tasks list as MRU one.
>> It means, that when a next task is picked to run on physical
>> CPU it
On Tue, Aug 29, 2017 at 10:52:34PM +0200, Alexandre Belloni wrote:
> Arnd, Olof,
>
> I understand this is very late in the cycle but I completely forgot to
> send that pull request alongside the 4.13 fixes.
> Most of the patches have been included in linux-next for a while so I
> don't this it is
On Tue, Aug 29, 2017 at 12:28:21AM +0900, Masahiro Yamada wrote:
> Hi Arnd, Olof,
>
>
> Sorry for my last-minute pull request.
> Please pull a little more for the upcoming merge window.
> Here are some trivial + new SoC support for UniPhier DT (64bit).
> Please pull!
>
>
> The following changes
On Tue, Aug 29, 2017 at 12:23:32AM +0900, Masahiro Yamada wrote:
> Hi Arnd, Olof,
>
> Sorry for my last-minute pull request.
> Please pull a little more for the upcoming merge window.
> Here are some trivial UniPhier DT (32bit) updates. Please pull!
>
>
>
> The following changes since commit 6
On Tue, Aug 08, 2017 at 11:29:13AM +0200, Robert Richter wrote:
> On 08.08.17 01:07:04, Jayachandran C wrote:
> > Add Robert Richter as the primary maintainer for this platform.
> >
> > Signed-off-by: Jayachandran C
> > ---
> > MAINTAINERS | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff
On Wed, Aug 30, 2017 at 10:33:50AM +0530, Anshuman Khandual wrote:
> diff --git a/mm/filemap.c b/mm/filemap.c
> index a497024..08f3042 100644
> --- a/mm/filemap.c
> +++ b/mm/filemap.c
> @@ -1181,6 +1181,18 @@ int __lock_page_killable(struct page *__page)
> int __lock_page_or_retry(struct page *pag
On Wed, Aug 30, 2017 at 12:51:02AM +0530, harsha wrote:
> Fixes checkpatch.pl warning: Use WARN_ON() rather than BUG_ON() and BUG()
>
> Signed-off-by: harsha
> ---
> drivers/staging/android/ion/ion.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/androi
Currently the driver boots only via device tree hence add a
dependency on CONFIG_OF. This leaves with a bunch of unused code
so clean that up. This patch also makes use of probe_new function
in place of the probe function so as to avoid passing i2c_device_id.
Signed-off-by: Keerthy
---
Changes i
vmw_fence_ops are not supposed to change at runtime. Functions
"dma_fence_init" working with const vmw_fence_ops provided
by . So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/gpu/drm/vmwgfx/vmwgfx_fence.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
On Tue, Aug 29, 2017 at 10:10:37PM +0200, Thomas Gleixner wrote:
> On Tue, 29 Aug 2017, Peter Zijlstra wrote:
> > So I have a patch _somewhere_ that preserves the event<->cpu relation
> > across hotplug and disable/enable would be sufficient. If you want I can
> > try and dig that out and make it w
On Thursday 08 June 2017 07:41 PM, Javier Martinez Canillas wrote:
> On Thu, Jun 8, 2017 at 3:32 PM, Enric Balletbo Serra
> wrote:
>> Hi Keerthy:
>>
>> 2017-06-08 12:46 GMT+02:00 Keerthy :
>>> Currently the driver boots only via device tree hence add a
>>> dependency on CONFIG_OF. This leaves wi
On Wed, Aug 30, 2017 at 02:20:37PM +0900, Sergey Senozhatsky wrote:
> Byungchul, a quick question.
Hello Sergey,
> have you measured the performance impact? somehow my linux-next is
Yeah, it might have performance impact inevitably.
> notably slower than earlier 4.13 linux-next. (e.g. scrolling
From: Samuel Mendoza-Jonas
Date: Wed, 30 Aug 2017 14:37:21 +1000
> On Mon, 2017-08-28 at 16:50 -0700, David Miller wrote:
>> From: Samuel Mendoza-Jonas
>> Date: Mon, 28 Aug 2017 16:18:40 +1000
>>
>> > This series (mainly patch 2) adds VLAN filtering to the NCSI
>> > implementation.
>> > A fair
On (08/29/17 19:58), Joe Perches wrote:
> > >
> > > Why?
> > >
> > > What's wrong with a simple printk?
> > > It'd still do a log_store.
> >
> > sure, it will. but in separate logbuf entries, and between two
> > consequent printk calls on the same CPU a lot of stuff can happen:
>
> I think you
Hi,
On Tuesday 29 August 2017 06:42 PM, Antoine Tenart wrote:
> Hi Kishon,
>
> On Tue, Aug 29, 2017 at 05:55:06PM +0530, Kishon Vijay Abraham I wrote:
>> On Tuesday 29 August 2017 04:53 PM, Antoine Tenart wrote:
>>> On Tue, Aug 29, 2017 at 04:34:17PM +0530, Kishon Vijay Abraham I wrote:
On M
On 08/23/2017 07:04 PM, Mark Rutland wrote:
> On Wed, Aug 23, 2017 at 10:58:42AM -0600, Tycho Andersen wrote:
>> Hi Mark,
>>
>> On Mon, Aug 14, 2017 at 05:50:47PM +0100, Mark Rutland wrote:
>>> That said, is there any reason not to use flush_tlb_kernel_range()
>>> directly?
>>
>> So it turns out
Fixed coding style issue
Signed-off-by: Harsha Sharma
---
drivers/staging/rtl8712/xmit_linux.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/rtl8712/xmit_linux.c
b/drivers/staging/rtl8712/xmit_linux.c
index d13fd15..03c6b0c 100644
--- a/drivers/stagin
Dear Talented,
I am Talent Scout For BLUE SKY FILM STUDIO, Present Blue sky Studio a Film
Corporation Located in the United State, is Soliciting for the Right to use
Your Photo/Face and Personality as One of the Semi -Major Role/ Character in
our Upcoming ANIMATED Stereoscope 3D Movie-The Story
On 08/27/2017 05:48 AM, Kirill A. Shutemov wrote:
>> +/* Transparent huge pages are not supported. */
>> +if (unlikely(pmd_trans_huge(*pmd)))
>> +goto out_walk;
> That's looks like a blocker to me.
>
> Is there any problem with making it supported (besides plain coding)?
IIUC
From: Huang Ying
The optimized clear_huge_page() isn't easy to read and understand.
This is suggested by Michael Hocko to improve it.
Suggested-by: Michal Hocko
Signed-off-by: "Huang, Ying"
---
mm/memory.c | 11 +++
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/mm/memo
Hi Antoine,
On Monday 28 August 2017 08:27 PM, Antoine Tenart wrote:
> On the CP110 unit, which can be found on various Marvell platforms such
> as the 7k and 8k (currently), a comphy (common PHYs) hardware block can
> be found. This block provides a number of PHYs which can be used in
> various m
On (08/23/17 09:03), Byungchul Park wrote:
[..]
> > Byungchul, did you add the crosslock checks to lockdep? Can you have a look
> > at
> > the above report? That report namely doesn't make sense to me.
>
> The report is talking about the following lockup:
>
> A work in a worker
On Wed, Aug 30, 2017 at 10:15:37AM +0800, Ming Lei wrote:
> Hi,
>
> On Tue, Aug 29, 2017 at 05:52:42PM +0200, Oleksandr Natalenko wrote:
> > Hello.
> >
> > Re-tested with v4.13-rc7 + proposed patch and got the same result.
>
> Maybe there is another issue, I didn't use dmcrypt on raid10, will
>
Hi,
>> This is great to see. Is there a Linux implementation of the server side (in
>> Samba?) so that the client can be tested without needing a Windows server?
>
> I'm not aware of a Linux implementation on server side.
Here's a very early work in progress branch:
https://git.samba.org/?p=met
On 08/29/2017 07:15 PM, Peter Zijlstra wrote:
> On Tue, Aug 29, 2017 at 03:18:25PM +0200, Laurent Dufour wrote:
>> On 29/08/2017 14:04, Peter Zijlstra wrote:
>>> On Tue, Aug 29, 2017 at 09:59:30AM +0200, Laurent Dufour wrote:
On 27/08/2017 02:18, Kirill A. Shutemov wrote:
>> +
>> +
On Tue, 2017-08-29 at 11:41 -0700, Kees Cook wrote:
> Can you also test with 14afee4b6092 ("net: convert sock.sk_wmem_alloc
> from atomic_t to refcount_t") reverted (instead of ARCH_HAS_REFCOUNT
> disabled)?
Nogo.
...
[[0;32m OK [0m] Mounted /abuild.
[[0;32m OK [0m] Mounted /homer.
[[0;3
> On Aug 27, 2017, at 8:05 PM, Mathieu Desnoyers
> wrote:
>
> - On Aug 27, 2017, at 3:53 PM, Andy Lutomirski l...@amacapital.net wrote:
>
>>> On Aug 27, 2017, at 1:50 PM, Mathieu Desnoyers
>>>
>>> wrote:
>>>
>>> Add a new MEMBARRIER_CMD_REGISTER_SYNC_CORE command to the membarrier
>>> syste
On Mon, 2017-08-28 at 16:50 -0700, David Miller wrote:
> From: Samuel Mendoza-Jonas
> Date: Mon, 28 Aug 2017 16:18:40 +1000
>
> > This series (mainly patch 2) adds VLAN filtering to the NCSI implementation.
> > A fair amount of code already exists in the NCSI stack for VLAN filtering
> > but
> >
From: "Ziqian SUN (Zamir)"
The mmiotrace tracer cannot be enabled with ftrace=mmiotrace in
kernel commandline. With this patch, a trace_noboot_tracer_list
is implemented and will be checked during system boot. If the
tracer declares itself as not for boot up, system will print out
a message and c
On 08/30/2017 11:25 AM, Ziqian SUN (Zamir) wrote:
From: "Ziqian SUN (Zamir)"
The mmiotrace tracer cannot be enabled with ftrace=mmiotrace in
kernel commandline. With this patch, a trace_noboot_tracer_list
is implemented and will be checked during system boot. If the
tracer declares itself as
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 decide when to resume/suspend.
Signed-off-by: Divagar Mohandass
---
drivers/misc/eeprom/at24
Obtain the size of the EEPROM chip from DT if the "size" property is
specified for the device.
Signed-off-by: Divagar Mohandass
---
drivers/misc/eeprom/at24.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/misc/eeprom/at24.c b/drivers/misc/eeprom/at24.c
index 764ff5df..2199c42 1
This series adds support for eeprom "size" property which will be read by the
driver for eeprom size. The existing ACPI has a different default size which
can be overridden with a DSD property value provided by the platform FW.
This series also adds support for runtime PM. The eeprom driver curren
This adds eeprom "size" as optional property for i2c eeproms.
The "size" property allows explicitly specifying the size of the
EEPROM chip in bytes.
Signed-off-by: Divagar Mohandass
---
Documentation/devicetree/bindings/eeprom/eeprom.txt | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Docu
Hi Sakari,
Thanks for your review comments.
My comments below.
---
^Divagar
>-Original Message-
>From: Sakari Ailus [mailto:sakari.ai...@iki.fi]
>Sent: Tuesday, August 22, 2017 2:26 PM
>To: Mohandass, Divagar
>Cc: robh...@kernel.org; mark.rutl...@arm.com; w...@the-dreams.de;
>devicet...
Hi Mathieu,
On Sun, Aug 27, 2017 at 01:50:35PM -0700, Mathieu Desnoyers wrote:
> Add a new MEMBARRIER_CMD_REGISTER_SYNC_CORE command to the membarrier
> system call. It allows processes to register their intent to have their
> threads issue core serializing barriers in addition to memory barriers
Hi Sakari,
Thanks for your review comments. Will address it in next patch version.
---
^Divagar
>-Original Message-
>From: Sakari Ailus [mailto:sakari.ai...@iki.fi]
>Sent: Tuesday, August 22, 2017 2:43 PM
>To: Mohandass, Divagar
>Cc: robh...@kernel.org; mark.rutl...@arm.com; w...@the-dr
Hi Sakari,
Thanks for your review comments. Will address it in next patch version.
---
^Divagar
>-Original Message-
>From: Sakari Ailus [mailto:sakari.ai...@iki.fi]
>Sent: Tuesday, August 22, 2017 2:41 PM
>To: Mohandass, Divagar
>Cc: robh...@kernel.org; mark.rutl...@arm.com; w...@the-dr
On 08/29/2017 05:34 PM, Peter Zijlstra wrote:
> On Tue, Aug 29, 2017 at 09:59:30AM +0200, Laurent Dufour wrote:
>> On 27/08/2017 02:18, Kirill A. Shutemov wrote:
+
+ if (unlikely(!vma->anon_vma))
+ goto unlock;
>>> It deserves a comment.
>> You're right I'll add it in the n
> -Original Message-
> From: Martin K. Petersen [mailto:martin.peter...@oracle.com]
> Sent: Tuesday, August 29, 2017 6:31 PM
> To: Long Li
> Cc: KY Srinivasan ; Haiyang Zhang
> ; James E . J . Bottomley
> ; de...@linuxdriverproject.org; linux-
> s...@vger.kernel.org; linux-kernel@vger.kern
On Tue, 2017-08-29 at 13:08 +0300, Sergei Shtylyov wrote:
> Hello!
>
> On 8/29/2017 12:20 PM, Chunfeng Yun wrote:
>
> > The mt8173-mtu3.txt actually holds the bindings for all mediatek
> > SoCs with usb3 DRD IP, so add a generic compatible and change the
> > name to mediatek,mtu3.txt.
> >
> > Si
46d41f4a30c2c61 # 08:02 G 11
00 0 0day base guard for 'devel-catchup-201708300632'
git bisect good 1b2f76d77a277bb70d38ad0991ed7f16bbc115a9 # 08:17 G 11
00 0 Merge tag 'perf-core-for-mingo-4.14-20170829' of
git://git.kernel.
From: Eric Biggers
Commit 7c051267931a ("mm, fork: make dup_mmap wait for mmap_sem for
write killable") made it possible to kill a forking task while it is
waiting to acquire its ->mmap_sem for write, in dup_mmap().
However, it was overlooked that this introduced an new error path before
the new
On Sat, Aug 26, 2017 at 11:41:06AM +0530, Arvind Yadav wrote:
> mei_cl_device_id are not supposed to change at runtime. All functions
> working with mei_cl_device_id provided by work
> with const mei_cl_device_id. So mark the non-const structs as const.
>
> Signed-off-by: Arvind Yadav
Reviewed-
On Wed, Aug 23, 2017 at 10:04:08PM +0530, Arvind Yadav wrote:
> amba_id are not supposed to change at runtime. All functions
> working with const amba_id. So mark the non-const structs as const.
>
> Signed-off-by: Arvind Yadav
Reviewed-by: Guenter Roeck
> ---
> drivers/watchdog/sp805_wdt.c |
On Mon, Aug 21, 2017 at 10:18:38PM +0530, Arvind Yadav wrote:
> i2c_device_id are not supposed to change at runtime. All functions
> working with i2c_device_id provided by work with
> const i2c_device_id. So mark the non-const structs as const.
>
> Signed-off-by: Arvind Yadav
Reviewed-by: Guent
From: "Ziqian SUN (Zamir)"
The mmiotrace tracer cannot be enabled with ftrace=mmiotrace in
kernel commandline. With this patch, a trace_noboot_tracer_list
is implemented and will be checked during system boot. If the
tracer declares itself as not for boot up, system will print out
a message and c
On Wed, Aug 16, 2017 at 10:27:03AM +0530, Arvind Yadav wrote:
> pnp_device_id are not supposed to change at runtime. All functions
> working with pnp_device_id provided by work with
> const pnp_device_id. So mark the non-const structs as const.
>
> Signed-off-by: Arvind Yadav
Reviewed-by: Guent
Nadav Amit wrote:
> Jerome Glisse wrote:
>
>> On Tue, Aug 29, 2017 at 07:46:07PM -0700, Nadav Amit wrote:
>>> Jérôme Glisse wrote:
>>>
Replacing all mmu_notifier_invalidate_page() by
mmu_notifier_invalidat_range()
and making sure it is bracketed by call to
mmu_notifier_i
Jerome Glisse wrote:
> On Tue, Aug 29, 2017 at 07:46:07PM -0700, Nadav Amit wrote:
>> Jérôme Glisse wrote:
>>
>>> Replacing all mmu_notifier_invalidate_page() by
>>> mmu_notifier_invalidat_range()
>>> and making sure it is bracketed by call to
>>> mmu_notifier_invalidate_range_start/
>>> end.
Hi Robert,
Got it and thanks your reply.
Shaokun
On 2017/8/29 20:47, Robert Richter wrote:
> Shaokun,
>
> On 29.08.17 17:26:00, Zhangshaokun wrote:
>> On 2017/8/24 20:03, Ganapatrao Kulkarni wrote:
>>> This is not a full event list, but a short list of useful events.
>>>
>>> Signed-off-by: Gana
Since the i2c driver of Spreadtrum can not be build as one module, thus
it should depend on CONFIG_I2C is build in.
Signed-off-by: Baolin Wang
---
drivers/i2c/busses/Kconfig |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kco
v2: Undo the renaming of the dft_eps_id variable in hci_pdn_table_ind
to resolve a compiler error.
Signed-off-by: Nick Fox
---
drivers/staging/gdm724x/hci_packet.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/gdm724x/hci_packet.h
b/drivers/staging/gdm724x/
From: Philipp Rossak
The Nanopi M1 has an onboard IR receiver.
This enables the onboard IR receiver subnode.
Signed-off-by: Philipp Rossak
---
arch/arm/boot/dts/sun8i-h3-nanopi-m1.dts | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/sun8i-h3-nanopi-m1.dts
b/arch/arm
From: Philipp Rossak
This Patchseries enables the IR controller and the dwmac-sun8i
on the Friendlyarm Nanopi M1 and Friendlyarm Nanopi M1 Plus boards.
On the Nanopi M1 Plus additionally the BT/Wifi module is activated.
Philipp Rossak (7):
ARM: dts: sun8i: h3: nanopi-m1: Enable IR controller
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
sequencing clocks and GPIO, as well as the chip's interrupt line.
Signed-off-by: Philipp Ro
From: Philipp Rossak
The dwmac-sun8i hardware is present on the Nanopi M1 Plus.
It uses an external PHY.
Signed-off-by: Philipp Rossak
---
arch/arm/boot/dts/sun8i-h3-nanopi-m1-plus.dts | 32 +++
1 file changed, 32 insertions(+)
diff --git a/arch/arm/boot/dts/sun8i-h3-n
From: Philipp Rossak
The Nanopi M1 Plus has an onboard IR receiver.
This enables the onboard IR receiver subnode.
Signed-off-by: Philipp Rossak
---
arch/arm/boot/dts/sun8i-h3-nanopi-m1-plus.dts | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/sun8i-h3-nanopi-m1-plus.
> We should never say "transient is for rising
> direction" or "ff_mt is for falling direction". any combination is fine.
Ok I agree that there is no hard and fast rule that "transient is for rising
direction" or "ff_mt is for falling direction".
But in our case, datasheet for these chips define t
From: Philipp Rossak
This node adds the definition for the UART3 RTS and CTS Pins
That makes it able to use UART3 with RTS and CTS.
Signed-off-by: Philipp Rossak
---
arch/arm/boot/dts/sunxi-h3-h5.dtsi | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/sunxi-h3-h5.dtsi
From: Philipp Rossak
The dwmac-sun8i hardware is present on the Nanopi M1.
It uses the internal PHY.
Signed-off-by: Philipp Rossak
---
arch/arm/boot/dts/sun8i-h3-nanopi-m1.dts | 11 +++
1 file changed, 11 insertions(+)
diff --git a/arch/arm/boot/dts/sun8i-h3-nanopi-m1.dts
b/arch/arm/
From: Philipp Rossak
The BT side of the AP6212 WiFi/BT combo module is connected to
uart3.
Enable BT on this board by enabling uart3 with using additionally
the cts and rts pins.
Signed-off-by: Philipp Rossak
---
arch/arm/boot/dts/sun8i-h3-nanopi-m1-plus.dts | 7 +++
1 file changed, 7 ins
On Tue, Aug 29, 2017 at 07:46:07PM -0700, Nadav Amit wrote:
> Jérôme Glisse wrote:
>
> > Replacing all mmu_notifier_invalidate_page() by
> > mmu_notifier_invalidat_range()
> > and making sure it is bracketed by call to
> > mmu_notifier_invalidate_range_start/
> > end.
> >
> > Note that because
It is prefered to use '"%s...", __func__ instead of function names for
logging. This commit replaces hardcoded function name strings to the
more preferred '"%s...", __func__' style. These warnings were reported
by checkpatch.pl.
Signed-off-by: Jonathan Whitaker
Changes in v2:
- Wrapped the cha
On Wed, 2017-08-30 at 11:47 +0900, Sergey Senozhatsky wrote:
> On (08/29/17 19:31), Joe Perches wrote:
> [..]
> > > the idea is not to do printk() on that seq buffer at all, but to
> > > log_store(), atomically, seq buffer messages
> > >
> > > spin_lock(&logbuf_lock)
> > > while (offset < seq_
Hi Jan,
Some trivial things i noticed, please consider if you are glad.
Thanks,
Shaokun
On 2017/8/29 21:12, Jan Glauber wrote:
> Add support for the PMU counters on Cavium SOC memory controllers.
>
> This patch also adds generic functions to allow supporting more
> devices with PMU counters.
>
Jérôme Glisse wrote:
> Replacing all mmu_notifier_invalidate_page() by mmu_notifier_invalidat_range()
> and making sure it is bracketed by call to
> mmu_notifier_invalidate_range_start/
> end.
>
> Note that because we can not presume the pmd value or pte value we have to
> assume the worse and
On (08/29/17 19:31), Joe Perches wrote:
[..]
> > the idea is not to do printk() on that seq buffer at all, but to
> > log_store(), atomically, seq buffer messages
> >
> > spin_lock(&logbuf_lock)
> > while (offset < seq_buffer->len) {
> > ...
> > log_store(seq->buffe
Hi Jacek,
On Tue, Aug 29, 2017 at 10:44:03PM +0200, Jacek Anaszewski wrote:
> Applied to the for-4.15 branch of linux-leds.git.
Great, thanks!
Willy
> -Original Message-
> From: Tom Talpey
> Sent: Monday, August 14, 2017 12:55 PM
> To: Long Li ; Steve French ;
> linux-c...@vger.kernel.org; samba-techni...@lists.samba.org; linux-
> ker...@vger.kernel.org; linux-r...@vger.kernel.org
> Subject: RE: [[PATCH v1] 05/37] [CIFS] SMBD: Impleme
I have a confidential deal for you, please contact me for more details via
this email immediately.
God Bless,
Ms.Lev
On Wed, 2017-08-30 at 11:25 +0900, Sergey Senozhatsky wrote:
> On (08/29/17 18:52), Joe Perches wrote:
> [..]
> > > We could simply add a seq_buf_printk() that is implemented in the printk
> > > proper, to parse the seq_buf buffer properly, and add the timestamps and
> > > such.
> >
> > No need.
> -Original Message-
> From: Tom Talpey
> Sent: Monday, August 14, 2017 1:44 PM
> To: Long Li ; Steve French ;
> linux-c...@vger.kernel.org; samba-techni...@lists.samba.org; linux-
> ker...@vger.kernel.org; linux-r...@vger.kernel.org
> Subject: RE: [[PATCH v1] 18/37] [CIFS] SMBD: Implemen
On (08/29/17 18:52), Joe Perches wrote:
[..]
> > We could simply add a seq_buf_printk() that is implemented in the printk
> > proper, to parse the seq_buf buffer properly, and add the timestamps and
> > such.
>
> No need. printk would already add timestamps.
the idea is not to do printk() on tha
> -Original Message-
> From: Christoph Hellwig [mailto:h...@infradead.org]
> Sent: Sunday, August 13, 2017 3:24 AM
> To: Long Li
> Cc: Steve French ; linux-c...@vger.kernel.org; samba-
> techni...@lists.samba.org; linux-kernel@vger.kernel.org; Long Li
>
> Subject: Re: [[PATCH v1] 15/37] [
Hi,
On Tue, Aug 29, 2017 at 05:52:42PM +0200, Oleksandr Natalenko wrote:
> Hello.
>
> Re-tested with v4.13-rc7 + proposed patch and got the same result.
Maybe there is another issue, I didn't use dmcrypt on raid10, will
test in your way to see if I can reproduce it.
BTW, could you share us whic
> -Original Message-
> From: Pavel Shilovsky [mailto:piastr...@gmail.com]
> Sent: Tuesday, August 29, 2017 5:49 PM
> To: Long Li
> Cc: Steve French ; linux-cifs c...@vger.kernel.org>; samba-technical ;
> Kernel Mailing List ; linux-
> r...@vger.kernel.org; Christoph Hellwig ; Tom Talpey
> -Original Message-
> From: Pavel Shilovsky [mailto:piastr...@gmail.com]
> Sent: Tuesday, August 29, 2017 5:50 PM
> To: Long Li
> Cc: Steve French ; linux-cifs c...@vger.kernel.org>; samba-technical ;
> Kernel Mailing List ; linux-
> r...@vger.kernel.org; Christoph Hellwig ; Tom Talpey
> -Original Message-
> From: Nikola Pajkovsky [mailto:npajkov...@suse.cz]
> Sent: Tuesday, August 29, 2017 4:59 AM
> To: dl-esc-Aacraid Linux Driver
> Cc: Nikola Pajkovsky ; James E.J. Bottomley
> ; Martin K. Petersen
> ; linux-s...@vger.kernel.org; linux-
> ker...@vger.kernel.org
> Subj
> -Original Message-
> From: Nikola Pajkovsky [mailto:npajkov...@suse.cz]
> Sent: Tuesday, August 29, 2017 4:59 AM
> To: dl-esc-Aacraid Linux Driver
> Cc: Nikola Pajkovsky ; James E.J. Bottomley
> ; Martin K. Petersen
> ; linux-s...@vger.kernel.org; linux-
> ker...@vger.kernel.org
> Subj
> -Original Message-
> From: Nikola Pajkovsky [mailto:npajkov...@suse.cz]
> Sent: Tuesday, August 29, 2017 4:59 AM
> To: dl-esc-Aacraid Linux Driver
> Cc: Nikola Pajkovsky ; James E.J. Bottomley
> ; Martin K. Petersen
> ; linux-s...@vger.kernel.org; linux-
> ker...@vger.kernel.org
> Subj
1 - 100 of 903 matches
Mail list logo
