From: Ajay Bhargav <ajay.bhargav@einfochips.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4 2/2] gpio: Add GPIO driver for Marvell SoC Armada100
Date: Wed, 10 Aug 2011 15:48:41 +0530 (IST) [thread overview]
Message-ID: <2103247581.73430.1312971521855.JavaMail.root@ahm.einfochips.com> (raw)
In-Reply-To: <1256544227.73428.1312971444460.JavaMail.root@ahm.einfochips.com>
----- "Prafulla Wadaskar" <prafulla@marvell.com> wrote:
> > -----Original Message-----
> > From: Ajay Bhargav [mailto:ajay.bhargav at einfochips.com]
> > Sent: Wednesday, August 10, 2011 2:47 PM
> > To: Prafulla Wadaskar
> > Cc: u-boot at lists.denx.de; Ajay Bhargav
> > Subject: [PATCH v4 2/2] gpio: Add GPIO driver for Marvell SoC
> Armada100
> >
> > This patch adds support for generic GPIO driver framework for
> Marvell
> > SoC Armada100.
> >
> > v4 - updated gpio.h file, removed modification in Armada100.h
>
> You are not following standard patch submission practice as indicated
> here
> http://www.denx.de/wiki/view/U-Boot/Patches#Sending_updated_patch_versions
>
> You need to document entire change history for each patch to be
> submitted below ---, this is important
>
Sorry for mistake..
Do i need to add history in each patch or first patch of a series patch?
I mean if I am submitting 2 patches in series I define history in patch 1/2.
Am I right?
Thanks & Regards,
Ajay Bhargav
next parent reply other threads:[~2011-08-10 10:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1256544227.73428.1312971444460.JavaMail.root@ahm.einfochips.com>
2011-08-10 10:18 ` Ajay Bhargav [this message]
2011-08-10 10:50 ` [U-Boot] [PATCH v4 2/2] gpio: Add GPIO driver for Marvell SoC Armada100 Prafulla Wadaskar
2011-08-10 9:17 Ajay Bhargav
2011-08-10 9:59 ` Prafulla Wadaskar
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=2103247581.73430.1312971521855.JavaMail.root@ahm.einfochips.com \
--to=ajay.bhargav@einfochips.com \
--cc=u-boot@lists.denx.de \
/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