Add a section to Documentation/livepatch/module-elf-format.rst
describing how klp-convert works for fixing relocations.
Signed-off-by: Lukas Hruska
Reviewed-by: Petr Mladek
Reviewed-by: Marcos Paulo de Souza
---
Documentation/livepatch/module-elf-format.rst | 67 +++
1 file cha
Add a section to Documentation/livepatch/module-elf-format.rst
describing how klp-convert works for fixing relocations.
Signed-off-by: Lukas Hruska
Reviewed-by: Petr Mladek
Reviewed-by: Marcos Paulo de Souza
---
Documentation/livepatch/module-elf-format.rst | 67 +++
1 file cha
On Mon, 2023-11-06 at 17:25 +0100, Lukas Hruska wrote:
> Add a section to Documentation/livepatch/module-elf-format.rst
> describing how klp-convert works for fixing relocations.
>
> Signed-off-by: Lukas Hruska
Reviewed-by: Marcos Paulo de Souza
> ---
> Documentation/livepatch/module-elf-form
On Mon 2023-11-06 17:25:13, Lukas Hruska wrote:
> Add a section to Documentation/livepatch/module-elf-format.rst
> describing how klp-convert works for fixing relocations.
>
> Signed-off-by: Lukas Hruska
Looks good to me:
Reviewed-by: Petr Mladek
Best Regards,
Petr
Add a section to Documentation/livepatch/module-elf-format.rst
describing how klp-convert works for fixing relocations.
Signed-off-by: Lukas Hruska
---
Documentation/livepatch/module-elf-format.rst | 67 +++
1 file changed, 67 insertions(+)
diff --git a/Documentation/livepatch/m
Hi,
On 4/1/21 5:07 PM, Mark Pearson wrote:
>
>
> On 01/04/2021 09:49, Hans de Goede wrote:
>> Hi,
>>
>> On 4/1/21 2:17 PM, Mauro Carvalho Chehab wrote:
>>> The file name: Documentation/ABI/testing/sysfs-platform_profile.rst
>>> should be, instead: Documentation/userspace-api/sysfs-platform_profi
Em Wed, 17 Feb 2021 10:34:34 +0200
Alexandru Ardelean escreveu:
> Since the new change to the IIO buffer infrastructure, the buffer/ and
> scan_elements/ directories have been merged into bufferY/ to have some
> attributes available per-buffer.
>
> This change updates the ABI docs to reflect thi
On 01/04/2021 09:49, Hans de Goede wrote:
> Hi,
>
> On 4/1/21 2:17 PM, Mauro Carvalho Chehab wrote:
>> The file name: Documentation/ABI/testing/sysfs-platform_profile.rst
>> should be, instead: Documentation/userspace-api/sysfs-platform_profile.rst.
>>
>> Update its cross-reference accordingly.
On Thu, 1 Apr 2021 15:44:08 +0200
Mauro Carvalho Chehab wrote:
> Em Wed, 17 Feb 2021 10:34:34 +0200
> Alexandru Ardelean escreveu:
>
> > Since the new change to the IIO buffer infrastructure, the buffer/ and
> > scan_elements/ directories have been merged into bufferY/ to have some
> > attribut
The file name: Documentation/ABI/testing/sysfs-platform_profile.rst
should be, instead: Documentation/userspace-api/sysfs-platform_profile.rst.
Update its cross-reference accordingly.
Fixes: a2ff95e018f1 ("ACPI: platform: Add platform profile support")
Fixes: 8e0cbf356377 ("Documentation: Add doc
Hi,
On 4/1/21 2:17 PM, Mauro Carvalho Chehab wrote:
> The file name: Documentation/ABI/testing/sysfs-platform_profile.rst
> should be, instead: Documentation/userspace-api/sysfs-platform_profile.rst.
>
> Update its cross-reference accordingly.
>
> Fixes: a2ff95e018f1 ("ACPI: platform: Add platfo
Change other related documentation file names from .txt to .rst
and be more explicit about their paths/locations.
Signed-off-by: Randy Dunlap
Cc: Dmitry Torokhov
Cc: linux-in...@vger.kernel.org
Cc: Jonathan Corbet
Cc: linux-...@vger.kernel.org
Cc: Johann Deneux
Cc: Anssi Hannula
---
where is
On Thu, 18 Feb 2021 12:19:48 +
Jonathan Cameron wrote:
> On Wed, 17 Feb 2021 10:34:34 +0200
> Alexandru Ardelean wrote:
>
> > Since the new change to the IIO buffer infrastructure, the buffer/ and
> > scan_elements/ directories have been merged into bufferY/ to have some
> > attributes avai
On Wed, 17 Feb 2021 10:34:34 +0200
Alexandru Ardelean wrote:
> Since the new change to the IIO buffer infrastructure, the buffer/ and
> scan_elements/ directories have been merged into bufferY/ to have some
> attributes available per-buffer.
>
> This change updates the ABI docs to reflect this c
Since the new change to the IIO buffer infrastructure, the buffer/ and
scan_elements/ directories have been merged into bufferY/ to have some
attributes available per-buffer.
This change updates the ABI docs to reflect this change.
The hwfifo attributes are not updated, as for now these should be
Change other related documentation file names from .txt to .rst
and be more explicit about their paths/locations.
Signed-off-by: Randy Dunlap
Cc: Dmitry Torokhov
Cc: linux-in...@vger.kernel.org
---
where is fftest mentioned here found? I only found one place:
https://github.com/flosse/linuxcon
On 08/12/20 05:34, Zenghui Yu wrote:
Update various words, including the wrong parameter name and the vague
description of the usage of "slot" field.
Signed-off-by: Zenghui Yu
---
Documentation/virt/kvm/api.rst | 16 +++-
1 file changed, 7 insertions(+), 9 deletions(-)
diff --gi
Update various words, including the wrong parameter name and the vague
description of the usage of "slot" field.
Signed-off-by: Zenghui Yu
---
Documentation/virt/kvm/api.rst | 16 +++-
1 file changed, 7 insertions(+), 9 deletions(-)
diff --git a/Documentation/virt/kvm/api.rst b/Docu
Update the documentation to mention that a SIGBUS will be sent
to tasks that opt-into L1D flushing and execute on non-SMT cores.
Signed-off-by: Balbir Singh
---
To be applied on top of tip commit id
767d46ab566dd489733666efe48732d523c8c332
Documentation/admin-guide/hw-vuln/l1d_flush.rst | 8 +++
Should be squashed into 66570e966dd9cb4f.
Signed-off-by: Peter Xu
---
Documentation/virt/kvm/api.rst | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/Documentation/virt/kvm/api.rst b/Documentation/virt/kvm/api.rst
index 094e128634d2..f78307e77371 100644
--- a/Documentation/v
It should be an accident when rebase, since we've already have section
8.25 (which is KVM_CAP_S390_DIAG318). Fix the number.
Should be squashed into 1a155254ff937ac92cf9940d.
Signed-off-by: Peter Xu
---
Documentation/virt/kvm/api.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
It should be an accident when rebase, since we've already have section
8.25 (which is KVM_CAP_S390_DIAG318). Fix the number.
Signed-off-by: Peter Xu
---
Documentation/virt/kvm/api.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/virt/kvm/api.rst b/Documentat
It should be an accident when rebase, since we've already have section
8.25 (which is KVM_CAP_S390_DIAG318). Fix the number.
Signed-off-by: Peter Xu
---
Documentation/virt/kvm/api.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/virt/kvm/api.rst b/Documentat
Documentation references Samsung S3C24xx and S3C64xx machine files in
multiple places but the files were traveling around the kernel multiple
times.
Signed-off-by: Krzysztof Kozlowski
---
.../admin-guide/kernel-parameters.txt | 2 +-
Documentation/arm/samsung-s3c24xx/gpio.rst| 4 ++
On Wed, Jul 8, 2020 at 12:10 PM Jonathan Corbet wrote:
>
> Either is fine with me; I can add the Fixes: tag. If you want it in
> 5.8-rc, it's maybe best if you just take it directly; I don't have another
> 5.8 pull in the works at the moment.
I took that as an ack, and applied it.
On Wed, 8 Jul 2020 12:05:16 -0700
Linus Torvalds wrote:
> On Wed, Jul 8, 2020 at 12:04 PM Randy Dunlap wrote:
> >
> > Should I resend it?
>
> Nah. I'm just wondering if I should apply it directly or let it go through
> Jon.
Either is fine with me; I can add the Fixes: tag. If you want it i
On Wed, Jul 8, 2020 at 12:04 PM Randy Dunlap wrote:
>
> Should I resend it?
Nah. I'm just wondering if I should apply it directly or let it go through Jon.
Linus
On 7/8/20 11:57 AM, Linus Torvalds wrote:
> On Wed, Jul 8, 2020 at 11:45 AM Randy Dunlap wrote:
>> - - Make sure you have at least gcc 4.6 available.
>> + - Make sure you have at least gcc 4.9 available.
>> -GNU C 4.8 gcc --version
>> +GNU C 4.9
On Wed, Jul 8, 2020 at 11:45 AM Randy Dunlap wrote:
> - - Make sure you have at least gcc 4.6 available.
> + - Make sure you have at least gcc 4.9 available.
> -GNU C 4.8 gcc --version
> +GNU C 4.9 gcc --version
Heh. The docs clearly wer
From: Randy Dunlap
Update Documentation for the gcc v4.9 upgrade requirement.
Fixes: 6ec4476ac825 ("Raise gcc version requirement to 4.9")
Signed-off-by: Randy Dunlap
---
Documentation/admin-guide/README.rst |2 +-
Documentation/process/changes.rst|2 +-
2 files changed, 2 insertio
On Thu, 18 Jun 2020 00:57:03 +0530
Souptick Joarder wrote:
> Now there are 5 cases. Updated the same.
>
> Signed-off-by: Souptick Joarder
> Cc: John Hubbard
> ---
> Documentation/core-api/pin_user_pages.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentatio
On 2020-06-17 12:27, Souptick Joarder wrote:
Now there are 5 cases. Updated the same.
Signed-off-by: Souptick Joarder
Cc: John Hubbard
---
Documentation/core-api/pin_user_pages.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/core-api/pin_user_pages.rst
Now there are 5 cases. Updated the same.
Signed-off-by: Souptick Joarder
Cc: John Hubbard
---
Documentation/core-api/pin_user_pages.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/core-api/pin_user_pages.rst
b/Documentation/core-api/pin_user_pages.rst
inde
On Thu, 7 May 2020 14:02:17 +0200
Vlastimil Babka wrote:
> During recent patch discussion [1] it became apparent that the "other_node"
> definition in the numastat documentation has always been different from actual
> implementation. It was also noted that the stats can be innacurate on systems
From: ChangJoon Lee
Hi, ALSA Teams,
This is documentation update purpose patch.
This patch does NOT alter any of operations.
This patch allows an application engineer to understand why they received
negative return
such as -EIO, -EBADFD, -ENOSYS, -ESTRPIPE and etc which are not fully
From: ChangJoon Lee
Hi, ALSA Teams,
This is documentation update purpose patch.
This patch does NOT alter any of operations.
This patch allows an application engineer to understand why they received
negative return
such as -EIO, -EBADFD, -ENOSYS, -ESTRPIPE and etc which are not fully
On Thu, 14 May 2020 11:20:59 +0200,
Takashi Iwai wrote:
>
> On Thu, 14 May 2020 11:07:15 +0200,
> changjoon@lge.com wrote:
> >
> > From: ChangJoon Lee
> >
> > Hi, ALSA Teams,
> >
> > This is documentation update purpose patch.
> > This pa
On Thu, 14 May 2020 11:07:15 +0200,
changjoon@lge.com wrote:
>
> From: ChangJoon Lee
>
> Hi, ALSA Teams,
>
> This is documentation update purpose patch.
> This patch does NOT alter any of operations.
>
> This patch allows an application engineer to understand wh
From: ChangJoon Lee
Hi, ALSA Teams,
This is documentation update purpose patch.
This patch does NOT alter any of operations.
This patch allows an application engineer to understand why they received
negative return
such as -EIO, -EBADFD, -ENOSYS, -ESTRPIPE and etc which are not fully
From: ChangJoon Lee
Signed-off-by: ChangJoon Lee
---
src/pcm/pcm.c | 57 ---
1 file changed, 54 insertions(+), 3 deletions(-)
diff --git a/src/pcm/pcm.c b/src/pcm/pcm.c
index 1064044c..b53797a6 100644
--- a/src/pcm/pcm.c
+++ b/src/pcm/pcm.c
@@ -8
On Thu, 14 May 2020 04:47:08 +0200,
CJ Lee wrote:
>
> Dear Tiwai san,
>
> First of all, thank you very much all those years you contributed on ALSA.
>
> Couple of days ago I emailed you over updating remark fields.
> The purpose of edit was providing more error and meaning to application
> engi
Dear Tiwai san,
First of all, thank you very much all those years you contributed on ALSA.
Couple of days ago I emailed you over updating remark fields.
The purpose of edit was providing more error and meaning to application
engineers.
For example, when snd_pcm_writei returned -EIO, application
From: ChangJoon Lee
ChangJoon Lee (1):
Updated negative return values for documentation update.
src/pcm/pcm.c | 57 ---
1 file changed, 54 insertions(+), 3 deletions(-)
--
2.26.2
From: ChangJoon Lee
Signed-off-by: ChangJoon Lee
---
src/pcm/pcm.c | 57 ---
1 file changed, 54 insertions(+), 3 deletions(-)
diff --git a/src/pcm/pcm.c b/src/pcm/pcm.c
index 1064044c..b53797a6 100644
--- a/src/pcm/pcm.c
+++ b/src/pcm/pcm.c
@@ -8
On Thu 07-05-20 14:02:17, Vlastimil Babka wrote:
> During recent patch discussion [1] it became apparent that the "other_node"
> definition in the numastat documentation has always been different from actual
> implementation. It was also noted that the stats can be innacurate on systems
> with memo
On 07/05/20 5:32 pm, Vlastimil Babka wrote:
> During recent patch discussion [1] it became apparent that the "other_node"
> definition in the numastat documentation has always been different from actual
> implementation. It was also noted that the stats can be innacurate on systems
> with memoryl
During recent patch discussion [1] it became apparent that the "other_node"
definition in the numastat documentation has always been different from actual
implementation. It was also noted that the stats can be innacurate on systems
with memoryless nodes.
This patch corrects the other_node definit
On Sat, Oct 12, 2019 at 07:49:53AM +0200, Manfred Spraul wrote:
> 1) wake_q_add() contains a memory barrier, and callers such as
> ipc/mqueue.c rely on this barrier.
> Unfortunately, this is documented in ipc/mqueue.c, and not in the
> description of wake_q_add().
> Therefore: Update the documentat
On Sat, 12 Oct 2019, Manfred Spraul wrote:
1) wake_q_add() contains a memory barrier, and callers such as
ipc/mqueue.c rely on this barrier.
Unfortunately, this is documented in ipc/mqueue.c, and not in the
description of wake_q_add().
Therefore: Update the documentation.
Removing/updating ipc/m
1) wake_q_add() contains a memory barrier, and callers such as
ipc/mqueue.c rely on this barrier.
Unfortunately, this is documented in ipc/mqueue.c, and not in the
description of wake_q_add().
Therefore: Update the documentation.
Removing/updating ipc/mqueue.c will happen with the next patch in the
1) wake_q_add() contains a memory barrier, and callers such as
ipc/mqueue.c rely on this barrier.
Unfortunately, this is documented in ipc/mqueue.c, and not in the
description of wake_q_add().
Therefore: Update the documentation.
Removing/updating ipc/mqueue.c will happen with the next patch in the
On 2019-10-03, Jonathan Corbet wrote:
> [Expanding CC a bit; this is the sort of change I'm reluctant to take
> without being sure it reflects what the community thinks.]
>
> On Wed, 2 Oct 2019 17:14:37 +0200
> Christian Brauner wrote:
>
> > Add additional information on how to ensure that sys
We've introduced new (somewhat subtle) behaviour regarding trailing
magic-links, so it's best to make sure everyone can follow along with
the reasoning behind trailing_magiclink().
Signed-off-by: Aleksa Sarai
---
Documentation/filesystems/path-lookup.rst | 80 ++-
1 file chan
On 19/08/2019 17:12:19+0200, Nicolas Ferre wrote:
> Update SAMA5D3 and SAM E70/S70/V70/V71 Family SoC Datasheets. URL are
> updated in Microchip documentation.
>
> Signed-off-by: Nicolas Ferre
> ---
> Documentation/arm/microchip.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
Update SAMA5D3 and SAM E70/S70/V70/V71 Family SoC Datasheets. URL are
updated in Microchip documentation.
Signed-off-by: Nicolas Ferre
---
Documentation/arm/microchip.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/arm/microchip.rst b/Documentation/arm/m
Hello
After some off line conversations with the LED maintainers I update the
documentation for the multicolor framework with what I hope to be a good
compromise.
I have add the "color_mix" (name is not set but could not think of a better one)
file for writing the monochrome LEDs as a group. Als
From: Martin Cracauer
Adds documentation about the write protection support.
Signed-off-by: Martin Cracauer
Signed-off-by: Andrea Arcangeli
[peterx: rewrite in rst format; fixups here and there]
Reviewed-by: Jerome Glisse
Reviewed-by: Mike Rapoport
Signed-off-by: Peter Xu
---
Documentation
From: Joao Moreira
Add a section to Documentation/livepatch/module-elf-format.txt
describing how klp-convert works for fixing relocations.
Signed-off-by: Joao Moreira
Signed-off-by: Joe Lawrence
---
Documentation/livepatch/livepatch.txt | 3 ++
Documentation/livepatch/module-elf-form
From: Martin Cracauer
Adds documentation about the write protection support.
Signed-off-by: Martin Cracauer
Signed-off-by: Andrea Arcangeli
[peterx: rewrite in rst format; fixups here and there]
Reviewed-by: Jerome Glisse
Reviewed-by: Mike Rapoport
Signed-off-by: Peter Xu
---
Documentation
From: Joao Moreira
Add a section to Documentation/livepatch/module-elf-format.txt
describing how klp-convert works for fixing relocations.
Signed-off-by: Joao Moreira
Signed-off-by: Joe Lawrence
---
Documentation/livepatch/livepatch.txt | 3 ++
Documentation/livepatch/module-elf-form
On Tue, 26 Feb 2019, Denis Efremov wrote:
> Recent "New LSM Hooks" discussion has led me to the
> thought that it might be a good idea to slightly
> update the current documentation. The patchset adds
> nothing new to the documentation, only fixes the old
> description of hooks to reflect their cu
On Wed, Mar 20, 2019 at 10:06:38AM +0800, Peter Xu wrote:
> From: Martin Cracauer
>
> Adds documentation about the write protection support.
>
> Signed-off-by: Martin Cracauer
> Signed-off-by: Andrea Arcangeli
> [peterx: rewrite in rst format; fixups here and there]
> Reviewed-by: Jerome Gliss
> > +building system, the second is done by a tool called klp-convert, which
> > can be
> > +found in "scripts/livepatch".
> > +
> > +When an unresolved relocation has as target a symbol whose name is also
> > used by
> > +different symbols throughout the kernel, the relocation cannot be resolv
From: Martin Cracauer
Adds documentation about the write protection support.
Signed-off-by: Martin Cracauer
Signed-off-by: Andrea Arcangeli
[peterx: rewrite in rst format; fixups here and there]
Reviewed-by: Jerome Glisse
Signed-off-by: Peter Xu
---
Documentation/admin-guide/mm/userfaultfd.
On Fri, Mar 01, 2019 at 11:13:13AM -0300, Joao Moreira wrote:
> Add a section to Documentation/livepatch/module-elf-format.txt
> describing how klp-convert works for fixing relocations.
>
> Signed-off-by: Joao Moreira
> ---
> Documentation/livepatch/module-elf-format.txt | 47
>
On Wed, Feb 27, 2019 at 7:10 AM Denis Efremov wrote:
> The rest of the warnings are about undocumented hooks. This patchset
> fixes the existing documentation. I will try to document the hooks from
> warnings in a separate patch. Some of the hooks are trivial enough, but
> others require me diggin
The rest of the warnings are about undocumented hooks. This patchset
fixes the existing documentation. I will try to document the hooks from
warnings in a separate patch. Some of the hooks are trivial enough, but
others require me digging into the code and mailing lists. Can't promise
to do it quic
On Tue, Feb 26, 2019 at 12:49 PM Denis Efremov wrote:
> Recent "New LSM Hooks" discussion has led me to the
> thought that it might be a good idea to slightly
> update the current documentation. The patchset adds
> nothing new to the documentation, only fixes the old
> description of hooks to refl
On 2/26/2019 12:49 PM, Denis Efremov wrote:
Recent "New LSM Hooks" discussion has led me to the
thought that it might be a good idea to slightly
update the current documentation. The patchset adds
nothing new to the documentation, only fixes the old
description of hooks to reflect their current s
Recent "New LSM Hooks" discussion has led me to the
thought that it might be a good idea to slightly
update the current documentation. The patchset adds
nothing new to the documentation, only fixes the old
description of hooks to reflect their current state.
V2 adds the clarification on arguments
On Tue, Feb 26, 2019 at 09:04:25AM +0200, Mike Rapoport wrote:
> On Tue, Feb 26, 2019 at 02:53:42PM +0800, Peter Xu wrote:
> > On Mon, Feb 25, 2019 at 11:19:32PM +0200, Mike Rapoport wrote:
> > > On Tue, Feb 12, 2019 at 10:56:30AM +0800, Peter Xu wrote:
> > > > From: Martin Cracauer
> > > >
> > >
On Tue, Feb 26, 2019 at 02:53:42PM +0800, Peter Xu wrote:
> On Mon, Feb 25, 2019 at 11:19:32PM +0200, Mike Rapoport wrote:
> > On Tue, Feb 12, 2019 at 10:56:30AM +0800, Peter Xu wrote:
> > > From: Martin Cracauer
> > >
> > > Adds documentation about the write protection support.
> > >
> > > Sign
On Mon, Feb 25, 2019 at 11:19:32PM +0200, Mike Rapoport wrote:
> On Tue, Feb 12, 2019 at 10:56:30AM +0800, Peter Xu wrote:
> > From: Martin Cracauer
> >
> > Adds documentation about the write protection support.
> >
> > Signed-off-by: Andrea Arcangeli
> > [peterx: rewrite in rst format; fixups
On Tue, Feb 12, 2019 at 10:56:30AM +0800, Peter Xu wrote:
> From: Martin Cracauer
>
> Adds documentation about the write protection support.
>
> Signed-off-by: Andrea Arcangeli
> [peterx: rewrite in rst format; fixups here and there]
> Signed-off-by: Peter Xu
Reviewed-by: Mike Rapoport
Pete
On Tue, Feb 12, 2019 at 10:56:30AM +0800, Peter Xu wrote:
> From: Martin Cracauer
>
> Adds documentation about the write protection support.
>
> Signed-off-by: Andrea Arcangeli
> [peterx: rewrite in rst format; fixups here and there]
> Signed-off-by: Peter Xu
Reviewed-by: Jérôme Glisse
> --
ernel. Most of the fixes are pretty
> obvious and can be checked by comparing an lsm hook declaration and
> its description in the LSM comment from lsm_hooks.h I tried to be
> exhaustive in the commits description and in every case to reference
> the original commit where the interface
n every case to reference
the original commit where the interface was changed without
documentation update.
Denis Efremov (10):
security: fix documentation for the sb_copy_data hook
security: fix documentation for the syslog hook
security: fix documentation for the socket_post_create hook
From: Martin Cracauer
Adds documentation about the write protection support.
Signed-off-by: Andrea Arcangeli
[peterx: rewrite in rst format; fixups here and there]
Signed-off-by: Peter Xu
---
Documentation/admin-guide/mm/userfaultfd.rst | 51
1 file changed, 51 insertions
On Thu, Feb 7, 2019 at 4:45 AM Denis Efremov wrote:
>
> Recent "New LSM Hooks" discussion has led me to the
> thought that it might be a good idea to slightly
> update the current documentation. The patchset adds
> nothing new to the documentation, only fixes the old
> description of hooks to refl
Recent "New LSM Hooks" discussion has led me to the
thought that it might be a good idea to slightly
update the current documentation. The patchset adds
nothing new to the documentation, only fixes the old
description of hooks to reflect their current state.
Denis Efremov (10):
security: fix doc
From: Martin Cracauer
Adds documentation about the write protection support.
Signed-off-by: Andrea Arcangeli
[peterx: rewrite in rst format; fixups here and there]
Signed-off-by: Peter Xu
---
Documentation/admin-guide/mm/userfaultfd.rst | 51
1 file changed, 51 insertions
From: Rafael J. Wysocki
Update the MAINTAINERS entry for cpuidle by making it clear that it
is not just drivers and adding a documentation record to it.
Signed-off-by: Rafael J. Wysocki
---
MAINTAINERS |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
Index: linux-pm/MAINTAINERS
On 02-01-19, 12:13, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> Update the MAINTAINERS entry for cpufreq by making it clear that it
> is not just drivers and adding current documentation records to it.
>
> Signed-off-by: Rafael J. Wysocki
> ---
> MAINTAINERS |4 +++-
> 1 file ch
From: Rafael J. Wysocki
Update the MAINTAINERS entry for cpufreq by making it clear that it
is not just drivers and adding current documentation records to it.
Signed-off-by: Rafael J. Wysocki
---
MAINTAINERS |4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
Index: linux-pm/MAINTAIN
Commit-ID: 7696f9910a9a40b8a952f57d3428515fabd2d889
Gitweb: https://git.kernel.org/tip/7696f9910a9a40b8a952f57d3428515fabd2d889
Author: Andrea Parri
AuthorDate: Mon, 16 Jul 2018 11:06:03 -0700
Committer: Ingo Molnar
CommitDate: Tue, 17 Jul 2018 09:30:34 +0200
sched/Documentation
The firmware loader has a fallback mechanism, and it now has some proper
kdoc, but we forgot to update the Documentation to use the new kdoc. Fix
that.
Signed-off-by: Luis R. Rodriguez
---
Documentation/driver-api/firmware/fallback-mechanisms.rst | 7 ++-
1 file changed, 6 insertions(+), 1 d
On Wed, 16 May 2018 13:18:23 -0600
Jonathan Corbet wrote:
> On Mon, 14 May 2018 12:19:59 -0500
> Kim Phillips wrote:
>
> > - Align and show updated ls devices output from the TC2, based on
> > current driver
> >
> > - Provide an example from an ETMv4 based system (Juno)
> >
> > - Reflect ch
On Mon, 14 May 2018 12:19:59 -0500
Kim Phillips wrote:
> - Align and show updated ls devices output from the TC2, based on
> current driver
>
> - Provide an example from an ETMv4 based system (Juno)
>
> - Reflect changes to the way the RAM write pointer is accessed since
> it got changed in
On 14 May 2018 at 13:18, Kim Phillips wrote:
> - Align and show updated ls devices output from the TC2, based on
> current driver
>
> - Provide an example from an ETMv4 based system (Juno)
>
> - Reflect changes to the way the RAM write pointer is accessed since
> it got changed in commit 7d83d
On 05/14/2018 12:18 PM, Kim Phillips wrote:
> - Align and show updated ls devices output from the TC2, based on
> current driver
>
> - Provide an example from an ETMv4 based system (Juno)
>
> - Reflect changes to the way the RAM write pointer is accessed since
> it got changed in commit 7d83d
- Align and show updated ls devices output from the TC2, based on
current driver
- Provide an example from an ETMv4 based system (Juno)
- Reflect changes to the way the RAM write pointer is accessed since
it got changed in commit 7d83d17795ef ("coresight: tmc: adding sysFS
management entrie
On 05/14/2018 10:19 AM, Kim Phillips wrote:
> - Align and show updated ls devices output from the TC2, based on
> current driver
>
> - Provide an example from an ETMv4 based system (Juno)
>
> - Reflect changes to the way the RAM write pointer is accessed since
> it got changed in commit 7d83d
- Align and show updated ls devices output from the TC2, based on
current driver
- Provide an example from an ETMv4 based system (Juno)
- Reflect changes to the way the RAM write pointer is accessed since
it got changed in commit 7d83d17795ef ("coresight: tmc: adding sysFS
management entrie
On 7 May 2018 at 16:29, Kim Phillips wrote:
> - Align and show updated ls devices output from the TC2, based on
> current driver
>
> - Provide an example from an ETMv4 based system (Juno)
>
> - Reflect changes to the way the RAM write pointer is accessed since
> it got changed in commit 7d83d1
- Align and show updated ls devices output from the TC2, based on
current driver
- Provide an example from an ETMv4 based system (Juno)
- Reflect changes to the way the RAM write pointer is accessed since
it got changed in commit 7d83d17795ef ("coresight: tmc: adding sysFS
management entrie
2018-03-01 6:47 GMT+09:00 Randy Dunlap :
> On 02/28/2018 01:32 PM, Arvind Prasanna wrote:
>> The package name is ncurses-devel for Redhat based distros
>> and libncurses-dev for Debian based distros.
>>
>> Signed-off-by: Arvind Prasanna
>
> Thanks. Looks good to me.
>
> Acked-by: Randy Dunlap
>
On 02/28/2018 01:32 PM, Arvind Prasanna wrote:
> The package name is ncurses-devel for Redhat based distros
> and libncurses-dev for Debian based distros.
>
> Signed-off-by: Arvind Prasanna
Thanks. Looks good to me.
Acked-by: Randy Dunlap
> ---
>
> Changes in v3:
> - Fix a package name in t
The package name is ncurses-devel for Redhat based distros
and libncurses-dev for Debian based distros.
Signed-off-by: Arvind Prasanna
---
Changes in v3:
- Fix a package name in the commit message.
Changes in v2:
- Add a missing echo as pointed out by one of the reviewers.
scripts/kconfig/lxd
Hi,
I think that you are missing my point, so let me start over and try to
clarify it.
In the patch description, it says "libncurses-devel" (not libncurses-dev).
In the patch itself, it says libncurses-dev (not libncurses-devel).
I suspect that one of these is incorrect. Which one is it?
Than
On 02/28/2018 09:39 AM, Arvind Prasanna wrote:
> Hi Randy:
>
> On 02/27/2018 10:59 PM, Arvind Prasanna wrote:
>> The package name is ncurses-devel for Redhat based distros
>> and libncurses-devel for Debian based distros.
>
> The above lines are part of the commit message and the patch says to in
1 - 100 of 510 matches
Mail list logo
