From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: linux-i2c@vger.kernel.org,
Jarkko Nikula <jarkko.nikula@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Ulf Hansson <ulf.hansson@linaro.org>
Subject: Re: Designware patches
Date: Sun, 19 Jun 2016 20:33:22 +0300 [thread overview]
Message-ID: <1466357602.30123.169.camel@linux.intel.com> (raw)
In-Reply-To: <20160619173034.GF2933@tetsubishi>
On Sun, 2016-06-19 at 19:30 +0200, Wolfram Sang wrote:
> >
> > > http://patchwork.ozlabs.org/project/linux-
> > > i2c/list/?submitter=&state=&q=design&archive=&delegate=
> >
> > Wow, there is a couple from ancient times!
>
> We can skip the one from 2013 :) And I missed the ack for the 2015
> one,
> will apply it now.
I assume that Jarkko's patches we should review or comment, but I don't
remember if it was the case that time.
>
> >
> > >
> > > 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?
> >
> > My patches can't be applied since it touches PCI part.
>
> I assume s/can't/can/ here and that
True
>
> http://patchwork.ozlabs.org/patch/610444/
>
> is obsolete meanwhile then?
Looks so wrt Jarkko's comment.
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2016-06-19 17:33 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 [this message]
2016-06-20 8:07 ` Jarkko Nikula
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=1466357602.30123.169.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=jarkko.nikula@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).