netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Samuel Ortiz <samuel@sortiz.org>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, irda-users@lists.sourceforge.net
Subject: Re: [PATCH 0/4] irda: IrDA updates for 2.6.26
Date: Mon, 7 Jul 2008 13:08:41 +0200	[thread overview]
Message-ID: <20080707110839.GA2949@sortiz.org> (raw)
In-Reply-To: <20080630.125954.182681597.davem@davemloft.net>

Hi Dave,

On Mon, Jun 30, 2008 at 12:59:54PM -0700, David Miller wrote:
> From: "Samuel Ortiz" <samuel@sortiz.org>
> Date: Mon, 30 Jun 2008 21:23:51 +0200
> 
> > Here goes a 4 patches set for IrDA.
> > This is against your net-next-2.6 tree.
> 
> Except for patch 2, these all look like bug fixes.
> 
> So I think patches 1, 3, and 4 are likely good candidates
> for net-2.6 and thus merging in to Linus for 2.6.26
> 
> What say you?
Sorry for the delay, spam assassin played tricks on me.
Yes, if you want to push 1,3 and 4 to net-2.6, it's really fine with
me.

Cheers,
Samuel.



  reply	other threads:[~2008-07-07 11:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-30 19:23 [PATCH 0/4] irda: IrDA updates for 2.6.26 Samuel Ortiz
2008-06-30 19:23 ` [PATCH 1/4] irda: via-ircc proper dma freeing Samuel Ortiz
2008-06-30 19:23 ` [PATCH 2/4] irda: Remove useless pm_dev references Samuel Ortiz
2008-06-30 19:23 ` [PATCH 3/4] irda: New device ID for nsc-ircc Samuel Ortiz
2008-06-30 19:23 ` [PATCH 4/4] irda: Fix netlink error path return value Samuel Ortiz
     [not found] ` <20080630192351.765611690-jcdQHdrhKHMdnm+yROfE0A@public.gmane.org>
2008-06-30 19:59   ` [PATCH 0/4] irda: IrDA updates for 2.6.26 David Miller
2008-07-07 11:08     ` Samuel Ortiz [this message]
     [not found]       ` <20080707110839.GA2949-jcdQHdrhKHMdnm+yROfE0A@public.gmane.org>
2008-07-07 11:10         ` David Miller

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=20080707110839.GA2949@sortiz.org \
    --to=samuel@sortiz.org \
    --cc=davem@davemloft.net \
    --cc=irda-users@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 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).