linux-m68k.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@uclinux.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: [PATCH 00/10] m68knommu: fix allnoconfig
Date: Tue, 07 Jul 2015 22:22:25 +1000	[thread overview]
Message-ID: <559BC481.6010004@uclinux.org> (raw)
In-Reply-To: <CAMuHMdXenF_87nwbiVAM_+or19xCAMLfDExOxRPbKvGk7Q2AuQ@mail.gmail.com>

Hi Geert,

On 07/07/15 19:00, Geert Uytterhoeven wrote:
> Hi Greg,
>
> On Tue, Jul 7, 2015 at 8:55 AM, Greg Ungerer <gerg@uclinux.org> wrote:
>> The following set of patches are designed to fix the issues causing a
>> "make allnoconfig" to fail for m68k. There is really only a couple of
>> problems, and those are easily fixed.
> Thanks!
>
> For 1-3:
> Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>

Thanks Geert. I will add that on, and push to m68knommu git
tree in the next day or so.

> Now I only have to fix the m68k+MMU allnoconfig build
>
>      $ echo CONFIG_MMU=y > allno.config
>      $ make allnoconfig KCONFIG_ALLCONFIG=1
>
> I have patches for some problems, but not all of them...

Do we care about allmodconfig and allyesconfig?
Looks like problems there too.

Regards
Greg

> 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
>

  reply	other threads:[~2015-07-07 12:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-07  6:55 [PATCH 00/10] m68knommu: fix allnoconfig Greg Ungerer
2015-07-07  6:55 ` [PATCH 01/10] m68knommu: force setting of CONFIG_CLOCK_FREQ for ColdFire Greg Ungerer
2015-07-07  6:55 ` [PATCH 02/10] m68knommu: improve the clock configuration defaults Greg Ungerer
2015-07-07  6:55 ` [PATCH 03/10] m68knommu: make ColdFire SoC selection a choice Greg Ungerer
2015-07-07  6:55 ` [PATCH 04/10] m68knommu: update defconfig for m5208evb Greg Ungerer
2015-07-07  6:55 ` [PATCH 05/10] m68knommu: update defconfig for ColdFire m5249evb Greg Ungerer
2015-07-07  6:55 ` [PATCH 06/10] m68knommu: update defconfig for ColdFire m5272c3 Greg Ungerer
2015-07-07  6:55 ` [PATCH 07/10] m68knommu: update defconfig for ColdFire m5275evb Greg Ungerer
2015-07-07  6:55 ` [PATCH 08/10] m68knommu: update defconfig for ColdFire m5307c3 Greg Ungerer
2015-07-07  6:55 ` [PATCH 09/10] m68knommu: update defconfig for ColdFire m5407c3 Greg Ungerer
2015-07-07  6:55 ` [PATCH 10/10] m68knommu: update defconfig for ColdFire m5475evb Greg Ungerer
2015-07-07  9:00 ` [PATCH 00/10] m68knommu: fix allnoconfig Geert Uytterhoeven
2015-07-07 12:22   ` Greg Ungerer [this message]
2015-07-07 12:45     ` Geert Uytterhoeven

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=559BC481.6010004@uclinux.org \
    --to=gerg@uclinux.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-m68k@vger.kernel.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).