Skip to content

Conversation

@ulfalizer
Copy link
Contributor

@ulfalizer ulfalizer commented Mar 13, 2019

Maybe this is some "just in case" thing that got copied around. There's
no need to have a blank line at the beginning or end of Kconfig files.

@ulfalizer ulfalizer force-pushed the kconfig-blank-lines branch 3 times, most recently from 2e71e10 to 4e3ebbf Compare March 13, 2019 07:30
@ulfalizer ulfalizer added area: Kconfig Trivial Changes that can be reviewed by anyone, i.e. doc changes, minor build system tweaks, etc. labels Mar 13, 2019
Copy link
Member

@aescolar aescolar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In my case it wasn't a "just in case" but a "just copy paste and replace" :)

@ulfalizer ulfalizer force-pushed the kconfig-blank-lines branch from 4e3ebbf to a88d01e Compare March 13, 2019 08:05
@ulfalizer ulfalizer changed the title Kconfig: Remove blank lines at beginning of files Kconfig: Remove blank lines at the beginning/end of files Mar 13, 2019
@ulfalizer
Copy link
Contributor Author

Checked the ends now too. Intense nitting.

Copy link
Contributor

@avisconti avisconti left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

seems good. Thx!

@codecov-io
Copy link

codecov-io commented Mar 13, 2019

Codecov Report

Merging #14452 into master will increase coverage by 0.13%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master   #14452      +/-   ##
==========================================
+ Coverage   51.98%   52.12%   +0.13%     
==========================================
  Files         308      308              
  Lines       45505    45523      +18     
  Branches    10543    10552       +9     
==========================================
+ Hits        23655    23728      +73     
+ Misses      17050    16990      -60     
- Partials     4800     4805       +5
Impacted Files Coverage Δ
boards/posix/nrf52_bsim/bstests_entry.c 57.6% <0%> (-3.27%) ⬇️
drivers/clock_control/nrf_power_clock.c 50% <0%> (-2.11%) ⬇️
ext/hal/nordic/nrfx/hal/nrf_rng.h 100% <0%> (ø) ⬆️
kernel/sched.c 84.32% <0%> (+0.31%) ⬆️
drivers/timer/nrf_rtc_timer.c 92.53% <0%> (+0.6%) ⬆️
boards/posix/nrf52_bsim/trace_hook.c 48.78% <0%> (+4.87%) ⬆️
boards/posix/nrf52_bsim/time_machine.c 55.73% <0%> (+8.19%) ⬆️
drivers/entropy/entropy_nrf5.c 89.9% <0%> (+13.71%) ⬆️
drivers/timer/sys_clock_init.c 15.38% <0%> (+15.38%) ⬆️
boards/posix/nrf52_bsim/argparse.c 46.98% <0%> (+15.66%) ⬆️
... and 1 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ebc4e83...af6245d. Read the comment docs.

@ulfalizer ulfalizer force-pushed the kconfig-blank-lines branch from a88d01e to af6245d Compare March 13, 2019 09:18
Maybe this is some "just in case" thing that got copied around. There's
no need to have a blank line at the beginning or end of Kconfig files.

Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
@ulfalizer ulfalizer force-pushed the kconfig-blank-lines branch from af6245d to 9675040 Compare March 13, 2019 11:23
@galak galak merged commit 5337639 into zephyrproject-rtos:master Mar 13, 2019
ulfalizer added a commit to ulfalizer/zephyr that referenced this pull request Mar 18, 2019
This one got away in
zephyrproject-rtos#14452. Didn't spot
there were two blank lines.

Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
galak pushed a commit that referenced this pull request Mar 26, 2019
This one got away in
#14452. Didn't spot
there were two blank lines.

Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: Kconfig Trivial Changes that can be reviewed by anyone, i.e. doc changes, minor build system tweaks, etc.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

10 participants