mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "Aaron Sierra" <asierra@xes-inc.com>,
	"Peter Hurley" <peter@hurleysoftware.com>,
	"Samuel Ortiz" <sameo@linux.intel.com>,
	"Agócs Pál" <agocs.pal.86@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] lpc_ich: fix gpio base and control offsets
Date: Mon, 28 Jan 2013 12:41:20 +0100	[thread overview]
Message-ID: <1359373280.1345.5.camel@x61.thuisdomein> (raw)
In-Reply-To: <1359120339.883.4.camel@x61.thuisdomein>

On Fri, 2013-01-25 at 14:25 +0100, Paul Bolle wrote:
> 1) Should I try booting with the updated module too?

Booting turned out to be a non-issue. I use lpc_ich as a module (Fedora
17 default) and lpc_ich isn't included by default in Fedora 17's
initramfs. So booting v3.7.5 with an updated module should hardly differ
from insmod'ing manually. And indeed, booting that way didn't lead to
any obvious issues.


Paul Bolle


  parent reply	other threads:[~2013-01-28 11:41 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <b9fec05c-d383-4282-b2af-c95855ff6abb@zimbra>
2013-01-24 20:52 ` Aaron Sierra
2013-01-25  9:47   ` Linus Walleij
2013-01-25 10:04     ` Paul Bolle
2013-01-25 11:06       ` Linus Walleij
2013-01-25 12:00         ` Paul Bolle
2013-01-25 12:43           ` Linus Walleij
2013-01-25 13:25             ` Paul Bolle
2013-01-25 13:42               ` Paul Bolle
2013-01-25 15:22                 ` Aaron Sierra
2013-01-28 11:41               ` Paul Bolle [this message]
2013-01-25 13:44     ` Peter Hurley
2013-01-25 15:28       ` Peter Hurley
2013-01-25 16:48     ` Samuel Ortiz
2013-01-28 10:11       ` Linus Walleij
2013-01-28 11:45         ` Paul Bolle
2013-02-03 17:02   ` Samuel Ortiz
2013-02-04 15:38     ` Aaron Sierra
2013-02-14 22:48     ` Anatol Pomozov
2013-02-15 10:16       ` Samuel Ortiz
2013-02-15 14:28         ` Anatol Pomozov

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=1359373280.1345.5.camel@x61.thuisdomein \
    --to=pebolle@tiscali.nl \
    --cc=agocs.pal.86@gmail.com \
    --cc=asierra@xes-inc.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter@hurleysoftware.com \
    --cc=sameo@linux.intel.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

all inboxes | Powered by JetHome®