public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft•net>
To: sfr@canb•auug.org.au
Cc: nhorman@tuxdriver•com, linux-next@vger•kernel.org,
	linux-kernel@vger•kernel.org, netdev@vger•kernel.org
Subject: Re: linux-next: origin tree build warnings
Date: Sun, 28 Dec 2008 20:21:15 -0800 (PST)	[thread overview]
Message-ID: <20081228.202115.210807179.davem@davemloft.net> (raw)
In-Reply-To: <20081229151749.8dd82c02.sfr@canb.auug.org.au>

From: Stephen Rothwell <sfr@canb•auug.org.au>
Date: Mon, 29 Dec 2008 15:17:49 +1100

> On Sun, 28 Dec 2008 20:01:45 -0800 (PST) David Miller <davem@davemloft•net> wrote:
> >
> > I'll take care of all of these issues, along with the
> 
> Thanks.
> 
> > ibmveth et al. ones you reported seperately.
> 
> Linus already took my patches for cifs, ibmveth and ehea (probably
> assuming that they were trivial).

Yep I noticed that, thanks a lot Stephen.

  reply	other threads:[~2008-12-29  4:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-29  0:35 linux-next: origin tree build warnings Stephen Rothwell
2008-12-29  4:01 ` David Miller
2008-12-29  4:17   ` Stephen Rothwell
2008-12-29  4:21     ` David Miller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-04-29  4:44 Stephen Rothwell
2009-04-29  7:52 ` Andrew Morton
2009-04-29 15:38   ` Tyler Hicks
2010-01-01  0:42 Stephen Rothwell
2010-01-01  0:50 ` Linus Torvalds
2010-01-01  1:22   ` Stephen Rothwell
2010-01-01  1:32     ` Linus Torvalds
2010-01-01  1:50       ` Stephen Rothwell
2010-01-02  9:32         ` Shilimkar, Santosh
2010-01-04 13:51       ` Samuel Ortiz

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=20081228.202115.210807179.davem@davemloft.net \
    --to=davem@davemloft$(echo .)net \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=nhorman@tuxdriver$(echo .)com \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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