public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: "Gabriel C" <nix.or.die@googlemail•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: Tree for July 14
Date: Mon, 14 Jul 2008 13:43:17 +0200	[thread overview]
Message-ID: <1820d69d0807140443x1c4ba0b3p46072164ea2fe48b@mail.gmail.com> (raw)
In-Reply-To: <20080714201249.947400d0.sfr@canb.auug.org.au>

2008/7/14 Stephen Rothwell <sfr@canb•auug.org.au>:
> Hi all,

Hi ,

>
> With the opening of the merge window, I am hoping my job becomes easier
> again ... :-)
>
> Changes since next-20080711:
>

make clean / mrproper is broken , I'm not sure when it broken , I'm
updating from
2.6.26-rc8-next-20080630.

...

crazy@thor:/work/crazy/linux/linux-next/git/linux-2.6$ LC_ALL=C make clean
scripts/Makefile.clean:17:
/work/crazy/linux/linux-next/git/linux-2.6/drivers/media/mdtv/Makefile:
No such file or directory
make[3]: *** No rule to make target
`/work/crazy/linux/linux-next/git/linux-2.6/drivers/media/mdtv/Makefile'.
 Stop.
make[2]: *** [drivers/media/mdtv] Error 2
make[1]: *** [drivers/media] Error 2
make: *** [_clean_drivers] Error 2

...

drivers/media/Makefile has 'obj-$(CONFIG_MDTV_ADAPTERS)  += mdtv/' but
I cannot see such a folder under drivers/media =). Removing mdtv from
Makefile fixes the problem.

Regards,

Gabriel

  reply	other threads:[~2008-07-14 11:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-14 10:12 linux-next: Tree for July 14 Stephen Rothwell
2008-07-14 11:43 ` Gabriel C [this message]
2008-07-14 13:47   ` Stephen Rothwell
2008-07-14 14:18 ` Gabriel C
2008-07-14 16:20 ` Takashi Iwai
2008-07-15  5:50   ` Benjamin Herrenschmidt
2008-07-14 16:20 ` Takashi Iwai
2008-07-14 16:25 ` Takashi Iwai
2008-07-14 16:25 ` Takashi Iwai
2008-07-14 17:12 ` Andrew Morton
2008-07-14 23:35 ` Rafael J. Wysocki
  -- strict thread matches above, loose matches on Subject: below --
2008-07-14 15:06 mkrufky
2009-07-14  7:06 Stephen Rothwell
2010-07-14  4:23 Stephen Rothwell

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=1820d69d0807140443x1c4ba0b3p46072164ea2fe48b@mail.gmail.com \
    --to=nix.or.die@googlemail$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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