From: Alexander Aring <alex.aring@gmail.com>
To: Alan Ott <alan@signal11.us>
Cc: Varka Bhadram <varkabhadram@gmail.com>,
linux-wpan@vger.kernel.org, Varka Bhadram <varkab@cdac.in>
Subject: Re: [PATCH wpan-next v3 0/3] cleanup for mrf24j40
Date: Wed, 24 Sep 2014 08:54:21 +0200 [thread overview]
Message-ID: <20140924065419.GA24434@omega> (raw)
In-Reply-To: <5420DF1B.1000302@signal11.us>
On Mon, Sep 22, 2014 at 10:46:51PM -0400, Alan Ott wrote:
> On 09/19/2014 06:57 AM, Varka Bhadram wrote:
> >changes since v2:
> >- generated patches based on wpan-next
> >
> >changes since v1:
> >- changes in commit messages and descriptions suggested by Alan Ott
> >
> >Varka Bhadram (3):
> > mrf24j40: fix Missing a blank line after declarations
> > mrf24j40: remove unnecessary return statement
> > mrf24j40: use pr_* / dev_* instead of printk()
> >
> > drivers/net/ieee802154/mrf24j40.c | 19 ++++++++++---------
> > 1 file changed, 10 insertions(+), 9 deletions(-)
> >
>
> Acked-by: Alan Ott <alan@signal11.us>
>
Patches applied to wpan-next/testing branch. Note I catch all patches to
the testing branch and when these are applied to bluetooth then I rebase
the master branch again to the bluetooth master branch.
After that you have these patches are inside of wpan-next master branch.
- Alex
prev parent reply other threads:[~2014-09-24 6:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-19 10:57 [PATCH wpan-next v3 0/3] cleanup for mrf24j40 Varka Bhadram
2014-09-19 10:57 ` [PATCH wpan-next v3 1/3] mrf24j40: fix Missing a blank line after declarations Varka Bhadram
2014-09-19 10:57 ` [PATCH wpan-next v3 2/3] mrf24j40: remove unnecessary return statement Varka Bhadram
2014-09-19 10:57 ` [PATCH wpan-next v3 3/3] mrf24j40: use pr_* / dev_* instead of printk() Varka Bhadram
2014-09-23 2:46 ` [PATCH wpan-next v3 0/3] cleanup for mrf24j40 Alan Ott
2014-09-24 6:54 ` Alexander Aring [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=20140924065419.GA24434@omega \
--to=alex.aring@gmail.com \
--cc=alan@signal11.us \
--cc=linux-wpan@vger.kernel.org \
--cc=varkab@cdac.in \
--cc=varkabhadram@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 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.