Re: Linux/m68k config again

[Geert Uytterhoeven <geert@linux-m68k.org>]

On Sat, Dec 28, 2013 at 8:11 PM, Geert Uytterhoeven
<geert@linux-m68k.org> wrote:
> Sorry, I should spend a bit more time updating upstream's defconfigs.

I updated my defconfig branch, cfr.
https://git.kernel.org/cgit/linux/kernel/git/geert/linux-m68k.git/log/?h=defconfig
(waiting for the mirror to catch up, ... ah it's there):

8ab14ab4c65b m68k: Update defconfigs for v3.13-rc1
63dde0ea0298 m68k: Update defconfigs for v3.12-rc1
00c2b18d5b98 m68k: Update defconfigs for v3.11
c36a061ef595 m68k: Update defconfigs for v3.10
ab824d77934f m68k/defconfig: Disable /sbin/hotplug fork-bomb by default
c6188d0f5756 m68k/defconfig: Use ext4 for ext2/ext3 file systems
51b9310f0a33 m68k/defconfig: Make NFS_V4 modular instead of builtin

The first two (i.e. the 2 at the bottom) I had already queued up for 3.14.

Anything missing/wrong/dangerous/suboptimal/...?

Yes, multi-defconfig still gives you kernels larger than 4 MiB, i.e. unbootable.
Suggestions for improvement are welcome. Switching to initramfs and
everything modular is not an option here.

Atari_defconfig has USB_HID and USB_STORAGE for EtherNAT and
NetUSBee, while multi_defconfig hasn't. I don't want to pollute everybody
with USB ;-)
Apart from that, multi_defconfig should be a superset of all other configs
(except Sun-3), as usual, but I didn't check.

Note that minimal configs are generated from the upstream tree, not from
the m68k tree.

Thanks!

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds