From: dinguyen@altera.com (Dinh Nguyen)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL]socfpga: DTS updates for v3.13
Date: Wed, 9 Oct 2013 16:54:14 -0500 [thread overview]
Message-ID: <1381355654.13129.1.camel@linux-builds1> (raw)
In-Reply-To: <87y562rwli.fsf@linaro.org>
Hi Kevin,
On Wed, 2013-10-09 at 13:57 -0700, Kevin Hilman wrote:
> <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.)
I should have known about this. Thanks for the feedback.
>
> Could you please respin a branch with the proper signoffs, and then I'll
> queue it up for v3.13.
Will do..
Dinh
>
> Thanks,
>
> Kevin
>
prev parent reply other threads:[~2013-10-09 21:54 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
2013-10-09 21:54 ` Dinh Nguyen [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=1381355654.13129.1.camel@linux-builds1 \
--to=dinguyen@altera.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.