From: Dan Carpenter <dan.carpenter@oracle.com>
To: micky <micky_ching@realsil.com.cn>
Cc: ulf.hansson@linaro.org, sameo@linux.intel.com,
gregkh@linuxfoundation.org, linux-mmc@vger.kernel.org,
chris@printf.net, linux-kernel@vger.kernel.org,
wei_wang@realsil.com.cn, devel@linuxdriverproject.org,
rogerable@realtek.com
Subject: Re: [PATCH v2 2/2] mmc: rtsx: modify error handle and remove smatchwarnings
Date: Mon, 28 Apr 2014 15:40:01 +0300 [thread overview]
Message-ID: <20140428124001.GV26890@mwanda> (raw)
In-Reply-To: <535E3D8D.3000309@realsil.com.cn>
On Mon, Apr 28, 2014 at 07:37:49PM +0800, micky wrote:
> Hi Chris and Ulf,
>
> This patch is denpend on commit c42deffd5b53c9e583d83c7964854ede2f12410d.
> <mmc: rtsx: add support for pre_req and post_req>, and we discard
> the previous commit.
> we want discard this patch also(it it now in linux-next), need I
> send another patch to
> revert or it will be discard automatically?
Send a patch to revert this patch as well. You should have sent both
at the same time so it didn't cause breakage...
regards,
dan carpenter
WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: micky <micky_ching@realsil.com.cn>
Cc: chris@printf.net, sameo@linux.intel.com, ulf.hansson@linaro.org,
gregkh@linuxfoundation.org, linux-mmc@vger.kernel.org,
linux-kernel@vger.kernel.org, wei_wang@realsil.com.cn,
rogerable@realtek.com, devel@linuxdriverproject.org
Subject: Re: [PATCH v2 2/2] mmc: rtsx: modify error handle and remove smatchwarnings
Date: Mon, 28 Apr 2014 15:40:01 +0300 [thread overview]
Message-ID: <20140428124001.GV26890@mwanda> (raw)
In-Reply-To: <535E3D8D.3000309@realsil.com.cn>
On Mon, Apr 28, 2014 at 07:37:49PM +0800, micky wrote:
> Hi Chris and Ulf,
>
> This patch is denpend on commit c42deffd5b53c9e583d83c7964854ede2f12410d.
> <mmc: rtsx: add support for pre_req and post_req>, and we discard
> the previous commit.
> we want discard this patch also(it it now in linux-next), need I
> send another patch to
> revert or it will be discard automatically?
Send a patch to revert this patch as well. You should have sent both
at the same time so it didn't cause breakage...
regards,
dan carpenter
next prev parent reply other threads:[~2014-04-28 12:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 5:35 [PATCH v2 0/2] mmc: rtsx: add new cmd type handle and modify error handle micky_ching
2014-03-27 5:35 ` micky_ching
2014-03-27 5:35 ` [PATCH v2 1/2] mmc: rtsx: add R1-no-CRC mmc command type handle micky_ching
2014-03-27 5:35 ` micky_ching
2014-04-28 11:30 ` micky
2014-04-28 11:30 ` micky
2014-04-28 12:16 ` Dan Carpenter
2014-04-28 12:16 ` Dan Carpenter
2014-03-27 5:35 ` [PATCH v2 2/2] mmc: rtsx: modify error handle and remove smatch warnings micky_ching
2014-03-27 5:35 ` micky_ching
2014-04-28 11:37 ` [PATCH v2 2/2] mmc: rtsx: modify error handle and remove smatchwarnings micky
2014-04-28 11:37 ` micky
2014-04-28 12:40 ` Dan Carpenter [this message]
2014-04-28 12:40 ` Dan Carpenter
2014-03-27 8:11 ` [PATCH v2 0/2] mmc: rtsx: add new cmd type handle and modify error handle Ulf Hansson
2014-03-27 8:11 ` Ulf Hansson
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=20140428124001.GV26890@mwanda \
--to=dan.carpenter@oracle.com \
--cc=chris@printf.net \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=micky_ching@realsil.com.cn \
--cc=rogerable@realtek.com \
--cc=sameo@linux.intel.com \
--cc=ulf.hansson@linaro.org \
--cc=wei_wang@realsil.com.cn \
/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.