public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Chuanxiao Dong <chuanxiao.dong@intel.com>
Cc: linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
	cjb@laptop.org, akpm@linux-foundation.org, arjan@linux.intel.com,
	alan@linux.intel.com, kmpark@infradead.org
Subject: Re: [PATCH v2 1/4]enable background operations for supported eMMC card
Date: Mon, 6 Dec 2010 13:28:49 +0100	[thread overview]
Message-ID: <201012061328.49738.arnd@arndb.de> (raw)
In-Reply-To: <20101203121338.GB18655@intel.com>

On Friday 03 December 2010, Chuanxiao Dong wrote:
> From 984adc755cf2f7966a89e510a50f085e314fe347 Mon Sep 17 00:00:00 2001
> From: Chuanxiao Dong <chuanxiao.dong@intel.com>
> Date: Mon, 22 Nov 2010 16:31:12 +0800
> Subject: [PATCH 1/4] mmc: Enabled background operations feature if eMMC card supports

These headers don't belong into a submission. If you use git-send-email,
they get cut off automatically, otherwise just remove them as you paste
the patch into your mail client.

> Background operations is a new feature defined in eMMC4.41 standard.
> Since this feature is opertional for eMMC card, so driver only enable

s/opertional/optional/

> @@ -54,6 +54,8 @@ struct mmc_ext_csd {
>  	unsigned int		sec_trim_mult;	/* Secure trim multiplier  */
>  	unsigned int		sec_erase_mult;	/* Secure erase multiplier */
>  	unsigned int		trim_timeout;		/* In milliseconds */
> +	unsigned int		bkops:1; /* background support bit */
> +	unsigned int		bkops_en:1; /* background enable bit */
>  };

Bit fields are not encouraged for kernel internal data structures,
just use "bool" variables here.

	Arnd

  parent reply	other threads:[~2010-12-06 12:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-03 12:13 [PATCH v2 1/4]enable background operations for supported eMMC card Chuanxiao Dong
2010-12-06  1:12 ` Kyungmin Park
2010-12-06  2:28   ` Dong, Chuanxiao
2010-12-06 12:28 ` Arnd Bergmann [this message]
2010-12-06 12:34   ` Dong, Chuanxiao
2010-12-06 13:44     ` Wolfram Sang
2011-05-02 19:53 ` Per Forlin
2011-05-05  7:50   ` Per Forlin

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=201012061328.49738.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=akpm@linux-foundation.org \
    --cc=alan@linux.intel.com \
    --cc=arjan@linux.intel.com \
    --cc=chuanxiao.dong@intel.com \
    --cc=cjb@laptop.org \
    --cc=kmpark@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox