linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	broonie@kernel.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	linux-next@vger.kernel.org, mhocko@suse.cz,
	mm-commits@vger.kernel.org, sfr@canb.auug.org.au,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: mmotm 2019-12-10-19-14 uploaded (objtool: func() falls through)
Date: Thu, 12 Dec 2019 12:48:59 -0600	[thread overview]
Message-ID: <20191212184859.zjj2ycfkvpcns5bk@treble> (raw)
In-Reply-To: <07777464-b9d8-ff1d-41d9-f62cc44f09f3@infradead.org>

On Wed, Dec 11, 2019 at 08:31:08AM -0800, Randy Dunlap wrote:
> On 12/10/19 7:14 PM, Andrew Morton wrote:
> > The mm-of-the-moment snapshot 2019-12-10-19-14 has been uploaded to
> > 
> >    http://www.ozlabs.org/~akpm/mmotm/
> > 
> > mmotm-readme.txt says
> > 
> > README for mm-of-the-moment:
> > 
> > http://www.ozlabs.org/~akpm/mmotm/
> > 
> > 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 (5.x
> > or 5.x-rcY).  The series file is in broken-out.tar.gz and is duplicated in
> > http://ozlabs.org/~akpm/mmotm/series
> > 
> > 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.
> 
> on x86_64:
> 
> drivers/hwmon/f71882fg.o: warning: objtool: f71882fg_update_device() falls through to next function show_pwm_auto_point_temp_hyst()
> drivers/ide/ide-probe.o: warning: objtool: hwif_register_devices() falls through to next function hwif_release_dev()
> drivers/ide/ide-probe.o: warning: objtool: ide_host_remove() falls through to next function ide_disable_port()

Randy, can you share the .o files?

-- 
Josh


  reply	other threads:[~2019-12-12 18:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20191206170123.cb3ad1f76af2b48505fabb33@linux-foundation.org>
2019-12-07  3:47 ` mmotm 2019-12-06-19-46 uploaded Andrew Morton
2019-12-07 16:35   ` mmotm 2019-12-06-19-46 uploaded (ethernet/freescale/gianfar) Randy Dunlap
2019-12-09  6:31   ` mmotm 2019-12-06-19-46 uploaded Shaokun Zhang
2019-12-11  1:35     ` Andrew Morton
2019-12-11  1:42       ` Shaokun Zhang
2019-12-11  1:58         ` Andrew Morton
2019-12-11  3:14 ` mmotm 2019-12-10-19-14 uploaded Andrew Morton
2019-12-11 16:31   ` mmotm 2019-12-10-19-14 uploaded (objtool: func() falls through) Randy Dunlap
2019-12-12 18:48     ` Josh Poimboeuf [this message]
2019-12-12 20:21       ` Randy Dunlap
2019-12-12 20:58         ` Josh Poimboeuf
2020-01-17 18:11           ` Josh Poimboeuf
2020-01-17 22:15             ` Randy Dunlap
2019-12-18  4:41 ` mmotm 2019-12-17-20-41 uploaded Andrew Morton

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=20191212184859.zjj2ycfkvpcns5bk@treble \
    --to=jpoimboe@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mhocko@suse.cz \
    --cc=mm-commits@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=rdunlap@infradead.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 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).