linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Joe Perches <joe@perches.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
	Andy Gross <andy.gross@linaro.org>,
	David Brown <david.brown@linaro.org>,
	Jonathan Cameron <jic23@kernel.org>,
	Hartmut Knaack <knaack.h@gmx.de>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Peter Meerwald-Stadler <pmeerw@pmeerw.net>
Subject: Re: [GIT PULL] Driver core patches for 5.1-rc1
Date: Wed, 6 Mar 2019 16:19:13 -0800	[thread overview]
Message-ID: <CAHk-=wi5D-fZBjiqo30XgmXJPpmLxTJvJKEDqHCAFiZo9QWC_w@mail.gmail.com> (raw)
In-Reply-To: <d596d6db449d4747b3eebf4cb42f6657ad42f989.camel@perches.com>

On Wed, Mar 6, 2019 at 4:09 PM Joe Perches <joe@perches.com> wrote:
> >
> > This is very funky, but that commit generates a new warning in a
> > totally unrelated area:
>
> Very very funky.
>
> Are you sure it's the __cold marking of an
> entirely unrelated function that isn't
> even used in the code with the new warning?

Yup, I bisected it, because it made no sense at all. There were no
changes to the driver itself in that pull request, but there was a new
warning.

> btw; what compiler version?

  gcc version 8.2.1 20181215 (Red Hat 8.2.1-6) (GCC)

FWIW,

               Linus

  reply	other threads:[~2019-03-07  0:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-06 10:33 [GIT PULL] Driver core patches for 5.1-rc1 Greg KH
2019-03-06 23:47 ` Linus Torvalds
2019-03-07  0:09   ` Joe Perches
2019-03-07  0:19     ` Linus Torvalds [this message]
2019-03-07  0:24       ` Linus Torvalds
2019-03-07  7:35   ` Arnd Bergmann
2019-03-19  6:12   ` Stephen Rothwell
2019-03-07  1:20 ` pr-tracker-bot

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='CAHk-=wi5D-fZBjiqo30XgmXJPpmLxTJvJKEDqHCAFiZo9QWC_w@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=andy.gross@linaro.org \
    --cc=david.brown@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jic23@kernel.org \
    --cc=joe@perches.com \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmeerw@pmeerw.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;
as well as URLs for NNTP newsgroup(s).