From: Greg KH <gregkh@linuxfoundation.org>
To: "Gustavo A. R. Silva" <silvagustavosilva@gmail.com>
Cc: jak@jak-linux.org,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Gustavo A. R. Silva" <garsilva@embeddedor.com>
Subject: Re: [PATCH 3/3] Staging: nvec: Fixed a typo
Date: Sun, 11 Jan 2015 13:37:37 -0800 [thread overview]
Message-ID: <20150111213737.GA20983@kroah.com> (raw)
In-Reply-To: <CANE5pd=DH=5U_O37Q0qBc+1hTrc8f=H0vhMuEBHCW5c0ek8+EA@mail.gmail.com>
On Sun, Jan 11, 2015 at 03:33:01PM -0600, Gustavo A. R. Silva wrote:
>
>
> 2015-01-11 15:27 GMT-06:00 Greg KH <gregkh@linuxfoundation.org>:
>
> On Sun, Jan 11, 2015 at 03:12:15PM -0600, Gustavo A. R. Silva wrote:
> > Fixed a typo in nvec.c file
> >
> > Signed-off-by: Gustavo A. R. Silva <garsilva@embeddedor.com>
> > ---
> > drivers/staging/nvec/nvec.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Where are patches 1/3 and 2/3?
>
>
> There are no such patches.
> I don't know why it is generating such label instead of just [PATCH].
How did you generate the patch?
> I updated my main Makefile and generated a local patch, could this be the
> reason?
I don't know.
> Should I modified that label to be just [PATCH]?
If you are sending 2 patches, they should be in order, with numbering.
greg k-h
prev parent reply other threads:[~2015-01-11 21:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-11 21:12 [PATCH 3/3] Staging: nvec: Fixed a typo Gustavo A. R. Silva
2015-01-11 21:27 ` Greg KH
[not found] ` <CANE5pd=DH=5U_O37Q0qBc+1hTrc8f=H0vhMuEBHCW5c0ek8+EA@mail.gmail.com>
2015-01-11 21:37 ` Greg KH [this message]
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=20150111213737.GA20983@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=garsilva@embeddedor.com \
--cc=jak@jak-linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=silvagustavosilva@gmail.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