From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Nathan Chancellor <natechancellor@gmail.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Subject: Re: linux-next: Tree for Dec 11
Date: Wed, 12 Dec 2018 09:53:40 +1100 [thread overview]
Message-ID: <20181212095340.35bcb8c6@canb.auug.org.au> (raw)
In-Reply-To: <20181212093632.774c0603@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 365 bytes --]
Hi Nathan,
On Wed, 12 Dec 2018 09:36:32 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> I have added that patch after the v4l-dvb tree for today. (and cc'd
> the v4l-dvb maintainer - who is also the author of the patch in the
> Fixes tag ...)
Sorry, I just realised that your original patch was sent to Mauro.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-12-11 22:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 7:26 linux-next: Tree for Dec 11 Stephen Rothwell
2018-12-11 17:38 ` Guenter Roeck
2018-12-11 18:04 ` Nathan Chancellor
2018-12-11 22:36 ` Stephen Rothwell
2018-12-11 22:53 ` Stephen Rothwell [this message]
2018-12-19 3:44 ` Stephen Rothwell
2018-12-20 11:43 ` Mauro Carvalho Chehab
2018-12-11 22:37 ` Guenter Roeck
-- strict thread matches above, loose matches on Subject: below --
2023-12-11 6:25 Stephen Rothwell
2020-12-11 10:11 Stephen Rothwell
2019-12-11 2:42 Stephen Rothwell
2017-12-11 5:32 Stephen Rothwell
2015-12-11 6:05 Stephen Rothwell
2014-12-11 10:38 Stephen Rothwell
2013-12-11 4:56 Stephen Rothwell
2013-12-11 4:59 ` Stephen Rothwell
2012-12-11 5:57 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=20181212095340.35bcb8c6@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mchehab@kernel.org \
--cc=natechancellor@gmail.com \
/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).