From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Christoph Hellwig <hch@lst.de>,
linux-kernel@vger.kernel.org,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
linux-acpi@vger.kernel.org,
Dan Williams <dan.j.williams@intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Borislav Petkov <bp@suse.de>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2 0/5] ACPI et al: convert to use new UUID API
Date: Wed, 31 May 2017 23:07:05 +0300 [thread overview]
Message-ID: <1496261225.28981.40.camel@linux.intel.com> (raw)
In-Reply-To: <20170531194152.65927-1-andriy.shevchenko@linux.intel.com>
On Wed, 2017-05-31 at 22:41 +0300, Andy Shevchenko wrote:
> [1]: git://git.infradead.org/users/hch/uuid.git
>
> Changelog v2:
> - append tags I have got so far
> - split single patch to few (5)
> - rebased on top of latest version of uuid-types branch [1]
Fengguang, looking to the above I just got an idea to come up with some
formal syntax in cover letter that will allow your tools to parse the
tree and branch on top of which it should be tested. Do you have
anything like that in place?
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Christoph Hellwig <hch@lst.de>,
linux-kernel@vger.kernel.org,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
linux-acpi@vger.kernel.org,
Dan Williams <dan.j.williams@intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Borislav Petkov <bp@suse.de>,
intel-gfx@lists.freedesktop.org
Cc: Fengguang Wu <lkp@intel.com>
Subject: Re: [PATCH v2 0/5] ACPI et al: convert to use new UUID API
Date: Wed, 31 May 2017 23:07:05 +0300 [thread overview]
Message-ID: <1496261225.28981.40.camel@linux.intel.com> (raw)
In-Reply-To: <20170531194152.65927-1-andriy.shevchenko@linux.intel.com>
On Wed, 2017-05-31 at 22:41 +0300, Andy Shevchenko wrote:
> [1]: git://git.infradead.org/users/hch/uuid.git
>
> Changelog v2:
> - append tags I have got so far
> - split single patch to few (5)
> - rebased on top of latest version of uuid-types branch [1]
Fengguang, looking to the above I just got an idea to come up with some
formal syntax in cover letter that will allow your tools to parse the
tree and branch on top of which it should be tested. Do you have
anything like that in place?
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2017-05-31 20:07 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 19:41 [PATCH v2 0/5] ACPI et al: convert to use new UUID API Andy Shevchenko
2017-05-31 19:41 ` Andy Shevchenko
2017-05-31 19:41 ` [PATCH v2 1/5] acpi, nfit: Switch to use new generic " Andy Shevchenko
2017-05-31 19:41 ` Andy Shevchenko
2017-06-01 14:26 ` Dan Williams
2017-06-05 16:01 ` Christoph Hellwig
2017-06-05 16:18 ` Andy Shevchenko
2017-06-05 16:18 ` Andy Shevchenko
2017-05-31 19:41 ` [PATCH v2 2/5] ACPI / APEI: " Andy Shevchenko
2017-05-31 19:41 ` Andy Shevchenko
2017-05-31 23:56 ` kbuild test robot
2017-05-31 23:56 ` [Intel-gfx] " kbuild test robot
2017-06-01 9:50 ` Andy Shevchenko
2017-06-01 9:50 ` [Intel-gfx] " Andy Shevchenko
2017-06-05 16:01 ` Christoph Hellwig
2017-06-05 16:19 ` Andy Shevchenko
2017-06-05 16:19 ` Andy Shevchenko
2017-06-05 16:22 ` Christoph Hellwig
2017-06-05 16:22 ` Christoph Hellwig
2017-06-05 16:28 ` Andy Shevchenko
2017-06-05 16:28 ` Andy Shevchenko
2017-05-31 19:41 ` [PATCH v2 3/5] ACPI / bus: " Andy Shevchenko
2017-05-31 22:42 ` Rafael J. Wysocki
2017-05-31 23:56 ` kbuild test robot
2017-05-31 23:56 ` kbuild test robot
2017-06-01 0:05 ` kbuild test robot
2017-06-01 0:05 ` kbuild test robot
2017-06-05 16:03 ` Christoph Hellwig
2017-06-05 16:03 ` Christoph Hellwig
2017-06-05 16:20 ` Andy Shevchenko
2017-06-05 16:20 ` Andy Shevchenko
2017-06-05 20:37 ` Rafael J. Wysocki
2017-06-05 20:37 ` Rafael J. Wysocki
2017-06-06 9:58 ` Christoph Hellwig
2017-05-31 19:41 ` [PATCH v2 4/5] ACPI / extlog: " Andy Shevchenko
2017-05-31 19:41 ` Andy Shevchenko
2017-06-05 16:06 ` Christoph Hellwig
2017-06-05 16:23 ` Andy Shevchenko
2017-06-05 16:23 ` Andy Shevchenko
2017-06-05 21:23 ` Christoph Hellwig
2017-05-31 19:41 ` [PATCH v2 5/5] ACPI: Switch to use generic guid_t in acpi_evaluate_dsm() Andy Shevchenko
2017-05-31 20:21 ` Mark Brown
2017-05-31 22:42 ` Rafael J. Wysocki
2017-06-01 6:03 ` Christoph Hellwig
2017-06-01 0:08 ` kbuild test robot
2017-06-01 0:08 ` kbuild test robot
2017-06-01 0:11 ` kbuild test robot
2017-06-01 0:11 ` kbuild test robot
2017-06-01 14:12 ` Jarkko Sakkinen
2017-06-01 14:12 ` Jarkko Sakkinen
2017-06-01 14:24 ` Dan Williams
2017-06-01 14:24 ` Dan Williams
2017-06-02 12:25 ` Adrian Hunter
2017-05-31 19:45 ` [PATCH v2 0/5] ACPI et al: convert to use new UUID API Christoph Hellwig
2017-05-31 19:45 ` ✗ Fi.CI.BAT: failure for " Patchwork
2017-05-31 20:07 ` Andy Shevchenko [this message]
2017-05-31 20:07 ` [PATCH v2 0/5] " Andy Shevchenko
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=1496261225.28981.40.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=bp@suse.de \
--cc=dan.j.williams@intel.com \
--cc=hch@lst.de \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rjw@rjwysocki.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.