From: merez@codeaurora.org
To: Seungwon Jeon <tgih.jun@samsung.com>
Cc: "S, Venkatraman" <svenkatr@ti.com>,
merez@codeaurora.org, linux-mmc@vger.kernel.org,
Chris Ball <cjb@laptop.org>,
linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
kgene.kim@samsung.com, dh.han@samsung.com
Subject: Re: [PATCH 2/2] mmc: core: Support packed command for eMMC4.5 device
Date: Sun, 13 Nov 2011 05:04:26 -0800 (PST) [thread overview]
Message-ID: <29dbe1d4d0e92bc4b4acf1ac2909f2df.squirrel@www.codeaurora.org> (raw)
In-Reply-To: <ea21d88d904af165cb911354e3f51ea6.squirrel@www.codeaurora.org>
>> On Fri, Nov 11, 2011 at 12:56 PM, Seungwon Jeon <tgih.jun@samsung.com>
>> wrote:
>>> Maya Erez wrote:
>>>> On Thu, Nov 10, 2011 Maya Erez wrote:
>>>> > S, Venkatraman <svenkatr@ti.com> wrote:
>>>> >> On Thu, Nov 3, 2011 at 7:23 AM, Seungwon Jeon
>>>> <tgih.jun@samsung.com>
>>>> wrote:
>>>> >> >> > +static u8 mmc_blk_chk_packable(struct mmc_queue *mq, struct
>>>> >> request *req)
>>>>
>>>> The function prepares the checkable list and not only checks if
>>>> packing
>>>> is
>>>> possible, therefore I think its name should change to reflect its real
>>>> action
>>> I labored at naming. Isn't it proper? :)
>>> Do you have any recommendation?
>>> group_pack_req?
>>>
How about mmc_blk_prep_packed_list?
Thanks,
Maya Erez
Consultant for Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
next prev parent reply other threads:[~2011-11-13 13:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-10 13:41 [PATCH 2/2] mmc: core: Support packed command for eMMC4.5 device merez
2011-11-11 7:26 ` Seungwon Jeon
2011-11-11 9:38 ` S, Venkatraman
2011-11-11 19:01 ` merez
2011-11-13 13:04 ` merez [this message]
2011-11-14 9:46 ` Seungwon Jeon
2011-11-15 12:48 ` merez
2011-11-17 2:02 ` Seungwon Jeon
2011-11-17 9:16 ` mmc: sdio: runtime PM and 8686 problems Joe Woodward
2011-11-14 9:44 ` [PATCH 2/2] mmc: core: Support packed command for eMMC4.5 device Seungwon Jeon
2011-11-15 13:27 ` merez
2011-11-17 2:21 ` Seungwon Jeon
2011-11-17 13:45 ` merez
-- strict thread matches above, loose matches on Subject: below --
2011-11-27 19:41 merez
2011-11-28 8:52 ` Seungwon Jeon
2011-12-01 13:51 ` merez
2011-12-02 9:06 ` Seungwon Jeon
2011-11-02 8:03 Seungwon Jeon
2011-11-02 10:59 ` Girish K S
2011-11-02 11:35 ` S, Venkatraman
2011-11-03 1:53 ` Seungwon Jeon
2011-11-04 14:46 ` S, Venkatraman
2011-11-07 3:45 ` Seungwon Jeon
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=29dbe1d4d0e92bc4b4acf1ac2909f2df.squirrel@www.codeaurora.org \
--to=merez@codeaurora.org \
--cc=cjb@laptop.org \
--cc=dh.han@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=svenkatr@ti.com \
--cc=tgih.jun@samsung.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