public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: YU Bo <tsu.yubo@gmail.com>
To: Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Kaur Chawla <amitoj1606@gmail.com>, Goyal <bhumirks@gmail.com>,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
	yuzibode@126.com
Subject: Re: [PATCH] Staging: wlan-ng: fix comments style
Date: Tue, 10 May 2016 21:05:15 -0400	[thread overview]
Message-ID: <20160511010514.GA3359@yubo-2> (raw)
In-Reply-To: <20160509122613.GA29165@kroah.com>

Hi Greg,
On Mon, May 09, 2016 at 02:26:13PM +0200, Kroah-Hartman wrote:
>On Sun, May 08, 2016 at 10:45:16AM -0400, YU Bo wrote:
>> The patch fixed warning reported by checkpatch.pl: Block comments use a
>> trailing */ on a separate line.
>>
>> Signed-off-by: YU Bo <tsu.yubo@gmail.com>
>> ---
>>  drivers/staging/wlan-ng/prism2mgmt.h |    4 ++--
>>  1 file changed, 2 insertions(+), 2 deletions(-)
>
>Patch doesn't apply to my tree, what branch did you make this against?
Thanks for your reply.
I made two branches on your tree:little,greg.
Each time i went into a branch and type:
git fetch origin && git rebase origin/staging-testing
then i repated on different branch.
Sure,i will reset my commit before these operations.
Due to network issue,i have to make patch on local kernel and `scp`
patch to my VPS then send you via mutt.It's ok for me to git am xx_xx.patch
but fail to apply git am xx_xx.mbox which save from mutt sometime:(
I will try to send you a series of patch and test it ok.
Thanks again.
>
>thanks,
>
>greg k-h

  reply	other threads:[~2016-05-11  1:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-08 14:45 [PATCH] Staging: wlan-ng: fix comments style YU Bo
2016-05-09 12:26 ` Kroah-Hartman
2016-05-11  1:05   ` YU Bo [this message]
2016-05-11  4:16     ` Kroah-Hartman

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=20160511010514.GA3359@yubo-2 \
    --to=tsu.yubo@gmail.com \
    --cc=amitoj1606@gmail.com \
    --cc=bhumirks@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yuzibode@126.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