public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: David Sin <davidsin@ti.com>
Cc: linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Lajos Molnar <molnar@ti.com>
Subject: Re: [RFC v2 6/8] TILER-DMM: Geometry and view manipulation functions
Date: Tue, 30 Nov 2010 16:55:49 -0800	[thread overview]
Message-ID: <20101201005549.GB29171@kroah.com> (raw)
In-Reply-To: <1291147139-23472-7-git-send-email-davidsin@ti.com>

On Tue, Nov 30, 2010 at 01:58:57PM -0600, David Sin wrote:
> From: Lajos Molnar <molnar@ti.com>
> 
> This patch contains information on TILER geometry, as well as
> tiler_view_t object manipulation functions.
> 
> It also contains an internal TILER header file to share geometric
> information with other TILER files.
> 
> Signed-off-by: Lajos Molnar <molnar@ti.com>
> Signed-off-by: David Sin <davidsin@ti.com>
> ---
>  drivers/misc/tiler/_tiler.h     |   48 +++++

Ick, no, just name it "tiler.h" please.  There should not be any need to
put _ in front of a .h file.

> +u32 tiler_bpp(const struct tiler_block_t *b)
> +{
> +	enum tiler_fmt fmt = tiler_fmt(b->phys);
> +	BUG_ON(fmt == TILFMT_INVALID || fmt == TILFMT_PAGE);

Don't cause the kernel to crash within a driver for no good reason like
this.  Please fix these to WARN_ON if it's really something that can
happen.

If not, then just remove it.

> +
> +	return geom[fmt].bpp;
> +}
> +EXPORT_SYMBOL(tiler_bpp);

EXPORT_SYMBOL_GPL() perhaps for all of these?

thanks,

greg k-h

  reply	other threads:[~2010-12-01  1:03 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-30 19:58 [RFC v2 0/8] TI DMM-TILER driver David Sin
2010-11-30 19:58 ` [RFC v2 1/8] TILER-DMM: DMM-PAT driver for TI TILER David Sin
2010-12-01  6:04   ` Varadarajan, Charulatha
2010-12-02  2:10     ` Kanigeri, Hari
2010-12-02  2:27       ` Kanigeri, Hari
2010-12-02  5:16         ` Varadarajan, Charulatha
2010-12-02 10:23           ` Hari Kanigeri
2010-12-02 10:31             ` Varadarajan, Charulatha
2010-11-30 19:58 ` [RFC v2 2/8] TILER-DMM: Container manager interface and utility definitons David Sin
2010-11-30 19:58 ` [RFC v2 3/8] TILER-DMM: Sample TCM implementation: Simple TILER Allocator (SiTA) David Sin
2010-11-30 19:58 ` [RFC v2 4/8] TILER-DMM: TILER Memory Manager interface and implementation David Sin
2010-11-30 19:58 ` [RFC v2 5/8] TILER-DMM: TILER interface file and documentation David Sin
2010-12-01  0:53   ` Greg KH
2010-11-30 19:58 ` [RFC v2 6/8] TILER-DMM: Geometry and view manipulation functions David Sin
2010-12-01  0:55   ` Greg KH [this message]
2010-11-30 19:58 ` [RFC v2 7/8] TILER-DMM: Main TILER driver implementation David Sin
2010-11-30 19:57   ` Randy Dunlap
2010-11-30 19:58 ` [RFC v2 8/8] TILER-DMM: Linking TILER driver into the Linux kernel build David Sin
2010-12-01  0:56   ` Greg KH
2010-12-02 13:46     ` David Sin
2010-12-01  6:47 ` [RFC v2 0/8] TI DMM-TILER driver Varadarajan, Charulatha
2010-12-02 13:52   ` David Sin

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=20101201005549.GB29171@kroah.com \
    --to=greg@kroah.com \
    --cc=davidsin@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=molnar@ti.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