From: tomasz.figa@gmail.com (Tomasz Figa)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/5] pinctrl: samsung: Data structure clean-up
Date: Sat, 11 Oct 2014 20:52:01 +0200 [thread overview]
Message-ID: <54397C51.20804@gmail.com> (raw)
In-Reply-To: <CACRpkdY1GjDEfRH=48e24m+UcKzdPhROJBKDertS+q+e0td03g@mail.gmail.com>
On 08.10.2014 12:23, Linus Walleij wrote:
> On Thu, Oct 2, 2014 at 8:52 PM, Tomasz Figa <tomasz.figa@gmail.com> wrote:
>
>> This series intends to clean up data structures used by pinctrl-samsung driver.
>> More specifically, it separates initial compile time constants from data used
>> at runtime, allowing unused variant data to be dropped and selected structures
>> constified to improve safety.
>
> Thanks!
>
> The patches missed the v3.18 merge window, but I have queued them up as
> the first thing to go into v3.19.
OK, thanks.
>
> Now I need you to help me check the patch set from Abhilash so I know
> what to do about that, whenever you have some time...
I've already acked previous version of that series, only with some minor
nitpicks pointed, but let me take a look at last version.
Best regards,
Tomasz
next prev parent reply other threads:[~2014-10-11 18:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-02 18:52 [PATCH v2 0/5] pinctrl: samsung: Data structure clean-up Tomasz Figa
2014-10-02 18:52 ` [PATCH v2 1/5] pinctrl: samsung: Make samsung_pinctrl_get_soc_data use ERR_PTR() Tomasz Figa
2014-10-02 18:52 ` [PATCH v2 2/5] pinctrl: samsung: Drop unused label field in samsung_pin_ctrl struct Tomasz Figa
2014-10-02 18:52 ` [PATCH v2 3/5] pinctrl: samsung: Constify samsung_pin_bank_type struct Tomasz Figa
2014-10-02 18:52 ` [PATCH v2 4/5] pinctrl: samsung: Constify samsung_pin_ctrl struct Tomasz Figa
2014-10-02 18:52 ` [PATCH v2 5/5] pinctrl: samsung: Separate per-bank init and runtime data Tomasz Figa
2014-10-08 10:23 ` [PATCH v2 0/5] pinctrl: samsung: Data structure clean-up Linus Walleij
2014-10-11 18:52 ` Tomasz Figa [this message]
2014-10-24 12:02 ` Linus Walleij
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=54397C51.20804@gmail.com \
--to=tomasz.figa@gmail.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).