From: Len Brown <lenb@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Moore, Robert" <robert.moore@intel.com>,
trenn@suse.de, linux-acpi@vger.kernel.org, jbeulich@novell.com
Subject: Re: [patch 04/10] acpi: adjust _acpi_{module,function}_namedefinitions
Date: Thu, 26 Jun 2008 22:20:26 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0806262210520.2988@localhost.localdomain> (raw)
In-Reply-To: <20080623124523.76f38d90.akpm@linux-foundation.org>
> > >But in future, such patches should definitely be based against ACPICA
> > >code. Len will probably announce here where to find the very latest
> > >sources, soon. Currently the latest official release linked to on
> > >http://lesswatts.org is still from 2006. AFAIK things will get better
> > >here, soon.
> > >
> > > Thomas
> >
> >
> > The latest ACPICA source can be found at the acpica.org website. In
> > fact, we have converted our source repository from CVS to git, and the
> > actual working git repository is now publicly available at
> >
> > http://www.acpica.org/repos/acpica.git/
> >
> > The acpica.org website was created at the end of 2007, and is now the
> > home of the acpica project.
> >
>
> OK, I'm now peeved.
please, don't be.
> I've sent this patch ten damned times now and only once was there any
> comment and it was this vague indecisive wafflefest from which I now
> discover I was removed from Cc.
it appears that the cc: list was trimmed when a discussion
about the ACPCIA git tree URL was sent.
Unfortunately on May 6th when bob e-mailed that he'd pulled the patch
into ACPICA, he replied to that branch of the thread and not the
original.
If I pulled from Bob instantaneously, you'd have got a reject
when creating -mm on that day. As it turns out, we had more
urgent fish to fry that day, so it came out the end of
the ACPICA->Linux pipe later.
> Well someone has now merged something else which wrecked this patch
> whcih I've been maintaining (for you guys!) for over two months.
>
> I'll drop it. Please try harder.
Please do drop it, because it is already in linux-acpi.
It probably didn't reject cleanly because Lindent is too.
In the future, please simply do not accept
patches to drivers/acpi/*/* (the ACPICA files) into -mm.
Instead, bounce them to the Linux/ACPI maintainer,
who will bounce them to the ACPICA maintainer --
which is the head of the stream for these sub-directories.
Yes, I could have and should have asked you to drop these
ACPICA cleanups back when I bounced them to Bob.
I certainly don't want to create more work for you.
thanks,
-Len
next prev parent reply other threads:[~2008-06-27 2:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-01 9:52 [patch 04/10] acpi: adjust _acpi_{module,function}_name definitions akpm
2008-05-02 10:06 ` Thomas Renninger
2008-05-02 12:41 ` Andrew Morton
2008-05-02 14:04 ` Thomas Renninger
2008-05-04 19:14 ` [patch 04/10] acpi: adjust _acpi_{module,function}_namedefinitions Moore, Robert
2008-05-06 12:51 ` Thomas Renninger
2008-05-06 17:36 ` [patch 04/10] acpi: adjust_acpi_{module,function}_namedefinitions Moore, Robert
2008-06-23 19:45 ` [patch 04/10] acpi: adjust _acpi_{module,function}_namedefinitions Andrew Morton
2008-06-27 2:20 ` Len Brown [this message]
2008-06-27 5:00 ` Andrew Morton
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=alpine.LFD.1.10.0806262210520.2988@localhost.localdomain \
--to=lenb@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=jbeulich@novell.com \
--cc=linux-acpi@vger.kernel.org \
--cc=robert.moore@intel.com \
--cc=trenn@suse.de \
/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