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 10:01:23 +0100 [thread overview]
Message-ID: <201411051001.23455.marex@denx.de> (raw)
In-Reply-To: <20141105171239.CB3C.AA925319@jp.panasonic.com>
On Wednesday, November 05, 2014 at 09:12:40 AM, Masahiro Yamada wrote:
> Hi Marek,
Hi Masahiro,
> On Wed, 5 Nov 2014 08:57:50 +0100
>
> Marek Vasut <marex@denx.de> wrote:
> > On Wednesday, November 05, 2014 at 08:48:19 AM, Masahiro Yamada wrote:
> > > Hi Marek,
> >
> > Hi!
> >
> > > (reduced Cc)
> > >
> > > On Wed, 5 Nov 2014 07:02:23 +0100
> > >
> > > Marek Vasut <marex@denx.de> wrote:
> > > > 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 ?
> > >
> > > No.
> > > Going forward I will do that. Thaks for your advice!
> >
> > I was just curious what Pavel does there, since I also got some spelling
> > corrections from him. Please don't take it like I want to add more work
> > on your plate.
>
> I was not sure if your question was addressed to me or Pavel,
> but never mind.
>
> I use nano editor for inputting git-log.
> It is just to press Ctrl-T to invoke aspell,
> so it will not load me with much work.
> Resending a patch just for a typo is a more tedious work.
Right, I'd be fine if the committer could just fix it without the need
for resend ...
> (Pavel, don't get me wrong. All you pointed out are good things.)
btw. I have this precommit hook to invoke checkpatch and you can possibly
add a postcommit (?) hook to invoke aspell too. Just a hint though ...
-->8--
marex at bfu:u-boot$ cat .git/hooks/pre-commit
#!/bin/sh
#
# pre-commit hook to run check-patch on the output and stop any commits
# that do not pass. Note, only for git-commit, and not for any of the
# other scenarios
#
# Copyright 2010 Ben Dooks, <ben-linux@fluff.org>
if git rev-parse --verify HEAD 2>/dev/null >/dev/null
then
against=HEAD
else
# Initial commit: diff against an empty tree object
against=4b825dc642cb6eb9a060e54bf8d69288fbee4904
fi
git diff --cached $against -- | ./scripts/checkpatch.pl --no-signoff -
--8<--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2014-11-05 9:01 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
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 [this message]
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=201411051001.23455.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