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 >

[PATCH] zh_CN:translation for block queue into Chinese

Translate block/queue-sysfs.txt into Chinese Signed-off-by: Norman Kern ---  .../translations/zh_CN/block/queue-sysfs.md    | 205 +  1 file changed, 205 insertions(+)  create mode 100644 Documentation/translations/zh_CN/block/queue-sysfs.md diff --git

Re: Sphinx version dependencies?

On Thu, Jul 19, 2018 at 02:15:56PM -0400, Theodore Y. Ts'o wrote: > Darrick has sent in patches to convert the ext4 documentation to use > rst and to be built as part of the full kernel documentation thanks. > In addition to that, he's imported the on-disk documentation from the > ext4 wiki into

Sphinx version dependencies?

Darrick has sent in patches to convert the ext4 documentation to use rst and to be built as part of the full kernel documentation thanks. In addition to that, he's imported the on-disk documentation from the ext4 wiki into the kernel sources, so hopefully we can keep it more up to date. When I

Re: [RFC]:Involved in Linux doc translation for Chinese

On Thu, 19 Jul 2018 18:20:52 +0800 Norman wrote: > 'Documentation/translations/'  has been discarded or not ? I found few > translations there :( It certainly has not been discarded. But it also cannot grow in the absence of contributions from interested developers — I certainly can't fill it

Re: [RFC]:Involved in Linux doc translation for Chinese

Hi, Jonathan 'Documentation/translations/'  has been discarded or not ? I found few translations there :( On 2018年07月19日 15:53, Norman wrote: Hi Harry, I have been a Linux kernel developer for several years, and I like it so much。 I spent much time on reading source codes, and I found

[RFC]:Involved in Linux doc translation for Chinese

Hi Harry, I have been a Linux kernel developer for several years, and I like it so much。 I spent much time on reading source codes, and I found many documents haven't been translated into Chinese, so I make a plan to translate all documents into Chinese to make others easily know the

Business Offer.

Greetings, Please I decided to contact you about this Business Offer. Please If you are not interested, ignore this mail and if you are interested please reply me and i will give you more information. Thanks, Peter Achilleos -- To unsubscribe from this list: send the line "unsubscribe linux-doc"

Proposal

Hello I have a business proposal of mutual benefits i would like to discuss with you i asked before and i still await your positive response thanks -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majord...@vger.kernel.org More majordomo info

[patch] printk format for u16 and u8

diff --git a/Documentation/printk-formats.txt b/Documentation/printk-formats.txt index 361789d..d878079 100644 --- a/Documentation/printk-formats.txt +++ b/Documentation/printk-formats.txt @@ -14,6 +14,7 @@ Integer types If variable is of Type,use printk format specifier:

Hello Beautiful

Hi Dear, my name is Jack and i am seeking for a relationship in which i will feel loved after a series of failed relationships. I am hoping that you would be interested and we could possibly get to know each other more if you do not mind. I am open to answering questions from you as i think

Product Inquiry

Hello Sir's greets Am Nguyễn Chaewon director of Golik Holdings Limited in HONGKONG We'd like to request the latest about the Newest Design,High Quality of your products Please send the latest quotation to us.As we have these signed contract from customer in Spain. what is the lead time

Re: [PATCH REPOST] libata: remove ata_sff_data_xfer_noirq()

On Wed, Jul 11, 2018 at 05:21:05PM +0200, Sebastian Andrzej Siewior wrote: > ata_sff_data_xfer_noirq() is invoked via the ->sff_data_xfer hook. The > latter is invoked by ata_pio_sector(), atapi_send_cdb() and > __atapi_pio_bytes() which in turn is invoked by ata_sff_hsm_move(). > The latter

[PATCH REPOST] libata: remove ata_sff_data_xfer_noirq()

ata_sff_data_xfer_noirq() is invoked via the ->sff_data_xfer hook. The latter is invoked by ata_pio_sector(), atapi_send_cdb() and __atapi_pio_bytes() which in turn is invoked by ata_sff_hsm_move(). The latter function requires that the "ap->lock" lock is held which needs to be taken with disabled

Re: [PATCH] Documentation : Update relay function types

On Sun, 8 Jul 2018 20:19:32 +0200 Yohan Pipereau wrote: > This patch updates two callback functions provided as an example in > relay API documentation : subbuf_start and create_buf_file_handler. > > These functions were using older and incorrect types causing an > "initialization from

info!!

Top of the day to you, this is in respect of a very beneficial transaction which you would not want to let go reply for more details, Regards, Lee -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majord...@vger.kernel.org More majordomo info at

[PATCH] Documentation : Update relay function types

This patch updates two callback functions provided as an example in relay API documentation : subbuf_start and create_buf_file_handler. These functions were using older and incorrect types causing an "initialization from incompatible pointer type". diffstat for this patch is: relay.txt |4

Re: [PATCH 1/2] fs: Fix attr.c kernel-doc

On Tue, Jul 03, 2018 at 08:08:34AM -0700, Matthew Wilcox wrote: > A couple of minor warnings. Both patches applied... -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majord...@vger.kernel.org More majordomo info at

[PATCH 2/2] fs: Add more kernel-doc to the produced documentation

People have gone to all the effort of writing kernel-doc for these functions; the least we can do is put them in the "Other functions" part of the VFS documentation. Signed-off-by: Matthew Wilcox --- Documentation/filesystems/index.rst | 33 + 1 file changed, 33

[PATCH 1/2] fs: Fix attr.c kernel-doc

A couple of minor warnings. Signed-off-by: Matthew Wilcox --- fs/attr.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/fs/attr.c b/fs/attr.c index e3d53bf12240..d22e8187477f 100644 --- a/fs/attr.c +++ b/fs/attr.c @@ -120,7 +120,6 @@ EXPORT_SYMBOL(setattr_prepare); *

Re: [PATCH v3 1/2] Documentation/sphinx: allow "functions" with no parameters

On Sat, 30 Jun 2018 17:59:27 +0300 Mike Rapoport wrote: > > > > Is this the right syntax? Should we rather have: > > > > .. kernel-doc:: lib/idr.c > >:functions: * > > IMHO :functions: with no parameters is simpler. What I would really like to have there, actually, is a regex

Re: [PATCH v3 1/2] Documentation/sphinx: allow "functions" with no parameters

On Sat, Jun 30, 2018 at 04:21:56AM -0700, Matthew Wilcox wrote: > On Sat, Jun 30, 2018 at 12:05:10AM +0300, Mike Rapoport wrote: > > @@ -488,14 +488,19 @@ doc: *title* > > .. kernel-doc:: drivers/gpu/drm/i915/intel_audio.c > > :doc: High Definition Audio over HDMI and Display Port > >

Re: [PATCH v3 0/2] Documentation/sphinx: add kind of "nodocs" directive

On Fri, 29 Jun 2018 15:07:34 -0600 Jonathan Corbet wrote: > > These patches allow passing "-no-doc-sections" option to scripts/kernel-doc > > from the sphinx generator. > > > > This allows to avoid duplicated DOC: sections when "kernel-doc:" directive > > is used without explicit selection of

Re: [PATCH v3 1/2] Documentation/sphinx: allow "functions" with no parameters

On Sat, Jun 30, 2018 at 12:05:10AM +0300, Mike Rapoport wrote: > @@ -488,14 +488,19 @@ doc: *title* > .. kernel-doc:: drivers/gpu/drm/i915/intel_audio.c > :doc: High Definition Audio over HDMI and Display Port > > -functions: *function* *[...]* > +functions: *[ function ...]* >

Re: [PATCH v3 0/2] Documentation/sphinx: add kind of "nodocs" directive

On Sat, 30 Jun 2018 00:05:09 +0300 Mike Rapoport wrote: > These patches allow passing "-no-doc-sections" option to scripts/kernel-doc > from the sphinx generator. > > This allows to avoid duplicated DOC: sections when "kernel-doc:" directive > is used without explicit selection of functions or

[PATCH v3 0/2] Documentation/sphinx: add kind of "nodocs" directive

Hi, These patches allow passing "-no-doc-sections" option to scripts/kernel-doc from the sphinx generator. This allows to avoid duplicated DOC: sections when "kernel-doc:" directive is used without explicit selection of functions or function types. For instance, [1] has "IDA description" and

[PATCH v3 1/2] Documentation/sphinx: allow "functions" with no parameters

When kernel-doc:: specified in .rst document without explicit directives, it outputs both comment and DOC: sections. If a DOC: section was explicitly included in the same document it will be duplicated. For example, the output generated for Documentation/core-api/idr.rst [1] has "IDA description"

[PATCH v3 2/2] docs/idr: use empty "functions" directive

to avoid duplication of DOC: sections in the middle of the API reference. Signed-off-by: Mike Rapoport Acked-by: Matthew Wilcox --- Documentation/core-api/idr.rst | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Documentation/core-api/idr.rst b/Documentation/core-api/idr.rst index

Re: [PATCH v2 1/2] Documentation/sphinx: allow "functions" with no parameters

On Wed, 20 Jun 2018 11:49:12 +0300 Mike Rapoport wrote: > > Looks good to me. Though I do realize now that I overlooked that this > > applies to not only functions, but also to other non-DOC documentation > > comments. I guess up to Jon to decide. > > We can name it

Re: [PATCH v2 1/2] Documentation/sphinx: allow "functions" with no parameters

On Wed, Jun 20, 2018 at 10:19:36AM +0300, Jani Nikula wrote: > On Wed, 20 Jun 2018, Mike Rapoport wrote: > > When kernel-doc:: specified in .rst document without explicit directives, > > it outputs both comment and DOC: sections. If a DOC: section was explicitly > > included in the same document

Re: [PATCH v2 1/2] Documentation/sphinx: allow "functions" with no parameters

On Wed, 20 Jun 2018, Mike Rapoport wrote: > When kernel-doc:: specified in .rst document without explicit directives, > it outputs both comment and DOC: sections. If a DOC: section was explicitly > included in the same document it will be duplicated. For example, the > output generated for

[PATCH v2 2/2] docs/idr: use empty "functions" directive

to avoid duplication of DOC: sections in the middle of the API reference. Signed-off-by: Mike Rapoport Acked-by: Matthew Wilcox --- Documentation/core-api/idr.rst | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Documentation/core-api/idr.rst b/Documentation/core-api/idr.rst index

[PATCH v2 1/2] Documentation/sphinx: allow "functions" with no parameters

When kernel-doc:: specified in .rst document without explicit directives, it outputs both comment and DOC: sections. If a DOC: section was explicitly included in the same document it will be duplicated. For example, the output generated for Documentation/core-api/idr.rst [1] has "IDA description"

[PATCH v2 0/2] Documentation/sphinx: add kind of "nodocs" directive

Hi, These patches allow passing "-no-doc-sections" option to scripts/kernel-doc from the sphinx generator. This allows to avoid duplicated DOC: sections when "kernel-doc:" directive is used without explicit selection of functions or function types. For instance, [1] has "IDA description" and

Re: [PATCH 0/2] Documentation/sphinx: add "nodocs" directive

On Tue, Jun 19, 2018 at 07:11:56AM -0700, Matthew Wilcox wrote: > On Mon, Jun 18, 2018 at 10:10:28AM -0700, Matthew Wilcox wrote: > > On Mon, Jun 18, 2018 at 04:36:34PM +0300, Mike Rapoport wrote: > > > Hi, > > > > > > These patches allow passing "-no-doc-sections" option to > > >

Re: [PATCH 0/2] Documentation/sphinx: add "nodocs" directive

On Mon, Jun 18, 2018 at 10:10:28AM -0700, Matthew Wilcox wrote: > On Mon, Jun 18, 2018 at 04:36:34PM +0300, Mike Rapoport wrote: > > Hi, > > > > These patches allow passing "-no-doc-sections" option to scripts/kernel-doc > > from the sphinx generator. > > > > This allows to avoid duplicated DOC:

Re: [PATCH 1/2] Documentation/sphinx: add "nodocs" directive

On Tue, Jun 19, 2018 at 11:09:42AM +0300, Jani Nikula wrote: > On Tue, 19 Jun 2018, Mike Rapoport wrote: > > On Tue, Jun 19, 2018 at 10:29:20AM +0300, Jani Nikula wrote: > >> On Tue, 19 Jun 2018, Mike Rapoport wrote: > >> > On Mon, Jun 18, 2018 at 11:01:32PM +0300, Jani Nikula wrote: > >> >> On

Re: [PATCH 1/2] Documentation/sphinx: add "nodocs" directive

On Tue, 19 Jun 2018, Mike Rapoport wrote: > On Tue, Jun 19, 2018 at 10:29:20AM +0300, Jani Nikula wrote: >> On Tue, 19 Jun 2018, Mike Rapoport wrote: >> > On Mon, Jun 18, 2018 at 11:01:32PM +0300, Jani Nikula wrote: >> >> On Mon, 18 Jun 2018, Mike Rapoport wrote: >> >> > When kernel-doc::

Re: [PATCH 1/2] Documentation/sphinx: add "nodocs" directive

On Tue, Jun 19, 2018 at 10:29:20AM +0300, Jani Nikula wrote: > On Tue, 19 Jun 2018, Mike Rapoport wrote: > > On Mon, Jun 18, 2018 at 11:01:32PM +0300, Jani Nikula wrote: > >> On Mon, 18 Jun 2018, Mike Rapoport wrote: > >> > When kernel-doc:: specified in .rst document without explicit

Re: [PATCH 1/2] Documentation/sphinx: add "nodocs" directive

On Tue, 19 Jun 2018, Mike Rapoport wrote: > On Mon, Jun 18, 2018 at 11:01:32PM +0300, Jani Nikula wrote: >> On Mon, 18 Jun 2018, Mike Rapoport wrote: >> > When kernel-doc:: specified in .rst document without explicit directives, >> > it outputs both comment and DOC: sections. If a DOC: section

Re: [PATCH 1/2] Documentation/sphinx: add "nodocs" directive

On Mon, Jun 18, 2018 at 11:01:32PM +0300, Jani Nikula wrote: > On Mon, 18 Jun 2018, Mike Rapoport wrote: > > When kernel-doc:: specified in .rst document without explicit directives, > > it outputs both comment and DOC: sections. If a DOC: section was explictly > > included in the same document

Re: [PATCH 1/2] Documentation/sphinx: add "nodocs" directive

On Mon, 18 Jun 2018, Mike Rapoport wrote: > When kernel-doc:: specified in .rst document without explicit directives, > it outputs both comment and DOC: sections. If a DOC: section was explictly > included in the same document it will be duplicated. For example, the > output generated for

Re: [PATCH 0/2] Documentation/sphinx: add "nodocs" directive

On Mon, Jun 18, 2018 at 04:36:34PM +0300, Mike Rapoport wrote: > Hi, > > These patches allow passing "-no-doc-sections" option to scripts/kernel-doc > from the sphinx generator. > > This allows to avoid duplicated DOC: sections when "kernel-doc:" directive > is used without explicit selection of

[PATCH 2/2] docs/idr: use "nodocs" directive

to avoid duplication of DOC: sections in the middle of the API reference. Signed-off-by: Mike Rapoport --- Documentation/core-api/idr.rst | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Documentation/core-api/idr.rst b/Documentation/core-api/idr.rst index 9078a5c..15eadf8 100644 ---

[PATCH 0/2] Documentation/sphinx: add "nodocs" directive

Hi, These patches allow passing "-no-doc-sections" option to scripts/kernel-doc from the sphinx generator. This allows to avoid duplicated DOC: sections when "kernel-doc:" directive is used without explicit selection of functions or function types. For instance, [1] has "IDA description" and

[PATCH 1/2] Documentation/sphinx: add "nodocs" directive

When kernel-doc:: specified in .rst document without explicit directives, it outputs both comment and DOC: sections. If a DOC: section was explictly included in the same document it will be duplicated. For example, the output generated for Documentation/core-api/idr.rst [1] has "IDA description"

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

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 FireWire. >> >> [PATCH v3 1/5] FireWire: clean up

Re: [PATCH RESEND] Documentation: filesystems: update filesystem locking documentation

On Tue, Jun 05, 2018 at 03:46:37PM -0400, Sean Anderson wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > > Your mission, should you choose to accept it, shall be to locate > > the old sig regarding the usual reaction to use of > > Quoted-Printable... > > > > IOW, fix your mail

Re: [PATCH RESEND] Documentation: filesystems: update filesystem locking documentation

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 > Your mission, should you choose to accept it, shall be to locate > the old sig regarding the usual reaction to use of > Quoted-Printable... > > IOW, fix your mail setup. Applied, but. Not sure what you mean by "Quoted-Printable"... Is PGP/MIME

Re: [PATCH] doc: update description of ceph mount option

On Mon, Jun 4, 2018 at 2:10 PM, Chengguang Xu wrote: > Based on code, default value of rsize/wsize is 16 MB. > > Signed-off-by: Chengguang Xu > --- > Documentation/filesystems/ceph.txt | 8 +++- > 1 file changed, 3 insertions(+), 5 deletions(-) > > diff --git

[PATCH] doc: update description of ceph mount option

Based on code, default value of rsize/wsize is 16 MB. Signed-off-by: Chengguang Xu --- Documentation/filesystems/ceph.txt | 8 +++- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/Documentation/filesystems/ceph.txt b/Documentation/filesystems/ceph.txt index

Ltd.

山东凌邦天翔电子科技（北京凌邦山东营销中心）优势。在这一步中，企业通过研究以上

Re: [PATCH] docs/vm: move ksm and transhuge from "user" to "internals" section.

On Tue, 29 May 2018 13:13:38 +0300 Mike Rapoport wrote: > After the userspace interface description for KSM and THP was split to > Documentation/admin-guide/mm, the remaining parts belong to the section > describing MM internals. > > Signed-off-by: Mike Rapoport Applied, thanks. jon -- To

[PATCH] docs/vm: move ksm and transhuge from "user" to "internals" section.

After the userspace interface description for KSM and THP was split to Documentation/admin-guide/mm, the remaining parts belong to the section describing MM internals. Signed-off-by: Mike Rapoport --- Documentation/vm/index.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff

Re: doc: Italian translation

On Monday, 28 May 2018 15:08:28 CEST Jonathan Corbet wrote: > On Sun, 27 May 2018 16:55:55 +0200 > > Federico Vaga wrote: > > here the doc-guide translated in Italian. This set of patches > > includes some minor changes to the main one. The idea of this > > first set of

Re: doc: Italian translation

On Sun, 27 May 2018 16:55:55 +0200 Federico Vaga wrote: > here the doc-guide translated in Italian. This set of patches includes > some minor changes to the main one. The idea of this first set of patches > is also to adjust the structure and our expectations. I've

Re: [PATCH v8 3/6] cpuset: Add cpuset.sched.load_balance flag to v2

On Thu, May 24, 2018 at 02:55:25PM -0400, Waiman Long wrote: > On 05/24/2018 11:43 AM, Peter Zijlstra wrote: > > I'm confused... why exactly do we have both domain and load_balance ? > > The domain is for partitioning the CPUs only. It doesn't change the load > balancing state. So the

Re: [PATCH v2 1/3] usb: gadget: ccid: add support for USB CCID Gadget Device

W dniu 28.05.2018 o 11:32, Marcus Folkesson pisze: > Hi Andrzej, > > Thank you for reviewing. > > On Mon, May 28, 2018 at 11:12:27AM +0200, Andrzej Pietrasiewicz wrote: >> W dniu 28.05.2018 o 10:38, Marcus Folkesson pisze: >>> Hi Andrzej, >>> >>> On Mon, May 28, 2018 at 09:04:51AM +0200, Andrzej

Re: [PATCH v2 1/3] usb: gadget: ccid: add support for USB CCID Gadget Device

Hi Andrzej, Thank you for reviewing. On Mon, May 28, 2018 at 11:12:27AM +0200, Andrzej Pietrasiewicz wrote: > W dniu 28.05.2018 o 10:38, Marcus Folkesson pisze: > > Hi Andrzej, > > > > On Mon, May 28, 2018 at 09:04:51AM +0200, Andrzej Pietrasiewicz wrote: > >> Mi Marcus, > >> > >> W dniu

Re: [PATCH v2 1/3] usb: gadget: ccid: add support for USB CCID Gadget Device

W dniu 28.05.2018 o 10:38, Marcus Folkesson pisze: > Hi Andrzej, > > On Mon, May 28, 2018 at 09:04:51AM +0200, Andrzej Pietrasiewicz wrote: >> Mi Marcus, >> >> W dniu 26.05.2018 o 23:19, Marcus Folkesson pisze: >>> Chip Card Interface Device (CCID) protocol is a USB protocol that >>> allows a

[RFT v3 2/4] perf script python: Add addr into perf sample dict

ARM CoreSight auxtrace uses 'sample->addr' to record the target address for branch instructions, so the data of 'sample->addr' is required for tracing data analysis. This commit collects data of 'sample->addr' into perf sample dict, finally can be used for python script for parsing event.

[RFT v3 3/4] perf script python: Add script for CoreSight trace disassembler

This commit adds python script to parse CoreSight tracing event and use command 'objdump' for disassembled lines, finally we can generate readable program execution flow for reviewing tracing data. The script receives CoreSight tracing packet with below format:

[RFT v3 4/4] coresight: Document for CoreSight trace disassembler

This commit documents CoreSight trace disassembler usage and gives example for it. Signed-off-by: Leo Yan --- Documentation/trace/coresight.txt | 52 +++ 1 file changed, 52 insertions(+) diff --git a/Documentation/trace/coresight.txt

[RFT v3 0/4] Perf script: Add python script for CoreSight trace disassembler

This patch series is to support for using 'perf script' for CoreSight trace disassembler, for this purpose this patch series adds a new python script to parse CoreSight tracing event and use command 'objdump' for disassembled lines, finally this can generate readable program execution flow for

[RFT v3 1/4] perf cs-etm: Generate branch sample for missed packets

Commit e573e978fb12 ("perf cs-etm: Inject capabilitity for CoreSight traces") reworks the samples generation flow from CoreSight trace to match the correct format so Perf report tool can display the samples properly. But the change has side effect for branch packet handling, it only generate

Re: [PATCH v2 1/3] usb: gadget: ccid: add support for USB CCID Gadget Device

Hi Andrzej, On Mon, May 28, 2018 at 09:04:51AM +0200, Andrzej Pietrasiewicz wrote: > Mi Marcus, > > W dniu 26.05.2018 o 23:19, Marcus Folkesson pisze: > > Chip Card Interface Device (CCID) protocol is a USB protocol that > > allows a smartcard device to be connected to a computer via a card > >

Re: [PATCH v2 2/3] Documentation: usb: add documentation for USB CCID Gadget Device

Hi Randy, On Sun, May 27, 2018 at 04:36:24PM -0700, Randy Dunlap wrote: > Hi, > > I have a few documentation comments below... > > On 05/26/2018 02:19 PM, Marcus Folkesson wrote: > > Add documentation to give a brief description on how to use the > > CCID Gadget Device. > > This includes a

Re: [PATCH v2 1/3] usb: gadget: ccid: add support for USB CCID Gadget Device

Mi Marcus, W dniu 26.05.2018 o 23:19, Marcus Folkesson pisze: > Chip Card Interface Device (CCID) protocol is a USB protocol that > allows a smartcard device to be connected to a computer via a card > reader using a standard USB interface, without the need for each manufacturer > of smartcards to

Re: [PATCH v2 2/3] Documentation: usb: add documentation for USB CCID Gadget Device

Hi, I have a few documentation comments below... On 05/26/2018 02:19 PM, Marcus Folkesson wrote: > Add documentation to give a brief description on how to use the > CCID Gadget Device. > This includes a description for all attributes followed by an example on > how to setup the device with

[PATCH 4/5] doc:it_IT: add doc-guide translation

Signed-off-by: Federico Vaga Signed-off-by: Alessia Mantegazza --- .../translations/it_IT/doc-guide/hello.dot | 3 + .../translations/it_IT/doc-guide/index.rst | 24 ++ .../translations/it_IT/doc-guide/kernel-doc.rst| 402

[PATCH 3/5] doc: add Italian translation skeleton

Signed-off-by: Federico Vaga Signed-off-by: Alessia Mantegazza --- Documentation/index.rst| 8 ++ .../translations/it_IT/disclaimer-ita.rst | 11 +++ Documentation/translations/it_IT/index.rst |

[PATCH 2/5] doc: add chapter labels

The idea is to make it easier to create references (doc-guide does the same). Signed-off-by: Federico Vaga --- Documentation/index.rst| 2 ++ Documentation/kernel-hacking/index.rst | 2 ++ 2 files changed, 4 insertions(+) diff --git

[PATCH 1/5] doc: typos and minor fixes

Signed-off-by: Federico Vaga --- Documentation/doc-guide/kernel-doc.rst| 2 +- Documentation/doc-guide/parse-headers.rst | 4 ++-- Documentation/doc-guide/sphinx.rst| 4 ++-- Documentation/index.rst | 2 +-

doc: Italian translation

Ciao Jonathan, here the doc-guide translated in Italian. This set of patches includes some minor changes to the main one. The idea of this first set of patches is also to adjust the structure and our expectations. We tried to translate everything in **Italian**; which means that we avoided

Re: [PATCH 1/3] usb: gadget: ccid: add support for USB CCID Gadget Device

On Sun, May 27, 2018 at 07:48:47AM +0200, Marcus Folkesson wrote: > On Sat, May 26, 2018 at 10:56:52PM +0200, Greg Kroah-Hartman wrote: > > On Sat, May 26, 2018 at 10:33:59PM +0200, Marcus Folkesson wrote: > > > Signed-off-by: Marcus Folkesson > > > > I can't take

Re: [PATCH 1/3] usb: gadget: ccid: add support for USB CCID Gadget Device

On Sat, May 26, 2018 at 10:56:52PM +0200, Greg Kroah-Hartman wrote: > On Sat, May 26, 2018 at 10:33:59PM +0200, Marcus Folkesson wrote: > > Signed-off-by: Marcus Folkesson > > I can't take patches without any changelog text. And why would you > submit a patch over

[PATCH v2 2/3] Documentation: usb: add documentation for USB CCID Gadget Device

Add documentation to give a brief description on how to use the CCID Gadget Device. This includes a description for all attributes followed by an example on how to setup the device with ConfigFS. Signed-off-by: Marcus Folkesson --- Documentation/usb/gadget_ccid.rst |

[PATCH v2 1/3] usb: gadget: ccid: add support for USB CCID Gadget Device

Chip Card Interface Device (CCID) protocol is a USB protocol that allows a smartcard device to be connected to a computer via a card reader using a standard USB interface, without the need for each manufacturer of smartcards to provide its own reader or protocol. This gadget driver makes Linux

[PATCH v2 3/3] MAINTAINERS: add USB CCID Gadget Device

Add MAINTAINERS entry for USB CCID Gadget Device Signed-off-by: Marcus Folkesson --- MAINTAINERS | 8 1 file changed, 8 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 078fd80f664f..e77c3d2bec89 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@

Re: [PATCH 1/3] usb: gadget: ccid: add support for USB CCID Gadget Device

On Sat, May 26, 2018 at 10:33:59PM +0200, Marcus Folkesson wrote: > Signed-off-by: Marcus Folkesson I can't take patches without any changelog text. And why would you submit a patch over 1000 lines without any? Please fix. thanks, greg k-h -- To unsubscribe from

[PATCH 3/3] MAINTAINERS: add USB CCID Gadget Device

Add MAINTAINERS entry for USB CCID Gadget Device Signed-off-by: Marcus Folkesson --- MAINTAINERS | 8 1 file changed, 8 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 078fd80f664f..e77c3d2bec89 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@

[PATCH 1/3] usb: gadget: ccid: add support for USB CCID Gadget Device

Signed-off-by: Marcus Folkesson --- drivers/usb/gadget/Kconfig | 17 + drivers/usb/gadget/function/Makefile | 1 + drivers/usb/gadget/function/f_ccid.c | 988 +++ drivers/usb/gadget/function/f_ccid.h | 91

[PATCH 2/3] Documentation: usb: add documentation for USB CCID Gadget Device

Signed-off-by: Marcus Folkesson --- Documentation/usb/gadget_ccid.rst | 267 ++ 1 file changed, 267 insertions(+) create mode 100644 Documentation/usb/gadget_ccid.rst diff --git a/Documentation/usb/gadget_ccid.rst

Re: [PATCH RESEND] Documentation: filesystems: update filesystem locking documentation

On Wed, May 23, 2018 at 10:29:10PM -0400, Sean Anderson wrote: > Documentation/filesystems/Locking no longer reflects current locking > semantics. i_mutex is no longer used for locking, and has been superseded > by i_rwsem. Additionally, ->iterate_shared() was not documented. Your mission, should

Re: [PATCH bpf-next v2 0/3] bpf: add boot parameters for sysctl knobs

On Fri, May 25, 2018 at 06:50:09PM +0200, Eugene Syromiatnikov wrote: > On Thu, May 24, 2018 at 04:34:51PM -0700, Alexei Starovoitov wrote: > > On Thu, May 24, 2018 at 09:41:08AM +0200, Jesper Dangaard Brouer wrote: > > > On Wed, 23 May 2018 15:02:45 -0700 > > > Alexei Starovoitov

Re: [PATCH V3 2/6] hwmon: Add support for RPi voltage sensor

On Fri, May 25, 2018 at 09:24:35PM +0200, Stefan Wahren wrote: > Currently there is no easy way to detect undervoltage conditions on a > remote Raspberry Pi. This hwmon driver retrieves the state of the > undervoltage sensor via mailbox interface. The handling based on > Noralf's modifications to

[PATCH V3 5/6] ARM: multi_v7_defconfig: Enable RPi voltage sensor

The patch enables the hwmon driver for the Raspberry Pi. Signed-off-by: Stefan Wahren --- arch/arm/configs/multi_v7_defconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm/configs/multi_v7_defconfig b/arch/arm/configs/multi_v7_defconfig index

[PATCH V3 3/6] firmware: raspberrypi: Register hwmon driver

Since the raspberrypi-hwmon driver is tied to the VC4 firmware instead of particular hardware its registration should be in the firmware driver. Signed-off-by: Stefan Wahren --- drivers/firmware/raspberrypi.c | 19 +++ 1 file changed, 19 insertions(+)

[PATCH V3 2/6] hwmon: Add support for RPi voltage sensor

Currently there is no easy way to detect undervoltage conditions on a remote Raspberry Pi. This hwmon driver retrieves the state of the undervoltage sensor via mailbox interface. The handling based on Noralf's modifications to the downstream firmware driver. In case of an undervoltage condition

[PATCH V3 4/6] ARM: bcm2835_defconfig: Enable RPi voltage sensor

The patch enables the hwmon driver for the Raspberry Pi. Signed-off-by: Stefan Wahren --- arch/arm/configs/bcm2835_defconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm/configs/bcm2835_defconfig b/arch/arm/configs/bcm2835_defconfig index

[PATCH V3 1/6] ARM: bcm2835: Add GET_THROTTLED firmware property

Recent Raspberry Pi firmware provides a mailbox property to detect under-voltage conditions. Here is the current definition. The u32 value returned by the firmware is divided into 2 parts: - lower 16-bits are the live value - upper 16-bits are the history or sticky value Bits: 0:

[PATCH V3 6/6] arm64: defconfig: Enable RPi voltage sensor

The patch enables the hwmon driver for the Raspberry Pi. Signed-off-by: Stefan Wahren --- arch/arm64/configs/defconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig index 3299505..e5c7198 100644 ---

[PATCH V3 0/6] hwmon: Add support for Raspberry Pi voltage sensor

A common issue for the Raspberry Pi is an inadequate power supply. Noralf Trønnes started a discussion [1] about writing such undervoltage conditions into the kernel log. Changes in V3: - rebase - simplify probing Changes in V2: - simplified Kconfig dependency suggested by Robin Murphy -

[PATCH v3 0/6] arm64: untag user pointers passed to the kernel

arm64 has a feature called Top Byte Ignore, which allows to embed pointer tags into the top byte of each pointer. Userspace programs (such as HWASan, a memory debugging tool [1]) might use this feature and pass tagged user pointers to the kernel through syscalls or other interfaces. This patch

[PATCH v3 1/6] arm64: add type casts to untagged_addr macro

This patch makes the untagged_addr macro accept all kinds of address types (void *, unsigned long, etc.) and allows not to specify type casts in each place where it is used. This is done by using __typeof__. Signed-off-by: Andrey Konovalov ---

[PATCH v3 3/6] arm64: untag user addresses in access_ok and __uaccess_mask_ptr

copy_from_user (and a few other similar functions) are used to copy data from user memory into the kernel memory or vice versa. Since a user can provided a tagged pointer to one of the syscalls that use copy_from_user, we need to correctly handle such pointers. Do this by untagging user pointers

[PATCH v3 4/6] mm, arm64: untag user addresses in mm/gup.c

mm/gup.c provides a kernel interface that accepts user addresses and manipulates user pages directly (for example get_user_pages, that is used by the futex syscall). Here we also need to handle the case of tagged user pointers. Add untagging to gup.c functions that use user pointers for vma

[PATCH v3 5/6] lib, arm64: untag addrs passed to strncpy_from_user and strnlen_user

strncpy_from_user and strnlen_user accept user addresses as arguments, and do not go through the same path as copy_from_user and others, so here we need to handle the case of tagged user addresses separately. Untag user pointers passed to these functions. Signed-off-by: Andrey Konovalov

[PATCH v3 6/6] arm64: update Documentation/arm64/tagged-pointers.txt

Add a note that work on passing tagged user pointers to the kernel via syscalls has started, but might not be complete yet. Signed-off-by: Andrey Konovalov --- Documentation/arm64/tagged-pointers.txt | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git

[PATCH v3 2/6] uaccess: add untagged_addr definition for other arches

To allow arm64 syscalls accept tagged pointers from userspace, we must untag them when they are passed to the kernel. Since untagging is done in generic parts of the kernel (like the mm subsystem), the untagged_addr macro should be defined for all architectures. Define it as a noop for other

<    1   2   3   4   5   6   7   8   9   10   >