From: Javi Merino <javi.merino@arm.com>
To: Emil Velikov <emil.l.velikov@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>,
ML dri-devel <dri-devel@lists.freedesktop.org>,
Daniel Vetter <daniel.vetter@intel.com>,
Guenter Roeck <linux@roeck-us.net>,
"Darrick J. Wong" <djwong@us.ibm.com>
Subject: Re: [PATCH 1/4] kernel.h: Implement DIV_ROUND_CLOSEST_ULL
Date: Fri, 20 Mar 2015 18:27:37 +0000 [thread overview]
Message-ID: <20150320182737.GA3091@e104805> (raw)
In-Reply-To: <CACvgo53hUpS-kecKv5-kvvr2tMzrr5HRFq+_Z35A35LKJqVp9A@mail.gmail.com>
On Fri, Mar 20, 2015 at 06:19:26PM +0000, Emil Velikov wrote:
> On 20 March 2015 at 11:14, Javi Merino <javi.merino@arm.com> wrote:
> > We have grown a number of different implementations of
> > DIV_ROUND_CLOSEST_ULL throughout the kernel. Move the i915 one to
> > kernel.h so that it can be reused.
> >
> > Cc: Daniel Vetter <daniel.vetter@intel.com>
> > Cc: Jani Nikula <jani.nikula@linux.intel.com>
> > Cc: David Airlie <airlied@linux.ie>
> > Cc: Darrick J. Wong <djwong@us.ibm.com>
> > Cc: Guenter Roeck <linux@roeck-us.net>
> > Cc: Andrew Morton <akpm@linux-foundation.org>
> > Signed-off-by: Javi Merino <javi.merino@arm.com>
> > ---
> > drivers/gpu/drm/i915/intel_drv.h | 4 +---
> > include/linux/kernel.h | 11 +++++++++++
> > 2 files changed, 12 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/intel_drv.h b/drivers/gpu/drm/i915/intel_drv.h
> > index eef79ccd0b7c..346e28fdd7dd 100644
> > --- a/drivers/gpu/drm/i915/intel_drv.h
> > +++ b/drivers/gpu/drm/i915/intel_drv.h
> > @@ -28,6 +28,7 @@
> > #include <linux/async.h>
> > #include <linux/i2c.h>
> > #include <linux/hdmi.h>
> > +#include <linux/kernel.h>
> Hi Javi,
>
> Small suggestion - can we include the header only where needed ?
> i915/intel_panel.c seems to be the only user of DIV_ROUND_CLOSEST
> which will need an update.
>
> Somewhat trivial pick but it will prevent ~40 unnecessary dives in kernel.h.
Sure, I'll fix it in the next version of the series.
Cheers,
Javi
next prev parent reply other threads:[~2015-03-20 18:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 11:14 [PATCH 0/4] Consolidate DIV_ROUND_CLOSEST_ULL() Javi Merino
2015-03-20 11:14 ` [PATCH 1/4] kernel.h: Implement DIV_ROUND_CLOSEST_ULL Javi Merino
2015-03-20 13:15 ` Alex Elder
2015-03-20 18:19 ` Emil Velikov
2015-03-20 18:19 ` Emil Velikov
2015-03-20 18:27 ` Javi Merino [this message]
2015-03-23 7:41 ` Daniel Vetter
2015-03-23 7:41 ` Daniel Vetter
2015-03-23 12:34 ` Jeff Epler
2015-03-23 17:04 ` Javi Merino
2015-03-23 17:04 ` Javi Merino
2015-03-24 11:49 ` Javi Merino
2015-03-24 11:49 ` Javi Merino
2015-03-20 11:14 ` [PATCH 2/4] clk: bcm/kona: use DIV_ROUND_CLOSEST_ULL() Javi Merino
2015-03-20 11:14 ` [PATCH 3/4] cpuidle: menu: " Javi Merino
2015-03-20 11:14 ` [PATCH 4/4] media: cxd2820r: " Javi Merino
2015-03-20 11:17 ` Antti Palosaari
2015-03-20 13:51 ` Alex Elder
2015-03-20 17:27 ` Javi Merino
2015-03-20 19:46 ` Alex Elder
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=20150320182737.GA3091@e104805 \
--to=javi.merino@arm.com \
--cc=akpm@linux-foundation.org \
--cc=daniel.vetter@intel.com \
--cc=djwong@us.ibm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=emil.l.velikov@gmail.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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.