[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20150506064242.GQ16501@mwanda>
Date: Wed, 6 May 2015 09:42:43 +0300
From: Dan Carpenter <dan.carpenter@...cle.com>
To: Scott Wood <scottwood@...escale.com>
Cc: Jose Rivera <German.Rivera@...escale.com>,
"devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>,
Stuart Yoder <stuart.yoder@...escale.com>,
"bhamciu1@...escale.com" <bhamciu1@...escale.com>,
"arnd@...db.de" <arnd@...db.de>,
"bhupesh.sharma@...escale.com" <bhupesh.sharma@...escale.com>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"agraf@...e.de" <agraf@...e.de>,
"nir.erez@...escale.com" <nir.erez@...escale.com>,
"itai.katz@...escale.com" <itai.katz@...escale.com>,
"R89243@...escale.com" <R89243@...escale.com>,
Richard Schmitt <richard.schmitt@...escale.com>
Subject: Re: [PATCH 1/7] staging: fsl-mc: MC bus IRQ support
On Tue, May 05, 2015 at 02:56:41PM -0500, Scott Wood wrote:
> > Don't insist that you must be special and different from everyone else.
>
> There are some users of U16_MAX, U32_MAX, and U64_MAX. Why use a limit
> for a different type than is being used? Why have s16/s32 at all if
> you're going to conflate it with short/int elsewhere?
I'm don't care about SHRT_MAX vs S16_MAX, I'm just saying generally,
people should fight every instinct they have to be unique in the kernel.
regards,
dan carpenter
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists