Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
to receive updates for the input subsystem. You will get:
- a quirk to i8042 to ignore timeout bit on Lifebook AH544
- a fixup to Synaptics RMI function 54 that was breaking some Dells
-
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
to receive updates for the input subsystem. You will get:
- a quirk to i8042 to ignore timeout bit on Lifebook AH544
- a fixup to Synaptics RMI function 54 that was breaking some Dells
-
Hi Georgi,
[auto build test ERROR on next-20170619]
[cannot apply to clk/clk-next robh/for-next linus/master v4.12-rc6 v4.12-rc5
v4.12-rc4 v4.12-rc6]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi Georgi,
[auto build test ERROR on next-20170619]
[cannot apply to clk/clk-next robh/for-next linus/master v4.12-rc6 v4.12-rc5
v4.12-rc4 v4.12-rc6]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi Linus,
Here are the target-pending fixes for v4.12-rc7 that have been queued up
for the last 2 weeks. Please go ahead and pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending.git master
This includes:
- Fix a TMR related kref underflow detected by the recent
Hi Linus,
Here are the target-pending fixes for v4.12-rc7 that have been queued up
for the last 2 weeks. Please go ahead and pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending.git master
This includes:
- Fix a TMR related kref underflow detected by the recent
On Sun, Jun 25, 2017 at 12:27:17AM -0400, Tejun Heo wrote:
> "cgroup.subtree_control" determines which resource types a cgroup
> wants to control. Unlike actual resource knobs, this is an attribute
> which belongs to the cgroup itself instead of its parent and thus
> should be writeable by the
On Sun, Jun 25, 2017 at 12:27:17AM -0400, Tejun Heo wrote:
> "cgroup.subtree_control" determines which resource types a cgroup
> wants to control. Unlike actual resource knobs, this is an attribute
> which belongs to the cgroup itself instead of its parent and thus
> should be writeable by the
Currently, cgroup only supports delegation to !root users and cgroup
namespaces don't get any special treatments. This limits the
usefulness of cgroup namespaces as they by themselves can't be safe
delegation boundaries. A process inside a cgroup can change the
resource control knobs of the
Currently, cgroup only supports delegation to !root users and cgroup
namespaces don't get any special treatments. This limits the
usefulness of cgroup namespaces as they by themselves can't be safe
delegation boundaries. A process inside a cgroup can change the
resource control knobs of the
Restructure cgroup_procs_write_permission() to make extending
permission logic easier.
This patch doesn't cause any functional changes.
Signed-off-by: Tejun Heo
---
kernel/cgroup/cgroup.c | 57 -
1 file changed, 33
Restructure cgroup_procs_write_permission() to make extending
permission logic easier.
This patch doesn't cause any functional changes.
Signed-off-by: Tejun Heo
---
kernel/cgroup/cgroup.c | 57 -
1 file changed, 33 insertions(+), 24
"cgroup.subtree_control" determines which resource types a cgroup
wants to control. Unlike actual resource knobs, this is an attribute
which belongs to the cgroup itself instead of its parent and thus
should be writeable by the delegatee in a delegated cgroup.
Update delegation documentation
"cgroup.subtree_control" determines which resource types a cgroup
wants to control. Unlike actual resource knobs, this is an attribute
which belongs to the cgroup itself instead of its parent and thus
should be writeable by the delegatee in a delegated cgroup.
Update delegation documentation
2017-06-22 8:28 GMT+09:00 Matthias Kaehlcke :
> For gcc stack alignment is configured with -mpreferred-stack-boundary=N,
> clang has the option -mstack-alignment=N for that purpose. Use the same
> alignment as with gcc.
>
> If the alignment is not specified clang assumes an
2017-06-22 8:28 GMT+09:00 Matthias Kaehlcke :
> For gcc stack alignment is configured with -mpreferred-stack-boundary=N,
> clang has the option -mstack-alignment=N for that purpose. Use the same
> alignment as with gcc.
>
> If the alignment is not specified clang assumes an alignment of
> 16
2017-06-22 17:58 GMT+09:00 Ingo Molnar :
>
> * Matthias Kaehlcke wrote:
>
>> This series fixes an issue with the stack of the x86 boot code not
>> being aligned as intended. Further it adapts the Makefile to account
>> for the fact that clang uses a different
2017-06-22 17:58 GMT+09:00 Ingo Molnar :
>
> * Matthias Kaehlcke wrote:
>
>> This series fixes an issue with the stack of the x86 boot code not
>> being aligned as intended. Further it adapts the Makefile to account
>> for the fact that clang uses a different option to configure the
>> stack
2017-06-19 16:28 GMT+09:00 Masahiro Yamada :
> Documentation/kbuild/makefiles.txt says the change for align options
> occurred at GCC 3.0, and Documentation/process/changes.rst says the
> minimal supported GCC version is 3.2, so it should be safe to hard-code
>
2017-06-19 16:28 GMT+09:00 Masahiro Yamada :
> Documentation/kbuild/makefiles.txt says the change for align options
> occurred at GCC 3.0, and Documentation/process/changes.rst says the
> minimal supported GCC version is 3.2, so it should be safe to hard-code
> -falign* options.
>
> Fix the only
Build targets using if_changed(_rule) must depend on FORCE so that
they are evaluated every time.
In order to include .*.cmd files correctly, build targets added to
"targets" must not be prefixed with $(obj)/ because it is done by
scripts/Makefile.lib .
Signed-off-by: Masahiro Yamada
Build targets using if_changed(_rule) must depend on FORCE so that
they are evaluated every time.
In order to include .*.cmd files correctly, build targets added to
"targets" must not be prefixed with $(obj)/ because it is done by
scripts/Makefile.lib .
Signed-off-by: Masahiro Yamada
---
I
On Sat, 2017-06-24 at 14:32 -0700, Palmer Dabbelt wrote:
> On Sat, 24 Jun 2017 08:42:05 PDT (-0700), b...@kernel.crashing.org wrote:
> > On Fri, 2017-06-23 at 19:01 -0700, Palmer Dabbelt wrote:
> > > > > +#define mmiowb() __asm__ __volatile__ ("fence io,io" : : :
> > > > > "memory");
> >
>
On Sat, 2017-06-24 at 14:32 -0700, Palmer Dabbelt wrote:
> On Sat, 24 Jun 2017 08:42:05 PDT (-0700), b...@kernel.crashing.org wrote:
> > On Fri, 2017-06-23 at 19:01 -0700, Palmer Dabbelt wrote:
> > > > > +#define mmiowb() __asm__ __volatile__ ("fence io,io" : : :
> > > > > "memory");
> >
>
On 6/24/17 5:35 AM, Matthias Schiffer wrote:
> The following functions are extended with a netlink_ext_ack argument to
> allow extended error reporting:
>
> * validate
> * newlink
> * changelink
> * slave_validate
> * slave_changelink
I would prefer separate patches for validate, slave_validate,
On 6/24/17 5:35 AM, Matthias Schiffer wrote:
> The following functions are extended with a netlink_ext_ack argument to
> allow extended error reporting:
>
> * validate
> * newlink
> * changelink
> * slave_validate
> * slave_changelink
I would prefer separate patches for validate, slave_validate,
On Fri, May 05, 2017 at 10:05:56AM +0200, Karim Eshapa wrote:
> Change the comment for an entry check inside function
> drain_mr_fqrni() with sleep for sufficient period
> of time instead of long time proccessor cycles.
>
> Signed-off-by: Karim Eshapa
> ---
>
On Fri, May 05, 2017 at 10:05:56AM +0200, Karim Eshapa wrote:
> Change the comment for an entry check inside function
> drain_mr_fqrni() with sleep for sufficient period
> of time instead of long time proccessor cycles.
>
> Signed-off-by: Karim Eshapa
> ---
> drivers/soc/fsl/qbman/qman.c | 25
On Fri, May 05, 2017 at 07:45:18AM +0200, Karim Eshapa wrote:
> Use msleep() instead of stucking with
> long delay will be more efficient.
>
> Signed-off-by: Karim Eshapa
> ---
> drivers/soc/fsl/qbman/qman.c | 6 +-
> 1 file changed, 1 insertion(+), 5 deletions(-)
On Fri, May 05, 2017 at 07:45:18AM +0200, Karim Eshapa wrote:
> Use msleep() instead of stucking with
> long delay will be more efficient.
>
> Signed-off-by: Karim Eshapa
> ---
> drivers/soc/fsl/qbman/qman.c | 6 +-
> 1 file changed, 1 insertion(+), 5 deletions(-)
Acked-by: Scott Wood
Hi Arnd,
[auto build test WARNING on linuxtv-media/master]
[also build test WARNING on v4.12-rc6 next-20170623]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi Arnd,
[auto build test WARNING on linuxtv-media/master]
[also build test WARNING on v4.12-rc6 next-20170623]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Fixed checkpatch.pl warnings of "function definition argument FOO should
also have an identifier name"
Found using checkpatch
Signed-off-by: Derek Robson
---
V2 had vauge subject and V1 comment above the line
V1 had vauge subject
Fixed checkpatch.pl warnings of "function definition argument FOO should
also have an identifier name"
Found using checkpatch
Signed-off-by: Derek Robson
---
V2 had vauge subject and V1 comment above the line
V1 had vauge subject
drivers/staging/rtl8192u/ieee80211/ieee80211.h | 2 +-
Fixed checkpatch.pl warnings of the form "function definition argument
'foo' should also have an identifier name" in header files.
Signed-off-by: Derek Robson
---
V2 had V1 comment above the line
V1 had vauge subject line
drivers/staging/sm750fb/sm750.h | 24
Fixed checkpatch.pl warnings of the form "function definition argument
'foo' should also have an identifier name" in header files.
Signed-off-by: Derek Robson
---
V2 had V1 comment above the line
V1 had vauge subject line
drivers/staging/sm750fb/sm750.h | 24
1 file
Fixed checkpatch warnings "Use #include instead of "
Found using checkpatch
Signed-off-by: Derek Robson
---
V2 had V1 comment above the line
V1 had vauge subject lines
drivers/staging/rtl8723bs/include/osdep_service_linux.h | 6 +++---
1 file changed, 3 insertions(+), 3
Fixed checkpatch warnings "Use #include instead of "
Found using checkpatch
Signed-off-by: Derek Robson
---
V2 had V1 comment above the line
V1 had vauge subject lines
drivers/staging/rtl8723bs/include/osdep_service_linux.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff
Fixed style of permissions to octal.
Found using checkpatch
Signed-off-by: Derek Robson
---
V1 and V2 had vauge subject lines
drivers/staging/unisys/visorhba/visorhba_main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Fixed style of permissions to octal.
Found using checkpatch
Signed-off-by: Derek Robson
---
V1 and V2 had vauge subject lines
drivers/staging/unisys/visorhba/visorhba_main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/unisys/visorhba/visorhba_main.c
Hi Ivan,
[auto build test ERROR on net/master]
[also build test ERROR on v4.12-rc6 next-20170623]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi Ivan,
[auto build test ERROR on net/master]
[also build test ERROR on v4.12-rc6 next-20170623]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Fix checkpatch.pl warnings of the form "function definition argument
'foo' should also have an identifier name" in header files.
Signed-off-by: Derek Robson
---
V1,V2 and V3 had vauge subject line.
drivers/staging/vt6655/card.h| 30 ++---
Fix checkpatch.pl warnings of the form "function definition argument
'foo' should also have an identifier name" in header files.
Signed-off-by: Derek Robson
---
V1,V2 and V3 had vauge subject line.
drivers/staging/vt6655/card.h| 30 ++---
drivers/staging/vt6655/channel.h |
Hi Georgi,
[auto build test ERROR on next-20170619]
[cannot apply to clk/clk-next robh/for-next linus/master v4.12-rc6 v4.12-rc5
v4.12-rc4 v4.12-rc6]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi Georgi,
[auto build test ERROR on next-20170619]
[cannot apply to clk/clk-next robh/for-next linus/master v4.12-rc6 v4.12-rc5
v4.12-rc4 v4.12-rc6]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi Baolin,
[auto build test ERROR on wsa/i2c/for-next]
[also build test ERROR on v4.12-rc6 next-20170623]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi Baolin,
[auto build test ERROR on wsa/i2c/for-next]
[also build test ERROR on v4.12-rc6 next-20170623]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
This has really been a long time, not sure we have any concern on this?
This change looks good to me which make the numa emulation more robust.
And David has acked.
Welcome any comments on this.
On Tue, May 02, 2017 at 09:04:50PM +0800, Wei Yang wrote:
>My previous patch "x86/mm/numa: Remove
This has really been a long time, not sure we have any concern on this?
This change looks good to me which make the numa emulation more robust.
And David has acked.
Welcome any comments on this.
On Tue, May 02, 2017 at 09:04:50PM +0800, Wei Yang wrote:
>My previous patch "x86/mm/numa: Remove
On Mon, May 15, 2017 at 10:58:24AM +0200, Michal Hocko wrote:
>From: Michal Hocko
>
[...]
>+void move_pfn_range_to_zone(struct zone *zone,
>+ unsigned long start_pfn, unsigned long nr_pages)
>+{
>+ struct pglist_data *pgdat = zone->zone_pgdat;
>+ int nid =
On Mon, May 15, 2017 at 10:58:24AM +0200, Michal Hocko wrote:
>From: Michal Hocko
>
[...]
>+void move_pfn_range_to_zone(struct zone *zone,
>+ unsigned long start_pfn, unsigned long nr_pages)
>+{
>+ struct pglist_data *pgdat = zone->zone_pgdat;
>+ int nid = pgdat->node_id;
Hi Michael,
[auto build test ERROR on powerpc/next]
[also build test ERROR on v4.12-rc6 next-20170623]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi Michael,
[auto build test ERROR on powerpc/next]
[also build test ERROR on v4.12-rc6 next-20170623]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
On Sat, 2017-06-24 at 08:58 +0200, Ingo Molnar wrote:
> * r...@redhat.com wrote:
>
> > From: Rik van Riel
> >
> > Several tests in the NAS benchmark seem to run a lot slower with
> > NUMA balancing enabled, than with NUMA balancing disabled. The
> > slower run
On Sat, 2017-06-24 at 08:58 +0200, Ingo Molnar wrote:
> * r...@redhat.com wrote:
>
> > From: Rik van Riel
> >
> > Several tests in the NAS benchmark seem to run a lot slower with
> > NUMA balancing enabled, than with NUMA balancing disabled. The
> > slower run time corresponds with increased
The latest maintenance release Git v2.13.2 is now available at
the usual places.
The tarballs are found at:
https://www.kernel.org/pub/software/scm/git/
The following public repositories all have a copy of the 'v2.13.2'
tag and the 'maint' branch that the tag points at:
url =
The latest maintenance release Git v2.13.2 is now available at
the usual places.
The tarballs are found at:
https://www.kernel.org/pub/software/scm/git/
The following public repositories all have a copy of the 'v2.13.2'
tag and the 'maint' branch that the tag points at:
url =
On Sat, Jun 24, 2017 at 3:59 PM, Masahiro Yamada
wrote:
>
> Sorry, I noticed a typo in my pull-request summary.
Pulled, with commit message fix-up.
Linus
On Sat, Jun 24, 2017 at 3:59 PM, Masahiro Yamada
wrote:
>
> Sorry, I noticed a typo in my pull-request summary.
Pulled, with commit message fix-up.
Linus
Hi Linus
Sorry, I noticed a typo in my pull-request summary.
> Kbuild fixes for v4.12 (2nd)
>
> - fix warnings of host programs
>
> - fix "make tags" when COMPILE_SOURCE=1 is specified along with O=
COMPILED_SOURCE=1
instead of
COMPILE_SOURCE=1
Could you fix it locally?
Hi Linus
Sorry, I noticed a typo in my pull-request summary.
> Kbuild fixes for v4.12 (2nd)
>
> - fix warnings of host programs
>
> - fix "make tags" when COMPILE_SOURCE=1 is specified along with O=
COMPILED_SOURCE=1
instead of
COMPILE_SOURCE=1
Could you fix it locally?
Hi Linus,
This is the 2nd round of Kbuild fixes for v4.12.
Nothing scary, just some random fixes.
Please pull!
The following changes since commit 08332893e37af6ae779367e78e444f8f9571511d:
Linux 4.12-rc2 (2017-05-21 19:30:23 -0700)
are available in the git repository at:
Hi Linus,
This is the 2nd round of Kbuild fixes for v4.12.
Nothing scary, just some random fixes.
Please pull!
The following changes since commit 08332893e37af6ae779367e78e444f8f9571511d:
Linux 4.12-rc2 (2017-05-21 19:30:23 -0700)
are available in the git repository at:
On Tue, Jun 13, 2017 at 03:38:18PM -0500, Christopher Bostic wrote:
> Reference the system device tree when configuring the watchdog.
> Configure for external signal generation if optional attribute
> 'external-signal' is present in device tree. Configure for
> reset system after timeout if the
On Tue, Jun 13, 2017 at 03:38:18PM -0500, Christopher Bostic wrote:
> Reference the system device tree when configuring the watchdog.
> Configure for external signal generation if optional attribute
> 'external-signal' is present in device tree. Configure for
> reset system after timeout if the
On Tue, Jun 13, 2017 at 03:38:17PM -0500, Christopher Bostic wrote:
> Describe new optional property 'external-signal'. When present in the
> system device tree an exernal signal is generated on watchdog timeout.
>
> Describe new optional property 'no-system-reset'. When present in the
> system
On Tue, Jun 13, 2017 at 03:38:17PM -0500, Christopher Bostic wrote:
> Describe new optional property 'external-signal'. When present in the
> system device tree an exernal signal is generated on watchdog timeout.
>
> Describe new optional property 'no-system-reset'. When present in the
> system
On Sat, 24 Jun 2017 02:41:42 PDT (-0700), ge...@linux-m68k.org wrote:
> Hi Palmer,
>
> On Sat, Jun 24, 2017 at 3:50 AM, Palmer Dabbelt wrote:
>> Multiple architectures define this as trivial function, and I'm adding
>> another one as part of the RISC-V port. This adds a
On Sat, 24 Jun 2017 08:42:05 PDT (-0700), b...@kernel.crashing.org wrote:
> On Fri, 2017-06-23 at 19:01 -0700, Palmer Dabbelt wrote:
>> > > +#define mmiowb()Â Â Â Â Â Â __asm__ __volatile__ ("fence io,io" : : :
>> > > "memory");
>
> I forgot if we already mentioned that but mmiowb is primarily
On Sat, 24 Jun 2017 02:34:06 PDT (-0700), ge...@linux-m68k.org wrote:
> Hi Palmer,
>
> On Sat, Jun 24, 2017 at 3:50 AM, Palmer Dabbelt wrote:
>> Multiple architectures define this as an empty function, and I'm adding
>> another one as part of the RISC-V port. This adds a
On Sat, 24 Jun 2017 08:42:05 PDT (-0700), b...@kernel.crashing.org wrote:
> On Fri, 2017-06-23 at 19:01 -0700, Palmer Dabbelt wrote:
>> > > +#define mmiowb()Â Â Â Â Â Â __asm__ __volatile__ ("fence io,io" : : :
>> > > "memory");
>
> I forgot if we already mentioned that but mmiowb is primarily
On Sat, 24 Jun 2017 02:34:06 PDT (-0700), ge...@linux-m68k.org wrote:
> Hi Palmer,
>
> On Sat, Jun 24, 2017 at 3:50 AM, Palmer Dabbelt wrote:
>> Multiple architectures define this as an empty function, and I'm adding
>> another one as part of the RISC-V port. This adds a __weak version of
>>
On Sat, 24 Jun 2017 02:41:42 PDT (-0700), ge...@linux-m68k.org wrote:
> Hi Palmer,
>
> On Sat, Jun 24, 2017 at 3:50 AM, Palmer Dabbelt wrote:
>> Multiple architectures define this as trivial function, and I'm adding
>> another one as part of the RISC-V port. This adds a __weak version of
>>
fs/xattr.c:516:10-17: WARNING opportunity for kstrdep (strcpy on line 519)
Use kstrdup rather than duplicating its implementation
Generated by: scripts/coccinelle/api/kstrdup.cocci
CC: Stefan Berger
Signed-off-by: Fengguang Wu
---
xattr.c
Hi Stefan,
[auto build test WARNING on linus/master]
[also build test WARNING on v4.12-rc6 next-20170623]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
fs/xattr.c:516:10-17: WARNING opportunity for kstrdep (strcpy on line 519)
Use kstrdup rather than duplicating its implementation
Generated by: scripts/coccinelle/api/kstrdup.cocci
CC: Stefan Berger
Signed-off-by: Fengguang Wu
---
xattr.c |3 +--
1 file changed, 1 insertion(+), 2
Hi Stefan,
[auto build test WARNING on linus/master]
[also build test WARNING on v4.12-rc6 next-20170623]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi,
On 16/06/2017 at 21:28:07 +0200, Krzysztof Kozlowski wrote:
> clk_enable() can fail so handle such case.
>
> Signed-off-by: Krzysztof Kozlowski
> ---
> drivers/rtc/rtc-s3c.c | 72
> ---
> 1 file changed, 57 insertions(+), 15
Hi,
On 16/06/2017 at 21:28:07 +0200, Krzysztof Kozlowski wrote:
> clk_enable() can fail so handle such case.
>
> Signed-off-by: Krzysztof Kozlowski
> ---
> drivers/rtc/rtc-s3c.c | 72
> ---
> 1 file changed, 57 insertions(+), 15 deletions(-)
>
On Thu, 22 Jun 2017 16:25:39 -0500
Rob Herring wrote:
> On Wed, Jun 14, 2017 at 05:13:15PM +0200, Fabrice Gasnier wrote:
> > Clock name has been updated during driver/DT binding review:
> > https://lkml.org/lkml/2016/12/13/718
> > Update DT binding doc to reflect this.
> >
> >
On Thu, 22 Jun 2017 16:25:39 -0500
Rob Herring wrote:
> On Wed, Jun 14, 2017 at 05:13:15PM +0200, Fabrice Gasnier wrote:
> > Clock name has been updated during driver/DT binding review:
> > https://lkml.org/lkml/2016/12/13/718
> > Update DT binding doc to reflect this.
> >
> > Fixes:
This is 4.12.0-rc5-00137-ga090bd4ff838 on a dual AthlonMP server tha has
been running fine until 4.11.0 included. 4.12.0-rc5-00137-ga090bd4ff838
was the first kernel after 4.11 that I tried and the problem happened
while compiling next kernel from git.
First it seems to be task jbd2/sda1-8:70
This is 4.12.0-rc5-00137-ga090bd4ff838 on a dual AthlonMP server tha has
been running fine until 4.11.0 included. 4.12.0-rc5-00137-ga090bd4ff838
was the first kernel after 4.11 that I tried and the problem happened
while compiling next kernel from git.
First it seems to be task jbd2/sda1-8:70
On Wed, 21 Jun 2017 16:30:15 +0200
Fabrice Gasnier wrote:
> Add support for STM32 Low-Power Timer, that can be used as counter
> or quadrature encoder.
>
> Signed-off-by: Fabrice Gasnier
Hmm. Sometime I'm going to ask you guys to document how all
On Wed, 21 Jun 2017 16:30:15 +0200
Fabrice Gasnier wrote:
> Add support for STM32 Low-Power Timer, that can be used as counter
> or quadrature encoder.
>
> Signed-off-by: Fabrice Gasnier
Hmm. Sometime I'm going to ask you guys to document how all these different
components fit together. Far
Em Wed, 21 Jun 2017 10:08:05 +0200
Johannes Thumshirn escreveu:
> Currently the media subsystem has a very creative abuse of the
> KERNEL_VERSION macro to encode an arbitrary version triplet for media
> drivers and device hardware revisions.
>
> This series introduces a new
Em Wed, 21 Jun 2017 10:08:05 +0200
Johannes Thumshirn escreveu:
> Currently the media subsystem has a very creative abuse of the
> KERNEL_VERSION macro to encode an arbitrary version triplet for media
> drivers and device hardware revisions.
>
> This series introduces a new macro called
On Wed, 21 Jun 2017 16:30:14 +0200
Fabrice Gasnier wrote:
> Add documentation for STMicroelectronics STM32 Low-Power Timer
> quadrature encoder and counter binding.
>
> Signed-off-by: Fabrice Gasnier
Acked-by: Jonathan Cameron
On Wed, 21 Jun 2017 16:30:14 +0200
Fabrice Gasnier wrote:
> Add documentation for STMicroelectronics STM32 Low-Power Timer
> quadrature encoder and counter binding.
>
> Signed-off-by: Fabrice Gasnier
Acked-by: Jonathan Cameron
> ---
> Changes in v2:
> - s/Low Power/Low-Power
> - remove
On Wed, 21 Jun 2017 16:30:13 +0200
Fabrice Gasnier wrote:
> Add support for LPTIMx_OUT triggers that can be found on some STM32
> devices. These triggers can be used then by ADC or DAC.
> Typical usage is to configure LPTimer as PWM output (via pwm-stm32-lp)
> and have
On Wed, 21 Jun 2017 16:30:13 +0200
Fabrice Gasnier wrote:
> Add support for LPTIMx_OUT triggers that can be found on some STM32
> devices. These triggers can be used then by ADC or DAC.
> Typical usage is to configure LPTimer as PWM output (via pwm-stm32-lp)
> and have synchronised analog
On Wed, 21 Jun 2017 16:30:12 +0200
Fabrice Gasnier wrote:
> Add documentation for STMicroelectronics STM32 Low-Power Timer Trigger
> binding.
>
> Signed-off-by: Fabrice Gasnier
looks sensible to me.
I'm kind of assuming this whole series will end
On Wed, 21 Jun 2017 16:30:12 +0200
Fabrice Gasnier wrote:
> Add documentation for STMicroelectronics STM32 Low-Power Timer Trigger
> binding.
>
> Signed-off-by: Fabrice Gasnier
looks sensible to me.
I'm kind of assuming this whole series will end up going through Lee and MFD.
Acked-by:
On Thu, 22 Jun 2017 13:44:34 +0800
Zhiyong Tao wrote:
> This commit adds mt7622 compatible node.
>
> Signed-off-by: Zhiyong Tao
> ---
> drivers/iio/adc/mt6577_auxadc.c |1 +
> 1 file changed, 1 insertion(+)
>
> diff --git
On Thu, 22 Jun 2017 13:44:34 +0800
Zhiyong Tao wrote:
> This commit adds mt7622 compatible node.
>
> Signed-off-by: Zhiyong Tao
> ---
> drivers/iio/adc/mt6577_auxadc.c |1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/iio/adc/mt6577_auxadc.c
On Thu, 22 Jun 2017 13:44:33 +0800
Zhiyong Tao wrote:
> This patch supports auxadc suspend/resume flow.
> Disable auxadc clk and power in suspend function.
> Enable axuadc clk and power in resume function.
>
> Signed-off-by: Zhiyong Tao
Worth
On Thu, 22 Jun 2017 13:44:33 +0800
Zhiyong Tao wrote:
> This patch supports auxadc suspend/resume flow.
> Disable auxadc clk and power in suspend function.
> Enable axuadc clk and power in resume function.
>
> Signed-off-by: Zhiyong Tao
Worth handling the cases where power management is not
On Fri, 23 Jun 2017 12:25:35 +0300
Eugen Hristev wrote:
> On 23.06.2017 01:07, kbuild test robot wrote:
> > Hi Eugen,
> >
> > [auto build test ERROR on iio/togreg]
> > [also build test ERROR on v4.12-rc6 next-20170622]
> > [if your patch is applied to the wrong git
On Fri, 23 Jun 2017 12:25:35 +0300
Eugen Hristev wrote:
> On 23.06.2017 01:07, kbuild test robot wrote:
> > Hi Eugen,
> >
> > [auto build test ERROR on iio/togreg]
> > [also build test ERROR on v4.12-rc6 next-20170622]
> > [if your patch is applied to the wrong git tree, please drop us a note
1 - 100 of 370 matches
Mail list logo