From: Dan Carpenter <dan.carpenter@oracle.com>
To: Christophe Jaillet <christophe.jaillet@wanadoo.fr>
Cc: linus.walleij@linaro.org, gnurou@gmail.com,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 2/2] gpio: x-gene: Remove a useless memset
Date: Fri, 1 May 2015 17:19:22 +0300 [thread overview]
Message-ID: <20150501141922.GE14154@mwanda> (raw)
In-Reply-To: <1430483346-10583-1-git-send-email-christophe.jaillet@wanadoo.fr>
The "[PATCH 2/2]" bit is a mistake. It's not part of a patchset. It's
just that you have sent two patches today. The first patch wasn't even
named [1/2]...
Unless, it is part of a patchset?? If so where is the first patch?
regards,
dan carpenter
next prev parent reply other threads:[~2015-05-01 14:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-01 12:29 [PATCH 2/2] gpio: x-gene: Remove a useless memset Christophe Jaillet
2015-05-01 14:19 ` Dan Carpenter [this message]
2015-05-01 14:54 ` Marion & Christophe JAILLET
2015-05-01 15:44 ` Dan Carpenter
2015-05-12 7:43 ` Linus Walleij
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=20150501141922.GE14154@mwanda \
--to=dan.carpenter@oracle.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=gnurou@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).