From: Toshiaki Yamane <yamanetoshi@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
Martyn Welch <martyn.welch@ge.com>,
Manohar Vanga <manohar.vanga@gmail.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/5] staging/vme: fix checkpatch warning
Date: Tue, 21 Aug 2012 20:11:20 +0900 [thread overview]
Message-ID: <CAOTypNQUFTVGc64BtB2VGAZ+JD4oVTXtmgdKVdzKF_7Kouttnw@mail.gmail.com> (raw)
In-Reply-To: <CAOTypNS40FOJ=D=sRigQaYJumXpCfH9Lu1c2B3jXy6epQuumVA@mail.gmail.com>
On Fri, Aug 17, 2012 at 11:30 PM, Toshiaki Yamane <yamanetoshi@gmail.com> wrote:
> On Fri, Aug 17, 2012 at 10:19 PM, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
>> On Fri, Aug 17, 2012 at 05:27:53PM +0900, Toshiaki Yamane wrote:
>>> On Fri, Aug 17, 2012 at 4:46 PM, Dan Carpenter <dan.carpenter@oracle.com> wrote:
>>> > You've got the same subject repeated 5 times.
>>> >
>>> > It would be better to merge all the vme_user.c printk fixes into
>>> > one patch.
>>> > [patch 1/3] Staging: vme: Fix a white space issue
>>> > [patch 2/3] Staging: vme: Use pr_ printks in vme_user.c
>>> > [patch 3/3] Staging: vme: Use pr_ printks in vme_pio2_core.c
>>> >
>>> > It's not a huge deal, it just seems like there was some confusion on
>>> > how to break patches up.
>>>
>>>
>>> Thanks for your reply!
>>> I will try to fix it.
>>
>> Please do, I can't take it as-is.
>
> I will stop, if you say so.
Greg-san,
I have misunderstood your reply. I am sorry...
I will send a patch from now.
--
Regards,
.
.
...
Yamane Toshiaki
yamanetoshi@gmail.com
next prev parent reply other threads:[~2012-08-21 11:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-21 13:00 [PATCH] staging/vme: fix checkpatch warnings Toshiaki Yamane
2012-07-23 0:53 ` Toshiaki Yamane
2012-08-17 5:04 ` [PATCH 1/5] staging/vme: fix checkpatch error Toshiaki Yamane
2012-08-17 5:05 ` [PATCH 2/5] staging/vme: fix checkpatch warning Toshiaki Yamane
2012-08-17 7:46 ` Dan Carpenter
2012-08-17 8:27 ` Toshiaki Yamane
2012-08-17 13:19 ` Greg Kroah-Hartman
2012-08-17 14:30 ` Toshiaki Yamane
2012-08-21 11:11 ` Toshiaki Yamane [this message]
2012-08-21 11:12 ` [PATCH 1/3] Staging: vme: Fix a white space issue Toshiaki Yamane
2012-08-21 11:12 ` [PATCH 2/3] staging/vme: Use pr_ printks in vme_user.c Toshiaki Yamane
2012-09-04 20:20 ` Greg Kroah-Hartman
2012-09-11 7:16 ` [PATCH 1/2] " Toshiaki Yamane
2012-09-11 7:17 ` [PATCH 2/2] staging/vme: Use dev_ " Toshiaki Yamane
2012-09-11 19:08 ` Greg Kroah-Hartman
2012-09-11 19:08 ` [PATCH 1/2] staging/vme: Use pr_ " Greg Kroah-Hartman
2012-09-12 7:36 ` Toshiaki Yamane
2012-09-12 14:04 ` Greg Kroah-Hartman
2012-08-21 11:13 ` [PATCH 3/3] staging/vme: Use pr_ printks in vme_pio2_core.c Toshiaki Yamane
2012-08-17 5:05 ` [PATCH 3/5] staging/vme: fix checkpatch warning Toshiaki Yamane
2012-08-17 5:05 ` [PATCH 4/5] " Toshiaki Yamane
2012-08-17 5:06 ` [PATCH 5/5] " Toshiaki Yamane
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=CAOTypNQUFTVGc64BtB2VGAZ+JD4oVTXtmgdKVdzKF_7Kouttnw@mail.gmail.com \
--to=yamanetoshi@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manohar.vanga@gmail.com \
--cc=martyn.welch@ge.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;
as well as URLs for NNTP newsgroup(s).