From: Ingo Molnar <mingo@elte.hu>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
Jeremy Fitzhardinge <jeremy@goop.org>,
Becky Bruce <beckyb@kernel.crashing.org>
Cc: jj@chaosbits.net, weiyi.huang@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: swiotlb: remove duplicated #include
Date: Sun, 4 Jan 2009 13:19:14 +0100 [thread overview]
Message-ID: <20090104121914.GA30255@elte.hu> (raw)
In-Reply-To: <20090104210420X.fujita.tomonori@lab.ntt.co.jp>
* FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp> wrote:
> On Sun, 4 Jan 2009 12:25:43 +0100
> Ingo Molnar <mingo@elte.hu> wrote:
>
> >
> > * Jesper Juhl <jj@chaosbits.net> wrote:
> >
> > > On Sun, 4 Jan 2009, Huang Weiyi wrote:
> > >
> > > > Removed duplicated #include in lib/swiotlb.c.
> > > >
> > >
> > > This is identical to a patch I already submitted -
> > > http://lkml.org/lkml/2009/1/2/360 - but I don't know if that one has been
> > > merged anywhere yet.
> >
> > i've applied yours to tip/core/urgent, thanks Jesper!
>
> The same cleanup is in tip/core/iommu:
>
> http://marc.info/?l=linux-kernel&m=123044446721529&w=2
yes, correct - as part of Becky and Jeremy's highmem series.
> My cleanup patches in it are trivial, but I like to see Becky's swiotlb
> highmem work, which is still in tip/core/iommu. When do you plan to push
> it to mainline?
In a few days, but wanted to hear back from either Jeremy or Becky first
about how well they actually work in their usecases.
Ingo
next prev parent reply other threads:[~2009-01-04 12:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-04 3:13 swiotlb: remove duplicated #include Huang Weiyi
2009-01-04 9:59 ` Jesper Juhl
2009-01-04 11:25 ` Ingo Molnar
2009-01-04 12:04 ` FUJITA Tomonori
2009-01-04 12:19 ` Ingo Molnar [this message]
2009-01-04 12:41 ` FUJITA Tomonori
2009-01-04 13:01 ` Ingo Molnar
2009-01-04 22:48 ` Jeremy Fitzhardinge
2009-01-05 2:40 ` FUJITA Tomonori
2009-01-05 13:16 ` Ingo Molnar
2009-01-09 16:37 ` Ian Campbell
2009-01-09 17:36 ` Becky Bruce
2009-01-09 18:10 ` Ian Campbell
2009-01-09 18:32 ` [PATCH 0/2] " Ian Campbell
2009-01-09 18:32 ` [PATCH 1/2] swiotlb: range_needs_mapping should take a physical address Ian Campbell
2009-01-09 18:32 ` [PATCH 2/2] swiotlb: do not use sg_virt() Ian Campbell
2009-01-11 3:58 ` FUJITA Tomonori
2009-01-11 3:58 ` [PATCH 1/2] swiotlb: range_needs_mapping should take a physical address FUJITA Tomonori
2009-01-11 3:55 ` [PATCH 0/2] Re: swiotlb: remove duplicated #include Ingo Molnar
2009-01-11 4:00 ` FUJITA Tomonori
2009-01-11 4:04 ` Ingo Molnar
2009-01-11 4:22 ` FUJITA Tomonori
2009-01-11 4:32 ` Ingo Molnar
2009-01-11 4:46 ` FUJITA Tomonori
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=20090104121914.GA30255@elte.hu \
--to=mingo@elte.hu \
--cc=beckyb@kernel.crashing.org \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=jeremy@goop.org \
--cc=jj@chaosbits.net \
--cc=linux-kernel@vger.kernel.org \
--cc=weiyi.huang@gmail.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