From: David Cohen <david.a.cohen@linux.intel.com>
To: "Westerberg, Mika" <mika.westerberg@intel.com>
Cc: "Zha, Qipeng" <qipeng.zha@intel.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
'Linus Walleij' <linus.walleij@linaro.org>
Subject: Re: [PATCH] Fix one issue in pinctrl-cherryview.c
Date: Fri, 27 Feb 2015 09:47:17 -0800 [thread overview]
Message-ID: <20150227174717.GA19392@psi-dev26.jf.intel.com> (raw)
In-Reply-To: <20150226071109.GY1758@lahna.fi.intel.com>
Hi Mika,
On Thu, Feb 26, 2015 at 09:11:09AM +0200, Westerberg, Mika wrote:
> On Thu, Feb 26, 2015 at 05:10:13AM +0200, Zha, Qipeng wrote:
> > Hi
> >
> > Please check below patch(or attached), thanks.
> >
> > this is verified on Intel cherrytrail platform on linux 3.19-rc6.
>
> In general you should send your patches inline and plain text to the
> interested parties. Please take some time reading Documentation/SubmittingPatches.
>
> Then do this:
>
> 1) git format-patch -1
>
> This results 0001-pinctrl-update-direction_output-function-of-cherryvi.patch
>
> 2) git send-email --dry-run --to self 0001-pinctrl-update-direction_output-function-of-cherryvi.patch
>
> Verify that it sends the patch only to you
>
> 3) git send-email --to self 0001-pinctrl-update-direction_output-function-of-cherryvi.patch
>
> Verify that the patch formatting and content is ok. If not, apply fixes
> and start from 1).
>
> Once you are happy with the result you can then send the patch like:
>
> 4) git send-email --to ... --cc ...
>
> and everyone is happy :)
>
> The patch itself looks good to me.
Not sure if I missed something, but where's the patch? :)
Br, David
next prev parent reply other threads:[~2015-02-27 17:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <C6287702A945AC47BE5DB5DFD4B5C6DD01841877@SHSMSX104.ccr.corp.intel.com>
2015-02-26 7:11 ` [PATCH] Fix one issue in pinctrl-cherryview.c Westerberg, Mika
2015-02-27 17:47 ` David Cohen [this message]
2015-03-09 9:17 ` Westerberg, Mika
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=20150227174717.GA19392@psi-dev26.jf.intel.com \
--to=david.a.cohen@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=mika.westerberg@intel.com \
--cc=qipeng.zha@intel.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;
as well as URLs for NNTP newsgroup(s).