public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	"Zhang, Rui" <rui.zhang@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-pm@lists.linux-foundation.org
Subject: Re: [GIT PATCH] ACPI patches for 2.6.26-rc0
Date: Thu, 1 May 2008 02:39:47 -0400	[thread overview]
Message-ID: <200805010239.48789.lenb@kernel.org> (raw)
In-Reply-To: <alpine.LFD.1.10.0804301153100.2980@woody.linux-foundation.org>

On Wednesday 30 April 2008, Linus Torvalds wrote:
> 
> On Wed, 30 Apr 2008, Len Brown wrote:
> > 
> > please pull from: 
> > 
> > git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6.git release
> 
> Ok, this clashed in some nasty ways in drivers/acpi/video.c due to the 
> non-racy /proc file creation changes that came through Andrew. I fixed up 
> the result, and it *looks* sane (and compiles), but I didn't actually test 
> it, and I don't know the code well. Can you double-check.

Thanks for merging video.c
When I did my builds, andrew had not yet scribbled on video.c.
I usually do a "last minute" pull to make sure you are not faced
with any merges, but this time when I did I got some version of your
tree that wouldn't build so I figured it was still moving and didn't
bother merging with it.

Anyway, I looked over this file and the things I looked for seemed okay,
but to be sure I'll repeat your merge tomorrow and see if I come
up with the same thing.

> There were some (smaller) rejects in drivers/misc/intel_menlow.c due to 
> two different versions of the same patch from Julia Lawall (again, the 
> other came through Andrew), and I picked the one from Andrew because it 
> had the later date. But again, you should double-check.

You picked the right one.
Indeed, it looks like the other files touched in Julia's earlier
patch (9030062f3d61f87c1e787b3aa134fa3a8e4b2d25)
don't handle the failure case quite right --
Rui and I will follow-up.

thanks,
-Len


  parent reply	other threads:[~2008-05-01  6:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-30 18:20 [GIT PATCH] ACPI patches for 2.6.26-rc0 Len Brown
2008-04-30 18:43 ` Andrew Morton
2008-04-30 19:00   ` Rafael J. Wysocki
2008-04-30 18:55 ` Linus Torvalds
2008-05-01  0:26   ` Stephen Rothwell
2008-05-01 12:16     ` Adrian Bunk
2008-05-01  6:39   ` Len Brown [this message]
2008-04-30 20:56 ` [patch] acpi: acpi_numa_init() build fix Ingo Molnar
2008-04-30 21:00   ` [patch] acpi: fix drivers/acpi/glue.c build error Ingo Molnar
2008-04-30 22:17     ` [linux-pm] " David Brownell

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=200805010239.48789.lenb@kernel.org \
    --to=lenb@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=rui.zhang@intel.com \
    --cc=torvalds@linux-foundation.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