From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org,
linux-pm@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Peter Anvin <hpa@zytor.com>, Wolfram Sang <wsa@the-dreams.de>,
Zhang Rui <rui.zhang@intel.com>,
Eduardo Valentin <edubezval@gmail.com>,
Hock Leong Kweh <hock.leong.kweh@intel.com>
Subject: Re: [PATCH v2 1/1] x86/platform/iosf_mbi: Remove duplicate definitions
Date: Wed, 25 Nov 2015 16:33:04 +0200 [thread overview]
Message-ID: <1448461984.15393.53.camel@linux.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1511251514580.12555@nanos>
On Wed, 2015-11-25 at 15:20 +0100, Thomas Gleixner wrote:
> On Wed, 11 Nov 2015, Andy Shevchenko wrote:
>
> > The read and write opcodes are global for all units on SoC and even
> across
> > Intel SoCs. Remove duplication of corresponding constants. At the
> same time
> > convert all current users.
> >
> > No functional change.
> >
> > Cc: Thomas Gleixner <tglx@linutronix.de>
> > Cc: Ingo Molnar <mingo@redhat.com>
> > Cc: Peter Anvin <hpa@zytor.com>
> > Cc: Wolfram Sang <wsa@the-dreams.de>
> > Cc: Zhang Rui <rui.zhang@intel.com>
> > Cc: Eduardo Valentin <edubezval@gmail.com>
> > Cc: Hock Leong Kweh <hock.leong.kweh@intel.com>
Eduardo, Rui, can you provide your ACKs or comments about the patch?
> >
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > ---
> > Since v1:
> > - satisfy kbuild robot
> >
> > arch/x86/include/asm/iosf_mbi.h | 49 +++++-----------
> ------
> > arch/x86/platform/atom/punit_atom_debug.c | 7 +---
> > arch/x86/platform/intel-quark/imr.c | 28 +++++--------
> > drivers/i2c/busses/i2c-designware-baytrail.c | 17 +++-----
> > drivers/powercap/intel_rapl.c | 10 ++---
> > drivers/thermal/intel_quark_dts_thermal.c | 61 ++++++++++++++
> --------------
> > drivers/thermal/intel_soc_dts_iosf.c | 43 ++++++++++----
> ------
>
> Hmm. Either we get acks of all maintainers and merge it through
> tip/x86/...
I prefer this way because…
> or we do the following:
>
> Add the new constants w/o using them in a seperate patch and ship
> that
> linuswards now. Then the subsystem maintainers can pick the
> individual
> patches up and after the merge window closes we remove the old
> constants in one go.
>
> Either way works for me.
…we are working on another fix which is based also on this patch. Can
you provide your ACK if you are okay with the changes to arch/x86 ?
>
> Thanks,
>
> tglx
>
>
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2015-11-25 14:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 17:59 [PATCH v2 1/1] x86/platform/iosf_mbi: Remove duplicate definitions Andy Shevchenko
2015-11-24 9:50 ` Andy Shevchenko
2015-11-24 13:26 ` Wolfram Sang
2015-11-25 14:20 ` Thomas Gleixner
2015-11-25 14:33 ` Andy Shevchenko [this message]
2015-11-25 14:37 ` Thomas Gleixner
2015-12-07 22:56 ` Rafael J. Wysocki
2015-12-04 2:05 ` Ong, Boon Leong
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=1448461984.15393.53.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=edubezval@gmail.com \
--cc=hock.leong.kweh@intel.com \
--cc=hpa@zytor.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rui.zhang@intel.com \
--cc=tglx@linutronix.de \
--cc=wsa@the-dreams.de \
/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