All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaehoon Chung <jh80.chung@samsung.com>
To: J Freyensee <james_p_freyensee@linux.intel.com>
Cc: Jaehoon Chung <jh80.chung@samsung.com>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
	Chris Ball <cjb@laptop.org>,
	Kyungmin Park <kyungmin.park@samsung.com>,
	Chuanxiao Dong <chuanxiao.dong@intel.com>,
	Hanumath Prasad <hanumath.prasad@stericsson.com>
Subject: Re: [RFC PATCH] mmc: support background operation
Date: Thu, 18 Aug 2011 11:11:55 +0900	[thread overview]
Message-ID: <4E4C74EB.8050702@samsung.com> (raw)
In-Reply-To: <4E4BE8C6.5040106@linux.intel.com>

Hi Jay..

I didn't know the tool 'sparse'. i will check the tool for your advice.
Thank you a lot for your help.. :)

> Unfortunately, I am still a little new to this area of the Linux kernel
> so I don't quite have the background to give an intelligent answer
> w/respect to eMMC 4.41 and BKOPS.  I just have 3 device driver accepts
> in the TTY space, so my contributions to patches are mainly basic code
> functionality and Linux kernel/device-driver gotchas.
> 
> Do you know the tool 'sparse'?  It's a good thing to try once, before
> submitting upstream, if you haven't done it.
> 
>>
>> Regards,
>> Jaehoon Chung
>>
>>
>>
> 
> 


  reply	other threads:[~2011-08-18  2:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-12 11:14 [RFC PATCH] mmc: support background operation Jaehoon Chung
2011-08-16 16:35 ` J Freyensee
2011-08-16 16:43   ` Chris Ball
2011-08-17  4:03   ` Jaehoon Chung
2011-08-17 16:13     ` J Freyensee
2011-08-18  2:11       ` Jaehoon Chung [this message]
2011-08-18  3:16         ` J Freyensee
2011-08-17  8:02 ` Seungwon Jeon
2011-08-17  8:13   ` Jaehoon Chung
2011-08-17  8:30     ` Jaehoon Chung

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=4E4C74EB.8050702@samsung.com \
    --to=jh80.chung@samsung.com \
    --cc=chuanxiao.dong@intel.com \
    --cc=cjb@laptop.org \
    --cc=hanumath.prasad@stericsson.com \
    --cc=james_p_freyensee@linux.intel.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-mmc@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 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.