From: 'Greg Kroah-Hartman' <gregkh@linuxfoundation.org>
To: Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp>
Cc: stable@vger.kernel.org, ben.hutchings@codethink.co.uk
Subject: Re: [PATCH v2 4.4 3/3] x86/fpu: Finish excising 'eagerfpu'
Date: Tue, 10 Jul 2018 16:10:20 +0200 [thread overview]
Message-ID: <20180710141020.GL1123@kroah.com> (raw)
In-Reply-To: <003401d41757$5601f730$0205e590$@toshiba.co.jp>
On Mon, Jul 09, 2018 at 04:34:57PM +0900, Daniel Sangorrin wrote:
> Oops, So sorry.
> I finally figured out why cc-cmd was not working.
> I had "suppresscc all" on my gitconfig for another project.
> I will resend the patches.
Please do, I did not get a solid set of patches here at all. I've
dropped the few that did make it through...
greg k-h
next prev parent reply other threads:[~2018-07-10 14:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 6:15 [PATCH v2 4.4 1/3] x86/fpu: Remove use_eager_fpu() Daniel Sangorrin
2018-07-09 6:31 ` [PATCH v2 4.4 2/3] x86/fpu: Remove struct fpu::counter Daniel Sangorrin
2018-07-09 6:40 ` [PATCH v2 4.4 3/3] x86/fpu: Finish excising 'eagerfpu' Daniel Sangorrin
2018-07-09 7:34 ` Daniel Sangorrin
2018-07-10 14:10 ` 'Greg Kroah-Hartman' [this message]
2018-07-11 0:59 ` Daniel Sangorrin
2018-07-11 11:07 ` 'Greg Kroah-Hartman'
2018-07-12 0:38 ` Daniel Sangorrin
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=20180710141020.GL1123@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ben.hutchings@codethink.co.uk \
--cc=daniel.sangorrin@toshiba.co.jp \
--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;
as well as URLs for NNTP newsgroup(s).