From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Paul Burton <paul.burton@imgtec.com>,
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: Thu, 24 Sep 2015 12:50:17 +0530 [thread overview]
Message-ID: <20150924072017.GE19202@sudip-pc> (raw)
In-Reply-To: <20150924070744.GD21784@linux-mips.org>
On Thu, Sep 24, 2015 at 09:07:44AM +0200, Ralf Baechle wrote:
> On Wed, Sep 23, 2015 at 02:42:36PM -0700, Paul Burton wrote:
>
> > 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 for reporting. The patch didn't apply cleanly and when applying
> it manually I forgot to git-add the new file. Of course the file was
> in the local repo so my test builds did succeed. I fixed that now.
next-20150924 also failed with the same error. I guess next-20150925
should be ok.
Today's build log at:
https://travis-ci.org/sudipm-mukherjee/parport/jobs/81906839
regards
sudip
next prev parent reply other threads:[~2015-09-24 7:20 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
2015-09-23 21:42 ` Paul Burton
2015-09-24 7:07 ` Ralf Baechle
2015-09-24 7:20 ` Sudip Mukherjee [this message]
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=20150924072017.GE19202@sudip-pc \
--to=sudipm.mukherjee@gmail.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=paul.burton@imgtec.com \
--cc=ralf@linux-mips.org \
--cc=sfr@canb.auug.org.au \
/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.