linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Randy Dunlap <rdunlap@infradead.org>,
	"David S. Miller" <davem@davemloft.net>,
	Anish Bhatt <anish@chelsio.com>,
	linux-mips@linux-mips.org, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, Guenter Roeck <linux@roeck-us.net>
Subject: [RFC PATCH 00/11] next: mips: Fix default configurations
Date: Sat, 20 Sep 2014 17:46:15 -0700	[thread overview]
Message-ID: <1411260386-6800-1-git-send-email-linux@roeck-us.net> (raw)

Commit 5d6be6a5d486 ('scsi_netlink : Make SCSI_NETLINK dependent on NET instead
of selecting NET') in linux-next changes 'select NET' to 'depends NET'. As a
result, many configurations which do not explicitly select CONFIG_NET are no
longer valid and need to be updated.

An alternative to this patch series would be to revert the original commit which
caused the problem. However, a simple revert is no longer possible due to
secondary commits changing more dependencies; an attempt to build
nlm_xlp_defconfig after reverting the commit still failed with a build error.
It would therefore be necessary to track down and revert all related commits.

This patch series attempts to fix the problem for the affected mips
configurations. I did not look into other architectures or configurations.

The command sequence to create the new configuration files is as follows.

- Run "make ARCH=mips <configuration>" on upstream kernel
- Copy resulting .config to next-20140919
- Run "make ARCH=mips olddefconfig" in next-20140919
- Run "make ARCH=mips savedefconfig"
- Copy resulting defconfig file to arch/mips/configs/<configuration>
- Build the image with the resulting configuration

This sequence results in building images for all modified configurations,
but due to secondary dependency changes can not guarantee correctness
or completeness. Only time will show if there are more problems.

             reply	other threads:[~2014-09-21  0:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-21  0:46 Guenter Roeck [this message]
2014-09-21  0:46 ` [RFC PATCH 01/11] next: mips: Fix gpr_defconfig Guenter Roeck
2014-09-21  0:46 ` [RFC PATCH 02/11] next: mips: Fix ip27_defconfig Guenter Roeck
2014-09-21  0:46 ` [RFC PATCH 03/11] next: mips: Fix jazz_defconfig Guenter Roeck
2014-09-21  0:46 ` [RFC PATCH 04/11] next: mips: Fix loongson3_defconfig Guenter Roeck
2014-09-21  0:46 ` [RFC PATCH 05/11] next: mips: Fix malta_defconfig Guenter Roeck
2014-09-21  0:46 ` [RFC PATCH 06/11] next: mips: Fix malta_kvm_defconfig Guenter Roeck
2014-09-21  0:46 ` [RFC PATCH 07/11] next: mips: Fix malta_kvm_guest_defconfig Guenter Roeck
2014-09-21  0:46 ` [RFC PATCH 08/11] next: mips: Fix mtx1_defconfig Guenter Roeck
2014-09-21  0:46 ` [RFC PATCH 09/11] next: mips: Fix nlm_xlp_defconfig Guenter Roeck
2014-09-21  0:46 ` [RFC PATCH 10/11] next: mips: Fix nlm_xlr_defconfig Guenter Roeck
2014-09-21  0:46 ` [RFC PATCH 11/11] next: mips: Fix rm200_defconfig Guenter Roeck
  -- strict thread matches above, loose matches on Subject: below --
2014-09-21  0:45 [RFC PATCH 00/11] next: mips: Fix default configurations Guenter Roeck
2014-09-21  0:44 Guenter Roeck

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=1411260386-6800-1-git-send-email-linux@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=anish@chelsio.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=netdev@vger.kernel.org \
    --cc=ralf@linux-mips.org \
    --cc=rdunlap@infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).