Linux I2C development
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Wolfram Sang <wsa@the-dreams.de>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
	Jarkko Nikula <jarkko.nikula@linux.intel.com>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	linux-i2c@vger.kernel.org
Subject: Re: [PULL] topic/designware-baytrail for 4.12
Date: Thu, 2 Mar 2017 16:19:27 +0100	[thread overview]
Message-ID: <b5d5dc89-3db4-3e61-f189-dde2685299f2@redhat.com> (raw)
In-Reply-To: <CAKMK7uFTyxz8d36g2A700Kpq2zHQfPdw6XMLUSeudW1tEhreDA@mail.gmail.com>

Hi,

On 02-03-17 15:47, Daniel Vetter wrote:
> On Thu, Mar 2, 2017 at 3:38 PM, Hans de Goede <hdegoede@redhat.com> wrote:
>> On 02-03-17 08:00, Daniel Vetter wrote:
>>>
>>> On Wed, Mar 01, 2017 at 11:42:48AM +0100, Daniel Vetter wrote:
>>>>
>>>> Hi all,
>>>>
>>>> topic/designware-baytrail-2017-03-01:
>>>> Baytrail PMIC vs. PMU race fixes from Hans de Goede
>>>>
>>>> I opted to put all the patches for all subsystems into the topic
>>>> branches,
>>>> so that if needed, each subsystem can apply refactorings to the entire
>>>> thing. Which might be needed since we're very early in the 4.12 cycle.
>>>>
>>>> This has baked for a few days in the drm-intel CI and looks good afaics.
>>>> I'll pull this into drm-intel.git for 4.12, feel free to pull into any
>>>> other subsystem where needed.
>>>
>>>
>>> Hold the presses, 0day found a compile warning. Not sure whether it's a
>>> special config or why I/0day didn't spot this in the few days I let this
>>> soak, but well.
>>>
>>> Hans, can you pls provide I fixup patch? I'll respin the pull once I have
>>> that.
>>
>>
>> Already done, I had already noticed this and posted a v4 of the series a
>> while back. It looks like you ended up merging v3. No problem the fix of
>> this issue was the only new thing in v4 of the series.
>>
>> Here is the fixed v4 of the patch causing this:
>> https://patchwork.ozlabs.org/patch/731998/
>
> Oops :( I updated topic/designware-baytrail, can you pls double-check
> it's the right stuff now?

Done, looks good now.

Regards,

Hans
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2017-03-02 15:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-01 10:42 [PULL] topic/designware-baytrail for 4.12 Daniel Vetter
2017-03-02  7:00 ` Daniel Vetter
2017-03-02 14:38   ` Hans de Goede
2017-03-02 14:47     ` Daniel Vetter
2017-03-02 15:19       ` Hans de Goede [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=b5d5dc89-3db4-3e61-f189-dde2685299f2@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jarkko.nikula@linux.intel.com \
    --cc=linux-i2c@vger.kernel.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