Re: [PATCH v3 4/5] powerpc/mm: restore top-down allocation when using movable_node

[Balbir Singh]

On 27/09/16 10:14, Reza Arbab wrote:
> On Tue, Sep 27, 2016 at 07:12:31AM +1000, Benjamin Herrenschmidt wrote:
>> In any case, if the memory hasn't been hotplug, this shouldn't be necessary 
>> as we shouldn't be considering it for allocation.
> 
> Right. To be clear, the background info I put in the commit log refers to 
> x86, where the SRAT can describe movable nodes which exist at boot.  They're 
> trying to avoid allocations from those nodes before they've been identified.
> 
> On power, movable nodes can only exist via hotplug, so that scenario can't 
> happen. We can immediately go back to top-down allocation. That is the 
> missing call being added in the patch.
> 

Can we fix cmdline_parse_movable_node() to do the right thing? I suspect that
code is heavily x86 only in the sense that no other arch needs it.

Balbir Singh.
--
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  http://vger.kernel.org/majordomo-info.html

[PULL] Documentation for 4.9

[Jonathan Corbet]

[Note you'll get a small conflict with
Documentation/sphinx-static/theme_overrides.css; just take the docs-4.9
side.  That's entirely the result of me still figuring out the best
fix-vs-features workflow, shouldn't happen again.]

The following changes since commit
29b4817d4018df78086157ea3a55c1d9424a7cfc:

  Linux 4.8-rc1 (2016-08-07 18:18:00 -0700)

are available in the git repository at:

  git://git.lwn.net/linux.git tags/docs-4.9

for you to fetch changes up to 3c76ff4765fbd382c095acc37f87e136a8dfc73d:

  URL changed for Linux Foundation TAB (2016-10-01 00:57:13 -0600)


This is the documentation update pull for the 4.9 merge window.

The Sphinx transition is still creating a fair amount of work.  Here we
have a number of fixes and, importantly, a proper PDF output solution,
thanks to Jani Nikula, Mauro Carvalho Chehab and Markus Heiser.

I've started a couple of new books: a driver API book (based on the old
device-drivers.tmpl) and a development tools book.  Both are meant to show
how we can integrate together our existing documentation into a more
coherent and accessible whole.  It involves moving some stuff around and
formatting changes, but, I think, the results are worth it.  The good news
is that most of our existing Documentation/*.txt files are *almost* in RST
format already; the amount of messing around required is minimal.

And, of course, there's the usual set of updates, typo fixes, and more.


Andi Shyti (1):
  Documentation: clk: update file names containing referenced structures

Andrey Smirnov (1):
  Documentation: DMA-API-HOWTO: Fix a typo

Baoquan He (1):
  docs: kernel-parameter: Improve the description of nr_cpus and maxcpus

Christoph Hellwig (1):
  DMA-API-HOWTO:  is no more

David A. Long (1):
  Documentation: kprobes: Document jprobes stack copying limitations

Eugeniu Rosca (1):
  kconfig-language: improve menuconfig usage description

Finn Thain (1):
  documentation/scsi: Remove nodisconnect parameter

Icenowy Zheng (1):
  Documentation: sunxi: Update Allwinner SoC documentation

Jani Nikula (3):
  Documentation/sphinx: build the media intermediate rst files for all 
outputs
  Documentation: switch to pdflatex for pdf generation
  Documentation: exclude media documentation from pdf generation

Jean Delvare (1):
  CodingStyle: Clarify and complete chapter 7

Joe Perches (1):
  CodingStyle: Remove "Don't use C99-style comments"

Jon Bailey (1):
  URL changed for Linux Foundation TAB

Jonathan Corbet (22):
  Merge branch 'xelatex' into doc/4.9
  docs: create a new dev-tools directory
  docs: sphinxify coccinelle.txt and add it to dev-tools
  docs: sphinxify sparse.txt and move to dev-tools
  docs: sphinxify kcov.txt and move to dev-tools
  docs: sphinixfy gcov.txt and move to dev-tools
  docs: sphinxify kasan.txt and move to dev-tools
  docs: sphinxify ubsan.txt and move it to dev-tools
  docs: sphinxify kmemleak.txt and move it to dev-tools
  docs: sphinxify kmemcheck.txt and move to dev-tools
  docs: Sphinxify gdb-kernel-debugging.txt and move to dev-tools
  Merge branch 'dev-tools' into doc/4.9
  Docs: sphinxify device-drivers.tmpl
  docs: split up the driver book
  docs: make kernel-doc handle varargs properly
  docs: Special-case function-pointer parameters in kernel-doc
  docs: Pull the HSI documentation together
  docs: split up serial-interfaces.rst
  docs: Don't format internal MPT docs
  Merge branch 'driver-api' into doc/4.9
  docs: Clean up bare :: lines
  docs: Remove space-before-label guidance from CodingStyle

Laura Abbott (2):
  mm, kasan: Update kasan docs to indicate arm64 support
  doc: ioctl: Add some clarifications to botching-up-ioctls

Laurent Navet (1):
  docs/driver-model: fix typo

Lorenzo Stoakes (1):
  x86: fix memory ranges in mm documentation

Markus Heiser (16):
  doc-rst: generic way to build only sphinx sub-folders
  doc-rst: add stand-alone conf.py to media folder
  doc-rst: add media/conf_nitpick.py
  doc-rst: add stand-alone conf.py to gpu folder
  doc-rst: add docutils config file
  doc-rst: add index to sub-folders
  doc-rst: add boilerplate to customize c-domain
  doc-rst:c-domain: ref-name of a function declaration
  doc-rst: moved *duplicate* warnings to nitpicky mode
  doc-rst: Revert "kernel-doc: fix handling of address_space tags"
  doc-rst: migrate ioctl CEC_DQEVENT to c-domain
  docs: sphinx-extensions: add metadata parallel-safe
  doc-rst: generic way to build PDF of sub-folders
  doc-rst: define PDF's of the media folder
  doc-rst:c-domain: fix sphinx version incompatibility
  doc-rst:c-domain: function-like macros arguments

Mauro Carvalho Chehab (55):
  docs-rst: fix a breakage 

[kselftest:next 19/20] htmldocs: scripts/Makefile.build:44: Documentation/Makefile: No such file or directory

[kbuild test robot]

tree:   
https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git next
head:   94c630ee73a4a1db18561511dfefc2e41d2e6d1e
commit: c6d2995da5409e3d0ef30c53287d3c17e450e96e [19/20] samples: move blackfin 
gptimers-example from Documentation
reproduce: make htmldocs

All errors (new ones prefixed by >>):

>> scripts/Makefile.build:44: Documentation/Makefile: No such file or directory
>> make[2]: *** No rule to make target 'Documentation/Makefile'.
   make[2]: Failed to remake makefile 'Documentation/Makefile'.

vim +44 scripts/Makefile.build

f77bf0142 Sam Ravnborg 2007-10-15  28  ldflags-y  :=
d72e5edbf Sam Ravnborg 2007-05-28  29  
720097d89 Sam Ravnborg 2009-04-19  30  subdir-asflags-y :=
720097d89 Sam Ravnborg 2009-04-19  31  subdir-ccflags-y :=
720097d89 Sam Ravnborg 2009-04-19  32  
3156fd052 Robert P. J. Day 2008-02-18  33  # Read auto.conf if it exists, 
otherwise ignore
c955ccafc Roman Zippel 2006-06-08  34  -include include/config/auto.conf
^1da177e4 Linus Torvalds   2005-04-16  35  
20a468b51 Sam Ravnborg 2006-01-22  36  include scripts/Kbuild.include
20a468b51 Sam Ravnborg 2006-01-22  37  
3156fd052 Robert P. J. Day 2008-02-18  38  # For backward compatibility check 
that these variables do not change
0c53c8e6e Sam Ravnborg 2007-10-14  39  save-cflags := $(CFLAGS)
0c53c8e6e Sam Ravnborg 2007-10-14  40  
2a6914703 Sam Ravnborg 2005-07-25  41  # The filename Kbuild has precedence 
over Makefile
db8c1a7b2 Sam Ravnborg 2005-07-27  42  kbuild-dir := $(if $(filter 
/%,$(src)),$(src),$(srctree)/$(src))
0c53c8e6e Sam Ravnborg 2007-10-14  43  kbuild-file := $(if $(wildcard 
$(kbuild-dir)/Kbuild),$(kbuild-dir)/Kbuild,$(kbuild-dir)/Makefile)
0c53c8e6e Sam Ravnborg 2007-10-14 @44  include $(kbuild-file)
^1da177e4 Linus Torvalds   2005-04-16  45  
0c53c8e6e Sam Ravnborg 2007-10-14  46  # If the save-* variables changed 
error out
0c53c8e6e Sam Ravnborg 2007-10-14  47  ifeq ($(KBUILD_NOPEDANTIC),)
0c53c8e6e Sam Ravnborg 2007-10-14  48  ifneq 
("$(save-cflags)","$(CFLAGS)")
49c57d254 Arnaud Lacombe   2011-08-15  49  $(error CFLAGS was 
changed in "$(kbuild-file)". Fix it to use ccflags-y)
0c53c8e6e Sam Ravnborg 2007-10-14  50  endif
0c53c8e6e Sam Ravnborg 2007-10-14  51  endif
4a5838ad9 Borislav Petkov  2011-03-01  52  

:: The code at line 44 was first introduced by commit
:: 0c53c8e6eb456cde30f2305421c605713856abc8 kbuild: check for wrong use of 
CFLAGS

:: TO: Sam Ravnborg 
:: CC: Sam Ravnborg 

---
0-DAY kernel test infrastructureOpen Source Technology Center
https://lists.01.org/pipermail/kbuild-all   Intel Corporation


.config.gz
Description: application/gzip

Re: [PATCH v3 1/5] drivers/of: introduce of_fdt_is_available()

[Rob Herring]

On Sun, Sep 25, 2016 at 1:36 PM, Reza Arbab  wrote:
> In __fdt_scan_reserved_mem(), the availability of a node is determined
> by testing its "status" property.
>
> Move this check into its own function, borrowing logic from the
> unflattened version, of_device_is_available().
>
> Another caller will be added in a subsequent patch.
>
> Signed-off-by: Reza Arbab 
> ---
>  drivers/of/fdt.c   | 26 +++---
>  include/linux/of_fdt.h |  2 ++
>  2 files changed, 25 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/of/fdt.c b/drivers/of/fdt.c
> index 085c638..9241c6e 100644
> --- a/drivers/of/fdt.c
> +++ b/drivers/of/fdt.c
> @@ -151,6 +151,23 @@ int of_fdt_match(const void *blob, unsigned long node,
> return score;
>  }
>
> +bool of_fdt_is_available(const void *blob, unsigned long node)

of_fdt_device_is_available

[...]

> +bool __init of_flat_dt_is_available(unsigned long node)

And of_flat_dt_device_is_available

With that,

Acked-by: Rob Herring 
--
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  http://vger.kernel.org/majordomo-info.html

[PATCH 7/7] vgacon: remove prehistoric macros

[Jiri Slaby]

These macros:
* CAN_LOAD_EGA_FONTS
* CAN_LOAD_PALETTE
* TRIDENT_GLITCH
* VGA_CAN_DO_64KB
* SLOW_VGA
are either always set or always unset. They come from the linux 2.1
times. And given nobody switched them to some configurable options, I
assume nobody actually uses them.

So remove the macros and leave in place appropriate branches of the
conditional code.

Signed-off-by: Jiri Slaby 
Cc: Tomi Valkeinen 
Cc: 
Cc: 
---
 Documentation/VGA-softcursor.txt | 12 --
 drivers/video/console/vgacon.c   | 49 
 2 files changed, 5 insertions(+), 56 deletions(-)

diff --git a/Documentation/VGA-softcursor.txt b/Documentation/VGA-softcursor.txt
index 70acfbf399eb..2ea8968b64a6 100644
--- a/Documentation/VGA-softcursor.txt
+++ b/Documentation/VGA-softcursor.txt
@@ -2,13 +2,11 @@ Software cursor for VGAby Pavel Machek 

 ===and Martin Mares 
 
Linux now has some ability to manipulate cursor appearance. Normally, you
-can set the size of hardware cursor (and also work around some ugly bugs in
-those miserable Trident cards--see #define TRIDENT_GLITCH in drivers/video/
-vgacon.c). You can now play a few new tricks:  you can make your cursor look
-like a non-blinking red block, make it inverse background of the character it's
-over or to highlight that character and still choose whether the original
-hardware cursor should remain visible or not.  There may be other things I have
-never thought of.
+can set the size of hardware cursor. You can now play a few new tricks:  you
+can make your cursor look like a non-blinking red block, make it inverse
+background of the character it's over or to highlight that character and still
+choose whether the original hardware cursor should remain visible or not.
+There may be other things I have never thought of.
 
The cursor appearance is controlled by a "[?1;2;3c" escape sequence
 where 1, 2 and 3 are parameters described below. If you omit any of them,
diff --git a/drivers/video/console/vgacon.c b/drivers/video/console/vgacon.c
index d13d5d372604..c22a56232b7c 100644
--- a/drivers/video/console/vgacon.c
+++ b/drivers/video/console/vgacon.c
@@ -60,15 +60,6 @@ static struct vgastate vgastate;
 
 #define BLANK 0x0020
 
-#define CAN_LOAD_EGA_FONTS /* undefine if the user must not do this */
-#define CAN_LOAD_PALETTE   /* undefine if the user must not do this */
-
-/* You really do _NOT_ want to define this, unless you have buggy
- * Trident VGA which will resize cursor when moving it between column
- * 15 & 16. If you define this and your VGA is OK, inverse bug will
- * appear.
- */
-#undef TRIDENT_GLITCH
 #define VGA_FONTWIDTH   8   /* VGA does not support fontwidths != 8 */
 /*
  *  Interface used by the world
@@ -157,18 +148,10 @@ static inline void write_vga(unsigned char reg, unsigned 
int val)
 * handlers, thus the write has to be IRQ-atomic.
 */
raw_spin_lock_irqsave(_lock, flags);
-
-#ifndef SLOW_VGA
v1 = reg + (val & 0xff00);
v2 = reg + 1 + ((val << 8) & 0xff00);
outw(v1, vga_video_port_reg);
outw(v2, vga_video_port_reg);
-#else
-   outb_p(reg, vga_video_port_reg);
-   outb_p(val >> 8, vga_video_port_val);
-   outb_p(reg + 1, vga_video_port_reg);
-   outb_p(val & 0xff, vga_video_port_val);
-#endif
raw_spin_unlock_irqrestore(_lock, flags);
 }
 
@@ -426,18 +409,6 @@ static const char *vgacon_startup(void)
request_resource(_resource,
 _console_resource);
 
-#ifdef VGA_CAN_DO_64KB
-   /*
-* get 64K rather than 32K of video RAM.
-* This doesn't actually work on all "VGA"
-* controllers (it seems like setting MM=01
-* and COE=1 isn't necessarily a good idea)
-*/
-   vga_vram_base = 0xa;
-   vga_vram_size = 0x1;
-   outb_p(6, VGA_GFX_I);
-   outb_p(6, VGA_GFX_D);
-#endif
/*
 * Normalise the palette registers, to point
 * the 16 screen colours to the first 16
@@ -627,11 +598,6 @@ static void vgacon_set_cursor_size(int xpos, int from, int 
to)
unsigned long flags;
int curs, cure;
 
-#ifdef TRIDENT_GLITCH
-   if (xpos < 16)
-   from--, to--;
-#endif
-
if ((from == cursor_size_lastfrom) && (to == cursor_size_lastto))
return;
cursor_size_lastfrom = from;
@@ -833,12 +799,10 @@ static void vga_set_palette(struct vc_data *vc, const 

[PATCH] regulator/overview.txt: Use ".." for ranges, instead of "->"

[Pavel Machek]

Using "->" to indicate range is not too common, switch to ".."

Signed-off-by: Pavel Machek 

--- a/Documentation/power/regulator/overview.txt
+++ b/Documentation/power/regulator/overview.txt
@@ -90,7 +90,7 @@ Some terms used in this document:-
operating parameters and is specified in the regulator
datasheet. i.e.
 
- - voltage output is in the range 800mV -> 3500mV.
+ - voltage output is in the range 800mV .. 3500mV.
  - regulator current output limit is 20mA @ 5V but is
10mA @ 10V.
 
@@ -99,8 +99,8 @@ Some terms used in this document:-
power domain to a particular power range. i.e.
 
  - Domain-1 voltage is 3300mV
- - Domain-2 voltage is 1400mV -> 1600mV
- - Domain-3 current limit is 0mA -> 20mA.
+ - Domain-2 voltage is 1400mV .. 1600mV
+ - Domain-3 current limit is 0mA .. 20mA.
 
Consumer Level: This is defined by consumer drivers
dynamically setting voltage or current limit levels.

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) 
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html


signature.asc
Description: Digital signature

kernel-doc

[Julia Lawall]

Hello,

I have the inpression that not all comments on specific functions are
using the following notation:

function_name() - Brief description of function.

They are good about using the -, but some don't have the () after the
function name and others (perhaps only one subsystem) have the function
name in all uppercase letters.  Do these issues break anything?

julia
--
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  http://vger.kernel.org/majordomo-info.html