From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/3] ARM: uniphier: enable SPL_OF_CONTROL
Date: Sat, 29 Aug 2015 15:56:14 +0200 [thread overview]
Message-ID: <201508291556.14656.marex@denx.de> (raw)
In-Reply-To: <CAK7LNATAD1nq048Fdc8SKn-ACeJf2oX1_MX+ihnV0+AcrCSHAA@mail.gmail.com>
On Saturday, August 29, 2015 at 02:03:39 AM, Masahiro Yamada wrote:
> Hi Marek,
Hi Masahiro,
> 2015-08-29 6:41 GMT+09:00 Marek Vasut <marex@denx.de>:
> > On Friday, August 28, 2015 at 02:23:54 PM, Masahiro Yamada wrote:
> >> 2015-08-28 20:28 GMT+09:00 Marek Vasut <marex@denx.de>:
> >> > On Friday, August 28, 2015 at 01:13:18 PM, Masahiro Yamada wrote:
> >> >> Device Tree really improves code maintainability and is now
> >> >> available for SPL too.
> >> >>
> >> >> This is the state-of-the-art implementation in U-boot.
> >> >>
> >> >> The board files (platform data) are no longer needed.
> >> >>
> >> >> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> >> >
> >> > Acked-by: Marek Vasut <marex@denx.de>
> >>
> >> Do you mean, Reviewed-by ?
> >>
> >> You do not have maintainership for any files this commit is touching.
> >
> > I meant acked-by, but I suspect the meaning of both acked-by and
> > reviewed-by is a bit ambiguous. Is there some document which explains
> > what acked-by and reviewed-by precisely mean ?
>
> Personally, I was very convinced with the last answer (Nov 14, 2012;
> 7:34am) in this thread:
> http://linux-kernel.2935.n7.nabble.com/acked-by-meaning-td551744.html
>
>
>
> If you want to refer to a more official one,
> https://www.kernel.org/doc/Documentation/SubmittingPatches
Oh, they did formalize it here. I didn't know about that, thanks!
> ------------->8------------
> Acked-by: is often used by the maintainer of the affected code when that
> maintainer neither contributed to nor forwarded the patch.
>
> [snip]
>
> Acked-by: does not necessarily indicate acknowledgement of the entire
> patch. For example, if a patch affects multiple subsystems and has an
> Acked-by: from one subsystem maintainer then this usually indicates
> acknowledgement of just the part which affects that maintainer's code.
> --------------8<---------------
>
>
> I think this is the typical usage of Acked-by:
> http://patchwork.ozlabs.org/patch/508716/
>
>
>
> In the kernel development, patch committers give Signed-off-by,
> but it is not the custom in U-boot.
We should certainly talk about the usage of SoB lines in U-Boot eventually.
> So, I guess it makes sense that custodians issue Acked-by instead of
> Signed-off-by.
That I am not so sure about. But, feel free to add my R-B to this patch if
you feel it's appropriate ;-)
Best regards,
Marek Vasut
next prev parent reply other threads:[~2015-08-29 13:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-28 11:13 [U-Boot] [PATCH 1/3] ARM: uniphier: select SPL_DM rather than default in defconfig Masahiro Yamada
2015-08-28 11:13 ` [U-Boot] [PATCH 2/3] ARM: uniphier: enable SPL_OF_CONTROL Masahiro Yamada
2015-08-28 11:28 ` Marek Vasut
2015-08-28 12:23 ` Masahiro Yamada
2015-08-28 21:41 ` Marek Vasut
2015-08-29 0:03 ` Masahiro Yamada
2015-08-29 13:56 ` Marek Vasut [this message]
2015-08-28 23:22 ` Simon Glass
2015-08-30 15:46 ` Masahiro Yamada
2015-08-28 11:13 ` [U-Boot] [PATCH 3/3] serial: uniphier: drop platform data support Masahiro Yamada
2015-08-28 23:22 ` Simon Glass
2015-08-30 15:46 ` Masahiro Yamada
2015-08-30 15:43 ` [U-Boot] [PATCH 1/3] ARM: uniphier: select SPL_DM rather than default in defconfig Masahiro Yamada
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=201508291556.14656.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