All of lore.kernel.org
 help / color / mirror / Atom feed
From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] [PATCH] hwmon: Request the I/O regions in platform
Date: Thu, 22 Feb 2007 20:21:07 +0000	[thread overview]
Message-ID: <20070222212107.4050b6dc.khali@linux-fr.org> (raw)
In-Reply-To: <20070221201208.0420dc7d.khali@linux-fr.org>

On Thu, 22 Feb 2007 12:06:18 -0800, Juerg Haefliger wrote:
> OK, with your patch (http://lkml.org/lkml/diff/2007/2/20/310/1)
> applied, it works as advertised :-)

Great, thanks for testing and reporting.

> However, your platform-io-region patch doesn't apply cleanly:
> 
> juno:/usr/src/linux-2.6.21-rc1# patch -p1 < ../jean.patch
> patching file drivers/hwmon/f71805f.c
> Hunk #1 succeeded at 35 with fuzz 2.
> missing header for unified diff at line 11 of patch
> can't find file to patch at input line 11
> Perhaps you used the wrong -p or --strip option?
> The text leading up to this was:
> --------------------------
> |
> | static struct platform_device *pdev;
> --------------------------
> File to patch:

I don't understand, I thought you had already applied that one? Either
way, it smells like a corrupted patch file. It's probably visible if
you open the patch file with a text editor. I guess your mailer saved
it with some encoding and you'd need to fix it before you can apply it
(e.g. using metamail.)

-- 
Jean Delvare


  parent reply	other threads:[~2007-02-22 20:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-21 19:12 [lm-sensors] [PATCH] hwmon: Request the I/O regions in platform Jean Delvare
2007-02-22 16:14 ` Juerg Haefliger
2007-02-22 16:47 ` Jean Delvare
2007-02-22 20:06 ` Juerg Haefliger
2007-02-22 20:21 ` Jean Delvare [this message]
2007-02-24 21:06 ` David Hubbard
2007-02-26 16:39 ` Jean Delvare

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=20070222212107.4050b6dc.khali@linux-fr.org \
    --to=khali@linux-fr.org \
    --cc=lm-sensors@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 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.