From: David Fries <David@Fries.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: pull w1 updates to linux-next?
Date: Wed, 15 Jan 2014 22:51:01 -0600 [thread overview]
Message-ID: <20140116045100.GB29560@spacedout.fries.net> (raw)
I've not submitted to linux-next before, would you pull the one wire
changes to linux-next? It has been posted and reviewed by one wire
maintainer Evgeniy Polyakov, and the 15 patch series was posted again
ready to go for GregKH to pick up. This is my one wire tree not
maintainer, and once merged upstream won't be updated unless I have
another set of changes.
cd5f76716a37ebef3e8b771d672ba552a25dafd5
git://github.com/dfries/linux.git w1_rework
--
David Fries <david@fries.net> PGP pub CB1EE8F0
http://fries.net/~david/
next reply other threads:[~2014-01-16 4:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 4:51 David Fries [this message]
2014-01-16 22:41 ` 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=20140116045100.GB29560@spacedout.fries.net \
--to=david@fries.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®