archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <>
Cc: Josh Poimboeuf <>,
	Peter Zijlstra <>
Subject: Re: mmotm 2018-05-10-16-34 uploaded (objtool)
Date: Thu, 10 May 2018 17:47:32 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 05/10/2018 04:35 PM, wrote:
> The mm-of-the-moment snapshot 2018-05-10-16-34 has been uploaded to
> mmotm-readme.txt says
> README for mm-of-the-moment:
> This is a snapshot of my -mm patch queue.  Uploaded at random hopefully
> more than once a week.
> You will need quilt to apply these patches to the latest Linus release (4.x
> or 4.x-rcY).  The series file is in broken-out.tar.gz and is duplicated in
> The file broken-out.tar.gz contains two datestamp files: .DATE and
> .DATE-yyyy-mm-dd-hh-mm-ss.  Both contain the string yyyy-mm-dd-hh-mm-ss,
> followed by the base kernel version against which this patch series is to
> be applied.
> This tree is partially included in linux-next.  To see which patches are
> included in linux-next, consult the `series' file.  Only the patches
> within the #NEXT_PATCHES_START/#NEXT_PATCHES_END markers are included in
> linux-next.
> A git tree which contains the memory management portion of this tree is
> maintained at git://
> by Michal Hocko.  It contains the patches which are between the
> "#NEXT_PATCHES_START mm" and "#NEXT_PATCHES_END" markers, from the series
> file,
> A full copy of the full kernel tree with the linux-next and mmotm patches
> already applied is available through git within an hour of the mmotm
> release.  Individual mmotm releases are tagged.  The master branch always
> points to the latest release, so it's constantly rebasing.

Hi Josh, Peter:

Is this something that you already have fixes for?

on x86_64:

drivers/video/fbdev/omap2/omapfb/dss/dispc.o: warning: objtool: dispc_runtime_suspend()+0xbb8: sibling call from callable instruction with modified stack frame
drivers/video/fbdev/omap2/omapfb/dss/dispc.o: warning: objtool: dispc_runtime_resume()+0xcc5: sibling call from callable instruction with modified stack frame


  reply	other threads:[~2018-05-11  0:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-10 23:35 mmotm 2018-05-10-16-34 uploaded akpm
2018-05-11  0:47 ` Randy Dunlap [this message]
2018-05-11  1:01   ` mmotm 2018-05-10-16-34 uploaded (objtool) Josh Poimboeuf
2018-05-11  1:06     ` Randy Dunlap
2018-05-11 15:45       ` Josh Poimboeuf

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \ \

* 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).