From: Mark Brown <broonie@kernel.org>
To: "Noralf Trønnes" <noralf@tronnes.org>
Cc: dri-devel@lists.freedesktop.org, linux-spi@vger.kernel.org
Subject: Re: Applied "spi: Add spi_is_bpw_supported()" to the spi tree
Date: Sun, 12 May 2019 12:08:00 +0900 [thread overview]
Message-ID: <20190512030800.GA21483@sirena.org.uk> (raw)
In-Reply-To: <e87abf19-4616-01e3-5bca-5938dee39c63@tronnes.org>
[-- Attachment #1.1: Type: text/plain, Size: 503 bytes --]
On Thu, May 09, 2019 at 05:50:36PM +0200, Noralf Trønnes wrote:
> I can't see this in for-5.2 or linux-next. You also gave me a topic
> branch for this, but I wasn't able to get an r-b on the drm patch in the
> few days left before the -rc5 cutoff in the drm subsystem. This means
> that the patch didn't go in through drm for 5.2.
Well, the graphics people can still pull the signed tag whenever they
get round to reviewing stuff. The patch should end up in the next merge
window as well.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-05-12 3:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-12 9:41 [PATCH 1/2] spi: Add spi_is_bpw_supported() Noralf Trønnes
2019-04-12 9:41 ` [PATCH 2/2] drm/tinydrm: Use spi_is_bpw_supported() Noralf Trønnes
2019-04-12 10:16 ` [PATCH 1/2] spi: Add spi_is_bpw_supported() Mark Brown
2019-04-15 8:53 ` Applied "spi: Add spi_is_bpw_supported()" to the spi tree Mark Brown
2019-05-09 15:50 ` Noralf Trønnes
2019-05-12 3:08 ` Mark Brown [this message]
2019-04-17 16:42 ` Mark Brown
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=20190512030800.GA21483@sirena.org.uk \
--to=broonie@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-spi@vger.kernel.org \
--cc=noralf@tronnes.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;
as well as URLs for NNTP newsgroup(s).