public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
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 19:30:34 +0200	[thread overview]
Message-ID: <20160619173034.GF2933@tetsubishi> (raw)
In-Reply-To: <1466356591.30123.167.camel@linux.intel.com>

[-- Attachment #1: Type: text/plain, Size: 654 bytes --]


> > 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'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

http://patchwork.ozlabs.org/patch/610444/

is obsolete meanwhile then?

Thanks,

   Wolfram


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-06-19 17:30 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 [this message]
2016-06-19 17:33     ` Andy Shevchenko
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=20160619173034.GF2933@tetsubishi \
    --to=wsa@the-dreams.de \
    --cc=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 \
    /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