All of lore.kernel.org
 help / color / mirror / Atom feed
From: viresh.linux@gmail.com (viresh kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/9] SPEAr13xx: Add header files
Date: Mon, 23 Apr 2012 17:17:59 +0530	[thread overview]
Message-ID: <CAOh2x==CVfODg=iOKPrQq2HYMAEFUBpwkrkZwW3f5As7Z2pTdA@mail.gmail.com> (raw)
In-Reply-To: <201204211837.35023.arnd@arndb.de>

On Sun, Apr 22, 2012 at 12:07 AM, Arnd Bergmann <arnd@arndb.de> wrote:
> It's still really ugly to have that in a global header file, including the
> hardcoded register addresses.

I will check if i can move this to clock.c for now, to move things quicker. :)

--
viresh

  reply	other threads:[~2012-04-23 11:47 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-20 17:22 [PATCH 0/9] Add support for SPEAr13xx SoCs Viresh Kumar
2012-04-20 17:22 ` [PATCH 1/9] SPEAr13xx: Add header files Viresh Kumar
2012-04-20 17:52   ` Arnd Bergmann
2012-04-21 12:27     ` viresh kumar
2012-04-21 18:37       ` Arnd Bergmann
2012-04-23 11:47         ` viresh kumar [this message]
2012-04-23 12:25           ` viresh kumar
2012-04-20 17:22 ` [PATCH 2/9] SPEAr13xx: Add source files Viresh Kumar
2012-04-20 18:15   ` Arnd Bergmann
2012-04-21 12:23     ` viresh kumar
2012-04-21 18:31       ` Arnd Bergmann
2012-04-20 17:22 ` [PATCH 3/9] SPEAr13xx: Add common clock framework support Viresh Kumar
2012-04-23 21:43   ` Turquette, Mike
2012-04-24  3:57     ` Viresh Kumar
2012-04-20 17:22 ` [PATCH 4/9] pinctrl: SPEAr: Create macro for declaring GPIO PINS Viresh Kumar
2012-04-20 17:22 ` [PATCH 6/9] SPEAr13xx: Add dts and dtsi files Viresh Kumar
2012-04-20 17:22 ` [PATCH 7/9] SPEAr13xx: Add compilation support Viresh Kumar
2012-04-20 17:22 ` [PATCH 8/9] SPEAr13xx: Add defconfig Viresh Kumar
2012-04-20 17:22 ` [PATCH 9/9] SPEAr: Update MAINTAINERS and Documentation Viresh Kumar
2012-04-20 18:21 ` [PATCH 0/9] Add support for SPEAr13xx SoCs Arnd Bergmann
2012-04-21 12:17   ` viresh kumar
2012-04-21 12:24     ` Arnd Bergmann
2012-04-21 12:29       ` viresh kumar

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='CAOh2x==CVfODg=iOKPrQq2HYMAEFUBpwkrkZwW3f5As7Z2pTdA@mail.gmail.com' \
    --to=viresh.linux@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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 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.