Skip to content

Merge lwip 2.0.2 stable #4814

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Aug 10, 2017
Merged

Merge lwip 2.0.2 stable #4814

merged 3 commits into from
Aug 10, 2017

Conversation

mikaleppanen
Copy link

Description

Merged lwIP 2.0.2 release to mbed OS. See http://savannah.nongnu.org/projects/lwip.
Added contributing.md with instructions how to integrate lwIP release to mbed OS
tree structure.

Tested with following combinations:
mbed-os-example-client application: ipv4 ethernet, ipv6 ethernet and ipv4 wlan.
mbed-os-cellular-example application: ipv4

Status

READY

Migrations

NO

Related PRs

None

Todos

  • Tests
  • Documentation

Deploy notes

None

Mika Leppänen added 2 commits July 24, 2017 13:17
…f93f4..7648b58

git-subtree-dir: features/FEATURE_LWIP/lwip-interface/lwip
git-subtree-split: 7648b58d03006bd60b9592f1853c167bf52b0193
* commit '7bbc850309fed8bf63017821f18aff03bca9233b':
  Squashed 'features/FEATURE_LWIP/lwip-interface/lwip/' changes from 10f93f4..7648b58
@mikaleppanen
Copy link
Author

@peknis01 please review the contributing.md.

@0xc0170
Copy link
Contributor

0xc0170 commented Jul 26, 2017

@mikaleppanen Thanks for the document describing the lwip update process 👍

@AnotherButler Please review the contributing document.

@theotherjimmy theotherjimmy changed the title Merged lwip 2.0.2 stable Merge lwip 2.0.2 stable Jul 27, 2017
Copy link
Contributor

@AnotherButler AnotherButler left a comment

Choose a reason for hiding this comment

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

@0xc0170 I've left my suggested changes. Please note that most of them involve adding articles and changing passive to active voice.

After this step there should be a new commit visible is mbed OS master branch that contains
the changes.

4. Verify that changes in new commit are correct, create a new branch push branch to your mbed-os fork for github review.
Copy link
Contributor

Choose a reason for hiding this comment

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

  • Please change "new commit" to "the new commit".
  • Please change "create" to "and create".
  • Please put "mbed-os" in code format.
  • Please capitalize the "g" and "h" in "GitHub".

Copy link
Author

Choose a reason for hiding this comment

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

Corrected.


`e.g. git subtree pull --squash -P features/FEATURE_LWIP/lwip-interface/lwip lwip-fork mbed-os-lwip-stable-2_0_2-prefixed -m "Merged lwip 2.0.2 stable"`

After this step there should be a new commit visible is mbed OS master branch that contains
Copy link
Contributor

Choose a reason for hiding this comment

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

  • Please add a comma after "step".
  • Please change "should be" to "is".
  • Please change "is mbed" to "in mbed".
  • Please change "master branch" to "the master branch".

Copy link
Contributor

Choose a reason for hiding this comment

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

This implies that you want "in mbed OS the master branch". I think " in the mbed OS master branch" is the more common form.

Copy link
Author

Choose a reason for hiding this comment

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

Corrected.

# Description

This document describes how to update mbed OS lwip stack. Mbed OS lwip stack is a copy of
lwip master repository. Stack is located in `FEATURE_LWIP/lwip-interface/lwip` directory.
Copy link
Contributor

Choose a reason for hiding this comment

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

Please put all paragraphs on one line because they don't always render properly when they're split like this.

Copy link
Author

Choose a reason for hiding this comment

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

Corrected.


`e.g. git fetch lwip-fork`

3. Do subtree pull for lwip prefixed branch in mbed OS root directory.
Copy link
Contributor

Choose a reason for hiding this comment

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

  • Please change "subtree pull" to "a subtree pull".
  • Please either capitalize "LWIP" to put it in code format.
  • Please change "mbed OS root directory" to "the mbed OS root directory".

Copy link
Author

Choose a reason for hiding this comment

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

Corrected.


`git clone [email protected]:ARMmbed/mbed-os.git`

2. Go to mbed OS root directory and add mbed OS lwip fork repository as remote. Fetch branches from fork.
Copy link
Contributor

Choose a reason for hiding this comment

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

  • Please change "mbed OS root directory" to "the mbed OS root directory".
  • Please add comma after "directory".
  • Please change "mbed OS lwip fork repository" to "the mbed OS LWIP fork repository".

Copy link
Author

Choose a reason for hiding this comment

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

Corrected.

fetched via mbed OS lwip fork repository. Repository is used to rename lwip source files
with `lwip_` prefix to make then compatible with mbed OS build system.

* Lwip master repository is under lwip project (<https://git.savannah.nongnu.org/git/lwip.git>).
Copy link
Contributor

Choose a reason for hiding this comment

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

Please change to "The LWIP master repository is part of the LWIP project."

Copy link
Author

Choose a reason for hiding this comment

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

Corrected.


When new releases or single commits are added from lwip master repository they need to be
fetched via mbed OS lwip fork repository. Repository is used to rename lwip source files
with `lwip_` prefix to make then compatible with mbed OS build system.
Copy link
Contributor

Choose a reason for hiding this comment

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

  • Please change "lwip_ prefix" to "the lwip_ prefix".
  • Please change "then" to "them".
  • Please change "mbed OS" to "the mbed OS".

Copy link
Author

Choose a reason for hiding this comment

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

Corrected.

This document describes how to update mbed OS lwip stack. Mbed OS lwip stack is a copy of
lwip master repository. Stack is located in `FEATURE_LWIP/lwip-interface/lwip` directory.

When new releases or single commits are added from lwip master repository they need to be
Copy link
Contributor

Choose a reason for hiding this comment

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

Please change the first sentence to "When you add new releases or single commits from the LWIP master repository, you must fetch them using the mbed OS LWIP fork repository."

Copy link
Author

Choose a reason for hiding this comment

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

Corrected.

lwip master repository. Stack is located in `FEATURE_LWIP/lwip-interface/lwip` directory.

When new releases or single commits are added from lwip master repository they need to be
fetched via mbed OS lwip fork repository. Repository is used to rename lwip source files
Copy link
Contributor

Choose a reason for hiding this comment

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

Please change start of second sentence to "Use the repository to rename LWIP source files".

Copy link
Author

Choose a reason for hiding this comment

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

Corrected.

@@ -0,0 +1,129 @@
# Description

This document describes how to update mbed OS lwip stack. Mbed OS lwip stack is a copy of
Copy link
Contributor

Choose a reason for hiding this comment

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

  • Please change "mbed OS lwip stack" to "the mbed OS LWIP stack".
  • Please change the second sentence to "The mbed OS LWIP stack is a copy of the LWIP master repository."

Copy link
Author

Choose a reason for hiding this comment

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

Corrected.

@0xc0170
Copy link
Contributor

0xc0170 commented Jul 31, 2017

@mikaleppanen Any update to the review?

@mikaleppanen
Copy link
Author

Corrected CONTRIBUTING.md review defects.

@0xc0170
Copy link
Contributor

0xc0170 commented Aug 2, 2017

Thanks @mikaleppanen

@AnotherButler All fine now?

Copy link
Contributor

@AnotherButler AnotherButler left a comment

Choose a reason for hiding this comment

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

Due to the new branding rollout that started yesterday, most instances of "mbed" need to change to "Mbed". Please note that some cases must remain lower case because they refer to the repo or other code. This is why I've called out all the instances that must change instead of suggesting you do a find and replace all.

I also left two minor comments not related to the new branding.

@0xc0170 I'm sorry we have to change this. I know y'all want to get this in quickly.


`e.g. git branch mbed-os-lwip-stable-2_0_2 STABLE-2_0_2_RELEASE_VER`

5. Push the branch to the mbed OS LWIP fork repository to keep the fork in sync.
Copy link
Contributor

Choose a reason for hiding this comment

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

I just noticed there are two 5s here. Please fix the numbering.

Copy link
Author

Choose a reason for hiding this comment

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

Corrected.


After this step, there is a new commit visible in the mbed OS master branch that contains the changes.

4. Verify that changes in the new commit are correct and create a new branch. Push the branch to your mbed OS fork for GitHub review.
Copy link
Contributor

Choose a reason for hiding this comment

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

Please add a comma after "correct" because two independent clauses connected by a coordinating conjunction require a comma after the first independent clause.

Copy link
Author

Choose a reason for hiding this comment

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

Corrected.

@@ -0,0 +1,118 @@
# Description

This document describes how to update the mbed OS LWIP stack. The mbed OS LWIP stack is a copy of the LWIP master repository. Stack is located in `FEATURE_LWIP/lwip-interface/lwip` directory.
Copy link
Contributor

Choose a reason for hiding this comment

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

Yesterday, Arm rolled out new branding guidelines. To reflect these changes please change "update the mbed OS" to update the Arm Mbed OS". In the second sentence, please change "mbed" to "Mbed".

Copy link
Author

Choose a reason for hiding this comment

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

Corrected.


This document describes how to update the mbed OS LWIP stack. The mbed OS LWIP stack is a copy of the LWIP master repository. Stack is located in `FEATURE_LWIP/lwip-interface/lwip` directory.

When you add new releases or single commits from the LWIP master repository, you must fetch them using the mbed OS LWIP fork repository. Use the repository to rename LWIP source files with the `lwip_` prefix to make them compatible with the mbed OS build system.
Copy link
Contributor

Choose a reason for hiding this comment

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

Please change "mbed" to "Mbed" both times in this line to reflect the new branding rollout.

Copy link
Author

Choose a reason for hiding this comment

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

Corrected.

When you add new releases or single commits from the LWIP master repository, you must fetch them using the mbed OS LWIP fork repository. Use the repository to rename LWIP source files with the `lwip_` prefix to make them compatible with the mbed OS build system.

* The LWIP master repository is part of the [LWIP project](https://savannah.nongnu.org/projects/lwip).
* The mbed OS LWIP fork repository is part of [ARMmbed](https://github.com/ARMmbed/lwip).
Copy link
Contributor

Choose a reason for hiding this comment

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

  • Please change "The mbed OS" to "The Mbed OS".
  • Please put "ARMmbed" in code format.

Copy link
Author

Choose a reason for hiding this comment

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

Corrected.


`e.g. git push origin mbed-os-lwip-stable-2_0_2-prefixed`

### Merging the prefixed release to the mbed OS repository
Copy link
Contributor

Choose a reason for hiding this comment

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

Please change "mbed" to "Mbed".

Copy link
Author

Choose a reason for hiding this comment

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

Corrected.


### Merging the prefixed release to the mbed OS repository

1. Clone the mbed OS repository.
Copy link
Contributor

Choose a reason for hiding this comment

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

Please change "mbed" to "Mbed".

Copy link
Author

Choose a reason for hiding this comment

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

Corrected.


`git clone [email protected]:ARMmbed/mbed-os.git`

2. Go to the mbed OS root directory, and add the mbed OS LWIP fork repository as remote. Fetch branches from fork.
Copy link
Contributor

Choose a reason for hiding this comment

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

Please change "mbed" to "Mbed" both times in this line.

Copy link
Author

Choose a reason for hiding this comment

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

Corrected.


`e.g. git fetch lwip-fork`

3. Do a subtree pull for LWIP prefixed branch in the mbed OS root directory.
Copy link
Contributor

Choose a reason for hiding this comment

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

Please change "mbed" to "Mbed".

Copy link
Author

Choose a reason for hiding this comment

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

Corrected.


`e.g. git subtree pull --squash -P features/FEATURE_LWIP/lwip-interface/lwip lwip-fork mbed-os-lwip-stable-2_0_2-prefixed -m "Merged lwip 2.0.2 stable"`

After this step, there is a new commit visible in the mbed OS master branch that contains the changes.
Copy link
Contributor

Choose a reason for hiding this comment

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

Please change "mbed" to "Mbed".

Copy link
Author

Choose a reason for hiding this comment

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

Corrected.

@mikaleppanen
Copy link
Author

Corrected CONTRIBUTING.md to new mbed style.

Copy link
Contributor

@AnotherButler AnotherButler left a comment

Choose a reason for hiding this comment

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

@mikaleppanen Thanks so much. LGTM 👍

@0xc0170
Copy link
Contributor

0xc0170 commented Aug 3, 2017

/morph test-nightly

@mbed-bot
Copy link

mbed-bot commented Aug 4, 2017

Result: FAILURE

Your command has finished executing! Here's what you wrote!

/morph test-nightly

Output

mbed Build Number: 934

Test failed!

@0xc0170
Copy link
Contributor

0xc0170 commented Aug 6, 2017

/morph test-nightly

2 similar comments
@0xc0170
Copy link
Contributor

0xc0170 commented Aug 6, 2017

/morph test-nightly

@studavekar
Copy link
Contributor

/morph test-nightly

@mbed-bot
Copy link

mbed-bot commented Aug 7, 2017

Result: FAILURE

Your command has finished executing! Here's what you wrote!

/morph test-nightly

Output

mbed Build Number: 947

Test failed!

@theotherjimmy
Copy link
Contributor

@studavekar It looks like the Arch PRO fell off. Could you give it a check?

@studavekar
Copy link
Contributor

Looks like ARM_BEETLE_SOC failed may be related to serial driver issue and we have fixed it.

/morph test-nightly

@mbed-bot
Copy link

mbed-bot commented Aug 8, 2017

Result: FAILURE

Your command has finished executing! Here's what you wrote!

/morph test-nightly

Output

mbed Build Number: 959

Build failed!

@0xc0170
Copy link
Contributor

0xc0170 commented Aug 8, 2017

/morph test-nightly

@mbed-bot
Copy link

mbed-bot commented Aug 8, 2017

Result: FAILURE

Your command has finished executing! Here's what you wrote!

/morph test-nightly

Output

mbed Build Number: 966

Build Prep failed!

@studavekar
Copy link
Contributor

Error in git checkout

15:17:12  > git checkout -f 4a99b3bbbc9d87e0b3c006e50e517d8f47ec1e07
15:27:12 ERROR: Timeout after 10 minutes
15:27:19 FATAL: Could not checkout 4a99b3bbbc9d87e0b3c006e50e517d8f47ec1e07
15:27:20 hudson.plugins.git.GitException: Command "git checkout -f 4a99b3bbbc9d87e0b3c006e50e517d8f47ec1e07" returned status code -1:
15:27:20 stdout: 

/morph test-nightly

@mbed-bot
Copy link

mbed-bot commented Aug 9, 2017

Result: SUCCESS

Your command has finished executing! Here's what you wrote!

/morph test-nightly

Output

mbed Build Number: 969

All builds and test passed!

@adbridge
Copy link
Contributor

adbridge commented Aug 11, 2017

The squash commit is now causing us issues with porting to 5.5.5 because it contains changes which were already backported to 5.5.4! ie it is based on an older codebase!! I'm not sure why the PR to master didn't complain! This is the kind of problem we see with squashing!!

I've spent 2 hours trying to manually apply this PR afterwards with little success due to the nasty and multiple conflicts that are coming up, thus this is not being backported.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants