Great renaming: use "series" instead of "family".

This is for greater consistency with the ST application notes, which
refer to migrating "across" series (e.g. F1 to F2), but compatibility
"within" a family (e.g. F1).

So:

- Move libmaple/stm32x/include/family to .../include/series/ and fix
  up includes appropriately.
- Refer to "family" headers as "series" headers in comments.
- Make similar "find and replace"-style changes to build system
  variable names and comments.
- Move support/ld/stm32/family to .../stm32/series.

Signed-off-by: Marti Bolivar <mbolivar@leaflabs.com>

1 files changed, 3 insertions, 3 deletions

diff --git a/libmaple/include/libmaple/rcc.h b/libmaple/include/libmaple/rcc.h
index a4b66e5..08f7c7e 100644
--- a/libmaple/include/libmaple/rcc.h
+++ b/libmaple/include/libmaple/rcc.h
@@ -37,9 +37,9 @@ extern "C"{
 #endif
 
 #include <libmaple/libmaple_types.h>
-#include <family/rcc.h>
+#include <series/rcc.h>
 
-/* Note: Beyond the usual (registers, etc.), it's up to the family
+/* Note: Beyond the usual (registers, etc.), it's up to the series
  * header to define the following types:
  *
  * - rcc_pllsrc: For each PLL source (passed to rcc_clk_init()).
@@ -49,7 +49,7 @@ extern "C"{
  * - rcc_clk_id: For each available peripheral. These are widely used
  *   as unique IDs (TODO extricate from RCC?). Peripherals which are
  *   common across families should use the same token for their
- *   rcc_clk_id in each family header.
+ *   rcc_clk_id in each series header.
  *
  * - rcc_clk_domain: For each clock domain (returned by rcc_dev_clk()).
  *