From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: Paul Cercueil <paul@crapouillou.net>,
od@zcrc.me,
"open list:BROADCOM NVRAM DRIVER" <linux-mips@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
kbuild test robot <lkp@intel.com>
Subject: Re: [PATCH] MIPS: ingenic: Add missing include
Date: Wed, 20 May 2020 11:27:57 +0200 [thread overview]
Message-ID: <20200520092757.GA12701@alpha.franken.de> (raw)
In-Reply-To: <CAAdtpL4cZ4==07=kNJf6Xkhnzy6jiqgMc1XzG0NV6RZi1KqgXA@mail.gmail.com>
On Wed, May 20, 2020 at 11:19:49AM +0200, Philippe Mathieu-Daudé wrote:
> Hi Thomas,
>
> On Wed, May 20, 2020 at 8:50 AM Thomas Bogendoerfer
> <tsbogend@alpha.franken.de> wrote:
> >
> > On Tue, May 19, 2020 at 11:22:30PM +0200, Paul Cercueil wrote:
> > > Add missing include which adds the prototype to plat_time_init().
> > >
> > > Fixes: f932449c11da ("MIPS: ingenic: Drop obsolete code, merge the rest in setup.c")
> > > Signed-off-by: Paul Cercueil <paul@crapouillou.net>
> > > Reported-by: kbuild test robot <lkp@intel.com>
> > > ---
> > > arch/mips/jz4740/setup.c | 1 +
> > > 1 file changed, 1 insertion(+)
> >
> > applied to mips-next.
>
> Since mips-next is not merged, can you simply squash the fix to the
> incomplete f932449c11da please?
no, I don't rebase mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2020-05-20 9:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 21:22 [PATCH] MIPS: ingenic: Add missing include Paul Cercueil
2020-05-20 6:45 ` Thomas Bogendoerfer
2020-05-20 9:19 ` Philippe Mathieu-Daudé
2020-05-20 9:27 ` Thomas Bogendoerfer [this message]
2020-05-20 10:01 ` Philippe Mathieu-Daudé
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=20200520092757.GA12701@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=f4bug@amsat.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=lkp@intel.com \
--cc=od@zcrc.me \
--cc=paul@crapouillou.net \
/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