linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: khilman@linaro.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL]socfpga: DTS updates for v3.13
Date: Wed, 09 Oct 2013 13:57:29 -0700	[thread overview]
Message-ID: <87y562rwli.fsf@linaro.org> (raw)
In-Reply-To: <1381198434-9583-1-git-send-email-dinguyen@altera.com> (dinguyen@altera.com's message of "Mon, 7 Oct 2013 21:13:54 -0500")

<dinguyen@altera.com> writes:

> Hi Kevin, Olof, and Arnd:
>
> Please consider these DTS updates for the Altera SOCFPGA platform for v3.13:
>
> Five of the six patches do NOT have an Ack from the DTS maintainers. I have
> sent the patches out for review, but since these patches do not change
> bindings nor add new ones, I don't think they will get too much attention.
>
> Please advise if you think I need to wait for Ack(s) from them.

The DT maintainers are primarily there to review new/modified bindings,
so if there are now new/modified bindings, it's not a hard requirement
for them to review/ack (though we still prefer it.)

In this case, it's mostly just reorganizing and cleanup of existing dts
data, so there are no problems with us taking it.

That being said, the patch content looks fine, but as a matter of
process, since you took accepted/queued these patches from Steffen into
your tree before passing them on to us, you should have a Signed-off-by:
on them instead of an Acked-by: since you're formally on the delivery
path. (c.f. sections 12 & 13 of Documentation/SubmittingPatches for all
the details.)

Could you please respin a branch with the proper signoffs, and then I'll
queue it up for v3.13.

Thanks,

Kevin

  reply	other threads:[~2013-10-09 20:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-08  2:13 [GIT PULL]socfpga: DTS updates for v3.13 dinguyen at altera.com
2013-10-09 20:57 ` Kevin Hilman [this message]
2013-10-09 21:54   ` Dinh Nguyen

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=87y562rwli.fsf@linaro.org \
    --to=khilman@linaro.org \
    --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).