Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: stable <stable@vger.kernel.org>
Subject: Re: More gcc related patches for stable releases
Date: Sun, 3 Jun 2018 10:49:45 +0200	[thread overview]
Message-ID: <20180603084945.GA21086@kroah.com> (raw)
In-Reply-To: <dde2bd83-78d3-1618-686d-2b46c6310b73@roeck-us.net>

On Sat, Jun 02, 2018 at 12:07:24PM -0700, Guenter Roeck wrote:
> Hi Greg,
> 
> The following patches are needed in various stable releases to build
> sparc/sparc64 images with gcc 7.3.0.
> 
> v4.4:
> 56962f8b250a Kbuild: change CC_OPTIMIZE_FOR_SIZE definition
> 
> v4.9 and earlier:
> 0fde7ad71ee3 sparc64: Fix build warnings with gcc 7.

Both now picked up, thanks.

> v4.9:
> 009615ab7fd4 USB: serial: cp210x: use tcflag_t to fix incompatible pointer type

This was already in my tree.

thanks,

greg k-h

      parent reply	other threads:[~2018-06-03  8:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-02 19:07 More gcc related patches for stable releases Guenter Roeck
2018-06-02 19:50 ` Nathan Chancellor
2018-06-02 20:50   ` Guenter Roeck
2018-06-03  8:49 ` Greg Kroah-Hartman [this message]

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=20180603084945.GA21086@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux@roeck-us.net \
    --cc=stable@vger.kernel.org \
    /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