From: Borislav Petkov <bp@alien8.de>
To: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
gregkh@linuxfoundation.org, len.brown@intel.com, rjw@sisk.pl,
arjan@linux.intel.com, jacob.jun.pan@linux.intel.com
Subject: Re: [PATCH v1 5/6] bitops: Introduce BIT_ULL
Date: Thu, 19 Sep 2013 19:28:19 +0200 [thread overview]
Message-ID: <20130919172819.GD9412@pd.tnic> (raw)
In-Reply-To: <523B2F57.2050504@linux.intel.com>
On Thu, Sep 19, 2013 at 10:07:35AM -0700, Srinivas Pandruvada wrote:
> The current definition for BIT_64 is in arch/x86/include/asm/bitops.h.
> I feel it should be applicable for all architectures and move to some
> common file.
Feel free to move it there or change BIT_64 to BIT_ULL or whatever ...
just don't add yet another redundant macro.
Thanks.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2013-09-19 17:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-19 16:00 [PATCH v1 0/6] Power Capping Framework and RAPL Driver Srinivas Pandruvada
2013-09-19 16:00 ` [PATCH v1 1/6] PowerCap: Documentation Srinivas Pandruvada
2013-09-19 16:00 ` [PATCH v1 2/6] PowerCap: Add class driver Srinivas Pandruvada
2013-09-19 16:00 ` [PATCH v1 3/6] PowerCap: Added to drivers build Srinivas Pandruvada
2013-09-19 16:00 ` [PATCH v1 4/6] x86/msr: add 64bit _on_cpu access functions Srinivas Pandruvada
2013-09-19 16:00 ` [PATCH v1 5/6] bitops: Introduce BIT_ULL Srinivas Pandruvada
2013-09-19 16:48 ` Borislav Petkov
2013-09-19 17:07 ` Srinivas Pandruvada
2013-09-19 17:28 ` Borislav Petkov [this message]
2013-09-19 18:14 ` Joe Perches
2013-09-19 18:34 ` Srinivas Pandruvada
2013-09-19 18:34 ` Joe Perches
2013-09-19 18:48 ` Borislav Petkov
2013-09-19 16:00 ` [PATCH v1 6/6] Introduce Intel RAPL power capping driver Srinivas Pandruvada
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=20130919172819.GD9412@pd.tnic \
--to=bp@alien8.de \
--cc=arjan@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jacob.jun.pan@linux.intel.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=srinivas.pandruvada@linux.intel.com \
/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).