netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: alan@linux.intel.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Build fixes for todays next tree
Date: Tue, 13 Oct 2009 00:21:53 -0700 (PDT)	[thread overview]
Message-ID: <20091013.002153.32447389.davem@davemloft.net> (raw)
In-Reply-To: <20091012152247.5694.77290.stgit@localhost.localdomain>

From: Alan Cox <alan@linux.intel.com>
Date: Mon, 12 Oct 2009 16:27:17 +0100

> Couple of networking warns/build fails

I'll apply these, thanks Alan.

      parent reply	other threads:[~2009-10-13  7:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-12 15:27 [PATCH 0/2] Build fixes for todays next tree Alan Cox
2009-10-12 15:27 ` [PATCH 1/2] libertas: fix build Alan Cox
2009-10-12 15:27 ` [PATCH 2/2] ethoc: fix warning from 32bit build Alan Cox
2009-10-13  7:21 ` 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=20091013.002153.32447389.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=alan@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --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).