From: Greg KH <gregkh@linuxfoundation.org>
To: Waldemar Brodkorb <wbx@openadk.org>
Cc: stable@vger.kernel.org, David Miller <davem@davemloft.net>,
sparclinux@vger.kernel.org
Subject: Re: gcc 7.1 sparc64 fixes
Date: Thu, 15 Jun 2017 07:51:37 +0000 [thread overview]
Message-ID: <20170615075137.GA26883@kroah.com> (raw)
In-Reply-To: <20170615073902.GZ26922@waldemar-brodkorb.de>
On Thu, Jun 15, 2017 at 09:39:03AM +0200, Waldemar Brodkorb wrote:
> Hi,
>
> I would like to suggest following patch for 4.4/4.9 stable
> kernel releases to fix gcc 7.1 compile issues:
>
> Subject: [PATCH] sparc64: make string buffers large enough
> Commit: b5c3206190f1fddd100b3060eb15f0d775ffeab8
No objection from me, David, mind if I queue this up?
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Waldemar Brodkorb <wbx@openadk.org>
Cc: stable@vger.kernel.org, David Miller <davem@davemloft.net>,
sparclinux@vger.kernel.org
Subject: Re: gcc 7.1 sparc64 fixes
Date: Thu, 15 Jun 2017 09:51:37 +0200 [thread overview]
Message-ID: <20170615075137.GA26883@kroah.com> (raw)
In-Reply-To: <20170615073902.GZ26922@waldemar-brodkorb.de>
On Thu, Jun 15, 2017 at 09:39:03AM +0200, Waldemar Brodkorb wrote:
> Hi,
>
> I would like to suggest following patch for 4.4/4.9 stable
> kernel releases to fix gcc 7.1 compile issues:
>
> Subject: [PATCH] sparc64: make string buffers large enough
> Commit: b5c3206190f1fddd100b3060eb15f0d775ffeab8
No objection from me, David, mind if I queue this up?
thanks,
greg k-h
next prev parent reply other threads:[~2017-06-15 7:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-15 7:39 gcc 7.1 sparc64 fixes Waldemar Brodkorb
2017-06-15 7:39 ` Waldemar Brodkorb
2017-06-15 7:51 ` Greg KH [this message]
2017-06-15 7:51 ` Greg KH
2017-06-15 14:57 ` David Miller
2017-06-15 14:57 ` David Miller
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=20170615075137.GA26883@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=davem@davemloft.net \
--cc=sparclinux@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=wbx@openadk.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.