From: Artem Bityutskiy <dedekind1@gmail.com>
To: Stefan Roese <stefan.roese@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH v2] mtd: cfi_cmdset_0002: Support Persistent Protection Bits (PPB) locking
Date: Thu, 17 Jan 2013 14:10:59 +0200 [thread overview]
Message-ID: <1358424659.2731.237.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <50F6B90F.8080905@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 452 bytes --]
On Wed, 2013-01-16 at 15:28 +0100, Stefan Roese wrote:
> >
> > Please, check allso the timeo warning.
>
> Hmmm. I didn't touch do_read_secsi_onechip() with this patch. And I'm
> not able to reproduce this warning. Are you sure this warning is
> introduced by this PPB locking patch?
Dunno, my tools sayse it is you. It may be mistaken. I compile with W=1,
this is why I see more warnings, I guess?
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-01-17 12:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-13 8:29 [PATCH v2] mtd: cfi_cmdset_0002: Support Persistent Protection Bits (PPB) locking Stefan Roese
2013-01-15 9:10 ` Artem Bityutskiy
2013-01-16 14:28 ` Stefan Roese
2013-01-17 12:10 ` Artem Bityutskiy [this message]
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=1358424659.2731.237.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=stefan.roese@gmail.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