From: Ronald Rojas <ronladred@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [PATCH v7] Staging: octeon: Fix blank lines warnings
Date: Wed, 21 Sep 2016 08:49:39 -0400 [thread overview]
Message-ID: <20160921124938.GB28807@fedora> (raw)
In-Reply-To: <20160920115119.GA14587@kroah.com>
On Tue, Sep 20, 2016 at 01:51:19PM +0200, Greg KH wrote:
> On Sun, Sep 18, 2016 at 07:04:19PM -0400, Ronald Rojas wrote:
> > Fixes several of the checkpatch.pl warnings to
> > not use multiple blank lines
> >
> > Signed-off-by: Ronald Rojas <ronladred@gmail.com>
> > ---
> > v7: changed to staging tree instead of torvalds tree
> > drivers/staging/octeon/ethernet.c | 2 --
> > 1 file changed, 2 deletions(-)
>
> What branch are you using? This still doesnt apply. Please use the
> staging-next or better yet, staging-testing.
I'd like to confirm that I'm doing this correctly so that the next patch
I send to you will be correct. This is what I have done:
I cloned your repository directly under gregkh/staging.git . I've checked
out staging-testing and created my own branch I called ronald-branch.
Then, when I had ronald-branch checked out, I ran "git merge staging-testing",
to make sure ronald-branch was up to date.
Then I make the appropriate changes and resubmit patch the patch?
>
> thanks,
>
> greg k-h
Thanks for the help,
Ronald Rojas
next prev parent reply other threads:[~2016-09-21 12:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-18 23:04 [PATCH v7] Staging: octeon: Fix blank lines warnings Ronald Rojas
2016-09-20 11:51 ` Greg KH
2016-09-21 12:49 ` Ronald Rojas [this message]
2016-09-21 14:00 ` Greg KH
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=20160921124938.GB28807@fedora \
--to=ronladred@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=outreachy-kernel@googlegroups.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 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.