Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] configs/pc_x86_64_{bios, efi}_defconfig: unbreak after qemu bump to linux-4.11
Date: Thu, 15 Jun 2017 11:31:54 +0200	[thread overview]
Message-ID: <87d1a5k35h.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <FE617696-0325-4F4C-B91C-38CCE98C76B6@openadk.org> (Waldemar Brodkorb's message of "Thu, 15 Jun 2017 08:36:36 +0200")

>>>>> "Waldemar" == Waldemar Brodkorb <wbx@openadk.org> writes:

 > Hi,
 >> Am 14.06.2017 um 23:36 schrieb Peter Korsgaard <peter@korsgaard.com>:
 >> 
 >> The pc_x86_64 defconfigs reuse the linux configuration from qemu_x86_64, ..

 > Wouldn't it be better to decouple the usage of the configs. I find it
 > not obvious that they share the same kernel config.

True. I've pushed this commit + a commit to use a dedicated linux
config for these pc defconfigs.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2017-06-15  9:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-14 21:36 [Buildroot] [PATCH] configs/pc_x86_64_{bios, efi}_defconfig: unbreak after qemu bump to linux-4.11 Peter Korsgaard
2017-06-15  6:36 ` Waldemar Brodkorb
2017-06-15  9:31   ` Peter Korsgaard [this message]
2017-06-15  9:31 ` Peter Korsgaard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87d1a5k35h.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox