linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: SAMSUNG: Fix build of dev- infrastructure for module.h changes
Date: Mon, 1 Aug 2011 20:35:00 +0900	[thread overview]
Message-ID: <20110801113454.GA16629@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20110801110318.GA11811@windriver.com>

On Mon, Aug 01, 2011 at 07:03:19AM -0400, Paul Gortmaker wrote:

> I double checked what I did against yours, and I was using the
> more minimal export.h in dev-wdt.c file.  Did I miss something
> where it really requires all of module.h file?

I don't know, my only interest at the time was in fixing the build for
my primary development platform after it broke suddenly during the merge
window.  Like I said yesterday the first I knew about any changes in
module.h was when Dave Jones mentioned it in response to my fix for
cpufreq, I had assumed it was an ARM-specific change.

      reply	other threads:[~2011-08-01 11:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-01  0:29 [PATCH] ARM: SAMSUNG: Fix build of dev- infrastructure for module.h changes Mark Brown
2011-08-01 11:03 ` Paul Gortmaker
2011-08-01 11:35   ` Mark Brown [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=20110801113454.GA16629@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).