From: Dan Carpenter <dan.carpenter@oracle.com>
To: Glen Lee <glen.lee@atmel.com>
Cc: gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
austin.shin@atmel.com, linux-wireless@vger.kernel.org,
Nicolas.FERRE@atmel.com, adel.noureldin@atmel.com,
tony.cho@atmel.com, leo.kim@atmel.com, adham.abozaeid@atmel.com
Subject: Re: [PATCH 1/4] staging: wilc1000: remove define COMPLEMENT_BOOT
Date: Thu, 19 Nov 2015 09:19:07 +0300 [thread overview]
Message-ID: <20151119061907.GQ18797@mwanda> (raw)
In-Reply-To: <1447898761-6938-1-git-send-email-glen.lee@atmel.com>
On Thu, Nov 19, 2015 at 11:05:58AM +0900, Glen Lee wrote:
> This patch removes define COMPLEMENT_BOOT in Makefile. The feature was removed
> by the following commit but the define was not removed. So remove completely.
>
> b46d68825c2d3af70ad18b53dfed6516e393b7fa
Put some human readable text next to the hash. The standard thing is to
include only the first 12 characters of the hash. If there are fewer
than 12 characters then we could get collisions but including the whole
hash is excessive.
This patch removes define COMPLEMENT_BOOT in Makefile. The feature was
removed by commit b46d68825c2d ('staging: wilc1000: remove
COMPLEMENT_BOOT') but the define was not removed. So remove completely.
regards,
dan carpenter
next prev parent reply other threads:[~2015-11-19 6:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 2:05 [PATCH 1/4] staging: wilc1000: remove define COMPLEMENT_BOOT Glen Lee
2015-11-19 2:05 ` [PATCH 2/4] staging: wilc1000: remove wilc memory allocation config Glen Lee
2015-11-19 2:06 ` [PATCH 3/4] staging: wilc1000: rename index to tcp_pending_ack_idx Glen Lee
2015-11-19 6:23 ` Dan Carpenter
2015-11-19 6:53 ` glen lee
2015-11-19 15:45 ` Greg KH
2015-11-20 1:30 ` glen lee
2015-11-19 2:06 ` [PATCH 4/4] staging: wilc1000: use kernel define byte order macros Glen Lee
2015-11-19 6:19 ` Dan Carpenter [this message]
2015-11-19 6:33 ` [PATCH 1/4] staging: wilc1000: remove define COMPLEMENT_BOOT glen lee
2015-12-18 22:32 ` Greg KH
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=20151119061907.GQ18797@mwanda \
--to=dan.carpenter@oracle.com \
--cc=Nicolas.FERRE@atmel.com \
--cc=adel.noureldin@atmel.com \
--cc=adham.abozaeid@atmel.com \
--cc=austin.shin@atmel.com \
--cc=devel@driverdev.osuosl.org \
--cc=glen.lee@atmel.com \
--cc=gregkh@linuxfoundation.org \
--cc=leo.kim@atmel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=tony.cho@atmel.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).