From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: Wolfram Sang <wsa@the-dreams.de>, linux-i2c@vger.kernel.org
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Ulf Hansson <ulf.hansson@linaro.org>
Subject: Re: Designware patches
Date: Mon, 20 Jun 2016 11:07:32 +0300 [thread overview]
Message-ID: <6ddfd64d-8c9a-8b10-bea5-ff2165b83e00@linux.intel.com> (raw)
In-Reply-To: <20160619170800.GB2933@tetsubishi>
On 06/19/2016 08:08 PM, Wolfram Sang wrote:
> Hi Jarkko and everyone,
>
> there are a bunch of patches pending for the designware driver and I am
> a bit lost e.g. if a series is superseding another series by taking a
> different approach, if there are contradicting series, or what would be
> a good order to pick them. May I ask for some assistance here? The list
> of patches can be seen here:
>
> http://patchwork.ozlabs.org/project/linux-i2c/list/?submitter=&state=&q=design&archive=&delegate=
>
> I'd suggest I apply patches whenever they get acked- or rev-by tags. Or
> drop them when someone says so in a reply to the patch. Does that sound
> like a plan?
>
Yeah, there has been some activity recently. So far I don't remember we
have any urgent fixes pending. Acked and reviewed patches are easy this
time: they are independent and there are no contradicting patches so
should be safe to apply.
Lucas De Marchi's patch seems to be still problematic for Christian.
Jisheng Zhang's and Ulf Hansson's sets are both around CLK and PM.
Hinting there are things needs to be changed. I quess Jisheng's patches
had some opens and left floating. Ulf's recent set is under discussion.
--
Jarkko
prev parent reply other threads:[~2016-06-20 8:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-19 17:08 Designware patches Wolfram Sang
2016-06-19 17:16 ` Andy Shevchenko
2016-06-19 17:30 ` Wolfram Sang
2016-06-19 17:33 ` Andy Shevchenko
2016-06-20 8:07 ` Jarkko Nikula [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=6ddfd64d-8c9a-8b10-bea5-ff2165b83e00@linux.intel.com \
--to=jarkko.nikula@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-i2c@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=ulf.hansson@linaro.org \
--cc=wsa@the-dreams.de \
/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).