On Sun, May 28, 2017 at 11:09 PM, Chen-Yu Tsai wrote:
> On Sat, May 27, 2017 at 6:23 PM, Icenowy Zheng wrote:
>> Allwinner R40 has a clock controlling unit like the ones on other
>> Allwinner SoCs after sun6i, and can also use a CCU-based driver.
>>
>> Add a compatible string for it.
>>
>> Signed
In Linux build system convention, we do not run tools such as
flex, bison, gperf during the kernel building. Instead, manage
generated C files in the repository with _shipped suffixes.
They are simply shipped (copied) removing the _shipped suffixes
during the kernel building.
Commit 7373f4f83c71
*.hash.c files are artifacts generated from *.gperf by using gperf.
Instead of running gperf, we conventionally version-control
*.hash.c_shipped files and copy them to *.hash.c during build.
It is true that this approach can minimize external tool dependency,
but we need to update the shipped file
When we added support for omap3, back in 2010, we added a new
type of V4L2 devices that aren't fully controlled via the V4L2
device node. Yet, we never made it clear, at the V4L2 spec,
about the differences between both types.
Let's document them with the current implementation.
Signed-off-by: Ma
Hi,
I am stuck in a similar problem recent days by chance.
I am just curious about the purpose of introduction of these *_shipped
file, are they just for user's convenience when user doesn't install the
those tools?
--
Sincerely,
Cao jin
On 08/19/2017 04:49 PM, Masahiro Yamada wrote:
> In Li
A few changes to security/keys documentation as suggested by Nick Desaulniers.
This is my first patch series, so apologies for the inevitable errors in
formatting, recipients, etc.
Josh Holland (2):
docs: Standardise capitalisation of section headers in core.rst
docs: Fix paths in security/ke
The table of contents in security/keys/core.rst had different
capitalisation to the section headers, which broke case-sensitive
search.
Signed-off-by: Josh Holland
---
Documentation/security/keys/core.rst | 22 +++---
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git
Several paths in the security/keys documentation were incorrect.
Signed-off-by: Josh Holland
---
Documentation/security/keys/core.rst | 4 ++--
Documentation/security/keys/request-key.rst | 2 +-
Documentation/security/keys/trusted-encrypted.rst | 2 +-
3 files changed, 4 inse
On Sat, Aug 19, 2017 at 1:49 AM, Masahiro Yamada
wrote:
>
> Here is one question. Is it acceptable to use those rules all the time?
> That is, generate those C files by flex, bison, gperf during the
> kernel building.
Yeah, I think we probably should do that.
However, when I just tested, I noti
On Sat, Aug 19, 2017 at 10:03 AM, Linus Torvalds
wrote:
>
> So one of the advantages of the pre-shipped files is that we can avoid
> that kind of crazy version issues with the tools.
Side note: the traditional way to handle this is autoconf etc. Since I
think autoconf is evil crap, I refuse to ha
On Sat, Aug 19, 2017 at 10:14 AM, Linus Torvalds
wrote:
>
> Anybody want to look at just getting rid of the gperf use?
I took a stab at it. It wasn't too bad, although I think this needs a
*lot* of testing, and I think it needs checking of Makefile
dependencies etc.
NOTE NOTE NOTE! This may be *
Ram Pai writes:
> diff --git a/arch/powerpc/kernel/traps.c b/arch/powerpc/kernel/traps.c
> index d4e545d..fe1e7c7 100644
> --- a/arch/powerpc/kernel/traps.c
> +++ b/arch/powerpc/kernel/traps.c
> @@ -20,6 +20,7 @@
> #include
> #include
> #include
> +#include
> #include
> #include
> #in
On Mon, 14 Aug 2017, Gilad Ben-Yossef wrote:
> dm-verity is starting async. crypto ops and waiting for them to complete.
> Move it over to generic code doing the same.
>
> This also fixes a possible data coruption bug created by the
> use of wait_for_completion_interruptible() without dealing
>
On Fri, Aug 18, 2017 at 03:06:52PM -0600, Andreas Dilger wrote:
> On Aug 18, 2017, at 1:47 PM, Eric Biggers wrote:
> > +Key hierarchy
> > +=
> > +
> > +Master Keys
> > +---
> > +
> > +Userspace should generate master keys either using a cryptographically
> > +secure random numb
The compatible string for Allwinner V3s SoC used to be missing.
Add it to the binding document.
Fixes: b074fede01c0 ("arm: sunxi: add support for V3s SoC")
Signed-off-by: Icenowy Zheng
---
Documentation/devicetree/bindings/arm/sunxi.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Docume
Allwinner R40 is a new SoC, with Quad Core Cortex-A7 and peripherals
like A20.
Add support for it.
Signed-off-by: Icenowy Zheng
---
Documentation/arm/sunxi/README | 6 ++
Documentation/devicetree/bindings/arm/sunxi.txt | 1 +
arch/arm/mach-sunxi/sunxi.c
16 matches
Mail list logo
