mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: <jamey@crl.dec.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] platform-device driver for MQ11xx graphics chip
Date: Fri, 5 Aug 2005 00:17:37 -0700	[thread overview]
Message-ID: <20050805001737.7bec8de7.akpm@osdl.org> (raw)
In-Reply-To: <20050802192041.C09C5B4262@lspace.crl.dec.com>

<jamey@crl.dec.com> wrote:
>
> 
> This patch adds platform_device driver for MQ11xx system-on-chip
> graphics chip.  This chip is used in several non-PCI ARM and MIPS
> platforms such as the iPAQ H5550.  Two subsequent patches add
> support for the framebuffer and USB gadget subdevices.  This patch
> adds the toplevel driver to drivers/platform because it does not
> provide any specific functionality (e.g., framebuffer) and it not tied
> to a named physical bus.  In these platforms, the MQ11xx is tied
> directly to the host bus.
> 
> ...
> +
> +static void
> +mq_free (struct mediaq11xx_base *zis, u32 addr, unsigned size)
> +{
> +	int i, j;
> +	u32 eaddr;
> +	struct mq_data *mqdata = to_mq_data (zis);
> +
> +	size = (size + MEMBLOCK_ALIGN - 1) & ~(MEMBLOCK_ALIGN - 1);
> +	eaddr = addr + size;
> +
> +	spin_lock (&mqdata->mem_lock);

It's unusual for a memory allocate/free function to not be IRQ-safe.  Will
there never be a requirement that mq_free() or mq_alloc() be called from
interrupts or softirq's?

> +	spin_unlock (&mqdata->mem_lock);

You've religiously used the wrong coding style throughout these patches:
neither core kernel nor arch/arm places a space before the opening paren. 
A little thing, but easy to get right.

There are eight-spaces where tabs should be in various places too..


      reply	other threads:[~2005-08-05  7:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-02 19:20 jamey
2005-08-05  7:17 ` Andrew Morton [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=20050805001737.7bec8de7.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=jamey@crl.dec.com \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®