linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] ARM: /proc/atags: Export also for DT
Date: Thu, 25 Jun 2015 11:02:45 +0100	[thread overview]
Message-ID: <20150625100244.GA7576@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1431719407-18230-1-git-send-email-pali.rohar@gmail.com>

On Fri, May 15, 2015 at 09:50:05PM +0200, Pali Roh?r wrote:
> This patch adds support for DT "/atags" and stores ATAG structure to DT.
> 
> It depends on "ARM: /proc/cpuinfo: DT: Add support for Revision" patches.
> 
> Pali Roh?r (2):
>   arm: devtree: Save atags if are in DT atags field
>   arm: boot: store ATAG structure into DT atag field
> 
>  arch/arm/boot/compressed/atags_to_fdt.c |    6 +++++-
>  arch/arm/kernel/devtree.c               |    6 ++++++
>  2 files changed, 11 insertions(+), 1 deletion(-)

What these patches are missing is a description of _why_ this is required
in any of the commit messages.  The commit messages seem to be describing
_what_ the change is doing, which is something that can be seen by reading
the patches, but it leaves the question of why this change is necessary
entirely open.

Please update the commit messages on the next patch revision.

-- 
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.

      parent reply	other threads:[~2015-06-25 10:02 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-06  8:49 [RESEND] [PATCH v2 0/2] ARM: /proc/cpuinfo: DT: Add support for Revision Pali Rohár
2015-05-06  8:49 ` [RESEND] [PATCH v2 1/2] arm: devtree: Set system_rev from DT revision Pali Rohár
2015-05-06  9:31   ` Arnd Bergmann
2015-05-06 10:37     ` Pali Rohár
2015-05-06 11:04       ` Arnd Bergmann
2015-05-06 11:44         ` Pali Rohár
2015-06-25  5:01           ` Tony Lindgren
2015-06-25  7:18             ` Pali Rohár
2015-06-25  7:22               ` Tony Lindgren
2015-06-25  7:27                 ` Pali Rohár
2015-06-25  7:41                   ` Tony Lindgren
2015-07-06 12:23             ` Pali Rohár
2015-07-06 12:31               ` Tony Lindgren
2015-07-06 13:12                 ` Pali Rohár
2015-07-06 13:55                   ` Tony Lindgren
2015-07-06 15:22                   ` Rob Herring
2015-07-06 16:20                     ` Pali Rohár
2015-07-06 16:36                       ` Pali Rohár
2015-07-06 17:30                       ` Rob Herring
2015-07-06 15:20                 ` Rob Herring
2015-07-06 15:24                   ` Tony Lindgren
2015-06-25 10:03           ` Russell King - ARM Linux
2015-05-06  8:49 ` [RESEND] [PATCH v2 2/2] arm: boot: convert ATAG_REVISION to DT revision field Pali Rohár
2015-05-15 19:50 ` [PATCH 0/2] ARM: /proc/atags: Export also for DT Pali Rohár
2015-05-15 19:50   ` [PATCH 1/2] arm: devtree: Save atags if are in DT atags field Pali Rohár
2015-05-15 20:09     ` Arnd Bergmann
2015-06-25  5:06       ` Tony Lindgren
2015-05-15 19:50   ` [PATCH 2/2] arm: boot: store ATAG structure into " Pali Rohár
2015-05-15 20:12     ` Arnd Bergmann
2015-05-15 20:16       ` Pali Rohár
2015-05-15 20:21         ` Arnd Bergmann
2015-06-25  5:12           ` Tony Lindgren
2015-06-25 10:02   ` Russell King - ARM Linux [this message]

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=20150625100244.GA7576@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).