From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Andy Shevchenko <andy.shevchenko@gmail•com>
Cc: Arnd Bergmann <arnd@arndb•de>, Darren Hart <dvhart@infradead•org>,
Linux-Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Ritesh Raj Sarraf <rrs@debian•org>,
Andy Shevchenko <andriy.shevchenko@linux•intel.com>
Subject: Re: linux-next: build warning after merge of the drivers-x86 tree
Date: Fri, 26 May 2017 19:07:48 +1000 [thread overview]
Message-ID: <20170526190748.211181ba@canb.auug.org.au> (raw)
In-Reply-To: <CAHp75Vf_JqM-TEewus706+aJ+5AydpDfrYMjgp-sN23zep6Ydw@mail.gmail.com>
Hi Andy,
On Fri, 26 May 2017 12:04:47 +0300 Andy Shevchenko <andy.shevchenko@gmail•com> wrote:
>
> On Fri, May 26, 2017 at 11:35 AM, Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> > On Fri, 26 May 2017 10:25:36 +0200 Arnd Bergmann <arnd@arndb•de> wrote:
> >>
> >> Andy wrote that he committed an updated patch on May 23. The git tree
> >> at git://git.infradead.org/users/dvhart/linux-platform-drivers-x86.git#for-next
> >> appears to currently contain an older state from May 15.
> >
> > So just not pushed out yet. That's fine, I will hopefully notice when
> > it turns up. Just checking that it wasn't forgotten.
>
> No, it wasn't, it it in testing branch, I 'm about to push to for-next.
Thanks. No rush.
--
Cheers,
Stephen Rothwell
next prev parent reply other threads:[~2017-05-26 9:07 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-19 3:23 linux-next: build warning after merge of the drivers-x86 tree Stephen Rothwell
2017-05-19 22:09 ` Darren Hart
2017-05-22 18:03 ` Andy Shevchenko
2017-05-25 23:34 ` Stephen Rothwell
2017-05-26 8:25 ` Arnd Bergmann
2017-05-26 8:35 ` Stephen Rothwell
2017-05-26 9:04 ` Andy Shevchenko
2017-05-26 9:07 ` Stephen Rothwell [this message]
2017-05-26 9:52 ` Andy Shevchenko
-- strict thread matches above, loose matches on Subject: below --
2025-04-30 10:45 Stephen Rothwell
2025-04-30 10:51 ` Antheas Kapenekakis
2025-04-30 10:55 ` Ilpo Järvinen
2025-04-30 11:01 ` Antheas Kapenekakis
2025-04-30 11:07 ` Ilpo Järvinen
2024-08-20 3:43 Stephen Rothwell
2024-08-20 4:31 ` Kuppuswamy Sathyanarayanan
2024-08-23 19:16 ` Joseph, Jithu
2024-07-15 7:03 Stephen Rothwell
2024-01-05 6:29 Stephen Rothwell
2023-02-03 2:53 Stephen Rothwell
2023-02-03 9:25 ` Hans de Goede
2021-02-04 5:13 Stephen Rothwell
2021-02-04 7:38 ` Hans de Goede
2021-02-04 15:05 ` Andy Shevchenko
2020-02-10 23:35 Stephen Rothwell
2020-02-10 23:39 ` Kammela, Gayatri
2020-02-11 21:07 ` Andy Shevchenko
2020-01-10 3:57 Stephen Rothwell
2020-01-10 9:47 ` Andy Shevchenko
2017-06-30 4:00 Stephen Rothwell
2017-06-30 5:12 ` Arvind Yadav
2017-07-01 3:32 ` Darren Hart
2016-12-14 2:50 Stephen Rothwell
2016-12-14 22:21 ` Darren Hart
2016-12-14 22:59 ` Darren Hart
2016-12-15 0:02 ` Stephen Rothwell
2016-12-15 4:07 ` Darren Hart
2010-08-27 1:59 Stephen Rothwell
2010-08-27 2:51 ` Matthew Garrett
2010-08-27 7:40 ` Dmitry Torokhov
2010-08-30 2:51 ` Stephen Rothwell
2010-06-25 3:25 Stephen Rothwell
2010-06-25 3:31 ` Matthew Garrett
2010-06-25 3:41 ` Matthew Garrett
2010-06-25 4:16 ` Stephen Rothwell
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=20170526190748.211181ba@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=andriy.shevchenko@linux$(echo .)intel.com \
--cc=andy.shevchenko@gmail$(echo .)com \
--cc=arnd@arndb$(echo .)de \
--cc=dvhart@infradead$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rrs@debian$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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