All of lore.kernel.org
 help / color / mirror / Atom feed
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: Mon, 05 Oct 2009 10:11:50 +0300	[thread overview]
Message-ID: <1254726710.3359.6.camel@localhost> (raw)
In-Reply-To: <1254726268.3359.3.camel@localhost>

On Mon, 2009-10-05 at 10:04 +0300, Artem Bityutskiy wrote:
> On Thu, 2009-10-01 at 13:08 +0530, Amul Kumar Saha wrote:
> > Note: Reposting with corrected Signed-Off
> > 
> > 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@samsung.com>
> > ---
> >  onenand_base.c |  172 +++++++++++++++++++++++++++++++++++----------------------
> >  1 file changed, 106 insertions(+), 66 deletions(-)
> 
> David decided to ignore the discussion and pushed your first patch
> instead of this one already.

Oh, David actually took the right patch, sorry. You decided to re-send
the old patch and did not address the nitpicks I pointed, e.g., there is
still:

DEBUG(MTD_DEBUG_LEVEL3, "onenand_erase: start = 0x%012llx, len = %llu
\n", (unsigned long long) instr->addr, (unsigned long long) instr->len);

Well, not big deal, but would be nice to have a follow up patch.

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)

  parent reply	other threads:[~2009-10-05  7:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <C45F9E809A3C4FB0A470336A43DCCB74@sisodomain.com>
2009-10-01  8:00 ` [PATCH] [OneNAND] Standardising prints in onenand_base.c 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 [this message]
2009-10-01  6:48 Amul Kumar Saha
2009-10-01  7:22 ` 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=1254726710.3359.6.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.