All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Daniel Gollub <daniel.gollub@gmail.com>, fio@vger.kernel.org
Subject: Re: [PATCH 1/4] Replace CONFIG_CPU_COUNT with plain CPU_COUNT
Date: Thu, 01 May 2014 11:22:26 -0600	[thread overview]
Message-ID: <536282D2.5030508@kernel.dk> (raw)
In-Reply-To: <1398946024-13566-1-git-send-email-daniel.gollub@gmail.com>

On 05/01/2014 06:07 AM, Daniel Gollub wrote:
> Fixes double-declartion issue of CPU_COUNT when fio.h is included by
> third-party projects.
> 
> Checking for a define of CPU_COUNT seems to be a common approach
> to deal with different versions of sched.h]

Thanks Daniel, applied all 5 of your patches.

-- 
Jens Axboe



      parent reply	other threads:[~2014-05-01 17:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-01 12:07 [PATCH 1/4] Replace CONFIG_CPU_COUNT with plain CPU_COUNT Daniel Gollub
2014-05-01 12:07 ` [PATCH 2/4] distinguish internal/ext. builds with FIO_INTERNAL Daniel Gollub
2014-05-01 12:07 ` [PATCH 3/4] Avoid double-declaration of ARRAY_SIZE Daniel Gollub
2014-05-01 12:07 ` [PATCH 4/4] Avoid double declaration of leXX_to_cpu Daniel Gollub
2014-05-01 17:22 ` Jens Axboe [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=536282D2.5030508@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=daniel.gollub@gmail.com \
    --cc=fio@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 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.