From: Andi Kleen <andi@firstfloor.org>
To: Harald Welte <laforge@gnumonks.org>
Cc: linux-acpi@vger.kernel.org
Subject: Re: [PATCH] [REPOST] Add Panasonic Laptop ACPI extras driver
Date: Fri, 22 Aug 2008 15:12:46 +0200 [thread overview]
Message-ID: <87y72pkxbl.fsf@basil.nowhere.org> (raw)
In-Reply-To: <20080822105820.GC27101@prithivi.gnumonks.org> (Harald Welte's message of "Fri, 22 Aug 2008 18:58:20 +0800")
Harald Welte <laforge@gnumonks.org> writes:
>
> oh, sorry for my ignorance. I just never got any confirmation and didn't see
> it in linux-2.6.git. Probably I should start adding linux-next to my workflow.
Or the git tree of the subsystem you're submitting, but linux-next
is more convenient because it's all in one. The main annoyance is
that you need git magic to update because they rebase all the time
(normal pull -u doesn't work)
>
> sorry once again for bothering you.
No problem. I must have forgotten to send out an ACK. I do merges
in batches and this sometimes happens.
-Andi
prev parent reply other threads:[~2008-08-22 13:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-22 3:00 [PATCH] [REPOST] Add Panasonic Laptop ACPI extras driver Harald Welte
2008-08-22 8:59 ` Andi Kleen
2008-08-22 10:58 ` Harald Welte
2008-08-22 13:12 ` Andi Kleen [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=87y72pkxbl.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=laforge@gnumonks.org \
--cc=linux-acpi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.