2017-01-27 6:40 GMT+08:00 Jonathan Corbet :
> OK, I've applied the whole set, thanks.
Thanks for applying!
> One thing, though: your messages came through with this header:
>
> Content-Type: text/plain; charset=y
>
> The screwy "charset=y" puts "git am" into a severely uncooperative mood
Hi Edward,
[auto build test ERROR on hwmon/hwmon-next]
[also build test ERROR on v4.10-rc5 next-20170125]
[cannot apply to linux/master]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/eajames-ib
From: "Edward A. James"
Add functions to parse the data structures that are specific to the OCC on
the POWER9 processor. These are the sensor data structures, including
temperature, frequency, power, and "caps."
Signed-off-by: Edward A. James
Signed-off-by: Andrew Jeffery
---
Documentation/hw
From: "Edward A. James"
Add code to tie the hwmon sysfs code and the POWER8 OCC code together, as
well as probe the entire driver from the I2C bus. I2C is the communication
method between the BMC and the P8 OCC.
Signed-off-by: Edward A. James
Signed-off-by: Andrew Jeffery
---
Documentation/de
From: "Edward A. James"
Add functions to parse the data structures that are specific to the OCC on
the POWER8 processor. These are the sensor data structures, including
temperature, frequency, power, and "caps."
Signed-off-by: Edward A. James
Signed-off-by: Andrew Jeffery
---
Documentation/hw
From: "Edward A. James"
This patchset adds a hwmon driver to support the OCC (On-Chip Controller)
on the IBM POWER8 and POWER9 processors, from a BMC (Baseboard Management
Controller). The OCC is an embedded processor that provides real time
power and thermal monitoring.
The driver provides an i
From: "Edward A. James"
Add functions to send SCOM operations over I2C bus. The BMC can
communicate with the Power8 host processor over I2C, but needs to use SCOM
operations in order to access the OCC register space.
Signed-off-by: Edward A. James
Signed-off-by: Andrew Jeffery
---
drivers/hwm
From: "Edward A. James"
Add core support for polling the OCC for it's sensor data and parsing that
data into sensor-specific information.
Signed-off-by: Edward A. James
Signed-off-by: Andrew Jeffery
---
Documentation/hwmon/occ| 40
MAINTAINERS| 7 +
drivers/hwmon/K
From: "Edward A. James"
Add a generic mechanism to expose the sensors provided by the OCC in
sysfs.
Signed-off-by: Edward A. James
Signed-off-by: Andrew Jeffery
---
Documentation/hwmon/occ | 62 ++
drivers/hwmon/occ/Makefile| 2 +-
drivers/hwmon/occ/occ_sysfs.c | 259
On Wed, 25 Jan 2017 12:14:31 +0800
Andy Deng wrote:
> Some of the sentences in Chapters 19 and 20 are re-translated:
>
> - Fixed translation errors in Section 2 of Chapter 19 to prevent
> misleading readers;
> - Retranslate some sentences to make the translation more clear and
> accurate.
O
On Mon, 23 Jan 2017 00:18:10 -0800
Matthew Wilcox wrote:
> Clearly nobody ever tried to build the documentation for the radix tree
> before:
>
> include/linux/radix-tree.h:400: warning: cannot understand function
> prototype: 'void ** radix_tree_iter_init(struct radix_tree_iter *iter,
> unsigned
On Tue, 24 Jan 2017 21:45:15 +0900
Masanari Iida wrote:
> This patch fix some double words found in Documentation.
Applied, thanks.
jon
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vg
On Mon, 23 Jan 2017 08:41:34 +1000
Darryl Bond wrote:
> Moved file zorro.rst to
> equivalent location as source in main tree, ie drivers/zorro This required
> creation of Documentation/drivers. It is my suggestion that the Documentation
> tree is organised in the same fashion as the source tre
On Tue, 17 Jan 2017 13:38:49 +
Steven Price wrote:
> Two of the example command lines use an argument to echo of "-c" which
> isn't valid in (most versions of) echo causing these examples to fail.
> Correct the argument to "-n" which works correctly.
Makes sense, applied (though those contro
On Mon, 16 Jan 2017 14:31:15 -0800
Florian Fainelli wrote:
> Add a bunch of entries reflective of programs that the kernel build:
> sortextable, dtc. And while at it, expand the lex*.c entries to cover
> e.g: dtc-lexer.c. Finally, exclude devicetable-offsets.h
Does anybody still use the dontdiff
From: Jani Nikula [mailto:jani.nik...@linux.intel.com]
> You can use /* private: */ within the struct to indicate the following
> members should not be included in the generated documentation. It does
> however mean you can't then document the members either, or you'll get
> warnings.
>
> I'm gene
On Thu, 26 Jan 2017, Matthew Wilcox wrote:
> Here's a little glitch that I'd like to see fixed:
>
> struct radix_tree_iter
> radix tree iterator state
> Definition
> struct radix_tree_iter {
> unsigned long index;
> unsigned long next_index;
> unsigned long tags;
> struct radix_tree_node *
On Thu, 26 Jan 2017, Jonathan Corbet wrote:
> Give me a new kerneldoc that passes those tests, and I'll happily
> merge it. (I have some sympathy with the idea that we should look
> into other parsers, but I would not hold up a new kerneldoc that
> passed those tests on this basis alone.)
I'll j
Here's a little glitch that I'd like to see fixed:
struct radix_tree_iter
radix tree iterator state
Definition
struct radix_tree_iter {
unsigned long index;
unsigned long next_index;
unsigned long tags;
struct radix_tree_node * node;
#ifdef CONFIG_RADIX_TREE_MULTIORDER
unsigned int shift
On Wed, 25 Jan 2017 20:07:47 +0100
Markus Heiser wrote:
> So, what I mean is, the new parser has to generate a complete different reST
> output and thats why we can't compare the perl parser with python one on a
> reST
> basis ... and if reST is different, HTML is different :(
>
> So we do not
On Thu, 26 Jan 2017, Markus Heiser wrote:
> Am 25.01.2017 um 21:59 schrieb Jani Nikula :
>
>>> But the problem I see here is, that the perl script generates a
>>> reST output which I can't use. As an example we can take a look at
>>> the man-page builder I shipped in the series.
>>
>> Sorry, I st
Am 25.01.2017 um 21:59 schrieb Jani Nikula :
>> But the problem I see here is, that the perl script generates a
>> reST output which I can't use. As an example we can take a look at
>> the man-page builder I shipped in the series.
>
> Sorry, I still don't understand *why* you can't use the same
22 matches
Mail list logo
