Hi all,
The patches fix some file paths and minor grammatical issues in the
GPIO/pinctrl documentation. Patches 3 and 4 are separate to ease review.
Cheers,
Andrew
Andrew Jeffery (4):
drivers-on-gpio.txt: Fix paths to GPIO driver source files
pinctrl.txt: Fix grammar in pinmux request list
Signed-off-by: Andrew Jeffery
---
Documentation/gpio/drivers-on-gpio.txt | 13 +++--
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/Documentation/gpio/drivers-on-gpio.txt
b/Documentation/gpio/drivers-on-gpio.txt
index 14bf95a13bae..306513251713 100644
--- a/Documentation/g
Signed-off-by: Andrew Jeffery
---
Documentation/pinctrl.txt | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/pinctrl.txt b/Documentation/pinctrl.txt
index 4976389e432d..cefcf5d88a1c 100644
--- a/Documentation/pinctrl.txt
+++ b/Documentation/pinctrl.txt
@@
Signed-off-by: Andrew Jeffery
---
Documentation/pinctrl.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/pinctrl.txt b/Documentation/pinctrl.txt
index cefcf5d88a1c..07d102c3d05a 100644
--- a/Documentation/pinctrl.txt
+++ b/Documentation/pinctrl.txt
@@ -286,7 +
Signed-off-by: Andrew Jeffery
---
Documentation/pinctrl.txt | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/Documentation/pinctrl.txt b/Documentation/pinctrl.txt
index 07d102c3d05a..6414a613cb8a 100644
--- a/Documentation/pinctrl.txt
+++ b/Documentation/pinctrl.
Hi,
This is fourth approach for replacing struct dma_attrs with unsigned
long.
The main patch (1/44) doing the change is split into many subpatches
for easier review (2-42). They should be squashed together when
applying.
*Important:* Patchset is tested on my ARM platforms and *only* build
te
The dma-mapping core and the implementations do not change the
DMA attributes passed by pointer. Thus the pointer can point to const
data. However the attributes do not have to be a bitfield. Instead
unsigned long will do fine:
1. This is just simpler. Both in terms of reading the code and sett
Scan all input files for EXPORT_SYMBOLs along with the explicitly
specified export files before actually parsing anything.
Signed-off-by: Jani Nikula
---
scripts/kernel-doc | 18 +-
1 file changed, 5 insertions(+), 13 deletions(-)
diff --git a/scripts/kernel-doc b/scripts/kernel
Hi Jon -
Thanks for merging the main Sphinx series! I greet you with another set
of patches on top. ;)
The main things here are reducing the noise on duplicate sections and
adding better support for extracting exported symbols when
EXPORT_SYMBOLs and kernel-doc are in separate files. And then the
Leftover cruft. No functional changes.
Signed-off-by: Jani Nikula
---
Documentation/sphinx/kernel-doc.py | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/Documentation/sphinx/kernel-doc.py
b/Documentation/sphinx/kernel-doc.py
index 4adfb0e91ecc..2856376cc62c 100644
--- a/Do
Using the default str.split doesn't return empty strings like the
current version does.
Signed-off-by: Jani Nikula
---
Documentation/sphinx/kernel-doc.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/sphinx/kernel-doc.py
b/Documentation/sphinx/kernel-doc.py
i
Let the user specify file patterns where to look for the EXPORT_SYMBOLs
in addition to the file with kernel-doc comments. This is directly based
on the -export-file FILE option added to kernel-doc in "kernel-doc: add
support for specifying extra files for EXPORT_SYMBOLs", but we extend
that with gl
Signed-off-by: Jani Nikula
---
scripts/kernel-doc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/scripts/kernel-doc b/scripts/kernel-doc
index 710615f3a4ff..a6f82c812c15 100755
--- a/scripts/kernel-doc
+++ b/scripts/kernel-doc
@@ -484,10 +484,10 @@ while ($ARGV[0] =~ m/^-
If the kernel-doc comments for functions are not in the same file as the
EXPORT_SYMBOL statements, the -export and -internal output selections do
not work as expected. This is typically the case when the kernel-doc
comments are in header files next to the function declarations and the
EXPORT_SYMBOL
Since
commit 32217761ee9db0215350dfe1ca4e66f312fb8c54
Author: Jani Nikula
Date: Sun May 29 09:40:44 2016 +0300
kernel-doc: concatenate contents of colliding sections
we started getting (more) errors on duplicate section names, especially
on the default section name "Description":
include
No functional changes.
Signed-off-by: Jani Nikula
---
scripts/kernel-doc | 3 ---
1 file changed, 3 deletions(-)
diff --git a/scripts/kernel-doc b/scripts/kernel-doc
index 27757c21551a..ac18eb5ed776 100755
--- a/scripts/kernel-doc
+++ b/scripts/kernel-doc
@@ -529,21 +529,18 @@ sub dump_section
Reduce duplication in follow-up work. No functional changes.
Signed-off-by: Jani Nikula
---
scripts/kernel-doc | 27 ++-
1 file changed, 18 insertions(+), 9 deletions(-)
diff --git a/scripts/kernel-doc b/scripts/kernel-doc
index a6f82c812c15..516d95fcefb7 100755
--- a/sc
On Fri, Jun 10, 2016 at 12:11:18PM +0200, Krzysztof Kozlowski wrote:
> The dma-mapping core and the implementations do not change the
> DMA attributes passed by pointer. Thus the pointer can point to const
> data. However the attributes do not have to be a bitfield. Instead
> unsigned long will d
Am 08.06.2016 um 21:49 schrieb Jonathan Corbet :
> So I've finally gotten a chance to make another pass over this stuff.
>
> Markus, your enthusiasm is great; I'm hoping you'll do great things
> helping us to improve the kernel's documentation toolchain.
With 7 years DocBook and 8 years reST
Add support for the the INA3221 26v capable, Triple channel,
Bi-Directional, Zero-Drift, Low-/High-Side, Current/Voltage Monitor
with I2C interface.
Signed-off-by: Andrew F. Davis
---
Documentation/hwmon/ina3221 | 35
drivers/hwmon/Kconfig | 11 ++
drivers/hwmon/Makefile | 1
Hello all,
This series adds support for the INA3221 Triple Current/Voltage Monitor.
Changes from v4:
- Drop DT support, will be added by Laxman in followup patches
Changes from v3:
- minor fixups from comments
- rebased on v4.7-rc1
Changes from v2:
- changed alarms to work on current
- add
Hi all,
this is my suggestion for a DocBook to reST movement. It includes
the doc build tools and a migration [3] of all DocBook-XML books to
the reST markup.
The kernel-doc HOWTO [1], the Template Book [2] and
make books-help
are your friends.
Any comments are welcome.
-- Markus
Hi Randy,
thanks for your amendments / has been fixed [1]
[1]
https://github.com/return42/linux/commit/98a9fc42cbd0c23b266ac28494dafe20d7920d05
Am 09.06.2016 um 20:05 schrieb Randy Dunlap :
> Hi,
>
> Some spellos and a few questions...
>> + b/Documentation/books/kernel-doc-HOWTO/vintage-kern
On 06/10/16 09:00, Markus Heiser wrote:
> Hi Randy,
>
> thanks for your amendments / has been fixed [1]
>
> [1]
> https://github.com/return42/linux/commit/98a9fc42cbd0c23b266ac28494dafe20d7920d05
>
> Am 09.06.2016 um 20:05 schrieb Randy Dunlap :
>
>> Hi,
>>
>> Some spellos and a few questions.
On Fri, Jun 10, 2016 at 10:32:33AM -0500, Andrew F. Davis wrote:
> Add support for the the INA3221 26v capable, Triple channel,
> Bi-Directional, Zero-Drift, Low-/High-Side, Current/Voltage Monitor
> with I2C interface.
>
> Signed-off-by: Andrew F. Davis
Applied to -next.
Can you by any chance
Am 07.06.2016 um 08:44 schrieb Jani Nikula :
> On Tue, 07 Jun 2016, Markus Heiser wrote:
>> I looked closer to rst2pdf, it supports only the docutils reST, but
>> not the sphinx superset ...
>>
>> -
>> $ rst2pdf index.rst
>> index.rst:15: (ERROR/3) Unknown interpreted text role "
On Fri, 10 Jun 2016, Markus Heiser wrote:
> Am 08.06.2016 um 21:49 schrieb Jonathan Corbet :
>> But please,
>> at this point, let's build on Jani's work and go from there. Things have
>> waited for long enough while we've gone around on this; I think what we
>> have is a good starting point.
>
>
On Fri, Jun 10, 2016 at 07:59:57AM +0200, Stephan Linz wrote:
> Cc: Joseph Jezak
> Cc: Jörg Sommer
> Signed-off-by: Stephan Linz
> ---
> Documentation/devicetree/bindings/leds/common.txt| 3 ++-
> Documentation/devicetree/bindings/leds/leds-gpio.txt | 4 ++--
> Documentation/laptops/asus-la
On Thu, Jun 9, 2016 at 9:55 PM, Jonathan Corbet wrote:
> On Sat, 4 Jun 2016 14:37:01 +0300
> Jani Nikula wrote:
>
>> When this lands in docs-next and we can backmerge to drm, we'll plunge
>> ahead and convert gpu.tmpl to rst, and have that ready for v4.8.
>
> That is now done — thanks for runnin
> -Original Message-
> From: David Kershner [mailto:david.kersh...@unisys.com]
> Sent: Wednesday, June 8, 2016 5:14 PM
> To: cor...@lwn.net; t...@linutronix.de; mi...@redhat.com;
> h...@zytor.com; Kershner, David A ;
> gre...@linuxfoundation.org; Arfvidson, Erik ;
> Sell, Timothy C ; hof...
On Fri, Jun 10, 2016 at 04:49:47PM +0200, Luis R. Rodriguez wrote:
> On Fri, Jun 10, 2016 at 12:11:18PM +0200, Krzysztof Kozlowski wrote:
> > The dma-mapping core and the implementations do not change the
> > DMA attributes passed by pointer. Thus the pointer can point to const
> > data. However
On Fri, Jun 10, 2016 at 10:16:00PM +0200, Krzysztof Kozlowski wrote:
> On Fri, Jun 10, 2016 at 04:49:47PM +0200, Luis R. Rodriguez wrote:
> > On Fri, Jun 10, 2016 at 12:11:18PM +0200, Krzysztof Kozlowski wrote:
> > > The dma-mapping core and the implementations do not change the
> > > DMA attribute
On 11 June 2016 at 04:17, Daniel Vetter wrote:
> On Thu, Jun 9, 2016 at 9:55 PM, Jonathan Corbet wrote:
>> On Sat, 4 Jun 2016 14:37:01 +0300
>> Jani Nikula wrote:
>>
>>> When this lands in docs-next and we can backmerge to drm, we'll plunge
>>> ahead and convert gpu.tmpl to rst, and have that r
On Fri, Jun 10, 2016 at 10:23:47PM +0200, Luis R. Rodriguez wrote:
> On Fri, Jun 10, 2016 at 10:16:00PM +0200, Krzysztof Kozlowski wrote:
> > On Fri, Jun 10, 2016 at 04:49:47PM +0200, Luis R. Rodriguez wrote:
> > > On Fri, Jun 10, 2016 at 12:11:18PM +0200, Krzysztof Kozlowski wrote:
> > > > The dma
On Fri, Jun 10, 2016 at 10:44:19PM +0200, Krzysztof Kozlowski wrote:
> On Fri, Jun 10, 2016 at 10:23:47PM +0200, Luis R. Rodriguez wrote:
> > On Fri, Jun 10, 2016 at 10:16:00PM +0200, Krzysztof Kozlowski wrote:
> > > The dma-attrs in current form were added around 2008 in 74bc7ceebfa1
> > > ("dma:
This is a "v4" of Greg Hackmann's DT bindings for ramoops. This is
what I'm going to land in the pstore tree unless there are strong and
convincing arguments against it. :)
I made a number of changes based people's feedback, and I want to get
it unblocked. This patch is already carried by Android,
From: Greg Hackmann
ramoops is one of the remaining places where ARM vendors still rely on
board-specific shims. Device Tree lets us replace those shims with
generic code.
These bindings mirror the ramoops module parameters, with two small
differences:
(1) dump_oops becomes an optional "no-dum
Signed-off-by: Michal Nazarewicz
---
Documentation/usb/gadget_multi.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/usb/gadget_multi.txt
b/Documentation/usb/gadget_multi.txt
index 5faf514..b3146dd 100644
--- a/Documentation/usb/gadget_multi.txt
+++ b/Documen
visorbus is currently located at drivers/staging/visorbus,
this patch moves it to drivers/virt.
Signed-off-by: David Kershner
Reviewed-by: Tim Sell
---
drivers/staging/unisys/Kconfig| 3 +--
drivers/staging/unisys/Makefile
This patchset is dependent on the previously-submitted patchset:
staging: unisys: fix visorbus & visorinput issues raised by tglx
This patchset moves drivers/staging/unisys/include to
include/linux/visorbus, and moves drivers/staging/unisys/visorbus to
drivers/virt/visorbus.
This patchse
This patch simple does a git mv of the
drivers/staging/unisys/Documentation directory to Documentation. Renames
overview.txt to visorbus.txt and renames sysfs-platform-visorchipset to
the correct name sysfs-bus-visorbus.
Signed-off-by: David Kershner
Reviewed-by: Tim Sell
---
.../ABI/stable/sys
Update include/linux to include the s-Par associated common include
header files needed for the s-Par visorbus.
Since we have now moved the include directories over to
include/linux/visorbus this patch makes all of the visor
drivers visorbus, visorinput, visornic, and visorhba use
the new include
> > > > From: Thomas Gleixner [mailto:t...@linutronix.de]
> > > >
> > > > I think I asked this before, but I might have missed the answer.
> > > >
> > > > Why is this a rw_sempahore? It's never taken with down_read and
> > looking
> > > > at the usage sites it's simply a mutex, right?
> > >
> > > I
43 matches
Mail list logo