From: Artem Bityutskiy <dedekind1@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: linux-mtd@lists.infradead.org,
David Woodhouse <dwmw2@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] jffs2: logging message neatening
Date: Wed, 29 Feb 2012 14:12:53 +0200 [thread overview]
Message-ID: <1330517573.3545.110.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1330517290.3545.107.camel@sauron.fi.intel.com>
[-- Attachment #1: Type: text/plain, Size: 274 bytes --]
On Wed, 2012-02-29 at 14:08 +0200, Artem Bityutskiy wrote:
> Also, there are several checkpatch.pl complaints, please, take a look:
Ok, I copy-pasted them, but actually took a look now and the
checkpatch.pl ones are non-issues.
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-02-29 12:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-15 23:56 [PATCH 0/4] jffs2: logging message neatening Joe Perches
2012-02-15 23:56 ` [PATCH 1/4] jffs2: Convert most D1/D2 macros to jffs2_dbg Joe Perches
2012-03-05 16:30 ` Artem Bityutskiy
2012-03-05 16:56 ` Joe Perches
2012-03-09 11:53 ` Artem Bityutskiy
2012-03-09 18:49 ` Joe Perches
2012-03-12 13:12 ` Artem Bityutskiy
2012-03-12 15:33 ` Joe Perches
2012-03-12 16:35 ` Artem Bityutskiy
2012-03-12 17:11 ` Joe Perches
2012-03-13 12:39 ` Artem Bityutskiy
2012-03-13 16:34 ` Joe Perches
2012-03-14 10:54 ` Artem Bityutskiy
2012-03-09 21:59 ` [PATCH l2-mtd] jffs2: Fix build when CONFIG_JFFS2_FS_DEBUG > 0 Joe Perches
2012-03-12 13:50 ` Artem Bityutskiy
2012-02-15 23:56 ` [PATCH 2/4] jffs2: Convert printks to pr_<level> Joe Perches
2012-02-15 23:56 ` [PATCH 3/4] jffs2: Use pr_fmt and remove jffs: from formats Joe Perches
2012-02-15 23:56 ` [PATCH 4/4] jffs2: Standardize JFFS_<LEVEL> uses Joe Perches
2012-02-29 12:08 ` [PATCH 0/4] jffs2: logging message neatening Artem Bityutskiy
2012-02-29 12:12 ` Artem Bityutskiy [this message]
2012-02-29 19:02 ` Joe Perches
2012-03-01 7:36 ` 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=1330517573.3545.110.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=joe@perches.com \
--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