public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Jim Davis <jim.epost@gmail•com>
Cc: linux-next <linux-next@vger•kernel.org>,
	Hans Verkuil <hans.verkuil@cisco•com>,
	Mauro Carvalho Chehab <mchehab@infradead•org>
Subject: Re: make distclean problem with next-20141124?
Date: Tue, 25 Nov 2014 08:09:59 +1100	[thread overview]
Message-ID: <20141125080959.5c987e8e@canb.auug.org.au> (raw)
In-Reply-To: <CA+r1Zhhkjnb8Pa-ALB9Q6TsQ5e_oRTMJYqY50A1=2u2yYfZ4dg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 986 bytes --]

Hi Jim,

On Mon, 24 Nov 2014 11:11:11 -0700 Jim Davis <jim.epost@gmail•com> wrote:
>
> jim@krebstar:~/linux2$ git describe
> next-20141124
> jim@krebstar:~/linux2$ git status
> HEAD detached at next-20141124
> nothing to commit, working directory clean
> jim@krebstar:~/linux2$ make distclean
> ./scripts/Makefile.clean:17: drivers/staging/media/omap24xx/Makefile: No
> such file or directory
> make[4]: *** No rule to make target
> `drivers/staging/media/omap24xx/Makefile'.  Stop.
> 
> Though git log does show commit db85a0403be4a59cf536a25622fe110feefba8d3,
> which should have removed the line from drivers/staging/media/Makefile that
> make is tripping over:
> 
> -obj-$(CONFIG_VIDEO_OMAP2)       += omap24xx/

There is another line in drivers/staging/media/Makefile immediately
below the one that was removed that was clearly missed:

obj-$(CONFIG_VIDEO_TCM825X)     += omap24xx/

-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

           reply	other threads:[~2014-11-24 21:10 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CA+r1Zhhkjnb8Pa-ALB9Q6TsQ5e_oRTMJYqY50A1=2u2yYfZ4dg@mail.gmail.com>]

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=20141125080959.5c987e8e@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=hans.verkuil@cisco$(echo .)com \
    --cc=jim.epost@gmail$(echo .)com \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=mchehab@infradead$(echo .)org \
    /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