From: Andrew Morton <akpm@linux-foundation.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org, mingo@redhat.com
Subject: Re: [PATCH] toshiba: Use ioremap_cached
Date: Tue, 29 Apr 2008 08:37:04 -0700 [thread overview]
Message-ID: <20080429083704.41855699.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080429152312.GB19410@elte.hu>
On Tue, 29 Apr 2008 17:23:12 +0200 Ingo Molnar <mingo@elte.hu> wrote:
>
> * Andrew Morton <akpm@linux-foundation.org> wrote:
>
> > > Acked-by: Ingo Molnar <mingo@elte.hu>
> > >
> > > i suspect this shouldnt go via x86.git but i've queued it up to
> > > track it.
> >
> > Please don't "queue things up to track them". Just queue them up to
> > merge them, or don't queue them at all.
> >
> > Because if you queue it up then I will not. If you later for some
> > reason unqueue it then volia, it is lost. We should aim to avoid
> > having multiple copies of a patch sitting around the place.
>
> but ... i dont just unqueue 'for some reason and then volia'. If we did
> that we'd be losing patches left and right. Every patch we unqueue
> happens in a very predictable protocol that should avoid patches getting
> lost.
>
> ( basically we only remove any patch when they are broken but even then
> there's a clear notification. Even a NAK or other fatal review
> feedback does not actually remove a patch in the typical case when the
> patch otherwise has practical use, and update is hoped for and the
> patch does not break things - it just freezes the patch at the "must
> not go upstream yet" end of the queue. )
>
> if we lose any patches then let us know so we can improve the protocol.
OK, in that case please don't say "i've queued it up to track it"!
Stick to the unambiguous, non-akpm-scary "applied" :)
prev parent reply other threads:[~2008-04-29 15:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 13:20 [PATCH] toshiba: Use ioremap_cached Alan Cox
2008-04-29 14:15 ` Ingo Molnar
2008-04-29 15:14 ` Andrew Morton
2008-04-29 15:23 ` Ingo Molnar
2008-04-29 15:37 ` Andrew Morton [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=20080429083704.41855699.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
/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