From: Borislav Petkov <bp@alien8.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: James Hogan <james.hogan@imgtec.com>, Arnd <arnd@arndb.de>,
linux-kernel <linux-kernel@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [GIT PULL] late arch/metag fixes for v3.9-rc1
Date: Sat, 2 Mar 2013 19:10:25 +0100 [thread overview]
Message-ID: <20130302181025.GA15498@pd.tnic> (raw)
In-Reply-To: <CA+55aFx1wKChQmAWgQR0iOdKr0bhLn7RLsZHj5ZuVVOtk8FXMw@mail.gmail.com>
On Sat, Mar 02, 2013 at 08:28:56AM -0800, Linus Torvalds wrote:
> On Sat, Mar 2, 2013 at 2:22 AM, James Hogan <james.hogan@imgtec.com> wrote:
> >
> > Okay, I've rebased the arch/metag tree onto mainline to make all the
> > back-merges unnecessary and applied those simple fixes into "Build
> > infrastructure" and "Various other headers" commits (additionally
> > trivially removing ARCH_NO_VIRT_TO_BUS which is also now unnecessary).
>
> No, this is *exactly* the wrong thing to do.
<snip good practices and musings about maintainer trees>
Hmm, so this comes up almost everytime new maintainers send stuff (and
when seasoned maintainers forget :)), maybe we should hold it down
somewhere in Documentation/ for future reference?
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2013-03-02 18:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-01 16:55 [GIT PULL] late arch/metag fixes for v3.9-rc1 James Hogan
2013-03-01 18:03 ` Linus Torvalds
2013-03-01 18:54 ` James Hogan
2013-03-02 10:22 ` James Hogan
2013-03-02 15:48 ` Stephen Rothwell
2013-03-02 16:22 ` James Hogan
2013-03-03 2:11 ` Stephen Rothwell
2013-03-02 16:28 ` Linus Torvalds
2013-03-02 16:31 ` Linus Torvalds
2013-03-02 18:10 ` Borislav Petkov [this message]
2013-03-02 18:40 ` Linus Torvalds
2013-03-02 19:19 ` Borislav Petkov
2013-03-02 19:25 ` Linus Torvalds
2013-03-02 19:06 ` Raymond Jennings
2013-03-02 19:05 ` James Hogan
2013-03-02 21:40 ` James Hogan
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=20130302181025.GA15498@pd.tnic \
--to=bp@alien8.de \
--cc=arnd@arndb.de \
--cc=james.hogan@imgtec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--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 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.