New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 848418 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
User never visited
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Renormalize config in kernel v4.4

Project Member Reported by dawidip@google.com, May 31 2018

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36

Steps to reproduce the problem:
1. run ./chromeos/scripts/kernelconfig olddefconfig
2. 
3. 

What is the expected behavior?
Shouldn't change anything.

What went wrong?
Config files were changed.

Did this work before? N/A 

Chrome version: 66.0.3359.139  Channel: n/a
OS Version: 
Flash Version:
 
Components: OS>Kernel
Labels: OS-Chrome
Cc: groeck@chromium.org pmalani@chromium.org swboyd@chromium.org
Owner: dawidip@chromium.org
Updating component, Owner, CC list.
Project Member

Comment 4 by bugdroid1@chromium.org, Jun 6 2018

Labels: merge-merged-chromeos-4.4
The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/24459c5d71d5b22e429bbf26d7867872320e196f

commit 24459c5d71d5b22e429bbf26d7867872320e196f
Author: dawidip <dawidip@google.com>
Date: Wed Jun 06 12:00:40 2018

CHROMIUM: config: renormalize config

`./chromeos/scripts/kernelconfig olddefconfig`.

CONFIG_EVE_ETSI_WORKAROUND comes from
commit c9f8c96c76b6 ("CHROMIUM: iwl7000: add Eve-specific wmm rules")

CONFIG_PRIME_NUMBERS comes from
commit 09c025bdae2f ("UPSTREAM: lib: Add a simple prime number generator")

CONFIG_ARM64_ERRATUM_1024718 comes from
commit 348f043ab6c6 ("arm64: Add work around for Arm Cortex-A55 Erratum
1024718")

CONFIG_DRM_DEBUG_SELFTEST and CONFIG_DRM_LIB_RANDOM probably come from
commit 18b1f72cb1b6 ("BACKPORT: drm/selftests: Rename the Kconfig option to
CONFIG_DRM_DEBUG_SELFTEST")

CONFIG_INTEL_VBTN is probably from
commit 9f2039bb1c98 ("UPSTREAM: intel-vbtn: new driver for Intel Virtual
Button")

BUG=chromium:848418
TEST=Build and boot on eve

Change-Id: Id293c4ddc8206693b669791f1d974d0eb86dcc4f
Signed-off-by: Dawid Pyczek <dawidip@google.com>
Reviewed-on: https://chromium-review.googlesource.com/1080177
Commit-Ready: Matt Delco <delco@google.com>
Tested-by: Matt Delco <delco@google.com>
Tested-by: Dawid Pyczek <dawidip@chromium.org>
Reviewed-by: Kirtika Ruchandani <kirtika@chromium.org>
Reviewed-by: Dawid Pyczek <dawidip@chromium.org>

[modify] https://crrev.com/24459c5d71d5b22e429bbf26d7867872320e196f/chromeos/config/x86_64/common.config
[modify] https://crrev.com/24459c5d71d5b22e429bbf26d7867872320e196f/chromeos/config/i386/common.config
[modify] https://crrev.com/24459c5d71d5b22e429bbf26d7867872320e196f/chromeos/config/base.config
[modify] https://crrev.com/24459c5d71d5b22e429bbf26d7867872320e196f/chromeos/config/arm64/common.config

Status: Assigned (was: Unconfirmed)
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.

Sign in to add a comment