From: Ralf Baechle <ralf@linux-mips.org>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] No I/O ports on the DECstation
Date: Thu, 7 Jun 2007 18:47:49 +0100 [thread overview]
Message-ID: <20070607174749.GB1893@linux-mips.org> (raw)
In-Reply-To: <Pine.LNX.4.64N.0705311359250.7856@blysk.ds.pg.gda.pl>
On Thu, May 31, 2007 at 02:21:11PM +0100, Maciej W. Rozycki wrote:
> > Stale patch?
>
> Not at all, it would seem. It applies just fine and is still required as
> of 2.6.22-rc3. These CONFIG_HAS_IOMEM and CONFIG_HAS_IOPORT options are
> pretty recent anyway -- there is little chance for anything about them to
> get stale yet.
Git is pickier than patch. Anything that will still be applied by patch
with a fuzz will be rejected by git-apply. For good reason, I several
times ended with a corrupt tree thanks to patch happily (miss-)applying
some stale patch with fuzz. Heck, it hit akpm recently ...
Anyway, this one was trivial and is in my queue tree now.
Ralf
next prev parent reply other threads:[~2007-06-07 17:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-29 14:08 [PATCH] No I/O ports on the DECstation Maciej W. Rozycki
2007-05-31 12:15 ` Ralf Baechle
2007-05-31 13:21 ` Maciej W. Rozycki
2007-06-07 17:47 ` Ralf Baechle [this message]
2007-06-07 18:01 ` Maciej W. Rozycki
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=20070607174749.GB1893@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.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.