From: Mike Frysinger <vapier.adi@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: cliffcai.sh@gmail.com, linux-mmc@vger.kernel.org,
linux-kernel@vger.kernel.org, cliff.cai@analog.com,
Bryan Wu <cooloney@kernel.org>
Subject: Re: [PATCH v4][mmc/host]:Blackfin SD Host Controller Driver
Date: Wed, 25 Nov 2009 17:25:20 -0500 [thread overview]
Message-ID: <8bd0f97a0911251425q178993fete79b675e2730bdec@mail.gmail.com> (raw)
In-Reply-To: <20091125140422.cdee4a0d.akpm@linux-foundation.org>
On Wed, Nov 25, 2009 at 17:04, Andrew Morton wrote:
> On Wed, 25 Nov 2009 23:19:50 +0800 cliffcai.sh wrote:
>> +struct dma_desc_array {
>> + unsigned long start_addr;
>> + unsigned short cfg;
>> + unsigned short x_count;
>> + short x_modify;
>> +} __attribute__((packed));
>
> __packed is preferred.
we should move this into the Blackfin dma.h at any rate
>> +static void sdh_start_cmd(struct sdh_host *host, struct mmc_command *cmd)
>> +{
>> + unsigned int sdh_cmd;
>> + unsigned int stat_mask;
>> +
>> + dev_dbg(mmc_dev(host->mmc), "%s enter cmd: 0x%p\n", __func__, cmd);
>> + WARN_ON(host->cmd != NULL);
>> + host->cmd = cmd;
>> +
>> + sdh_cmd = 0;
>> + stat_mask = 0;
>> +
>> + sdh_cmd |= cmd->opcode;
>> +
>> + if (cmd->flags & MMC_RSP_PRESENT) {
>> + sdh_cmd |= CMD_RSP;
>> + stat_mask |= CMD_RESP_END;
>> + } else
>> + stat_mask |= CMD_SENT;
>
> Arguably wrong from a coding-style POV and looks weird IMO. Adds a bit
> of risk that subsequent coders will think they're writing in python adn
> will add bugs.
i dont really get what you're referring to here. the code in question
looks ifne to me, and i dont see anything "python-esque" about it
> Fixes:
>
> - } else
> + } else }
guessing you actually meant '{' there
-mike
next prev parent reply other threads:[~2009-11-25 22:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 15:19 cliffcai.sh
2009-11-25 22:04 ` Andrew Morton
2009-11-25 22:25 ` Mike Frysinger [this message]
2009-11-25 22:43 ` Andrew Morton
2009-11-29 21:39 ` Mike Frysinger
2009-12-04 2:08 ` Mike Frysinger
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=8bd0f97a0911251425q178993fete79b675e2730bdec@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cliff.cai@analog.com \
--cc=cliffcai.sh@gmail.com \
--cc=cooloney@kernel.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
all inboxes | Powered by JetHome®