linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: t.figa@samsung.com (Tomasz Figa)
To: linux-arm-kernel@lists.infradead.org
Subject: Samsung-clk patches for 3.15
Date: Fri, 24 Jan 2014 15:38:33 +0100	[thread overview]
Message-ID: <52E27AE9.7040501@samsung.com> (raw)

Hi,

Linux 3.14 is going to include Andrzej Hajda's patches converting 
Samsung clock drivers to use clock ID defines in include/dt-bindings, 
instead of local enums, but to avoid unnecessary merge conflicts we have 
converted only the clock driver, leaving DTS files unchanged yet.

We intend to complete the conversion in 3.15, by replacing magic numbers 
in DTS files with respective preprocessor macros, but to reduce 
potential conflicts we need help of you, Samsung clock patches authors :).

I'd like to ask anybody who already has patches for DTS files adding any 
clock-related contents still using numeric IDs, e.g. clock properties in 
nodes or full nodes containing clock properties, to make sure that the 
patches are merged before Andrzej sends the conversion patches. Then 
Andrzej's script will generate patches updating all clock properties, 
leaving no numeric IDs in DTS files.

If you are just starting your work on a patch that introduces changes as 
mentioned above, please make sure to already use clock macros, not 
numeric IDs. Otherwise you risk having needless rebases with a lot of 
conflicts. You have been warned ;).

Best regards,
Tomasz

             reply	other threads:[~2014-01-24 14:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-24 14:38 Tomasz Figa [this message]
2014-01-27 23:37 ` Samsung-clk patches for 3.15 Tomasz Figa
2014-01-28  0:09   ` Kukjin Kim
2014-01-28  0:17     ` Tomasz Figa
2014-02-14  0:05       ` Kukjin Kim
2014-02-14  0:24         ` Kukjin Kim

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=52E27AE9.7040501@samsung.com \
    --to=t.figa@samsung.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 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).