From: Artem Bityutskiy <dedekind1@gmail.com>
To: Kevin Cernekee <cernekee@gmail.com>
Cc: linux-mtd@lists.infradead.org, dwmw2@infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mtd: cfi_cmdset_0002: Fix trivial merge conflict
Date: Thu, 29 Apr 2010 08:34:22 +0300 [thread overview]
Message-ID: <1272519262.7750.66.camel@localhost> (raw)
In-Reply-To: <02d08adf6882611e6c0121481e70a61d20a10acf@localhost.localdomain>
On Wed, 2010-04-28 at 17:26 -0700, Kevin Cernekee wrote:
> Stefani Seibold's patch changed chip->mutex, once a spinlock, into a
> mutex. This patch applies the same change to cfi_amdstd_reset(), part
> of the new reboot notifier code.
>
> Signed-off-by: Kevin Cernekee <cernekee@gmail.com>
> ---
> drivers/mtd/chips/cfi_cmdset_0002.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/mtd/chips/cfi_cmdset_0002.c b/drivers/mtd/chips/cfi_cmdset_0002.c
> index d356827..c16b8ce 100644
> --- a/drivers/mtd/chips/cfi_cmdset_0002.c
> +++ b/drivers/mtd/chips/cfi_cmdset_0002.c
> @@ -1945,7 +1945,7 @@ static int cfi_amdstd_reset(struct mtd_info *mtd)
>
> chip = &cfi->chips[i];
>
> - spin_lock(chip->mutex);
> + mutex_lock(&chip->mutex);
>
> ret = get_chip(map, chip, chip->start, FL_SHUTDOWN);
> if (!ret) {
> @@ -1954,7 +1954,7 @@ static int cfi_amdstd_reset(struct mtd_info *mtd)
> put_chip(map, chip, chip->start);
> }
>
> - spin_unlock(chip->mutex);
> + mutex_unlock(&chip->mutex);
> }
>
> return 0;
Could you instead resend one patch which is a merge of this one and the
old one, please?
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2010-04-29 5:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-29 0:26 [PATCH] mtd: cfi_cmdset_0002: Fix trivial merge conflict Kevin Cernekee
2010-04-29 5:34 ` Artem Bityutskiy [this message]
2010-04-29 17:26 ` [PATCHv3] mtd: cfi_cmdset_0002: Add reboot notifier for AMD flashes Kevin Cernekee
2010-05-05 5:40 ` Artem Bityutskiy
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=1272519262.7750.66.camel@localhost \
--to=dedekind1@gmail.com \
--cc=cernekee@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).