From: Greg KH <gregkh@linuxfoundation.org>
To: nayeem <itachi.opsrc@gmail.com>
Cc: German.Rivera@freescale.com, stuart.yoder@freescale.com,
agraf@suse.de, hgujulan@visteon.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: fsl-mc/bus: mc-bus.c: Fixed coding style issues
Date: Thu, 3 Sep 2015 09:48:34 -0700 [thread overview]
Message-ID: <20150903164834.GD31709@kroah.com> (raw)
In-Reply-To: <1440177897-3640-1-git-send-email-itachi.opsrc@gmail.com>
On Fri, Aug 21, 2015 at 10:54:57PM +0530, nayeem wrote:
> Fixed coding style issues where kernel types u16,u64,u32 should
> be preferred over uint16_t,uint64_t,uint32_t
>
> Signed-off-by: Nayeemahmed Badebade <itachi.opsrc@gmail.com>
This name needs to match your name in the "From:" line of your email.
Please fix up and resend.
thanks,
greg k-h
next prev parent reply other threads:[~2015-09-03 16:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-21 17:24 [PATCH] Staging: fsl-mc/bus: mc-bus.c: Fixed coding style issues nayeem
2015-09-03 16:48 ` Greg KH [this message]
2015-09-04 17:00 ` Nayeemahmed Badebade
2015-09-04 17:48 ` Jose Rivera
2015-09-04 18:00 ` gregkh
2015-09-04 18:33 ` Joe Perches
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=20150903164834.GD31709@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=German.Rivera@freescale.com \
--cc=agraf@suse.de \
--cc=hgujulan@visteon.com \
--cc=itachi.opsrc@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stuart.yoder@freescale.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.