From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Yoshinori Sato <ysato@users.sourceforge.jp>
Cc: Randy Dunlap <rdunlap@infradead.org>,
kbuild test robot <lkp@intel.com>,
kbuild-all@01.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
"Sasha Levin (Microsoft)" <sashal@kernel.org>,
Rich Felker <dalias@libc.org>,
linux-sh@vger.kernel.org
Subject: Re: [linux-stable-rc:linux-5.0.y 1434/2350] arch/sh/kernel/cpu/sh2/clock-sh7619.o:undefined reference to `followparent_recalc'
Date: Sun, 2 Jun 2019 17:43:14 +1000 [thread overview]
Message-ID: <20190602174314.09f5f337@canb.auug.org.au> (raw)
In-Reply-To: <871s0cqx33.wl-ysato@users.sourceforge.jp>
[-- Attachment #1: Type: text/plain, Size: 1291 bytes --]
Hi Yoshinori,
On Sun, 02 Jun 2019 16:13:04 +0900 Yoshinori Sato <ysato@users.sourceforge.jp> wrote:
>
> Since I created a temporary sh-next, please get it here.
> git://git.sourceforge.jp/gitroot/uclinux-h8/linux.git tags/sh-next
I have added that tree to linux-next from tomorrow. However, thet is
no sh-next tag in that tree, so I used the sh-next branch. I don't
think you need the back merge of Linus' tree.
Thanks for adding your subsystem tree as a participant of linux-next. As
you may know, this is not a judgement of your code. The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window.
You will need to ensure that the patches/commits in your tree/series have
been:
* submitted under GPL v2 (or later) and include the Contributor's
Signed-off-by,
* posted to the relevant mailing list,
* reviewed by you (or another maintainer of your subsystem tree),
* successfully unit tested, and
* destined for the current or next Linux merge window.
Basically, this should be just what you would send to Linus (or ask him
to fetch). It is allowed to be rebased if you deem it necessary.
--
Cheers,
Stephen Rothwell
sfr@canb.auug.org.au
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-06-02 7:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 7:31 [linux-stable-rc:linux-5.0.y 1434/2350] arch/sh/kernel/cpu/sh2/clock-sh7619.o:undefined reference to `followparent_recalc' kbuild test robot
2019-05-30 14:43 ` Randy Dunlap
2019-05-31 0:00 ` Stephen Rothwell
2019-06-02 7:13 ` Yoshinori Sato
2019-06-02 7:43 ` Stephen Rothwell [this message]
2019-06-02 11:29 ` Yoshinori Sato
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=20190602174314.09f5f337@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=dalias@libc.org \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=linux-sh@vger.kernel.org \
--cc=lkp@intel.com \
--cc=rdunlap@infradead.org \
--cc=sashal@kernel.org \
--cc=ysato@users.sourceforge.jp \
/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;
as well as URLs for NNTP newsgroup(s).