Re: [PATCH] docs/core-api: make mm-api.rst more structured

On Wed, 28 Nov 2018 16:45:44 +0200 Mike Rapoport wrote: > The mm-api.rst covers variety of memory management APIs under "More Memory > Management Functions" section. The descriptions included there are in a > random order there are quite a few of them which makes the section too > long. > >

Re: [PATCH v2 2/2] core-api/memory-hotplug.rst: divide Locking Internal section by different locks

On 06.12.18 01:26, Wei Yang wrote: > Currently locking for memory hotplug is a little complicated. > > Generally speaking, we leverage the two global lock: > > * device_hotplug_lock > * mem_hotplug_lock > > to serialise the process. > > While for the long term, we are willing to have more

Re: [PATCH v2 2/2] core-api/memory-hotplug.rst: divide Locking Internal section by different locks

On Thu, Dec 06, 2018 at 08:26:22AM +0800, Wei Yang wrote: > Currently locking for memory hotplug is a little complicated. > > Generally speaking, we leverage the two global lock: > > * device_hotplug_lock > * mem_hotplug_lock > > to serialise the process. > > While for the long term, we

Re: [PATCH 2/2] core-api/memory-hotplug.rst: divide Locking Internal section by different locks

On Wed, Dec 05, 2018 at 01:13:10PM +0100, Michal Hocko wrote: >On Wed 05-12-18 10:34:26, Wei Yang wrote: >> Currently locking for memory hotplug is a little complicated. >> >> Generally speaking, we leverage the two global lock: >> >> * device_hotplug_lock >> * mem_hotplug_lock >> >> to

Re: [PATCH 2/2] core-api/memory-hotplug.rst: divide Locking Internal section by different locks

On Wed 05-12-18 10:34:26, Wei Yang wrote: > Currently locking for memory hotplug is a little complicated. > > Generally speaking, we leverage the two global lock: > > * device_hotplug_lock > * mem_hotplug_lock > > to serialise the process. > > While for the long term, we are willing to

Re: [PATCH 1/2] admin-guide/memory-hotplug.rst: remove locking internal part from admin-guide

On Wed 05-12-18 10:34:25, Wei Yang wrote: > Locking Internal section exists in core-api documentation, which is more > suitable for this. > > This patch removes the duplication part here. > > Signed-off-by: Wei Yang Yes this doesn't really make any sense in an admin guide. It is a pure

Re: [PATCH 2/2] core-api/memory-hotplug.rst: divide Locking Internal section by different locks

On Wed, Dec 05, 2018 at 10:40:45AM +0200, Mike Rapoport wrote: >On Wed, Dec 05, 2018 at 10:34:26AM +0800, Wei Yang wrote: >> Currently locking for memory hotplug is a little complicated. >> >> Generally speaking, we leverage the two global lock: >> >> * device_hotplug_lock >> *

Re: [PATCH 2/2] core-api/memory-hotplug.rst: divide Locking Internal section by different locks

On Wed, Dec 05, 2018 at 09:08:47AM +0100, David Hildenbrand wrote: >On 05.12.18 03:34, Wei Yang wrote: >> Currently locking for memory hotplug is a little complicated. >> >> Generally speaking, we leverage the two global lock: >> >> * device_hotplug_lock >> * mem_hotplug_lock >> >> to

Re: [PATCH 1/2] admin-guide/memory-hotplug.rst: remove locking internal part from admin-guide

On Wed, Dec 05, 2018 at 10:30:13AM +0200, Mike Rapoport wrote: >On Wed, Dec 05, 2018 at 09:03:24AM +0100, David Hildenbrand wrote: >> On 05.12.18 03:34, Wei Yang wrote: >> > Locking Internal section exists in core-api documentation, which is more >> > suitable for this. >> > >> > This patch

Re: [PATCH 1/2] admin-guide/memory-hotplug.rst: remove locking internal part from admin-guide

On Wed, Dec 05, 2018 at 09:03:24AM +0100, David Hildenbrand wrote: >On 05.12.18 03:34, Wei Yang wrote: >> Locking Internal section exists in core-api documentation, which is more >> suitable for this. >> >> This patch removes the duplication part here. >> >> Signed-off-by: Wei Yang >> --- >>

Re: [PATCH 2/2] core-api/memory-hotplug.rst: divide Locking Internal section by different locks

On Wed, Dec 05, 2018 at 10:34:26AM +0800, Wei Yang wrote: > Currently locking for memory hotplug is a little complicated. > > Generally speaking, we leverage the two global lock: > > * device_hotplug_lock > * mem_hotplug_lock > > to serialise the process. > > While for the long term, we

Re: [PATCH 1/2] admin-guide/memory-hotplug.rst: remove locking internal part from admin-guide

On Wed, Dec 05, 2018 at 09:03:24AM +0100, David Hildenbrand wrote: > On 05.12.18 03:34, Wei Yang wrote: > > Locking Internal section exists in core-api documentation, which is more > > suitable for this. > > > > This patch removes the duplication part here. > > > > Signed-off-by: Wei Yang > >

Re: [PATCH 2/2] core-api/memory-hotplug.rst: divide Locking Internal section by different locks

On 05.12.18 03:34, Wei Yang wrote: > Currently locking for memory hotplug is a little complicated. > > Generally speaking, we leverage the two global lock: > > * device_hotplug_lock > * mem_hotplug_lock > > to serialise the process. > > While for the long term, we are willing to have more

Re: [PATCH 1/2] admin-guide/memory-hotplug.rst: remove locking internal part from admin-guide

On 05.12.18 03:34, Wei Yang wrote: > Locking Internal section exists in core-api documentation, which is more > suitable for this. > > This patch removes the duplication part here. > > Signed-off-by: Wei Yang > --- > Documentation/admin-guide/mm/memory-hotplug.rst | 40 >

RE,

-- Hello, First of all i will like to apologies for my manner of communication because you do not know me personally, its due to the fact that i have a very important proposal for you.

Re: Did You Receive My Last Mail?

Hello, My name is ms. Reem Al-Hashimi. The UAE minister of state for international cooparation. I got your contact from an email database from your country. I have a financial transaction i would like to discuss with you. Please reply to reem2...@daum.net, for more details if you are

Re: [PATCH 1/1] scripts/kernel-doc: Fix struct and struct field attribute processing

On Thu, 22 Nov 2018 13:06:04 +0200 Sakari Ailus wrote: > The kernel-doc attempts to clear the struct and struct member attributes > from the API documentation it produces. It falls short of the job in the > following respects: > > - extra whitespaces are left where __attribute__((...)) was

RE,

Hello, First of all i will like to apologies for my manner of communication because you do not know me personally, its due to the fact that i have a very important proposal for you.

RE,

Hello, First of all i will like to apologies for my manner of communication because you do not know me personally, its due to the fact that i have a very important proposal for you.

RE,

Hello, First of all i will like to apologies for my manner of communication because you do not know me personally, its due to the fact that i have a very important proposal for you.

RE,

Hello, First of all i will like to apologies for my manner of communication because you do not know me personally, its due to the fact that i have a very important proposal for you.

Re: [PATCH security-next v5 00/30] LSM: Explict ordering

On 11/14/2018 1:04 PM, Casey Schaufler wrote: > On 10/24/2018 1:12 PM, Kees Cook wrote: >> On Wed, Oct 24, 2018 at 1:56 AM, Casey Schaufler >> wrote: >>> On 10/23/2018 12:05 PM, Casey Schaufler wrote: On 10/23/2018 11:50 AM, Kees Cook wrote: > Did you poke around at my combined

Re: [PATCH v2] docs/admin-guide/mm/concepts.rst: grammar and style fixups

On Sun, 11 Nov 2018 11:24:23 +0200 Mike Rapoport wrote: > Signed-off-by: Mike Rapoport > Reviewed-by: Randy Dunlap > --- > > v2: address Matthew's feedback > > Documentation/admin-guide/mm/concepts.rst | 51 > --- > 1 file changed, 26 insertions(+), 25

Re: [PATCH] docs/mm: update kmalloc kernel-doc description

On Sun, 11 Nov 2018 18:48:44 +0200 Mike Rapoport wrote: > Add references to GFP documentation and the memory-allocation.rst and remove > GFP_USER, GFP_DMA and GFP_NOIO descriptions. > > While on it slightly change the formatting so that the list of GFP flags > will be rendered as "description"

Re: [PATCH] Link the memory allocation guide from the MM docs

On Mon, 19 Nov 2018 08:00:49 -0800 Matthew Wilcox wrote: > I just went looking for the memory allocation guide in the MM docs instead > of in the core API. For the benefit of the next person who makes that > mistake, link to it from the MM docs. > > Signed-off-by: Matthew Wilcox Applied,

Re: [PATCH] Link the memory allocation guide from the MM docs

On Mon, Nov 19, 2018 at 08:00:49AM -0800, Matthew Wilcox wrote: > I just went looking for the memory allocation guide in the MM docs instead > of in the core API. For the benefit of the next person who makes that > mistake, link to it from the MM docs. > > Signed-off-by: Matthew Wilcox

Re: [PATCH v2] Document /proc/pid PID reuse behavior

On Mon, Nov 19, 2018 at 2:54 AM, Pavel Machek wrote: > On Mon 2018-11-05 13:22:05, Daniel Colascione wrote: >> State explicitly that holding a /proc/pid file descriptor open does >> not reserve the PID. Also note that in the event of PID reuse, these >> open file descriptors refer to the old,

Re: [PATCH v1 2/8] mm: convert PG_balloon to PG_offline

> > diff --git a/include/linux/page-flags.h b/include/linux/page-flags.h > index 50ce1bddaf56..f91da3d0a67e 100644 > --- a/include/linux/page-flags.h > +++ b/include/linux/page-flags.h > @@ -670,7 +670,7 @@ PAGEFLAG_FALSE(DoubleMap) > #define PAGE_TYPE_BASE 0xf000 > /* Reserve

Re: [PATCH security-next v5 00/30] LSM: Explict ordering

On 10/24/2018 1:12 PM, Kees Cook wrote: > On Wed, Oct 24, 2018 at 1:56 AM, Casey Schaufler > wrote: >> On 10/23/2018 12:05 PM, Casey Schaufler wrote: >>> On 10/23/2018 11:50 AM, Kees Cook wrote: >>> Did you poke around at my combined series?

Re: [PATCH v2] doc: tracing: Fix a number of typos

On Thu, 1 Nov 2018 09:57:17 -0400 Amir Livneh wrote: > Trivial fixes to spelling mistakes in ftrace.rst > > v2: tripple -> triple > > Signed-off-by: Amir Livneh Applied, thanks. jon

Re: [PATCH] docs/admin-guide/mm/concepts.rst: grammar fixups

On Mon, Nov 05, 2018 at 11:29:27PM -0800, Randy Dunlap wrote: > On 11/5/18 10:35 PM, Mike Rapoport wrote: > > On Mon, Nov 05, 2018 at 01:12:40PM -0800, Matthew Wilcox wrote: > >> On Mon, Nov 05, 2018 at 09:58:15PM +0200, Mike Rapoport wrote: > >>> @@ -21,10 +21,10 @@ Virtual Memory Primer > >>>

Re: [PATCH] docs/admin-guide/mm/concepts.rst: grammar fixups

On 11/5/18 10:35 PM, Mike Rapoport wrote: > On Mon, Nov 05, 2018 at 01:12:40PM -0800, Matthew Wilcox wrote: >> On Mon, Nov 05, 2018 at 09:58:15PM +0200, Mike Rapoport wrote: >>> @@ -21,10 +21,10 @@ Virtual Memory Primer >>> The physical memory in a computer system is a limited resource and >>>

Re: [PATCH] docs/admin-guide/mm/concepts.rst: grammar fixups

On Mon, Nov 05, 2018 at 01:12:40PM -0800, Matthew Wilcox wrote: > On Mon, Nov 05, 2018 at 09:58:15PM +0200, Mike Rapoport wrote: > > @@ -21,10 +21,10 @@ Virtual Memory Primer > > The physical memory in a computer system is a limited resource and > > even for systems that support memory hotplug

Re: [PATCH] docs/admin-guide/mm/concepts.rst: grammar fixups

On Mon, Nov 05, 2018 at 09:58:15PM +0200, Mike Rapoport wrote: > @@ -21,10 +21,10 @@ Virtual Memory Primer > The physical memory in a computer system is a limited resource and > even for systems that support memory hotplug there is a hard limit on > the amount of memory that can be installed.

Re: [PATCH] docs/admin-guide/mm/concepts.rst: grammar fixups

On 11/5/18 11:58 AM, Mike Rapoport wrote: > From: Mike Rapoport > > Signed-off-by: Mike Rapoport > Cc: Randy Dunlap > --- > > There was a couple of grammar fixes Randy suggested a while ago, but it > seems I've never sent them out. > > Documentation/admin-guide/mm/concepts.rst | 39 >

Re: [GIT PULL] Compiler Attributes for v4.20-rc1

On Mon, Nov 5, 2018 at 5:15 AM Martin Schwidefsky wrote: > > This patch would work for me: Thanks, applied, Linus

Re: [GIT PULL] Compiler Attributes for v4.20-rc1

On Mon, 5 Nov 2018 14:15:35 +0100 Martin Schwidefsky wrote: > > Follow-up question: the __no_sanitize_address_or_inline define has the > 'notrace' > option that is missing for __no_kasan_or_inline. We need that option for > __load_psw_mask, if we do the replacement all users of

Re: [GIT PULL] Compiler Attributes for v4.20-rc1

On Mon, 5 Nov 2018 07:02:56 +0100 Martin Schwidefsky wrote: > On Fri, 2 Nov 2018 09:09:32 -0700 > Linus Torvalds wrote: > > > On Fri, Nov 2, 2018 at 2:43 AM Andrey Ryabinin > > wrote: > > > > > > You're right, version checks shouldn't matter here. But > > > __no_sanitize_address_or_inline

Re: [GIT PULL] Compiler Attributes for v4.20-rc1

On Fri, 2 Nov 2018 09:09:32 -0700 Linus Torvalds wrote: > On Fri, Nov 2, 2018 at 2:43 AM Andrey Ryabinin > wrote: > > > > You're right, version checks shouldn't matter here. But > > __no_sanitize_address_or_inline > > shouldn't have been added in the first place, because we already have > >

Re: [GIT PULL] Compiler Attributes for v4.20-rc1

On 11/02/2018 07:11 PM, Linus Torvalds wrote: > On Fri, Nov 2, 2018 at 6:16 AM Andrey Ryabinin > wrote: >> >> On 11/02/2018 04:46 AM, Linus Torvalds wrote: >>> >>> So I _think_ the KASAN config should have a >>> >>> depends on CC_IS_GCC && GCC_VERSION >= 40902 >>> >>> on it, but maybe

Re: [GIT PULL] Compiler Attributes for v4.20-rc1

On Fri, Nov 2, 2018 at 6:16 AM Andrey Ryabinin wrote: > > On 11/02/2018 04:46 AM, Linus Torvalds wrote: > > > > So I _think_ the KASAN config should have a > > > > depends on CC_IS_GCC && GCC_VERSION >= 40902 > > > > on it, but maybe there is something I'm missing. > > I'd rather use

Re: [GIT PULL] Compiler Attributes for v4.20-rc1

On Fri, Nov 2, 2018 at 2:43 AM Andrey Ryabinin wrote: > > You're right, version checks shouldn't matter here. But > __no_sanitize_address_or_inline > shouldn't have been added in the first place, because we already have almost > the same >__no_kasan_or_inline: Ahh, very good. Vasily, Martin -

Re: [GIT PULL] Compiler Attributes for v4.20-rc1

On 11/02/2018 04:46 AM, Linus Torvalds wrote: > On Thu, Nov 1, 2018 at 10:06 AM Linus Torvalds > wrote: >> >> The logic for using __no_sanitize_address *used* to be >> >> #if GCC_VERSION >= 40902 > > Ok, looking around, I think this has less to do with the attribute > being recognized,

Re: [GIT PULL] Compiler Attributes for v4.20-rc1

On Fri, Nov 2, 2018 at 2:52 AM Linus Torvalds wrote: > > Anyway, I decided to do the merge by just getting rid of the > GCC_VERSION check around __no_sanitize_address_or_inline entirely. If > you enable KASAN, then a function with that marking just won't be > marked inline. I was a bit confused

Re: [GIT PULL] Compiler Attributes for v4.20-rc1

On 11/01/2018 08:06 PM, Linus Torvalds wrote: > On Mon, Oct 22, 2018 at 3:59 AM Miguel Ojeda > wrote: >> >> Here it is the Compiler Attributes series/tree, which tries to disentangle >> the include/linux/compiler*.h headers and bring them up to date. > > I've finally emptied the "normal" pull

Re: [GIT PULL] Compiler Attributes for v4.20-rc1

On Thu, Nov 1, 2018 at 10:06 AM Linus Torvalds wrote: > > The logic for using __no_sanitize_address *used* to be > > #if GCC_VERSION >= 40902 Ok, looking around, I think this has less to do with the attribute being recognized, and simply just being because KASAN itself wants gcc-4.9.2. I'm

Re: [GIT PULL] Compiler Attributes for v4.20-rc1

On Thu, Nov 1, 2018 at 6:06 PM Linus Torvalds wrote: > > I'm not sure how much that matters (maybe the original check for 4.9.2 > was just a random pick by Andrey? Added to cc), but together with the > movement to that looks like it also > wouldn't want the CONFIG_KASAN tests, I wonder what the

Re: [PATCH] doc: tracing: Fix a number of typos

On 2018-10-31 14:16, Amir Livneh wrote: > @@ -2978,7 +2978,7 @@ The following commands are supported: >When the function is hit, it will dump the contents of the ftrace >ring buffer to the console. This is useful if you need to debug >something, and want to dump the trace when a

Re: [PATCH v10 4/9] dt-bindings: i3c: Document core bindings

On Fri, 26 Oct 2018 16:43:28 +0200, Boris Brezillon wrote: > A new I3C subsystem has been added and a generic description has been > created to represent the I3C bus and the devices connected on it. > > Document this generic representation. > > Cc: Rob Herring > Signed-off-by: Boris Brezillon

Re: [PATCH security-next v5 00/30] LSM: Explict ordering

On Wed, Oct 24, 2018 at 1:56 AM, Casey Schaufler wrote: > On 10/23/2018 12:05 PM, Casey Schaufler wrote: >> On 10/23/2018 11:50 AM, Kees Cook wrote: >> >>> Did you poke around at my combined series? >>>

Re: [PATCH security-next v5 00/30] LSM: Explict ordering

On 10/23/2018 12:05 PM, Casey Schaufler wrote: > On 10/23/2018 11:50 AM, Kees Cook wrote: > >> Did you poke around at my combined series? >> https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/log/?h=lsm/ordering-v6-blob-sharing > I hope to do that on the plane later today. I had a

Re: [PATCH security-next v5 00/30] LSM: Explict ordering

On 10/23/2018 11:50 AM, Kees Cook wrote: > On Tue, Oct 23, 2018 at 9:48 AM, Casey Schaufler > wrote: >> On 10/12/2018 12:01 PM, Kees Cook wrote: >>> On Friday, October 12, 2018 3:19 AM, John Johansen >>> wrote: It isn't perfect but it manages consistency across distros as best as can

Re: [PATCH 1/2] Compiler Attributes: add support for __fallthrough (gcc >= 7.1)

On Mon, Oct 22, 2018 at 11:15 AM Bernd Petrovitsch wrote: > > Hi all! > > On 22/10/18 19:54, Nick Desaulniers wrote: > > On Mon, Oct 22, 2018 at 10:50 AM Bernd Petrovitsch > > wrote: > [...] > >> PS: clang++ errors with "fallthrough annotation in unreachable code" if > >> [[fallthrough]] is

Re: [PATCH] doc: fix a typo in adding-syscalls.rst

On Thu, 18 Oct 2018 17:47:50 +0200 cor...@poussif.eu wrote: > There was a typo in adding-syscalls.rst that could mislead developers > to add a C filename in a makefile instead of an object filename. > This error, while not keeping developers from contributing could slow > the development process

Re: [PATCH v2 00/22] xfs-4.20: major documentation surgery

On Mon, 15 Oct 2018 02:55:49 -0700 Christoph Hellwig wrote: > > OK, I've had a long conversation with the LF lawyer, and she said clearly > > that we really should not be introducing CC-SA material into the kernel > > source tree. It's a pain; I really do like CC-SA better for > >

Re: [PATCH v2 00/22] xfs-4.20: major documentation surgery

On Thu, Oct 11, 2018 at 11:27:35AM -0600, Jonathan Corbet wrote: > On Sat, 6 Oct 2018 10:51:54 +1000 > Dave Chinner wrote: > > > Can you let us know whether the CC-by-SA 4.0 license is acceptible > > or not? That's really the only thing that we need clarified at this > > point - if it's OK I'll

Re: [PATCH v2 00/22] xfs-4.20: major documentation surgery

On Thu, Oct 11, 2018 at 11:27:35AM -0600, Jonathan Corbet wrote: > On Sat, 6 Oct 2018 10:51:54 +1000 Dave Chinner > wrote: > > > Can you let us know whether the CC-by-SA 4.0 license is > > acceptible or not? That's really the only thing that we need > > clarified at this point - if it's OK I'll

Re: [PATCH v2 00/22] xfs-4.20: major documentation surgery

On Sat, 6 Oct 2018 10:51:54 +1000 Dave Chinner wrote: > Can you let us know whether the CC-by-SA 4.0 license is acceptible > or not? That's really the only thing that we need clarified at this > point - if it's OK I'll to pull this into the XFS tree for the 4.20 > merge window. If not, we'll go

Re: [PATCH 2/2] docs/vm: split memory hotplug notifier description to Documentation/core-api

On Sun, Oct 07, 2018 at 08:46:40AM -0600, Jonathan Corbet wrote: > On Fri, 5 Oct 2018 01:11:01 +0300 > Mike Rapoport wrote: > > > The memory hotplug notifier description is about kernel internals rather > > than admin/user visible API. Place it appropriately. > > > > Signed-off-by: Mike

Re: [PATCH] docs: improve readability for people with poorer eyesight

On Thu, 4 Oct 2018 18:06:03 -0700 "Darrick J. Wong" wrote: > o my eyesight still hasn't fully recovered, so in the meantime it's > been difficult to read the online documentation. Here's some stylesheet > overrides I've been using to make it easier for me to read them: >

Re: [PATCH 2/2] docs/vm: split memory hotplug notifier description to Documentation/core-api

On Fri, 5 Oct 2018 01:11:01 +0300 Mike Rapoport wrote: > The memory hotplug notifier description is about kernel internals rather > than admin/user visible API. Place it appropriately. > > Signed-off-by: Mike Rapoport One little nit... > Documentation/admin-guide/mm/memory-hotplug.rst|

Re: [PATCH 2/2] docs: promote the ext4 data structures book to top level

On Fri, 5 Oct 2018 19:49:52 -0400 "Theodore Y. Ts'o" wrote: > On Thu, Oct 04, 2018 at 05:59:44PM -0700, Darrick J. Wong wrote: > > From: Darrick J. Wong > > > > Move the ext4 data structures book to Documentation/filesystems/ext4/ > > since the administrative information moved elsewhere. > >

Re: [PATCH v2 00/22] xfs-4.20: major documentation surgery

On Sat, 6 Oct 2018 06:29:51 -0700 Matthew Wilcox wrote: > I had an informal chat with Bradley Kuhn at LinuxCon Japan about using > CC-BY-SA-4.0 and he indicated that I was probably better off using the > GPL-2(+) for documentation. I've changed the XArray documentation from > CC-BY-SA-4.0 to

Re: [PATCH v2 00/22] xfs-4.20: major documentation surgery

On Sat, Oct 06, 2018 at 10:51:54AM +1000, Dave Chinner wrote: > On Wed, Oct 03, 2018 at 09:18:11PM -0700, Darrick J. Wong wrote: > > Hi all, > > > > This series converts the existing in-kernel xfs documentation to rst > > format, links it in with the rest of the kernel's rst documetation, and > >

Re: [PATCH v5 00/15] Compiler Attributes

On Sat, Oct 6, 2018 at 9:13 AM Sedat Dilek wrote: > > Hi Miguel, > > In my testoings I am booting in QEMU and on bare metal. > Both tests were successful. Wow! I only wanted to confirm it booted and/or run for a while -- but having more information is always good. Thanks a *lot*! I will add a

Re: [PATCH v2 00/22] xfs-4.20: major documentation surgery

On Fri, Oct 05, 2018 at 07:01:20PM -0600, Jonathan Corbet wrote: > On Sat, 6 Oct 2018 10:51:54 +1000 > Dave Chinner wrote: > > > Can you let us know whether the CC-by-SA 4.0 license is acceptible > > or not? That's really the only thing that we need clarified at this > > point - if it's OK I'll

Re: [PATCH v2 00/22] xfs-4.20: major documentation surgery

On Sat, 6 Oct 2018 10:51:54 +1000 Dave Chinner wrote: > Can you let us know whether the CC-by-SA 4.0 license is acceptible > or not? That's really the only thing that we need clarified at this > point - if it's OK I'll to pull this into the XFS tree for the 4.20 > merge window. If not, we'll go

Re: [PATCH v2 00/22] xfs-4.20: major documentation surgery

On Wed, Oct 03, 2018 at 09:18:11PM -0700, Darrick J. Wong wrote: > Hi all, > > This series converts the existing in-kernel xfs documentation to rst > format, links it in with the rest of the kernel's rst documetation, and > then begins pulling in the contents of the Data Structures & Algorithms >

Re: [PATCH] docs: improve readability for people with poorer eyesight

On Thu, Oct 04, 2018 at 06:06:03PM -0700, Darrick J. Wong wrote: > Hi, > > So my eyesight still hasn't fully recovered, so in the meantime it's > been difficult to read the online documentation. Here's some stylesheet > overrides I've been using to make it easier for me to read them: >

Re: [PATCH 2/2] docs: promote the ext4 data structures book to top level

On Thu, Oct 04, 2018 at 05:59:44PM -0700, Darrick J. Wong wrote: > From: Darrick J. Wong > > Move the ext4 data structures book to Documentation/filesystems/ext4/ > since the administrative information moved elsewhere. > > Signed-off-by: Darrick J. Wong Thanks, applied and pushed out to the

Re: [PATCH 0/2] ext4: even more documentation fixes

On 10/5/18 8:22 AM, Theodore Y. Ts'o wrote: > On Thu, Oct 04, 2018 at 07:48:31PM -0700, Randy Dunlap wrote: >> Hi Darrick, >> >> I don't see patch 2/2 anywhere (my inbox, email archives)... > > Probably because it's moving a lot of files around, so the diffs were 276k. Oh, yeah. Thanks. --

Re: [PATCH 0/2] ext4: even more documentation fixes

On Thu, Oct 04, 2018 at 07:48:31PM -0700, Randy Dunlap wrote: > Hi Darrick, > > I don't see patch 2/2 anywhere (my inbox, email archives)... Probably because it's moving a lot of files around, so the diffs were 276k. > > -- > ~Randy

Re: [PATCH 0/2] ext4: even more documentation fixes

On 10/4/18 5:59 PM, Darrick J. Wong wrote: > Hi all, > > This series fixes some problems that were brought up during review for > the XFS documentation which I hadn't known about when pushing the ext4 > documentation during the 4.19 cycle. > > The first patch moves the ext4 mount option and

Re: [PATCH v5 00/15] Compiler Attributes

Hi Sedat, On Mon, Sep 24, 2018 at 10:46 AM Sedat Dilek wrote: > > [ Please CC me I am not subcribed to this ML ] > > Quote from : > > Tested-by: Sedat Dilek (against Linux > v4.19-rc5 and built with LLVM/Clang v7) Thanks a lot for testing! Which

Re: [PATCH] doc: Fix acronym "FEKEK" in ecryptfs

On Mon, 17 Sep 2018 11:34:48 +0200 Felix Eckhofer wrote: > "FEFEK" was incorrectly used as acronym for "File Encryption Key > Encryption Key". This replaces all occurences with "FEKEK". > > Signed-off-by: Felix Eckhofer > --- > Documentation/security/keys/ecryptfs.rst | 8 > 1 file

Re: [PATCH] Documentation: filesystems: remove reminiscences of POHMELFS

20.09.2018, 16:11, "Greg Kroah-Hartman" : >>  Since likely any delopment of the filesystem is halted, the change removes >>  the abandoned POHMELFS documentation from the kernel tree. >> >>  Signed-off-by: Vladimir Zapolskiy > > I've taken this through the staging tree as that is where this

Re: [PATCH] Documentation: filesystems: remove reminiscences of POHMELFS

On Wed, Sep 12, 2018 at 03:44:19PM +0300, Vladimir Zapolskiy wrote: > The POHMELFS filesystem was removed in 2012 by commit 67435319866f8 > ("staging: pohmelfs: remove drivers/staging/pohmelfs") promising that > a newer version will be included to the kernel, but unfortunately > it didn't happen.

Re: [PATCH 00/19] mtd: rawnand: API cleanup (2nd batch)

Hi Boris, Boris Brezillon wrote on Mon, 17 Sep 2018 10:29:39 +0200: > On Sat, 15 Sep 2018 19:54:40 +0200 > Miquel Raynal wrote: > > > Hi Boris, > > > > Boris Brezillon wrote on Fri, 7 Sep 2018 > > 00:38:32 +0200: > > > > > Hello, > > > > > > This is the 2nd batch of API cleanup

Re: [PATCH 00/19] mtd: rawnand: API cleanup (2nd batch)

On Sat, 15 Sep 2018 19:54:40 +0200 Miquel Raynal wrote: > Hi Boris, > > Boris Brezillon wrote on Fri, 7 Sep 2018 > 00:38:32 +0200: > > > Hello, > > > > This is the 2nd batch of API cleanup patches. This time we move > > deprecated hooks/fields to the nand_legacy struct, and then move some >

Re: [PATCH 00/19] mtd: rawnand: API cleanup (2nd batch)

Hi Boris, Boris Brezillon wrote on Fri, 7 Sep 2018 00:38:32 +0200: > Hello, > > This is the 2nd batch of API cleanup patches. This time we move > deprecated hooks/fields to the nand_legacy struct, and then move some > of the code found in nand_base.c into separate source/header files. > >

Re: [PATCH] Documentation: fix image_size default value

On Saturday, September 1, 2018 6:51:15 AM CEST Vladimir D. Seleznev wrote: > This commit updates the default value of /sys/power/image_size in > the documentation. > > Since ac5c24ec1e983313ef0015258fba6f630e54e7cn the `image_size' value is > set to about 2/5 of RAM, according to

Re: nodocs in 4.19-rcX

On 9/11/18 8:25 AM, Jonathan Corbet wrote: > On Mon, 10 Sep 2018 15:51:20 -0700 > Randy Dunlap wrote: > >> 4.19-rc contains some users of :nodocs: but that is not recognized yet, >> so we get: >> >> lnx-419-rc3/Documentation/core-api/boot-time-mm.rst:78: ERROR: Error in >> "kernel-doc"

Re: nodocs in 4.19-rcX

On Mon, 10 Sep 2018 15:51:20 -0700 Randy Dunlap wrote: > 4.19-rc contains some users of :nodocs: but that is not recognized yet, > so we get: > > lnx-419-rc3/Documentation/core-api/boot-time-mm.rst:78: ERROR: Error in > "kernel-doc" directive: > unknown option: "nodocs". > > .. kernel-doc::

Re: [PATCH 2/2] MAINTAINERS: add i2c to the excludes for Documentation

On Fri, 7 Sep 2018 12:30:22 +0200 Wolfram Sang wrote: > I'll handle these myself but thanks for providing the fallback! > > Signed-off-by: Wolfram Sang > --- > MAINTAINERS | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/MAINTAINERS b/MAINTAINERS > index 2698ee553008..39c39dd6fba6

Re: [PATCH 19/19] mtd: rawnand: Move JEDEC code to nand_jedec.c

On Fri, 7 Sep 2018 10:40:44 +0200 Ladislav Michl wrote: > Hi Boris, > > this patchseries is really amazing clean up. Thank you! I'm glad I'm not the only one to find it useful :-). > > On Fri, Sep 07, 2018 at 12:38:51AM +0200, Boris Brezillon wrote: > > This moves ONFI related code to

Re: [PATCH 19/19] mtd: rawnand: Move JEDEC code to nand_jedec.c

Hi Boris, this patchseries is really amazing clean up. Thank you! On Fri, Sep 07, 2018 at 12:38:51AM +0200, Boris Brezillon wrote: > This moves ONFI related code to nand_onfi.c and ONFI related > struct/macros to include/linux/mtd/onfi.h. Seems above commit log comes from previous patch.

Re: Italian translations and broken links

On Fri, 24 Aug 2018 13:51:18 +0200 Federico Vaga wrote: > Since there are many documents, this take time and perhaps we can already > push > the ones which are ready. > > My big dilemma is (which is more general): what about broken references? Do > we > keep broken links which we know they

Re: Italian translations and broken links

Answer to this email address, I did a mistake :) On Friday, August 24, 2018 1:51:18 PM CEST Federico Vaga wrote: > Hi Jon, > > just one question about how do you prefer us to proceed. We are translating > the process directory. > My idea was to complete it and then push it. This because the

Re: [PATCH v2 0/5] FireWire: clean up kernel-doc, add Documentation chapter

On 06/16/2018 04:55 PM, Randy Dunlap wrote: > On 04/15/2018 07:10 PM, Takashi Sakamoto wrote: >> Hi, >> >> On Apr 14 2018 10:27, Randy Dunlap wrote: >>> This patch series cleans up kernel-doc warnings in several >>> FireWire source files and then adds a Documentation driver-api >>> chapter for

Re: [PATCH] Remove gendered language from management style documentation

On Tue, 7 Aug 2018 19:47:51 +0100 Fox Foster wrote: > This small commit replaces gendered pronouns for neutral ones. > > Signed-off-by: Fox Foster Applied, thanks. jon

Re: [PATCH v2] scripts/kernel-doc: Escape all literal braces in regexes

On Sun, 5 Aug 2018 17:41:09 +0100 Ben Hutchings wrote: > Commit 720ac2ef479d ("PATCH scripts/kernel-doc") fixed the two > instances of literal braces that Perl 5.28 warns about, but there are > still more than it doesn't warn about. > > Escape all left braces that are treated as literal

Re: Bug#905116: [PATCH v2] scripts/kernel-doc: Escape all literal braces in regexes

On Mon, 2018-08-06 at 07:14 -0600, Jonathan Corbet wrote: > On Sun, 5 Aug 2018 17:41:09 +0100 > Ben Hutchings wrote: > > > Commit 720ac2ef479d ("PATCH scripts/kernel-doc") fixed the two > > instances of literal braces that Perl 5.28 warns about, but there are > > still more than it doesn't warn

Re: [PATCH v2] scripts/kernel-doc: Escape all literal braces in regexes

On Sun, 5 Aug 2018 17:41:09 +0100 Ben Hutchings wrote: > Commit 720ac2ef479d ("PATCH scripts/kernel-doc") fixed the two > instances of literal braces that Perl 5.28 warns about, but there are > still more than it doesn't warn about. So where can I find this commit of which you speak? I can't

Re: [PATCH v1] doc: translation for block queue into Chinese

On Fri, 27 Jul 2018 10:41:19 +0800 Norman wrote: > Translate block/queue-sysfs.txt into Chinese > > Signed-off-by: Norman Kern Unfortunately, this patch has been white-space mangled by your mailer. Please fix your mailer (Documentation/process/email-clients.rst has useful hints to that end)

Re: [PATCH] zh_CN:translation for block queue into Chinese

Hi, Jonathan I didn't mean to translate it into markdown, I just feel it looks better in markdown. I pay more attention on the contents but not the format and I just want to translate all block module docs into Chinese. I'll convert the format into plain text format and resend. Thanks for your

Re: [PATCH] zh_CN:translation for block queue into Chinese

On Fri, 20 Jul 2018 10:27:06 +0800 Norman wrote: > Translate block/queue-sysfs.txt into Chinese > > Signed-off-by: Norman Kern > --- >  .../translations/zh_CN/block/queue-sysfs.md    | 205 > + So...are you translating this into markdown format? Please don't do that,

Re: [RFC PATCH 00/13] ext4: major documentation surgery

On Sat, Jul 21, 2018 at 11:19:54AM -0700, Darrick J. Wong wrote: > > I pondered that -- maybe leave all the ext4 stuff clustered together, > but link to it from the actual user/admin guide section? > Yeah, I think it makes keep the ext4 (and in the future, xfs, btrfs, f2fs, etc.) files clustered

Re: [RFC PATCH 00/13] ext4: major documentation surgery

On Sat, Jul 21, 2018 at 10:19:46AM -0400, Theodore Y. Ts'o wrote: > On Tue, Jul 10, 2018 at 10:16:42AM -0700, Darrick J. Wong wrote: > > Hi all, > > > > This series converts the existing in-kernel ext4 documentation to rst > > format, links it in with the rest of the kernel's rst documetation,

RE: MY NAME IS MRS BELLA YOSTIN MOHAMMAD

Hello Dear. My Name is Mrs. Bella Yostin Mohammad, I got your contact from a business directory search and I decided to contact you directly. well am originally from South Africa, but based in London, i am searching for a reliable and honest and understanding person to go into partnership in

Re: [RFC PATCH 00/13] ext4: major documentation surgery

On Tue, Jul 10, 2018 at 10:16:42AM -0700, Darrick J. Wong wrote: > Hi all, > > This series converts the existing in-kernel ext4 documentation to rst > format, links it in with the rest of the kernel's rst documetation, and > then begins pulling in the contents of the on-disk layout page in the >

  1   2   3   4   5   6   7   8   9   10   >