`dev-interface` document gives examples for accessing i2c from
userspace.
There's a note warning developers about the different `i2c-dev.h` header
files which were shipped with the kernel and i2c-tools separately.
However, these commits in i2c-tools repository suggests that the header
files are n
`dev-interface` document gives examples for accessing i2c from
userspace.
There's a note warning developers about the different `i2c-dev.h` header
files which were shipped with the kernel and i2c-tools separately.
However, these commits in i2c-tools repository suggests that the header
files are n
On 12/09/2017 08:02 AM, Masahiro Yamada wrote:
>
> Signed-off-by: Masahiro Yamada
> ---
>
> Documentation/process/changes.rst | 25 +
> scripts/Makefile.lib | 20 +---
> 2 files changed, 42 insertions(+), 3 deletions(-)
>
> diff --git a/Docu
The URLs in mono.rst redirect to pages on www.mono-project.com, so let's
update them. I took the liberty to update the compilation instructions
to the Linux-specific version, because readers of the kernel
documentation will most likely use Linux.
Signed-off-by: Jonathan Neuschäfer
---
Documentat
In Linux build system convention, pre-generated files are version-
controlled with a "_shipped" suffix. During the kernel building,
they are simply shipped (copied) removing the suffix.
>From users' point of view, this approach can reduce external tool
dependency for the kernel build,
>From deve
In Linux build system convention, pre-generated files are version-
controlled with a "_shipped" suffix. During the kernel building,
they are simply shipped (copied) removing the suffix.
This approach can reduce external tool dependency for the kernel build,
but it is tedious to manually regenerat
On Fri, Dec 08, 2017 at 06:18:45PM -0800, Joe Perches wrote:
> On Sat, 2017-12-09 at 12:27 +1100, Tobin C. Harding wrote:
> > On Fri, Dec 08, 2017 at 01:22:37PM -0800, Joe Perches wrote:
>
> > > Outside of the documentation, what could be useful is for
> > > someone to add a tool to verify %p exte
On 09/12/2017, Pavel Machek wrote:
> Yeah, what I'm saying is that maybe we need to extend generic power
> supply driver.
I don't know about that, you would have to ask the maintainers if that
is appropriate.
Thanks for the time!
Ognjen
--
To unsubscribe from this list: send the line "unsubscrib
On Sat 2017-12-09 11:29:51, Ognjen Galić wrote:
> On 09/12/2017, Pavel Machek wrote:
> > In newer series (I can't find it at the moment, sorry)
>
> The new series is a 3-patch patchset that obsoletes this
> patch. It is in the testing stage and will be pushed to
> the mailing lists and maintainer
On 09/12/2017, Pavel Machek wrote:
> In newer series (I can't find it at the moment, sorry)
The new series is a 3-patch patchset that obsoletes this
patch. It is in the testing stage and will be pushed to
the mailing lists and maintainers in a few days.
> Maybe we should have separate status "no
Hi!
In newer series (I can't find it at the moment, sorry) you return
"NOT_CHARGING" status when not charging because of wear control.
Maybe we should have separate status "not charging due to wear
control"?
Thanks,
Pavel
-
11 matches
Mail list logo