From: Artem Bityutskiy <dedekind1@gmail.com>
To: Amul Kumar Saha <amul.saha@samsung.com>
Cc: Kyungmin Park <kmpark@infradead.org>,
David Woodhouse <dwmw2@infradead.org>,
linux-mtd@lists.infradead.org, adrian.hunter@nokia.com
Subject: Re: [PATCH] [OneNAND] Standardising prints in onenand_base.c
Date: Thu, 01 Oct 2009 10:22:02 +0300 [thread overview]
Message-ID: <1254381722.32310.12.camel@localhost> (raw)
In-Reply-To: <6F989B9D46154BEAAC2255BA790F089B@sisodomain.com>
On Thu, 2009-10-01 at 12:18 +0530, Amul Kumar Saha wrote:
> This patch resolves all the prints present in onenand_base.c
> Primarily, it replaces the hard-coded function names in the prints,
> and makes use of __func__.
>
> Signed-off-by: Amul Kumar Saha <amul.saha at samsung.com>
Your patch is line-wrapped and not applicable:
[dedekind@eru l2-mtd-2.6.git]$ git am amul
Applying: Standardising prints in onenand_base.c
fatal: corrupt patch at line 69
Patch failed at 0001 Standardising prints in onenand_base.c
When you have resolved this problem run "git am --resolved".
If you would prefer to skip this patch, instead run "git am --skip".
To restore the original branch and stop patching run "git am --abort".
[dedekind@eru l2-mtd-2.6.git]$ patch -p1 < .git/rebase-apply/patch
patching file drivers/mtd/onenand/onenand_base.c
patch: **** malformed patch at line 69: (int) len);
Please, refer:
Documentation/SubmittingPatches
Documentation/email-clients.txt
An tiny nit-pick below:
> ---
> onenand_base.c | 172 +++++++++++++++++++++++++++++++++++----------------------
> 1 file changed, 106 insertions(+), 66 deletions(-)
>
> diff --git a/drivers/mtd/onenand/onenand_base.c b/drivers/mtd/onenand/onenand_base.c
> index ff66e43..ba760a2 100644
> --- a/drivers/mtd/onenand/onenand_base.c
> +++ b/drivers/mtd/onenand/onenand_base.c
... snip ...
> } else if (state == FL_READING) {
> - printk(KERN_ERR "onenand_wait: read timeout! ctrl=0x%04x intr=0x%04x\n", ctrl, interrupt);
> + printk(KERN_ERR "%s: read timeout! ctrl=0x%04x intr=0x%04x\n",
> + __func__, ctrl, interrupt);
You use one tab here, ok.
> @@ -1015,7 +1018,8 @@ static int onenand_recover_lsb(struct mtd_info *mtd, loff_t addr, int status)
> /* We are attempting to reread, so decrement stats.failed
> * which was incremented by onenand_wait due to read failure
> */
> - printk(KERN_INFO "onenand_recover_lsb: Attempting to recover from uncorrectable read\n");
> + printk(KERN_INFO "%s: Attempting to recover from uncorrectable read\n",
> + __func__);
But you use 2 tabs here, which is inconsistent.
Also, you missed one place:
DEBUG(MTD_DEBUG_LEVEL3, "onenand_mlc_read_ops_nolock: from = 0x%08x, len
= %i\n", (unsigned int) from, (int) len)
... snip ...
> @@ -3214,7 +3249,8 @@ int flexonenand_set_boundary(struct mtd_info *mtd, int die,
> new = boundary + (die * this->density_mask);
> ret = flexonenand_check_blocks_erased(mtd, min(old, new) + 1, max(old, new));
> if (ret) {
> - printk(KERN_ERR "flexonenand_set_boundary: Please erase blocks before boundary change\n");
> + printk(KERN_ERR "%s: Please erase blocks"
> + "before boundary change\n", __func__);
This will be printed as "Please erase blocksbefore boundary change",
i.e., not space.
... snip ...
> @@ -3408,8 +3446,8 @@ static void onenand_resume(struct mtd_info *mtd)
> if (this->state == FL_PM_SUSPENDED)
> onenand_release_device(mtd);
> else
> - printk(KERN_ERR "resume() called for the chip which is not"
> - "in suspended state\n");
> + printk(KERN_ERR "%s: resume() called for the chip which is not"
> + "in suspended state\n", __func__);
Ditto.
... snip ...
Otherwise looks ok.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2009-10-01 7:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-01 6:48 [PATCH] [OneNAND] Standardising prints in onenand_base.c Amul Kumar Saha
2009-10-01 7:22 ` Artem Bityutskiy [this message]
[not found] <C45F9E809A3C4FB0A470336A43DCCB74@sisodomain.com>
2009-10-01 8:00 ` Artem Bityutskiy
2009-10-01 11:08 ` Amul Kumar Saha
2009-10-01 12:32 ` Artem Bityutskiy
2009-10-02 11:29 ` Amul Kumar Saha
2009-10-01 8:01 ` Artem Bityutskiy
2009-10-05 7:04 ` Artem Bityutskiy
2009-10-05 7:11 ` David Woodhouse
2009-10-05 7:13 ` Artem Bityutskiy
2009-10-05 7:22 ` David Woodhouse
2009-10-05 7:30 ` Artem Bityutskiy
2009-10-05 7:11 ` 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=1254381722.32310.12.camel@localhost \
--to=dedekind1@gmail.com \
--cc=adrian.hunter@nokia.com \
--cc=amul.saha@samsung.com \
--cc=dwmw2@infradead.org \
--cc=kmpark@infradead.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 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.