All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Daniel J Blueman <daniel@numascale.com>
Cc: Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	x86@kernel.org, linux-kernel@vger.kernel.org,
	linux-pci@vger.kernel.org, Steffen Persvold <sp@numascale.com>
Subject: Re: [PATCH v3 3/5] Numachip: Add safe is-present function
Date: Mon, 3 Nov 2014 20:45:42 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.11.1411032044590.5308@nanos> (raw)
In-Reply-To: <1414915813-2462-3-git-send-email-daniel@numascale.com>

On Sun, 2 Nov 2014, Daniel J Blueman wrote:

> Add safe function to check if Numachip is detected, to be used elsewhere.

I cannot find a use case for this. I guess this is a left over of the
earlier 2G change, right?
 
Thanks,

	tglx

  reply	other threads:[~2014-11-03 19:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-02  8:10 [PATCH v3 1/5] Numachip: Fix 16-bit APIC ID truncation Daniel J Blueman
2014-11-02  8:10 ` [PATCH v3 2/5] Numachip: Elide self-IPI ICR polling Daniel J Blueman
2014-11-02  8:10 ` [PATCH v3 3/5] Numachip: Add safe is-present function Daniel J Blueman
2014-11-03 19:45   ` Thomas Gleixner [this message]
2014-11-03 22:55     ` Daniel J Blueman
2014-11-03 22:58       ` Thomas Gleixner
2014-11-02  8:10 ` [PATCH v3 4/5] Numachip: APIC driver cleanups Daniel J Blueman
2014-11-02  8:10 ` [PATCH v3 5/5] Use 2GB memory block size on large x86-64 systems Daniel J Blueman
2014-11-03 19:38   ` Thomas Gleixner
2014-11-03 23:15     ` Daniel J Blueman
2014-11-03 23:36       ` Thomas Gleixner
2014-11-04  7:30         ` Daniel J Blueman
2014-11-04  7:50           ` Thomas Gleixner

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=alpine.DEB.2.11.1411032044590.5308@nanos \
    --to=tglx@linutronix.de \
    --cc=bhelgaas@google.com \
    --cc=daniel@numascale.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=sp@numascale.com \
    --cc=x86@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 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.