From: Shuah Khan <shuah.khan@hp.com>
To: David Miller <davem@davemloft.net>
Cc: kyungmin.park@samsung.com, arnd@arndb.de,
m.szyprowski@samsung.com, sam@ravnborg.org,
sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org,
shuahkhan@gmail.com
Subject: Re: [PATCH RFT RESEND linux-next] sparc: dma-mapping: support debug_dma_mapping_error
Date: Fri, 26 Oct 2012 15:40:24 -0600 [thread overview]
Message-ID: <1351287624.6885.4.camel@lorien2> (raw)
In-Reply-To: <20121026.151055.328093458246032481.davem@davemloft.net>
On Fri, 2012-10-26 at 15:10 -0400, David Miller wrote:
> From: David Miller <davem@davemloft.net>
> Date: Fri, 26 Oct 2012 15:01:53 -0400 (EDT)
>
> > From: Shuah Khan <shuah.khan@hp.com>
> > Date: Fri, 26 Oct 2012 10:13:09 -0600
> >
> >> Add support for debug_dma_mapping_error() call to avoid warning from
> >> debug_dma_unmap() interface when it checks for mapping error checked
> >> status. Without this patch, device driver failed to check map error
> >> warning is generated.
> >>
> >> Signed-off-by: Shuah Khan <shuah.khan@hp.com>
> >
> > Why are you resending this?
> >
> > When you resend patches, you have to give a reason. Did the patch
> > change? Are you updating the CC: list of the patch posting? Are
> > you correcting something else?
>
> In fact you sent this _3_ times. Please, don't do this, or at least
> explain why you are reposting something each time.
I am really sorry for the noise. I forgot to mark this explicitly for
linux-next the first time and this patch depends on a patch that went
into linux-next. I sent a few patches for several architectures and lost
track. I meant to add explanation before I hit send. The reason for
resend is to tag it for linux-next.
-- Shuah
next prev parent reply other threads:[~2012-10-26 21:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-26 0:36 [PATCH RFT] sparc: dma-mapping: support debug_dma_mapping_error Shuah Khan
2012-10-26 0:38 ` [PATCH RFT RESEND] " Shuah Khan
2012-10-26 16:13 ` [PATCH RFT RESEND linux-next] " Shuah Khan
2012-10-26 19:01 ` David Miller
2012-10-26 19:10 ` David Miller
2012-10-26 21:40 ` Shuah Khan [this message]
2012-11-10 0:38 ` David Miller
2012-11-10 0:52 ` Shuah Khan
2012-11-10 0:54 ` David Miller
2012-11-10 1:21 ` Shuah Khan
2012-11-15 17:39 ` Shuah Khan
2012-11-17 12:22 ` [PATCH RFT] " Joerg Roedel
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=1351287624.6885.4.camel@lorien2 \
--to=shuah.khan@hp.com \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=sam@ravnborg.org \
--cc=shuahkhan@gmail.com \
--cc=sparclinux@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox