linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: ralf@linux-mips.org (ralf at linux-mips.org)
To: linux-arm-kernel@lists.infradead.org
Subject: [patch 11/14] i8253: Consolidate definitions of PIT_LATCH
Date: Wed, 01 Jun 2011 19:05:07 +0100	[thread overview]
Message-ID: <20110601180610.832810002@duck.linux-mips.net> (raw)
In-Reply-To: 20110601180456.801265664@duck.linux-mips.net

An embedded and charset-unspecified text was scrubbed...
Name: i8253-sort-out-pit_latch-definitions.patch
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20110601/dca93b95/attachment.ksh>

  parent reply	other threads:[~2011-06-01 18:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20110601180456.801265664@duck.linux-mips.net>
2011-06-01 18:04 ` [patch 02/14] i8253: Unify all kernel declarations of i8253_lock in <linux/i8253.h> ralf at linux-mips.org
2011-06-01 18:05 ` ralf at linux-mips.org [this message]
2011-06-01 18:05 ` [patch 12/14] i8253: Move remaining content and delete <asm/i8253.h> ralf at linux-mips.org
2011-06-02 11:29   ` Sergei Shtylyov

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=20110601180610.832810002@duck.linux-mips.net \
    --to=ralf@linux-mips.org \
    --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).