Skip to content
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

kernel : Update recent kernel commit ID and BB files #40

Closed
wants to merge 1 commit into from

Conversation

pino-kim
Copy link
Contributor

@pino-kim pino-kim commented Oct 4, 2018

I update riscv-linux verion 4.15 and 4.18 kernel bbfile, head to recent
commit. And add SUMMAARY, DESCRIPTION field to provide imformation of
kernel bbfile.

update kernel bbfiles and add SUMMARY, DESCRIPTION field.

signed-off-by: pino-kim sungwon.pino@gmail.com

@pino-kim
Copy link
Contributor Author

pino-kim commented Oct 4, 2018

Dear @kraj, @alistair23 and ALL EXPERT~!!!
I want to feel in the DESCRIPTION field. So I suggest it.
please check it and give me a feedback.
I recommend it here
https://github.com/Freescale/meta-freescale/blob/master/recipes-kernel/linux/linux-fslc_4.18.bb

DESCRIPTION = "Linux kernel based on mainline kernel used by RISC-V Community BSP in order to \
provide support for some backported features and fixes, or because it was applied in linux-next \
and takes some time to become part of a stable version, or because it is not applicable for \
upstreaming."

@@ -1,6 +1,9 @@
require recipes-kernel/linux/linux-riscv-common.inc

SUMMARY = "RISC-V Community BSP RISC-V Linux kernel with backported features and fiexes"
DESCRIPTION = ""
Copy link
Collaborator

Choose a reason for hiding this comment

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

empty description is not preferred. Just do not set it, then summary appears as description as well.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Dear @kraj.
Thanks to reply.
I PR it balnk to ask Desription content.

I suggest content below.
Below content is good or bad? If bad I will remove that Description field.

DESCRIPTION = "Linux kernel based on mainline kernel used by RISC-V Community BSP in order to \
provide support for some backported features and fixes, or because it was applied in linux-next \
and takes some time to become part of a stable version, or because it is not applicable for \
upstreaming."

Copy link
Collaborator

Choose a reason for hiding this comment

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

looks good

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks. I update PR.

recipes-kernel/linux/linux-riscv_4.18.bb Outdated Show resolved Hide resolved
I update  riscv-linux verion 4.15 and 4.18 kernel bbfile, head to recent
commit. And add SUMMAARY, DESCRIPTION field to provide imformation of
kernel bbfile.

update kernel bbfiles and add SUMMARY, DESCRIPTION field.

signed-off-by: pino-kim <sungwon.pino@gmail.com>
Copy link
Collaborator

@kraj kraj left a comment

Choose a reason for hiding this comment

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

LGTM

@kraj
Copy link
Collaborator

kraj commented Oct 4, 2018

you have also bumped up srcrevs, how have you tested it ? this will help me in avoiding some testing

@pino-kim
Copy link
Contributor Author

pino-kim commented Oct 4, 2018

@kraj.
Ok hold this PR please.
I bootup test kernel 4.18 with runqemu but not yet kernel 4.15.

I will test both kernel commit head with runqemu command.
If bootup success, fine to use that srcrevs?

@pino-kim pino-kim mentioned this pull request Oct 5, 2018
@pino-kim
Copy link
Contributor Author

pino-kim commented Oct 5, 2018

Dear @kraj
I make some #41 to report build log and bootup picture.
I think changed srcrevs fetch well when build.
So continue this PR please, merge or not.

@kraj
Copy link
Collaborator

kraj commented Oct 8, 2018

this has been squashed into #42

@kraj kraj closed this Oct 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants