public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Gene Heskett <gheskett@wdtv.com>, Jason Cooper <jason@lakedaemon.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: AMD microcode fails to update with v3.8.3 and newer, bisect failed
Date: Wed, 01 Jan 2014 18:48:11 -0800	[thread overview]
Message-ID: <52C4D36B.9080507@infradead.org> (raw)
In-Reply-To: <201401012140.09972.gheskett@wdtv.com>

On 01/01/14 18:40, Gene Heskett wrote:
> On Wednesday 01 January 2014, Gene Heskett wrote:
>> On Wednesday 01 January 2014, Jason Cooper wrote:
> 
> Can you please repost that X64 default configuration "make" line, that 
> message seems to have encountered my expiry rules.
> 
> Thanks Jason.

Jason said:
$ make x86_64_defconfig
[in http://marc.info/?l=linux-kernel&m=138829693820368&w=2 ]


I would have said:
$ make ARCH=x86_64 defconfig


-- 
~Randy

  reply	other threads:[~2014-01-02  2:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-01 22:51 I'll pay along, if somebody would tell me the rules Gene Heskett
2014-01-02  0:19 ` AMD microcode fails to update with v3.8.3 and newer, bisect failed Jason Cooper
2014-01-02  2:25   ` Gene Heskett
2014-01-02  2:40     ` Gene Heskett
2014-01-02  2:48       ` Randy Dunlap [this message]
2014-01-02  2:52         ` Gene Heskett
2014-01-02  4:08     ` Ken Moffat
2014-01-02  4:45       ` Ken Moffat
2014-01-02  5:24         ` Gene Heskett
2014-01-02 18:15           ` Ken Moffat
2014-01-02 23:12             ` Gene Heskett
2014-01-03 14:55               ` Gene Heskett
2014-01-02  4:53       ` Gene Heskett

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=52C4D36B.9080507@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=gheskett@wdtv.com \
    --cc=jason@lakedaemon.net \
    --cc=linux-kernel@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