All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: alex.bluesman.smirnov@gmail.com
Cc: netdev@vger.kernel.org, linux-zigbee-devel@lists.sourceforge.net
Subject: Re: [PATCH 0/5][6lowpan] several fixes for 6lowpan
Date: Wed, 25 Apr 2012 20:35:54 -0400 (EDT)	[thread overview]
Message-ID: <20120425.203554.1187346578559639487.davem@davemloft.net> (raw)
In-Reply-To: <1335264671-27127-1-git-send-email-alex.bluesman.smirnov@gmail.com>

From: Alexander Smirnov <alex.bluesman.smirnov@gmail.com>
Date: Tue, 24 Apr 2012 14:51:06 +0400

> the following patch-set contains several fixes/improvements for 6lowpan:
> 1. fix: segmentation fault caused by mlme request
> 2. impr: move frame allocation code to a separate function
> 3. fix: clean up fragments list if module unloaded
> 4. impr: duplicate definition of IEEE802154_ALEN
> 5. fix: add missing spin_lock_init()
> 
> Could you please review them?

You need to not mix bug fixe patches with one which perform
cleanups and code refactoring.

Submit the pure bug fixes as one set, against the 'net' tree.

Then submit the rest as another set, against the 'net-next' tree.

Thanks.

      parent reply	other threads:[~2012-04-26  0:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-24 10:51 [PATCH 0/5][6lowpan] several fixes for 6lowpan Alexander Smirnov
2012-04-24 10:51 ` [PATCH 1/5] 6lowpan: fix segmentation fault caused by mlme request Alexander Smirnov
     [not found] ` <1335264671-27127-1-git-send-email-alex.bluesman.smirnov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-04-24 10:51   ` [PATCH 2/5] 6lowpan: move frame allocation code to a separate function Alexander Smirnov
2012-04-24 10:51   ` [PATCH 3/5] 6lowpan: clean up fragments list if module unloaded Alexander Smirnov
2012-04-24 10:51 ` [PATCH 4/5] 6lowpan: duplicate definition of IEEE802154_ALEN Alexander Smirnov
2012-04-24 10:51 ` [PATCH 5/5] 6lowpan: add missing spin_lock_init() Alexander Smirnov
2012-04-26  0:35 ` 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=20120425.203554.1187346578559639487.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=alex.bluesman.smirnov@gmail.com \
    --cc=linux-zigbee-devel@lists.sourceforge.net \
    --cc=netdev@vger.kernel.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 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.