From: Ingo Molnar <mingo@elte.hu>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Joerg Roedel <joerg.roedel@amd.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"hpa@zytor.com" <hpa@zytor.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
the arch/x86 maintainers <x86@kernel.org>
Subject: Re: [PATCH 0/3] make swiotlb prototypes generic
Date: Mon, 11 Aug 2008 19:43:49 +0200 [thread overview]
Message-ID: <20080811174349.GP4524@elte.hu> (raw)
In-Reply-To: <57C9024A16AD2D4C97DC78E552063EA3083841F6@orsmsx505.amr.corp.intel.com>
* Luck, Tony <tony.luck@intel.com> wrote:
> > this small series of patches introduce a generic header file for the software
> > IO/TLB implementation in lib/swiotlb.c. Currently each architecture using this
> > code defines the prototypes itself. The prototypes are moved to
> > include/linux/swiotlb.h and this file is included in architecture specific code
> > for X86 and IA64. The changes are compile tested for both architectures.
>
> Boot tested on ia64 (using generic_defconfig, tiger_defconfig and
> zx1_defconfig).
given that this touches both x86 and ia64, i suspect queueing it in -mm
(as it is already) and merging it upstream from there would be the best
approach?
Ingo
next prev parent reply other threads:[~2008-08-11 17:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-07 13:06 [PATCH 0/3] make swiotlb prototypes generic Joerg Roedel
2008-08-07 13:06 ` [PATCH 1/3] introduce generic header file for the software IO/TLB Joerg Roedel
2008-08-07 13:06 ` [PATCH 2/3] x86: use common header for " Joerg Roedel
2008-08-07 13:06 ` [PATCH 3/3] ia64: " Joerg Roedel
2008-08-07 17:36 ` [PATCH 0/3] make swiotlb prototypes generic Luck, Tony
2008-08-11 17:43 ` Ingo Molnar [this message]
2008-08-11 17:55 ` Luck, Tony
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=20080811174349.GP4524@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=joerg.roedel@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=x86@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.