On Wed, Sep 21, 2016 at 06:51:13PM -0600, Shuah Khan wrote:
> Move pcmcia crc32hash tool from Documentation to tools/pcmcia and
> remove it from Documentation Makefile. Update location information
> for this tool. Create a new Makefile to build pcmcia. It can be built
> from top level directory or
Move accounting tool to tools and remove it from Documentation
Makefile. Update location information for this tool. Create a
new Makefile to build accounting. It can be built from top level
directory or from accounting directory:
Run make -C tools/accounting or cd tools/accounting; make
Signed-of
Move laptops dslm tool to tools/laptop/dslm and remove it from
Documentation Makefile. Update location information for this
tool. Create a new Makefile to build dslm. It can be built
from top level directory or from laptops directory:
Run make -C tools/laptop/dslm or cd tools/laptop/dslm; make
Si
Move runnable tools from Documentation to tools. I moved just the
tools code, and left documentation files as is.
Based on the v1 series feedback, This v2 series moves accounting,
laptops/dslm, and pcmcia to tools.
If v2 patches look good, and if I get an okay, I will try to get
these into 4.9-rc
Move pcmcia crc32hash tool from Documentation to tools/pcmcia and
remove it from Documentation Makefile. Update location information
for this tool. Create a new Makefile to build pcmcia. It can be built
from top level directory or from pcmcia directory:
Run make -C tools/pcmcia or cd tools/pcmcia;
On 09/21/2016 02:59 AM, Mike Galbraith wrote:
On Tue, 2016-09-20 at 09:42 -0400, Waiman Long wrote:
This patch introduces a new futex implementation called
throughput-optimized (TO) futexes.
nit: 'TO' sounds way too much like timeout... TP? You even use 'to' as
shorthand for timeout in the nex
On Tue, Sep 20, 2016 at 2:08 AM, Jesper Dangaard Brouer
wrote:
> Hi all,
>
> As promised, I've started documenting the XDP eXpress Data Path):
>
> [1]
> https://prototype-kernel.readthedocs.io/en/latest/networking/XDP/index.html
>
> IMHO the documentation have reached a stage where it is useful
On Wed, 2016-09-21 at 15:54 -0600, Jonathan Corbet wrote:
> Recent discussion has made it clear that there is no community consensus
> on this particular rule. Remove it now, lest it inspire yet another set
> of unwanted "cleanup" patches.
Thanks. I believe it's better to remove this one too.
--
On Wed, Sep 21, 2016 at 08:13:37PM +0530, Aneesh Kumar K.V wrote:
So we are looking at two step online process here. The above explained
the details nicely. Can you capture these details in the commit message. ie,
to say that when using 'echo online-movable > state' we allow the move from
normal
Recent discussion has made it clear that there is no community consensus
on this particular rule. Remove it now, lest it inspire yet another set
of unwanted "cleanup" patches.
This partially reverts 865a1caa4b6b (CodingStyle: Clarify and complete
chapter 7).
Cc: Jean Delvare
Signed-off-by: Jona
Shuah Khan wrote:
> Move timers examples to samples and remove it from Documentation
> Makefile. Create a new Makefile to build timers. It can be built
> from top level directory or from timers directory:
>
> Run make -C samples/timers or cd samples/timers; make
>
> Acked-by: Jonathan Corbet
> Sig
On Wed, 21 Sep 2016 08:51:05 -0300
Mauro Carvalho Chehab wrote:
> Add cross references for the development process documents
> that were converted to ReST:
> Documentation/SubmitChecklist
> Documentation/SubmittingDrivers
> Documentation/SubmittingPatches
> Documentation/d
On Wed, 21 Sep 2016 07:49:18 -0300
Mauro Carvalho Chehab wrote:
> As this file is mentioned at the development-process/ book,
> let's convert it to ReST markup.
Applied, thanks.
jon
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majord...@vge
>
> Move misc-devices/mei examples to samples/mei and remove it from
> Documentation Makefile. Delete misc-devices/Makefile.
>
> Create a new Makefile to build samples/mei. It can be built from top level
> directory or from mei directory:
>
> Run make -C samples/mei or cd samples/mei; make
>
>
On Wed, 21 Sep 2016 13:47:29 -0600
Shuah Khan wrote:
> Move runnable examples code from Documentation to samples. I moved
> just the example code, and left documentation files as is.
>
> I dropped accounting, laptops, and pcmcia from this v2 series as per
> the v1 feedback on these being a bette
On Wed, Sep 21, 2016 at 01:47:30PM -0600, Shuah Khan wrote:
> Move misc-devices/mei examples to samples/mei and remove it from
> Documentation Makefile. Delete misc-devices/Makefile.
>
> Create a new Makefile to build samples/mei. It can be built from top
> level directory or from mei directory:
>
Move watchdog examples to samples and remove it from Documentation
Makefile. Create a new Makefile to build watchdog. It can be built
from top level directory or from watchdog directory:
Run make -C samples/watchdog or cd samples/watchdog; make
Signed-off-by: Shuah Khan
---
Documentation/Makefi
Move auxdisplay examples to samples and remove it from Documentation
Makefile. Create a new Makefile to build auxdisplay. It can be built
from top level directory or from auxdisplay directory:
Run make -C samples/auxdisplay or cd samples/auxdisplay; make
Signed-off-by: Shuah Khan
---
Documentat
Move misc-devices/mei examples to samples/mei and remove it from
Documentation Makefile. Delete misc-devices/Makefile.
Create a new Makefile to build samples/mei. It can be built from top
level directory or from mei directory:
Run make -C samples/mei or cd samples/mei; make
Acked-by: Jonathan Co
Move runnable examples code from Documentation to samples. I moved
just the example code, and left documentation files as is.
I dropped accounting, laptops, and pcmcia from this v2 series as per
the v1 feedback on these being a better fit under tools. I will send
a separate v2 for them.
If v2 pat
Move timers examples to samples and remove it from Documentation
Makefile. Create a new Makefile to build timers. It can be built
from top level directory or from timers directory:
Run make -C samples/timers or cd samples/timers; make
Acked-by: Jonathan Corbet
Signed-off-by: Shuah Khan
---
Doc
Hi Tejun,
On Wed, Sep 21, 2016 at 7:56 PM, Tejun Heo wrote:
> Hello, Parav.
>
> On Wed, Sep 21, 2016 at 10:13:38AM +0530, Parav Pandit wrote:
>> We have completed review from Tejun, Christoph.
>> HFI driver folks also provided feedback for Intel drivers.
>> Matan's also doesn't have any more comm
Reza Arbab writes:
> On Wed, Sep 21, 2016 at 12:39:51PM +0530, Aneesh Kumar K.V wrote:
>>What I was checking was how will one mark a node movable in ppc64 ? I
>>don't see ppc64 code doing the equivalent of memblock_mark_hotplug().
>
> Post boot, the marking mechanism is not necessary. You can cre
Hello, Parav.
On Wed, Sep 21, 2016 at 10:13:38AM +0530, Parav Pandit wrote:
> We have completed review from Tejun, Christoph.
> HFI driver folks also provided feedback for Intel drivers.
> Matan's also doesn't have any more comments.
>
> If possible, if you can also review, it will be helpful.
>
On Wed, Sep 21, 2016 at 08:51:05AM -0300, Mauro Carvalho Chehab wrote:
> Add cross references for the development process documents
> that were converted to ReST:
> Documentation/SubmitChecklist
> Documentation/SubmittingDrivers
> Documentation/SubmittingPatches
> Documentat
On Wed, Sep 21, 2016 at 12:39:51PM +0530, Aneesh Kumar K.V wrote:
What I was checking was how will one mark a node movable in ppc64 ? I
don't see ppc64 code doing the equivalent of memblock_mark_hotplug().
Post boot, the marking mechanism is not necessary. You can create a
movable node by putt
> The original style was correct, the new style is wrong.
I find your feedback interesting for further clarifications.
> Multi-line indents get curly braces for readability.
How do you think about to transform such an information
into an official specification for the the document "CodingStyle"
Add cross references for the development process documents
that were converted to ReST:
Documentation/SubmitChecklist
Documentation/SubmittingDrivers
Documentation/SubmittingPatches
Documentation/development-process/development-process.rst
Documentation/stabl
As this file is mentioned at the development-process/ book,
let's convert it to ReST markup.
Signed-off-by: Mauro Carvalho Chehab
---
This one corresponds to patch 27/29 of the last patch series. Changes:
- Removed all the rename stuff from it
- Clean up bare :: lines
Documentation/email-clie
Em Tue, 20 Sep 2016 18:56:45 -0600
Jonathan Corbet escreveu:
> On Tue, 20 Sep 2016 08:36:29 -0300
> Mauro Carvalho Chehab wrote:
>
> > This patch series update the kernel-docs.txt file, removing broken links,
> > adding
> > newer ones and ordering documents in published date.
>
> OK, I'm st
Em Tue, 20 Sep 2016 18:44:54 -0600
Jonathan Corbet escreveu:
> On Mon, 19 Sep 2016 08:07:34 -0300
> Mauro Carvalho Chehab wrote:
>
> > That's the 4th version of this series. It also contains a second patch
> > series
> > with more ReST conversions and documentation improvements.
> > This patch
On Tue, 20 Sep 2016 19:47:07 -0700
Alexei Starovoitov wrote:
> On Tue, Sep 20, 2016 at 11:08:44AM +0200, Jesper Dangaard Brouer via
> iovisor-dev wrote:
> > Hi all,
> >
> > As promised, I've started documenting the XDP eXpress Data Path):
> >
> > [1]
> > https://prototype-kernel.readthedocs.
Reza Arbab writes:
> On Mon, Sep 19, 2016 at 11:59:35AM +0530, Aneesh Kumar K.V wrote:
>>Movable node also does.
>> memblock_set_bottom_up(true);
>>What is the impact of that. Do we need changes equivalent to that ? Also
>>where are we marking the nodes which can be hotplugged, ie where do w
33 matches
Mail list logo
