public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Michal Simek <monstr@monstr•eu>
To: microblaze-uclinux@itee•uq.edu.au
Cc: nacc@us•ibm.com, linuxppc-dev@lists•ozlabs.org, miltonm@bga•com
Subject: Re:
Date: Wed, 20 Oct 2010 15:31:09 +1000	[thread overview]
Message-ID: <4CBE7E9D.3040107@monstr.eu> (raw)
In-Reply-To: <1287422825-14999-2-git-send-email-nacc@us.ibm.com>

Nishanth Aravamudan wrote:
> Use set_dma_ops and remove now used-once oddly named temp pointer sd.
> 
> Signed-off-by: Milton Miller <miltonm@bga•com>
> Signed-off-by: Nishanth Aravamudan <nacc@us•ibm.com>
> Cc: benh@kernel•crashing.org
> Cc: linuxppc-dev@lists•ozlabs.org
> ---

Maybe I forget to write you that this patch is already applied.
http://git.monstr.eu/git/gitweb.cgi?p=linux-2.6-microblaze.git;a=commit;h=9a6df6cbfd903b6d9b4b1021f46d78601adfac77


Thanks,
Michal

-- 
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian

  reply	other threads:[~2010-10-20  5:31 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1287422825-14999-1-git-send-email-nacc@us.ibm.com>
2010-10-18 17:26 ` [PATCH 1/7] microblaze: pci-common cleanup Nishanth Aravamudan
2010-10-20  5:31   ` Michal Simek [this message]
2010-11-01  6:29   ` Michal Simek
2010-10-18 17:26 ` [PATCH 2/7] ppc/vio: use dma ops helpers Nishanth Aravamudan
2010-10-18 17:27 ` [PATCH 3/7] ppc/pasemi: clean up pasemi iommu table initializations Nishanth Aravamudan
2010-10-18 17:27 ` [PATCH 4/7] ppc/cell: beat dma ops cleanup Nishanth Aravamudan
2010-10-18 17:27 ` [PATCH 5/7] ppc/dart: iommu table cleanup Nishanth Aravamudan
2010-10-18 17:27 ` [PATCH 6/7] ppc/pseries: iommu cleanup Nishanth Aravamudan
2010-10-18 17:27 ` [PATCH 7/7] ppc64 iommu: use coherent_dma_mask for alloc_coherent Nishanth Aravamudan
2022-04-05 21:41 rcu_sched self-detected stall on CPU Miguel Ojeda
2022-04-06  9:31 ` Zhouyi Zhou
2022-04-06 17:00   ` Paul E. McKenney
2022-04-08  7:23     ` Michael Ellerman
2022-04-08 14:42       ` Michael Ellerman
2022-04-13  5:11         ` Nicholas Piggin
2022-04-22 15:53           ` Thomas Gleixner
2022-04-23  2:29             ` Re: Nicholas Piggin
  -- strict thread matches above, loose matches on Subject: below --
2019-08-30 19:54 [PATCH] Revert "asm-generic: Remove unneeded __ARCH_WANT_SYS_LLSEEK macro" Arnd Bergmann
     [not found] ` <20190830202959.3539-1-msuchanek@suse.de>
2019-08-30 20:32   ` Arnd Bergmann
2010-08-18 20:56 Wolfgang Denk
2010-08-19  1:04 ` Stephen Rothwell
2010-09-02  6:14 ` Re: Wolfgang Denk
2010-09-02 14:51   ` Rupjyoti Sarmah
2010-09-07  6:29   ` RE: Rupjyoti Sarmah
2009-07-23 14:38 Solomon Peachy
2009-07-26 23:38 ` Benjamin Herrenschmidt
2008-08-21  6:21 Schmid Alexander
2008-08-21  9:48 ` Wolfgang Denk
2008-01-02 18:16 Re: rsa
2007-11-01 18:18 Mead, Joseph
2007-11-01 19:07 ` Grant Likely
2007-11-02  9:35 ` MingLiu
2007-04-27 19:15 Mead, Joseph
2007-04-27 20:30 ` Scott Coulter
2007-04-12 15:44 Milton Miller
2007-04-13  2:23 ` Benjamin Herrenschmidt
2007-04-13 18:45   ` Re: Segher Boessenkool
2007-04-13 18:59     ` Re: Sergei Shtylyov
2007-04-13 19:10       ` Re: Segher Boessenkool
1999-05-18  7:26 nicolas.boussekeyt
1999-05-18 18:03 ` Alex Vallens

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=4CBE7E9D.3040107@monstr.eu \
    --to=monstr@monstr$(echo .)eu \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    --cc=microblaze-uclinux@itee$(echo .)uq.edu.au \
    --cc=miltonm@bga$(echo .)com \
    --cc=nacc@us$(echo .)ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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