to pick, but nothing really substantive to complain
about, so:
Acked-by: Jonathan Corbet
[...]
> +IPE is a Linux Security Module, which allows for a configurable policy
I'd drop the comma (I told you these were nits!)
[...]
> +IPE Policy
> +~~
> +
> +IPE policy is de
On Wed, 1 Jul 2020 05:13:16 +0100
Matthew Wilcox wrote:
> > > -It turned out though that above approach has led to
> > > -abuses when the restricted gfp mask is used "just in case" without a
> > > -deeper consideration which leads to problems because an excessive use
> > > -of GFP_NOFS/GFP_NOIO c
On Fri, 3 Jul 2020 20:20:07 -0700
Randy Dunlap wrote:
> Remove duplicated words from Documentation/admin-guide/ files.
>
>
> Cc: Jonathan Corbet
> Cc: linux-...@vger.kernel.org
> Cc: cgro...@vger.kernel.org
> Cc: dm-devel@redhat.com
> Cc: Mauro Carvalh
On Sat, 27 Jun 2020 12:31:38 +0200
"Alexander A. Klimov" wrote:
> Rationale:
> Reduces attack surface on kernel devs opening the links for MITM
> as HTTPS traffic is much harder to manipulate.
>
> Deterministic algorithm:
> For each file:
> If not .svg:
> For each line:
> If doesn't
On Tue, 16 Apr 2019 09:28:52 -0400
Mike Snitzer wrote:
> Can you help me understand why this is the direction text based
> Documenation is taking in the Linux kernel? All I see is markup, and
> escaping of characters, that is a chore to administer over time.
This is a discussion that was mostly
On Tue, 16 Apr 2019 11:48:59 -0400
Mike Snitzer wrote:
> Think the last piece I'm missing is: how does one edit a .rst document
> without having to know to sprinkle syntactic sugar around? Does emacs
> have a ReST mode? If not what client interface are people using to
> properly change these do
On Thu, 18 Apr 2019 09:42:23 -0300
Mauro Carvalho Chehab wrote:
> After thinking a little bit and doing some tests, I think a good solution
> would be to add ":orphan:" markup to the new .rst files that were not
> added yet into the main body (e. g. something like the enclosed example).
Interest
On Tue, 23 Apr 2019 19:11:58 +0200
Peter Zijlstra wrote:
> When writing, I now have to be bothered about this format crap over just
> trying to write a coherent document.
Just write text, it'll all work out in the end :)
> Look at crap like this:
>
> "The memory allocations via :c:func:`kmallo
On Tue, 23 Apr 2019 15:01:32 +0200
Peter Zijlstra wrote:
> But yes, I have 0 motivation to learn or abide by rst. It simply doesn't
> give me anything in return. There is no upside, only worse text files :/
So I believe it gives even you one thing in return: documentation that is
more accessible
On Tue, 23 Apr 2019 17:19:44 -0300
Mauro Carvalho Chehab wrote:
> Anyway, one of the things that occurred to me is that maybe
> some scripting work or a ReST extension could do something to parse
> "Documentation/foo" as :doc:`Documentation/foo` without needing to
> explicitly use any ReST speci
On Tue, 23 Apr 2019 23:38:16 +0200
Borislav Petkov wrote:
> But exactly this - *having* to do rst formatting would mean a lot of
> getting used to and people writing something which is not necessarily
> correct rst and someone else fixing up after them.
Remember that most of our docs are 99% RST
On Tue, 4 Jun 2019 15:27:19 -0300
Helen Koike wrote:
> The example in the docs regarding multiple device-mappers is invalid (it
> has a wrong number of arguments), it's a left over from previous
> versions of the patch.
> Replace the example with an valid and tested one.
>
> Signed-off-by: Hele
On Mon, 7 Oct 2019 13:24:49 -0400
Bryan Gurney wrote:
> Convert the dm-dust documentation to ReST formatting, using literal
> blocks for all of the shell command, shell output, and log output
> examples.
>
> Add dm-dust to index.rst.
>
> Additionally, fix an annotation in the "querying for spe
On Tue, 26 Nov 2019 15:16:13 -0500
Mike Snitzer wrote:
> I already staged this for 5.5 here:
> https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git/commit/?h=dm-5.5&id=484e0d2b11e1fdd0d17702b282eb2ed56148385f
>
> But I don't plan to send to Linus for a week or 2...
>
> If
On Mon, 17 Oct 2016 21:17:10 +0900
Masanari Iida wrote:
> This patch fix spelling typos in Documentation/device-mapper/dm-raid.txt.
Applied to the docs tree, thanks.
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
On Sun, 19 Mar 2017 03:04:24 +0530
sayli karnik wrote:
> The patch fixes a spelling error (hexidecimal->hexadecimal).
FYI, normal changelog style favors an imperative mood and avoiding terms
like "this patch". So I changed the above to:
Fix a spelling error (hexidecimal->hexadecimal)
On Tue, 9 Oct 2018 11:31:31 +0300
Nikolay Borisov wrote:
> Commit ef548c551e72 ("dm flakey: introduce "error_writes" feature")
> added the ability to dm flakey to error out writes in contrast to
> silently dropping it with 'drop_writes'. Unfortunately this feature
> is not currently documented a
Randy Dunlap writes:
> Maintainers of specific kernel subsystems are only Cc-ed on their
> respective patches, not the entire series. [if all goes well]
>
> These patches are based on linux-next-20230127.
So I've applied a bunch of these
> [PATCH 1/9] Documentation: admin-guide: correct spelli
Bart Van Assche writes:
> On 2/2/23 10:33, Randy Dunlap wrote:
>> On 2/2/23 10:09, Jonathan Corbet wrote:
>>> Randy Dunlap writes:
>>>> [PATCH 6/9] Documentation: scsi/ChangeLog*: correct spelling
>>>> [PATCH 7/9] Documentation: scsi: correct spe
Bagas Sanjaya writes:
> On Sun, Jun 04, 2023 at 12:06:03PM -0700, Russell Harmon wrote:
>> Specifically:
>> interleave_sectors = 32768
>> buffer_sectors = 128
>> block_size = 512
>> journal_watermark = 50
>> commit_time = 1
>
> Your patch description duplicates the diff content belo
20 matches
Mail list logo
