public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Richard Purdie <rpurdie@rpsys•net>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
	Andrew Morton <akpm@linux-foundation•org>,
	Michael Hennerich <michael.hennerich@analog•com>,
	Mike Frysinger <vapier@gentoo•org>
Subject: Re: linux-next: build failure after merge of the backlight tree
Date: Wed, 19 May 2010 10:56:49 +1000	[thread overview]
Message-ID: <20100519105649.ab2d4d26.sfr@canb.auug.org.au> (raw)
In-Reply-To: <1274198064.24454.252.camel@rex>

[-- Attachment #1: Type: text/plain, Size: 354 bytes --]

Hi Richard,

On Tue, 18 May 2010 08:54:24 -0700 Richard Purdie <rpurdie@rpsys•net> wrote:
>
> Sorry about that. A bad combination of travel with limited internet
> access followed by illness. I've pushed a fix, thanks.

Thanks for that.

-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-05-19  0:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-10  2:43 linux-next: build failure after merge of the backlight tree Stephen Rothwell
2010-05-10  5:41 ` Mike Frysinger
2010-05-17  3:32 ` Stephen Rothwell
2010-05-18 15:54   ` Richard Purdie
2010-05-19  0:56     ` Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-05-27  3:11 Stephen Rothwell
2015-05-27  7:45 ` Lee Jones
2024-02-26  2:28 Stephen Rothwell
2024-03-05  0:16 ` Stephen Rothwell
2024-03-05  9:17   ` Lee Jones
2024-03-05 22:55     ` Stephen Rothwell
2024-03-06  3:04       ` Stephen Rothwell
2024-03-07  8:24         ` Lee Jones
2024-03-07  9:04           ` Lee Jones
2024-03-07 19:30             ` Stephen Rothwell

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=20100519105649.ab2d4d26.sfr@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=akpm@linux-foundation$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=michael.hennerich@analog$(echo .)com \
    --cc=rpurdie@rpsys$(echo .)net \
    --cc=vapier@gentoo$(echo .)org \
    /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