[PATCH] Documentation: HOWTO: update git home URL in translations

Homepage url of git in HOWTO document was updated by commit e234ebf7881c013b654113f0a208977ac3ce1d01 ("Documentation/HOWTO: update git home URL") but not applied to several translations. This commit updates them. Signed-off-by: SeongJae Park --- Documentation/ko_KR/HOWTO |

[PATCH] Documentatio: HOWTO: remove regression postings info from translations

Obsolete info about regression postings were removed by commit 5645a717c6ee61e67d38aa9f15cb9db074e1e99d ("Documentation: HOWTO: remove obsolete info about regression postings") but not applied to translations. This commit applies the change to translations. Signed-off-by: SeongJae Park

Re: [PATCH v6 01/24] i2c-mux: add common data for every i2c-mux instance

Wolfram Sang wrote: > > > wonder even more if we couldn't supply num_adapters to i2c_mux_alloc() > > > and reserve the memory statically. i2c busses are not > > > dynamic/hot-pluggable so that should be good enough? > > > > Yes, that would work, but it would take some restructuring in some of > >

Re: [PATCH 4/4] serial: doc: .break_ctl() may sleep

On 04/15/2016 03:41 PM, Jonathan Corbet wrote: > On Fri, 15 Apr 2016 15:31:30 -0700 > Peter Hurley wrote: > >> The only caller of the uart driver's break_ctl() method is >> uart_break_ctl(), which is serial core's proxy tty driver break_ctl() >> method. uart_break_ctl()

Re: [PATCH 4/4] serial: doc: .break_ctl() may sleep

On Fri, 15 Apr 2016 15:31:30 -0700 Peter Hurley wrote: > The only caller of the uart driver's break_ctl() method is > uart_break_ctl(), which is serial core's proxy tty driver break_ctl() > method. uart_break_ctl() claims the struct tty_port::mutex to prevent >

Re: [PATCH 4/4] serial: doc: .break_ctl() may sleep

On 04/15/2016 03:01 PM, Jonathan Corbet wrote: > On Thu, 14 Apr 2016 11:08:11 +0200 > Geert Uytterhoeven wrote: > >> As mutex_lock() must not be called with interrupts disabled, >> .break_ctl() may sleep. > > So I've applied the first three to the docs tree, but this

[RFC v1 3/4] x86, boot: Implement ASLR for kernel memory sections (x86_64)

Randomizes the virtual address space of kernel memory sections (physical memory mapping, vmalloc & vmemmap) for x86_64. This security feature mitigates exploits relying on predictable kernel addresses. These addresses can be used to disclose the kernel modules base addresses or corrupt specific

[RFC v1 2/4] x86, boot: PUD VA support for physical mapping (x86_64)

Minor change that allows early boot physical mapping of PUD level virtual addresses. This change prepares usage of different virtual addresses for KASLR memory randomization. It has no impact on default usage. Signed-off-by: Thomas Garnier --- Based on next-20160413 ---

[RFC v1 4/4] x86, boot: Memory hotplug support for KASLR memory randomization

Add a new option (CONFIG_RANDOMIZE_MEMORY_PHYSICAL_PADDING) to define the padding used for the physical memory mapping section when KASLR memory is enabled. It ensures there is enough virtual address space when CONFIG_MEMORY_HOTPLUG is used. The default value is 10 terabytes. If

[RFC v1 1/4] x86, boot: Refactor KASLR entropy functions

Move the KASLR entropy functions in x86/libray to be used in early kernel boot for KASLR memory randomization. Signed-off-by: Thomas Garnier --- Based on next-20160413 --- arch/x86/boot/compressed/aslr.c | 76 +++

[RFC v1 0/4] x86, boot: KASLR memory implementation (x86_64)

This is RFC v1 for KASLR memory implementation on x86_64. It was reviewed early by Kees Cook. ***Background: The current implementation of KASLR randomizes only the base address of the kernel and its modules. Research was published showing that static memory can be overwitten to elevate

Re: [PATCH 4/4] serial: doc: .break_ctl() may sleep

On Thu, 14 Apr 2016 11:08:11 +0200 Geert Uytterhoeven wrote: > As mutex_lock() must not be called with interrupts disabled, > .break_ctl() may sleep. So I've applied the first three to the docs tree, but this one stopped me. The changelog doesn't really say why the

Re: [PATCH v3] ARM64: ACPI: Update documentation for latest specification version

On 04/15/2016 03:35 PM, Jonathan Corbet wrote: > On Mon, 28 Mar 2016 18:06:42 -0600 > Al Stone wrote: > >> This patch reflects going back through and examining the specs in detail >> and updating content appropriately. Whilst there, a few odds and ends of >> typos were

Re: [PATCH v2 2/5] Documentation: update Michael K. Johnson's work

On Thu, 31 Mar 2016 12:10:30 +0100 Luis de Bethencourt wrote: > The URL for "Writing Linux Device Drivers" hasn't been available in some > time. Updating the entry to Michael K. Johnson's "Linux Kernel Hackers' > Guide" OK, I've applied this one to the docs tree.

Re: [PATCH v3] ARM64: ACPI: Update documentation for latest specification version

On Mon, 28 Mar 2016 18:06:42 -0600 Al Stone wrote: > This patch reflects going back through and examining the specs in detail > and updating content appropriately. Whilst there, a few odds and ends of > typos were caught as well. This brings the documentation up to date

Re: [PATCH] irqchip, gicv3-its, numa: Enable workaround for Cavium thunderx erratum 23144

I will resend this with a proper version tag. -Robert On 15.04.16 21:15:34, Robert Richter wrote: > From: Ganapatrao Kulkarni > > The erratum fixes the hang of ITS SYNC command by avoiding inter node > io and collections/cpu mapping on thunderx dual-socket

Re: [PATCH v10 4/5] tpm: Initialize TPM and get durations and timeouts

On Fri, Apr 15, 2016 at 09:50:15AM -0400, Stefan Berger wrote: > @@ -69,12 +73,19 @@ static ssize_t vtpm_proxy_fops_read(struct file *filp, > char __user *buf, > size_t len; > int sig, rc; > > - sig = wait_event_interruptible(proxy_dev->wq, proxy_dev->req_len != 0); > + sig

Re: [PATCH v2] procfs: expose umask in /proc//status

On Thu, Apr 14, 2016 at 4:08 AM, Richard W.M. Jones wrote: > It's not possible to read the process umask without also modifying it, > which is what umask(2) does. A library cannot read umask safely, > especially if the main program might be multithreaded. > > Add a new status

Re: [PATCH v3] ARM64: ACPI: Update documentation for latest specification version

On 04/15/2016 08:37 AM, Lorenzo Pieralisi wrote: > Hi Al, > > On Mon, Mar 28, 2016 at 06:06:42PM -0600, Al Stone wrote: >> The ACPI 6.1 specification was recently released at the end of January >> 2016, but the arm64 kernel documentation for the use of ACPI was written >> for the 5.1 version of

Re: [PATCH v2] procfs: expose umask in /proc//status

On Fri, Apr 15, 2016 at 02:29:52PM +0100, Richard W.M. Jones wrote: > > The use case is that we have endless trouble with people setting weird > umask() values (usually on the grounds of "security"), and then > everything breaking. I'm on the hook to fix these. We'd like to add > debugging to

Re: [PATCH] Add EDAC peripheral init functions & Ethernet EDAC.

On 04/15/2016 04:40 AM, Mauro Carvalho Chehab wrote: Em Thu, 14 Apr 2016 09:35:01 -0500 Rob Herring escreveu: On Tue, Apr 12, 2016 at 05:12:55PM -0500, ttha...@opensource.altera.com wrote: This patch set adds the memory initialization functions for Altera's Arria10

Re: [PATCH] crypto: document correct return value for request allocation

On Sat, Apr 02, 2016 at 10:54:56AM -0500, Eric Biggers wrote: > Signed-off-by: Eric Biggers Applied. -- Email: Herbert Xu Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt -- To unsubscribe

Re: [PATCH v3] ARM64: ACPI: Update documentation for latest specification version

Hi Al, On Mon, Mar 28, 2016 at 06:06:42PM -0600, Al Stone wrote: > The ACPI 6.1 specification was recently released at the end of January > 2016, but the arm64 kernel documentation for the use of ACPI was written > for the 5.1 version of the spec. There were significant additions to the > spec

[PATCH v10 4/5] tpm: Initialize TPM and get durations and timeouts

Add the retrieval of TPM 1.2 durations and timeouts. Since this requires the startup of the TPM, do this for TPM 1.2 and TPM 2. Signed-off-by: Stefan Berger CC: linux-ker...@vger.kernel.org CC: linux-doc@vger.kernel.org CC: linux-...@vger.kernel.org ---

Re: [PATCH v5 07/24] regulator: pwm: use pwm_get_args() where appropriate

On Thu, Apr 14, 2016 at 09:17:27PM +0200, Boris Brezillon wrote: > The PWM framework has clarified the concept of reference PWM config > (the platform dependent config retrieved from the DT or the PWM > lookup table) and real PWM state. Acked-by: Mark Brown signature.asc