From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 6/6] linux/kernel.h: sync min, max, min3, max3 macros with Linux
Date: Wed, 5 Nov 2014 07:02:23 +0100 [thread overview]
Message-ID: <201411050702.24075.marex@denx.de> (raw)
In-Reply-To: <20141105140608.CB29.AA925319@jp.panasonic.com>
On Wednesday, November 05, 2014 at 06:06:09 AM, Masahiro Yamada wrote:
> Hi Pavel,
>
> Thanks for your close checking.
>
>
> On Tue, 4 Nov 2014 20:50:13 +0100
>
> Pavel Machek <pavel@denx.de> wrote:
> > On Tue 2014-11-04 20:26:26, Masahiro Yamada wrote:
> > > U-Boot has never cared about the type when we get max/min of two
> > > values, but Linux Kernel does. This commit gets min, max, min3, max3
> > > macros synced with the kernel introduing type checks.
> >
> > "introducing"
>
> I will fix this.
Are you linting the patches with aspell or something ?
[...]
Best regards,
Marek Vasut
next prev parent reply other threads:[~2014-11-05 6:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 11:26 [U-Boot] [PATCH 0/6] Collect utility macros to include/linux/kernel.h synced with Linux Masahiro Yamada
2014-11-04 11:26 ` [U-Boot] [PATCH 1/6] replace DIV_ROUND with DIV_ROUND_CLOSEST Masahiro Yamada
2014-11-04 11:26 ` [U-Boot] [PATCH 2/6] include/common.h: remove DIV_ROUND definition Masahiro Yamada
2014-11-04 11:26 ` [U-Boot] [PATCH 3/6] include: move various macros to include/linux/kernel.h Masahiro Yamada
2014-11-04 11:26 ` [U-Boot] [PATCH 4/6] linux/kernel.h: import more macros Masahiro Yamada
2014-11-04 11:26 ` [U-Boot] [PATCH 5/6] linux/kernel.h: add typechecking to roundup macro Masahiro Yamada
2014-11-04 11:26 ` [U-Boot] [PATCH 6/6] linux/kernel.h: sync min, max, min3, max3 macros with Linux Masahiro Yamada
2014-11-04 19:50 ` Pavel Machek
2014-11-05 5:06 ` Masahiro Yamada
2014-11-05 6:02 ` Marek Vasut [this message]
2014-11-05 7:48 ` Masahiro Yamada
2014-11-05 7:57 ` Marek Vasut
2014-11-05 8:12 ` Masahiro Yamada
2014-11-05 9:01 ` Marek Vasut
2014-11-06 11:59 ` Pavel Machek
2014-11-06 9:22 ` Lukasz Majewski
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=201411050702.24075.marex@denx.de \
--to=marex@denx.de \
--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