On Wed, 20 Feb 2019 23:46:09 +0100
Federico Vaga wrote:
> The patches fixes some typos in process/license-rules.rst
>
> Signed-off-by: Federico Vaga
Applied, thanks.
jon
On Wed, 20 Feb 2019 20:02:33 -0800
Randy Dunlap wrote:
> From: Randy Dunlap
>
> Fix minimum gcc version as specified in Documentation/process/changes.rst.
>
> Suggested-by: Matthew Wilcox
> Signed-off-by: Randy Dunlap
> ---
> Documentation/admin-guide/README.rst |2 +-
> 1 file changed,
On Thu, 21 Feb 2019 21:29:59 +0100
Federico Vaga wrote:
> Synchonise translations: CN, IT, JP, KR
>
> commit 2c71d305caf9 ("docs: process: Remove outdated info about -git patches")
>
> I can guarantee for the Italian translations, but since we are removing
> an entire chapter I think I did it r
On Thu, 21 Feb 2019 12:02:28 -0700
Jonathan Corbet wrote:
> Al Viro's recent "braindump" on how struct file refcounting works is too
> good to lose, so let's capture it in Documentation/. There are two changes
> here:
>
> - Clean up the filesystem book, move
Work up some text posted by Al and add it to the filesystem manual.
Co-developed-by: Al Viro
Signed-off-by: Jonathan Corbet
---
Documentation/filesystems/index.rst | 1 +
Documentation/filesystems/lifecycles.rst | 357 +++
2 files changed, 358 insertions(+)
create
s all just moving stuff around.
Signed-off-by: Jonathan Corbet
---
Documentation/filesystems/api-summary.rst | 150
Documentation/filesystems/index.rst | 394 ++
Documentation/filesystems/journalling.rst | 184 ++
Documentation/filesystems/path-looku
nges other than some connecting
text.
- Bring in Al's text, with a fair amount of language tweaking and later
corrections applied.
Hopefully this is just the beginning.
Jonathan Corbet (2):
docs: Bring some order to filesystem documentation
docs: Add struct file refcounting and SCM_RIGHTS
The following changes since commit
bfeffd155283772bbe78c6a05dec7c0128ee500c:
Linux 5.0-rc1 (2019-01-06 17:08:20 -0800)
are available in the Git repository at:
git://git.lwn.net/linux.git tags/docs-5.0-fix
for you to fetch changes up to 0358affb5cd8bbd685a6ab163a36dd28a818da73:
Documentat
On Mon, 11 Feb 2019 16:32:33 +0300
Alexey Budankov wrote:
> The patch set extends the first version of perf-security.rst documentation
> file [1], [2], [3] with the following topics:
>
> 1) perf_events/Perf resource limits and control management that describes
>RLIMIT_NOFILE and perf_event_m
On Fri, 15 Feb 2019 08:29:48 +0100
Nicholas Mc Guire wrote:
> The common cases of attributes wrappers should probably be using the
> __ATTR_XXX macros to make code more concise and readable but the current
> sysfs.txt does not point developers to those convenience macros. Further
> there is no no
On Tue, 12 Feb 2019 15:41:01 +0100
Arnd Bergmann wrote:
> As linux-5.0.x is coming up soon, the documentation should match,
> in particular the README.rst file, so change all 4.x references
> accordingly. There was a mix of lowercase and uppercase X here,
> which I changed to using lowercase cons
On Mon, 11 Feb 2019 14:38:04 -0800
frowand.l...@gmail.com wrote:
> From: Frank Rowand
>
> "If no *function* if specified" should instead be
> "If no *function* is specified".
>
> Reported-by: Matthew Wilcox
> Signed-off-by: Frank Rowand
Applied, thanks.
jon
On Fri, 8 Feb 2019 16:30:38 +0100
Federico Vaga wrote:
> It clarifies that the DMA description pointer returned by
> `dmaengine_prep_*` function should not be used after submission.
>
> Signed-off-by: Federico Vaga
> ---
> Documentation/driver-api/dmaengine/client.rst | 7 +++
> 1 file cha
On Thu, 7 Feb 2019 15:15:42 -0500
Waiman Long wrote:
> Fix a grammatical error in the dentry-state text and clarify the usage
> of negative dentries.
>
> Fixes: af0c9af1b3f66 ("fs/dcache: Track & report number of negative dentries")
Linus, perhaps you'd like to take this one directly? It seem
On Sun, 10 Feb 2019 18:12:59 +0100
Jonathan Neuschäfer wrote:
> As can be seen by clicking around the timeline on web.archive.org[1],
> there were no -git patches/tarballs on kernel.org since release 3.1.
>
> [1]: https://web.archive.org/web/2003073843/http://www.kernel.org/
>
> Signed-off-
On Mon, 11 Feb 2019 13:31:58 +0200
Andy Shevchenko wrote:
> > From: Randy Dunlap
> >
> > Fix markup warnings by inserting blank lines.
> > Also correct one typo.
> >
> > Documentation/laptops/lg-laptop.rst:2: WARNING: Explicit markup ends
> > without a blank line; unexpected unindent.
> > Docum
On Sun, 10 Feb 2019 22:34:11 -0800
Randy Dunlap wrote:
> From: Randy Dunlap
>
> Fix markup warning by quoting the '*' character with a backslash.
>
> Documentation/vm/slub.rst:71: WARNING: Inline emphasis start-string without
> end-string.
>
> Signed-off-by: Randy Dunlap
> Cc: Christoph Lam
On Mon, 11 Feb 2019 14:43:23 +0100
Christoph Hellwig wrote:
> AFAIK we never had a isa_virt_to_phys, it always was
> isa_virt_to_bus.
>
> Signed-off-by: Christoph Hellwig
> ---
> Documentation/DMA-ISA-LPC.txt | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documen
On Sun, 10 Feb 2019 19:58:11 +0100 (CET)
Thomas Gleixner wrote:
> On Sat, 9 Feb 2019, Philippe Ombredanne wrote:
> > > + * Both "GPL v2" and "GPL" (the latter also in dual licensed strings) are
> > > + * merily stating that the module is licensed under the GPL v2, but are
> > > not
> >
> > Ni
On Mon, 4 Feb 2019 16:29:31 -0800
Frank Rowand wrote:
> On 2/2/19 12:56 PM, Matthew Wilcox wrote:
> > On Fri, Feb 01, 2019 at 02:04:16PM -0800, frowand.l...@gmail.com wrote:
> >>Include documentation for each *function* in *source*.
> >> - If no *function* if specified, the documentaion fo
On Fri, 08 Feb 2019 14:40:28 +1100
Michael Ellerman wrote:
> > - I don't think this should be a top-level directory full of docs; the top
> > level is already rather overpopulated. At worst, we should create an
> > arch/ directory for architecture-specific docs.
>
> We currently have arch
On Fri, 8 Feb 2019 13:35:39 -0200
Shayenne Moura wrote:
> Remove KMS cleanup task from documentation solved by patchset
> https://patchwork.freedesktop.org/series/54310/
>
> Signed-off-by: Shayenne Moura
This seems like a worthy change, but Documentation/gpu is managed by the
DRM maintainers.
On Thu, 7 Feb 2019 17:03:15 +1100
"Tobin C. Harding" wrote:
> As discussed at LCA here is the start to the docs conversion for PowerPC
> to RST.
>
> This applies cleanly on top of the mainline (5.20-rc5) and Jon's tree
> (docs-next branch).
>
> I'm guessing it should go in through the PowerPC
On Mon, 21 Jan 2019 11:17:21 +
Quentin Perret wrote:
> The recently introduced Energy Aware Scheduling (EAS) feature relies on
> a large set of concepts, assumptions, and design choices that are
> probably not obvious for an outsider. Moreover, enabling EAS on a
> particular platform isn't st
On Fri, 25 Jan 2019 12:07:00 -0600
Jeremy Linton wrote:
> For a while Arm64 has been capable of force enabling
> or disabling the kpti mitigations. Lets make sure the
> documentation reflects that.
>
> Signed-off-by: Jeremy Linton
> Cc: Jonathan Corbet
> Cc: linux-...@
On Mon, 4 Feb 2019 22:30:47 +0100
Federico Vaga wrote:
> This patch adds the Italian translation for the following documents
> in Documentation/process:
>
> - applying-patches
> - submit-checklist
> - submitting-drivers
> - changes
> - stable api nonsense
>
> Signed-off-by: Federico Vaga
App
On Wed, 23 Jan 2019 21:22:55 +0100
Federico Vaga wrote:
> This patch translates in Italian the content of the following patch
>
> 7967656ffbfa coding-style: Clarify the expectations around bool
>
> Signed-off-by: Federico Vaga
Applied, thanks.
jon
On Tue, 29 Jan 2019 15:11:40 +0100 (CET)
Thomas Gleixner wrote:
> On Tue, 29 Jan 2019, Jessica Yu wrote:
> > +++ Thomas Gleixner [28/01/19 23:38 +0100]:
> > > +"GPL" Module is licensed under GPL version
> > > 2. This
> > > + does not expre
On Wed, 06 Feb 2019 23:55:38 +0100
Federico Vaga wrote:
> I am having a look at this document and I am wandering if this is an
> useful
> document? Clearly I see value in the table with all requirements
> summarised,
> but I do not see it for the rest of the document.
>
> So, I propose to actu
On Fri, 1 Feb 2019 10:30:58 +0300
Alexey Budankov wrote:
> Elaborate on possible perf_event/Perf privileged users groups
> and document steps about creating such groups.
>
> Signed-off-by: Alexey Budankov
> ---
> Documentation/admin-guide/perf-security.rst | 43 +
> 1 file
On Fri, 1 Feb 2019 10:29:11 +0300
Alexey Budankov wrote:
> Extend perf-security.rst file with perf_events/Perf resource control
> section describing RLIMIT_NOFILE and perf_event_mlock_kb settings for
> performance monitoring user processes.
>
> Signed-off-by: Alexey Budankov
Overall these patc
On Sun, 3 Feb 2019 21:00:19 +0100
Otto Sabart wrote:
> Legacy IO schedulers (cfq, deadline and noop) were removed in
> f382fb0bcef4.
>
> The documentation for deadline was retained because it carries over to
> mq-deadline as well, but location of the doc file was changed over time.
>
> The old
On Mon, 4 Feb 2019 14:16:57 +0530
Kamalesh Babulal wrote:
> Fix the spelling of 'functionnality' -> 'functionality'.
>
> Signed-off-by: Kamalesh Babulal
Applied, thanks.
jon
On Tue, 22 Jan 2019 19:46:32 +0100
Greg Kroah-Hartman wrote:
> The networking maintainer keeps a public list of the patches being
> queued up for the next round of stable releases. Be sure to check there
> before asking for a patch to be applied so that you do not waste
> people's time.
>
> Sig
On Tue, 22 Jan 2019 10:34:08 +0100
Adam Borowski wrote:
> Drivers under MIT, BSD-17-clause, or uncle-Bob's-newest-take-on-PD are
> all fine, not just GPL.
>
> Signed-off-by: Adam Borowski
> ---
> Not reformatting to fill lines, it'll semi-conflict with another patch
> that's been acked but not
On Fri, 1 Feb 2019 09:52:52 -0700
Jason Gunthorpe wrote:
> Doc folks, what is the feedback on these patches? Should I take
> them through the rdma tree?
If you think they are ready (it seemed that there were still comments on
one of the patches?) I'll take them, just let me know.
Thanks,
jon (
On Wed, 30 Jan 2019 18:25:15 +0100
Jonathan Neuschäfer wrote:
> Recently, Free Electrons was renamed to Bootlin[1]. Less recently, the
> Linux Cross Reference (LXR) at lxr.free-electrons.com was replaced by
> Elixir[2], and lxr.free-electrons.com redirected first to
> elixir.free-electrons.com an
On Fri, 1 Feb 2019 14:04:16 -0800
frowand.l...@gmail.com wrote:
> Fix a typo in kernel-doc.rst
>
> Signed-off-by: Frank Rowand
Applied, thanks.
jon
On Fri, 1 Feb 2019 13:54:39 -0800
frowand.l...@gmail.com wrote:
> (1) The command to generate man pages is truncated in the pdf version
> of the document. Reformat the command into multiple lines to prevent
> the truncation.
>
> (2) Older versions of git do not support all variants of pathspec
On Wed, 30 Jan 2019 14:57:21 +0200
"Joel Nider" wrote:
> Have you had a chance to review this patchset?
I've been mostly away from the keyboard for the last week; will be back
and dealing with things soon.
Thanks,
jon
On Fri, 18 Jan 2019 13:38:22 +
Corentin Labbe wrote:
> This patch fixes two typos, a missing "e" and dma-api/driver_filter was
> incorrectly typed dma-api/driver-filter.
>
> Signed-off-by: Corentin Labbe
So I've applied this, but...
> Documentation/DMA-API.txt | 4 ++--
> 1 file changed,
On Fri, 18 Jan 2019 21:38:32 +0100
Otto Sabart wrote:
> Convert scaling document into reStructuredText and add reference to
> scaling document into main table of contents in network documentation.
>
> There are no semantic changes.
>
> There are no references to "scaling.txt" file. Whole kernel
On Sun, 20 Jan 2019 12:16:29 +0100
Federico Vaga wrote:
> Keep consistent the document. In the document, option references
> are always linked, except for the one I fixed with this patch
>
> Signed-off-by: Federico Vaga
Applied, thanks.
jon
On Fri, 18 Jan 2019 15:50:47 -0700
Jason Gunthorpe wrote:
> There has been some confusion since checkpatch started warning about bool
> use in structures, and people have been avoiding using it.
>
> Many people feel there is still a legitimate place for bool in structures,
> so provide some guid
On Sat, 19 Jan 2019 23:13:41 +0100
Federico Vaga wrote:
> This patch adds the Italian translation for the following documents
> in Documentation/process:
>
> - applying-patches
> - submit-checklist
> - submitting-drivers
> - changes
> - stable api nonsense
>
> Signed-off-by: Federico Vaga
In
On Sat, 19 Jan 2019 23:14:22 +0100
Federico Vaga wrote:
> It aligns the italian translation with the latest changes:
>
> ae67ee6c5e1d docs: fix Co-Developed-by docs
> 3fe5dbfef47e Documentation/process/coding-style.rst: don't use "extern" with
> function prototypes
>
> Signed-off-by: Federico
On Fri, 18 Jan 2019 22:58:04 +0100
Federico Vaga wrote:
> The link referred by the note can't be retrieved: this patch just
> remove that old note.
>
> Signed-off-by: Federico Vaga
> ---
> Documentation/process/stable-api-nonsense.rst | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
On Fri, 18 Jan 2019 16:45:04 -0800
Tony Jones wrote:
> On 1/17/19 1:45 AM, Seeteena Thoufeek wrote:
>
> > +if sys.version_info[0] < 3:
> > +import cPickle
> > +else:
> > +import _pickle as cPickle
>
> Do you really need this?
>
> pickle is already in Python2.
Did you mean in Python3
Commit-ID: 70921ae25f944423f0abf096f73455c586da0652
Gitweb: https://git.kernel.org/tip/70921ae25f944423f0abf096f73455c586da0652
Author: Jonathan Corbet
AuthorDate: Tue, 8 Jan 2019 17:04:32 -0700
Committer: Thomas Gleixner
CommitDate: Fri, 18 Jan 2019 00:18:45 +0100
genirq: Fix the
On Thu, 17 Jan 2019 23:14:08 +0100
Federico Vaga wrote:
> in this document
>
> Documentation/process/stable-api-nonsense.rst
>
> there is this note:
>
>
>
> Is it possible to get it fixed with the proper link? I searched for it
> without
> success. If that comment is impossible to find I w
n and make the warning go away.
Signed-off-by: Jonathan Corbet
---
Hopefully I've sent this to the right place; perhaps this file needs to be
added to the MAINTAINERS entry?
include/linux/dma-fence-array.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/linux/dma-fence-array.
On Wed, 9 Jan 2019 20:57:22 +0100
Otto Sabart wrote:
> Add markups which are necessary for successful conversion into
> reStructuredText.
>
> There are no semantic changes.
>
> Signed-off-by: Otto Sabart
This seems generally good, except:
> Documentation/networking/scaling.txt | 131 +++
On Wed, 16 Jan 2019 11:26:51 +0100
Thomas Gleixner wrote:
> Recent SPDX conversions introduced new wreckage:
>
> arch/sh/lib/ashiftrt.S: 1:42 Invalid Exception ID: GCC-exception-2.0
> ...
> arch/sh/include/mach-ecovec24/mach/partner-jet-setup.txt: 1:38 Invalid
> token: "
> ,,,
>
> The firs
On Wed, 16 Jan 2019 07:51:35 +0800
Yang Shi wrote:
> We don't do page cache reparent anymore when offlining memcg, so update
> force empty related content accordingly.
>
> Reviewed-by: Shakeel Butt
> Acked-by: Michal Hocko
> Cc: Johannes Weiner
> Signed-off-by: Yang Shi
> ---
> Documentatio
On Wed, 16 Jan 2019 21:53:36 +0530
Seeteena Thoufeek wrote:
> Support both Python 2 and Python 3 in mem-phys-addr.py. ``print`` is now a
> function rather than a statement. This should have no functional change.
>
> Fix lambda syntax error.
So, I just picked one of these at random
> Signed
On Tue, 15 Jan 2019 22:37:01 +0200
"Joel Nider" wrote:
> Jonathan Corbet wrote on 01/15/2019 08:08:54 PM:
> > The intent behind the user-space API manual is to document the user-space
> > API; it's meant to be read by people writing applications and such.
>
On Tue, 15 Jan 2019 18:29:59 +0200
"Joel Nider" wrote:
> > I think this is a horrible direction to take. The current document is
> > clearly for _users_. All this documentation you've added is for kernel
> > hackers. It needs to go in a different file, or not be added at all.
> >
> Hmm, tha
On Tue, 15 Jan 2019 08:14:02 -0700
Jason Gunthorpe wrote:
> > Move user_verbs from infiniband to userspace while changing the
> > format. Replace the existing Documentation/infiniband/user_verbs.txt
> > with Documentation/userspace-api/user_verbs.rst. No substantial changes
> > to the content - j
Commit-ID: f0ca26ca4f36dc781cc50c15ca63a5cf02d720dc
Gitweb: https://git.kernel.org/tip/f0ca26ca4f36dc781cc50c15ca63a5cf02d720dc
Author: Jonathan Corbet
AuthorDate: Tue, 8 Jan 2019 17:04:32 -0700
Committer: Thomas Gleixner
CommitDate: Tue, 15 Jan 2019 17:09:33 +0100
genirq: Fix the
On Mon, 14 Jan 2019 09:14:59 +0200
Joel Nider wrote:
> While using this guide to learn the new documentation method, I saw
> a few phrases that I felt could be improved. These small changes
> improve the grammar and choice of words to further enhance the
> installation instructions.
>
> Signed-o
On Mon, 14 Jan 2019 20:32:58 +0200
Mike Rapoport wrote:
> Fix the mismatch between "Useful GFP flag combinations" section naming in
> the DOC: section in include/linux/gfp.h and
> Documentation/core-api/mm-api.rst
>
> Signed-off-by: Mike Rapoport
> ---
> Documentation/core-api/mm-api.rst | 2 +
On Mon, 14 Jan 2019 13:47:34 +0200
Mike Rapoport wrote:
> Mention that when a part of a slab cache might be exported to the
> userspace, the cache should be created using kmem_cache_create_usercopy()
>
> Signed-off-by: Mike Rapoport
Hmm...I didn't know that :)
Applied, thanks.
jon
On Fri, 11 Jan 2019 17:14:10 +0100
Vincent Whitchurch wrote:
> Bits are usually numbered starting from zero, so 4 should be bit 2, not
> bit 3.
>
> Suggested-by: Matthew Wilcox
> Signed-off-by: Vincent Whitchurch
> ---
> Documentation/sysctl/vm.txt | 2 +-
> 1 file changed, 1 insertion(+), 1
On Fri, 11 Jan 2019 14:40:59 +0100
Christian Brauner wrote:
> This documents the Android binderfs filesystem used to dynamically add and
> remove binder devices that are private to each instance.
>
> Signed-off-by: Christian Brauner
Two quick notes:
> ---
> /* Changelog */
> v1:
> - switch fr
On Mon, 14 Jan 2019 09:56:21 -0700
Jason Gunthorpe wrote:
> > Documentation/infiniband/user_verbs.rst | 70
> > +
> > Documentation/infiniband/user_verbs.txt | 69
> >
> > 2 files changed, 70 insertions(+), 69 deletions(-)
> > c
ds
> without a blank line; unexpected unindent.
> Documentation/misc-devices/ibmvmc.rst:: WARNING: document isn't included in
> any toctree
>
> Signed-off-by: Randy Dunlap
> Cc: Steven Royer
> Cc: Jonathan Corbet
Rather than make another new top-level entry to a
On Sun, 13 Jan 2019 19:28:58 -0800
Randy Dunlap wrote:
> Fix Sphinx warning in coding-style.rst:
>
> Documentation/process/coding-style.rst:446: WARNING: Inline interpreted text
> or phrase reference start-string without end-string.
>
> Signed-off-by: Randy Dunlap
Applied, thanks.
jon
rnings from the docs
build, freeing us to focus on the ones that matter more. So make
kerneldoc be silent about missing descriptions for any field containing a
".".
Signed-off-by: Jonathan Corbet
---
scripts/kernel-doc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --g
On Fri, 11 Jan 2019 00:56:42 +0100
Christian Brauner wrote:
> > - Please consider doing this in RST and tying it into our documentation
> >tree. It's *almost* RST now, so the effort required will be almost
> >zero.
>
> Oh sure. I simply didn't know. I was just going by the files unde
On Fri, 11 Jan 2019 00:13:09 +0100
Christian Brauner wrote:
> This documents the Android binderfs filesystem used to dynamically add and
> remove binder devices that are private to each instance.
>
> Signed-off-by: Christian Brauner
Seems like a worthwhile addition overall. I know nothing abo
n 'irq_affinity_desc'
Add the missing information, making the docs build 0.001% quieter.
Signed-off-by: Jonathan Corbet
---
include/linux/interrupt.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/linux/interrupt.h b/include/linux/interrupt.h
index c672f34235e7..4a728dba0
script was mostly written by Randy Dunlap; I
enhanced the script a bit. There does not appear to be a good home for
this script. so create tools/debugging for tools of this nature.
Signed-off-by: Randy Dunlap
Signed-off-by: Thorsten Leemhuis
[ jc: rewrote changelog
On Sun, 23 Dec 2018 02:01:02 +0100
Federico Vaga wrote:
> It translats the document process/submitting-patches.rst.
>
> Signed-off-by: Federico Vaga
> ---
> .../it_IT/process/submitting-patches.rst | 862 +-
> 1 file changed, 858 insertions(+), 4 deletions(-)
Now applied,
On Mon, 07 Jan 2019 07:30:29 -0800 (PST)
David Miller wrote:
> Jon, do you want to integrate these? I'm fine with that and I don't
> anticiapte
> any serious conflicts.
I'll do that shortly, thanks.
jon
The following changes since commit
942104a21ce4951420ddf6c6b3179a0627301f7e:
docs: improve pathname-lookup document structure (2018-12-20 08:47:18 -0700)
are available in the Git repository at:
git://git.lwn.net/linux.git tags/docs-5.0-fixes
for you to fetch changes up to 93fb7f19985a08bbe3
Sorry for the delay in responding to this ... $EXCUSES ...
On Fri, 21 Dec 2018 16:26:31 +0100
Thorsten Leemhuis wrote:
> > Here's an idea if you feel like improving this: rather than putting an
> > inscrutable program inline, add a taint_status script to scripts/ that
> > prints out the status
On Sat, 29 Dec 2018 09:59:14 +0800
Huang Shijie wrote:
> Update the document, since we have renamed addr_in_gen_pool to
> gen_pool_has_addr.
>
> Signed-off-by: Huang Shijie
So I was looking to apply this, but I don't see anywhere in mainline or
-next where this change has been made...?
Thanks
On Tue, 1 Jan 2019 22:40:14 -0200
Marcos Paulo de Souza wrote:
> After 7ca01926463a, legacy rq tagging was removed, so block/blk-tag.c
> does not exists anymore. When generating pdfdocs, sphinx complains about
> this missing file:
>
> Error: Cannot open file ./block/blk-tag.c
> Error: Cannot op
On Wed, 2 Jan 2019 08:01:49 -0800
Tejun Heo wrote:
> On Sun, Dec 30, 2018 at 05:50:44PM +0100, Otto Sabart wrote:
> > Improve readability using the :file: markup.
>
> Heh, that's a minor plus for formatted output and minor minus for the
> source. If this is a convention generally followed for
On Sat, 29 Dec 2018 11:24:34 -0800
Linus Torvalds wrote:
> New signing key? And one that you forgot to push out to keyservers?
Sort of...some time ago, I tried to be a good kid and made a separate
signing subkey like Konstantin told me to. Then I couldn't ever get the
nitrokey thing to work and
On Sun, 30 Dec 2018 17:49:45 +0100
Otto Sabart wrote:
> The graphviz looks better. This patch also fixes multiple build warnings:
> "WARNING: Block quote ends without a blank line; unexpected unindent."
>
> Signed-off-by: Otto Sabart
The graphviz looks better *in some settings*, such as the fo
On Fri, 21 Dec 2018 09:44:44 -0800
Tim Chen wrote:
> Andi and I have made an update to our draft of the Spectre admin guide.
> We may be out on Christmas vacation for a while. But we want to
> send it out for everyone to take a look.
>
> Thanks.
>
> Tim
>
> From: Andi Kleen
>
> There are no
o foobar
doc:it: fixes in process/1.Intro
doc:it: add some process/* translations
doc:process: add links where missing
Geert Uytterhoeven (1):
Documentation/ras: Typo s/use use/use/
Helen Koike (1):
configfs: fix wrong name of struct in documentation
Jonathan C
On Mon, 10 Dec 2018 09:58:37 +1100
NeilBrown wrote:
> However we now have a stub section "Pathname lookup" which serves only
> to introduce another stub sectoin "Pathname lookup in Linux", which does
> little more than introduce the rest of the section.
> This seems inelegant, and is probably why
On Fri, 7 Dec 2018 17:11:58 -0200
Helen Koike wrote:
> The name of the struct is configfs_bin_attribute instead of
> configfs_attribute
>
> Signed-off-by: Helen Koike
>
> ---
>
> Documentation/filesystems/configfs/configfs.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> dif
On Thu, 20 Dec 2018 09:59:13 +0200
Mike Rapoport wrote:
> ping?
Sorry, been traveling, and I still don't really know what to do with
patches that are more mm/ than Documentation/. I've just applied these,
though.
Thanks,
jon
On Thu, 20 Dec 2018 16:23:38 +0100
Thorsten Leemhuis wrote:
> While at it: Jonathan, you mentioned putting the script in scripts/, but
> according to the Makefile in that directory it is "for various helper
> programs used throughout the kernel for the build process". That's one
> reason why it f
On Wed, 19 Dec 2018 22:47:18 -0800
Hunter Lannon wrote:
> This is my first patch submitted. I hope I can finally say I have a
> commit in the Linux source code :)
I expect you'll get there, but this patch won't be the one that crosses
the bar for you. Here's some suggestions for how to do it su
On Mon, 17 Dec 2018 16:20:42 +0100
Thorsten Leemhuis wrote:
> Hi! Find my first contribution to the kernel documentation in the reply to
> this
> mail. Hopefully a lot more will follow.
Hopefully! Looking forward to it.
> Sorry for using the simple table format for the table. I only noticed t
On Sat, 8 Dec 2018 20:38:56 -0800
Randy Dunlap wrote:
> On 11/12/18 8:08 AM, Jonathan Corbet wrote:
> > On Sun, 11 Nov 2018 18:36:30 -0800
> > Greg KH wrote:
> >
> >> We should have a checklist. That's a great idea. Now to find someone
> >> to w
On Fri, 7 Dec 2018 11:53:40 +1100
Stephen Rothwell wrote:
> Today's linux-next merge of the jc_docs tree got a conflict in:
>
> Documentation/filesystems/index.rst
>
> between commit:
>
> 1b71a6809f96 ("fs-verity: add a documentation file")
>
> from the fscrypt tree and commit:
>
> 7bb
On Fri, 30 Nov 2018 09:22:17 -0500
"Michael S. Tsirkin" wrote:
> Fix an extra space that sneaked in with commit 09c205afd "(x86, boot:
> Define the 2.12 bzImage boot protocol").
>
> Signed-off-by: Michael S. Tsirkin
Applied, thanks.
jon
On Sat, 1 Dec 2018 13:44:29 +0100
Nicholas Mc Guire wrote:
> There are a number of cases where conversions to devm_* API have been
> done but developers forgot that this conversion may imply that return
> values need to be checked for failure of internal resource handling
> like allocation. Whil
On Sun, 2 Dec 2018 18:40:09 +0100
Federico Vaga wrote:
> - fix broken links and some
> - fix some grammar errors
>
> Signed-off-by: Federico Vaga
Applied thanks (and the new translations as well).
jon
On Thu, 06 Dec 2018 08:00:58 +1100
NeilBrown wrote:
> > Is there a reason you used "include" rather than just adding it to the
> > TOC tree with the rest?
>
> Simple. I didn't know what I was doing, and so randomly made changes until
> the result seemed acceptable - then I stopped. If there
On Wed, 5 Dec 2018 17:10:48 -0800
Kees Cook wrote:
> On Tue, Nov 27, 2018 at 12:15 AM Alexey Budankov
> wrote:
> >
> >
> > Implement initial version of perf-security.rst documentation file
> > covering security concerns of perf_event_paranoid settings.
> >
> > Suggested-by: Thomas Gleixner
> >
On Fri, 30 Nov 2018 14:41:11 -0500
Steven Rostedt wrote:
> > - * Wirzenius wrote this portably, Torvalds fucked it up :-)
> > + * Wirzenius wrote this portably, Torvalds hugged it up :-)
>
> Since the code has been greatly modified since that comment was added,
> I would say the comment is sim
On Sun, 11 Nov 2018 18:36:30 -0800
Greg KH wrote:
> We should have a checklist. That's a great idea. Now to find someone
> to write it... :)
Do we think the LPC session might have the right people to create such a
thing? If so, I can try to put together a coherent presentation of the
result.
On Thu, 8 Nov 2018 11:15:53 -0800
Daniel Jordan wrote:
> > - You have kerneldoc comments for the API functions, but you don't pull
> > those into the documentation itself. Adding some kernel-doc directives
> > could help to fill things out nicely with little effort.
>
> I thought this par
On Mon, 5 Nov 2018 11:55:46 -0500
Daniel Jordan wrote:
> Motivates and explains the ktask API for kernel clients.
A couple of quick thoughts:
- Agree with Peter on the use of "task"; something like "job" would be far
less likely to create confusion. Maybe you could even call it a "batch
j
701 - 800 of 1693 matches
Mail list logo
