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: Fri, 25 Jan 2013 13:00:32 +0100	[thread overview]
Message-ID: <1359115232.6647.14.camel@x61.thuisdomein> (raw)
In-Reply-To: <CACRpkdb0V=yasmJv1ygL7cq6G3uGf6+QAZ7GR5a3bb1-XJgiiA@mail.gmail.com>

On Fri, 2013-01-25 at 12:06 +0100, Linus Walleij wrote:
> Basically I do git log and when I see this I think:
> 
> commit 0c418844dce21fa7000b51190f393c7d6a7ee12d
> Author: Paul Bolle <pebolle@tiscali.nl>
> Date:   Mon Nov 19 21:04:11 2012 +0100
> 
>     mfd: lpc_ich: One uninitialized cell is no error
> 
> "Hm, there is another guy who's actually using this hardware."

I see, thanks. (Note to self: I should work on my psychic abilities. If
all those quacks can use them it can't be too hard.)

> "If this patch breaks it he will probably be upset."

I backported this patch to 3.7.5 (which I'm still running now). That
basically meant applying e294bc91760e11d2f1ebbac1d0a979069edf7adb ("mfd:
lpc_ich: Fix resource request for [mem 0x00000000]") first and then
manually adding some harmless context changes (ie, __devinit and
__devexit stuff).

Would testing on 3.7.5 be helpful?


Paul Bolle


  reply	other threads:[~2013-01-25 12:00 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 [this message]
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
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=1359115232.6647.14.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®