mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: "Bryan O'Sullivan" <bos@pathscale.com>
Cc: rdreier@cisco.com, ebiederm@xmission.com,
	linux-kernel@vger.kernel.org, openib-general@openib.org
Subject: Re: [PATCH] IB/ipath - program intconfig register using new HT irq hook
Date: Wed, 8 Nov 2006 14:44:02 -0800	[thread overview]
Message-ID: <20061108144402.0b6a7b23.akpm@osdl.org> (raw)
In-Reply-To: <545156d49f883c43af70.1163024486@localhost.localdomain>

On Wed, 08 Nov 2006 14:21:26 -0700
"Bryan O'Sullivan" <bos@pathscale.com> wrote:

> Eric's changes to the htirq infrastructure require corresponding
> modifications to the ipath HT driver code so that interrupts are still
> delivered properly.
> 
> Signed-off-by: Bryan O'Sullivan <bryan.osullivan@qlogic.com>
> Cc: Eric W. Biederman <ebiederm@xmission.com>
> Cc: Roland Dreier <rdreier@cisco.com>
> 
> diff -r 69779e2890e3 -r 545156d49f88 drivers/infiniband/hw/ipath/ipath_driver.c
> --- a/drivers/infiniband/hw/ipath/ipath_driver.c	Wed Nov 08 14:17:04 2006 -0800
> +++ b/drivers/infiniband/hw/ipath/ipath_driver.c	Wed Nov 08 14:19:27 2006 -0800

so...  Is this:

htirq-refactor-so-we-only-have-one-function-that-writes-to-the-chip.patch
htirq-allow-buggy-drivers-of-buggy-hardware-to-write-the-registers.patch
htirq-allow-buggy-drivers-of-buggy-hardware-to-write-the-registers-update.patch
ib-ipath-program-intconfig-register-using-new-ht-irq-hook.patch

considered 2.6.19 material?

  reply	other threads:[~2006-11-08 22:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-08 21:21 Bryan O'Sullivan
2006-11-08 22:44 ` Andrew Morton [this message]
2006-11-08 23:08   ` Bryan O'Sullivan
2006-11-08 23:18     ` Andrew Morton
2006-11-09  5:29       ` Eric W. Biederman

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=20061108144402.0b6a7b23.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=bos@pathscale.com \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openib-general@openib.org \
    --cc=rdreier@cisco.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®