From: David Miller <davem@davemloft.net>
To: stefan@osg.samsung.com
Cc: linux-wpan@vger.kernel.org, alex.aring@gmail.com,
marcel@holtmann.org, netdev@vger.kernel.org
Subject: Re: pull-request: ieee802154 2017-09-20
Date: Fri, 22 Sep 2017 21:29:57 -0700 (PDT) [thread overview]
Message-ID: <20170922.212957.1788701109019802150.davem@davemloft.net> (raw)
In-Reply-To: <20170921205606.GA14244@work.Speedport_W_724V_09011603_05_010>
From: Stefan Schmidt <stefan@osg.samsung.com>
Date: Thu, 21 Sep 2017 22:56:07 +0200
> Here comes a pull request for ieee802154 changes I have queued up for
> this merge window.
>
> Normally these have been coming through the bluetooth tree but as this
> three have been falling through the cracks so far and I have to review
> and ack all of them anyway I think it makes sense if I save the
> bluetooth people some work and handle them directly.
>
> Its the first pull request I send to you so please let me know if I did
> something wrong or if you prefer a different format.
Pulled, thanks.
prev parent reply other threads:[~2017-09-23 4:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 20:56 pull-request: ieee802154 2017-09-20 Stefan Schmidt
2017-09-23 4:29 ` David Miller [this message]
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=20170922.212957.1788701109019802150.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alex.aring@gmail.com \
--cc=linux-wpan@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=stefan@osg.samsung.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