From: Paul Burton <paul.burton@imgtec.com>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Ralf Baechle <ralf@linux-mips.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
<linux-next@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
"Maciej W. Rozycki" <macro@linux-mips.org>,
<linux-mips@linux-mips.org>
Subject: Re: linux-next: Tree for Sep 23
Date: Wed, 23 Sep 2015 14:42:36 -0700 [thread overview]
Message-ID: <20150923214236.GA28778@NP-P-BURTON> (raw)
In-Reply-To: <20150923074207.GA27002@sudip-pc>
On Wed, Sep 23, 2015 at 01:12:08PM +0530, Sudip Mukherjee wrote:
> On Wed, Sep 23, 2015 at 02:23:43PM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20150922:
> mips allmodconfig failed with the error:
> No rule to make target 'arch/mips/mm/sc-debugfs.o', needed by 'arch/mips/mm/built-in.o'
>
> caused by:
> 13ea0032658d ("MIPS: Allow L2 prefetch to be configured via debugfs")
>
> regards
> sudip
Hi Ralf,
That patch as I submitted it definitely adds arch/mips/mm/sc-debugfs.c
but somehow that file has been lost from the commit in your
mips-for-linux-next tree. Could you re-apply it?
Thanks,
Paul
WARNING: multiple messages have this Message-ID (diff)
From: Paul Burton <paul.burton@imgtec.com>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Ralf Baechle <ralf@linux-mips.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
"Maciej W. Rozycki" <macro@linux-mips.org>,
linux-mips@linux-mips.org
Subject: Re: linux-next: Tree for Sep 23
Date: Wed, 23 Sep 2015 14:42:36 -0700 [thread overview]
Message-ID: <20150923214236.GA28778@NP-P-BURTON> (raw)
Message-ID: <20150923214236.EBxcDycHdukl-gyVk4s9S6hHSr83K-aaN2TJln-tAKs@z> (raw)
In-Reply-To: <20150923074207.GA27002@sudip-pc>
On Wed, Sep 23, 2015 at 01:12:08PM +0530, Sudip Mukherjee wrote:
> On Wed, Sep 23, 2015 at 02:23:43PM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20150922:
> mips allmodconfig failed with the error:
> No rule to make target 'arch/mips/mm/sc-debugfs.o', needed by 'arch/mips/mm/built-in.o'
>
> caused by:
> 13ea0032658d ("MIPS: Allow L2 prefetch to be configured via debugfs")
>
> regards
> sudip
Hi Ralf,
That patch as I submitted it definitely adds arch/mips/mm/sc-debugfs.c
but somehow that file has been lost from the commit in your
mips-for-linux-next tree. Could you re-apply it?
Thanks,
Paul
next prev parent reply other threads:[~2015-09-23 21:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 4:23 linux-next: Tree for Sep 23 Stephen Rothwell
2015-09-23 7:42 ` Sudip Mukherjee
2015-09-23 21:42 ` Paul Burton [this message]
2015-09-23 21:42 ` Paul Burton
2015-09-24 7:07 ` Ralf Baechle
2015-09-24 7:20 ` Sudip Mukherjee
2015-09-23 18:08 ` linux-next: Tree for Sep 23 (netfilter) Randy Dunlap
-- strict thread matches above, loose matches on Subject: below --
2025-09-23 16:52 linux-next: Tree for Sep 23 Mark Brown
2024-09-23 4:14 Stephen Rothwell
2022-09-23 8:47 Stephen Rothwell
2021-09-23 5:09 Stephen Rothwell
2020-09-23 11:30 Stephen Rothwell
2016-09-23 6:30 Stephen Rothwell
2014-09-23 8:24 Stephen Rothwell
2013-09-23 7:37 Stephen Rothwell
2013-09-23 7:37 ` 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=20150923214236.GA28778@NP-P-BURTON \
--to=paul.burton@imgtec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-next@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=sfr@canb.auug.org.au \
--cc=sudipm.mukherjee@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.