From: Ingo Molnar <mingo@elte.hu>
To: Adrian Bunk <bunk@kernel.org>
Cc: Dmitri Vorobiev <dmitri.vorobiev@gmail.com>,
tglx@linutronix.de, hpa@zytor.com, linux-kernel@vger.kernel.org,
Alexander Viro <viro@ftp.linux.org.uk>
Subject: Re: x86: fix a couple of sparse warnings
Date: Mon, 28 Apr 2008 17:01:56 +0200 [thread overview]
Message-ID: <20080428150156.GA7412@elte.hu> (raw)
In-Reply-To: <20080428135957.GK16379@cs181133002.pp.htv.fi>
* Adrian Bunk <bunk@kernel.org> wrote:
> On Mon, Apr 28, 2008 at 05:43:25PM +0400, Dmitri Vorobiev wrote:
> > 2008/4/28 Adrian Bunk <bunk@kernel.org>:
> > >
> > > /me wonders what was wrong with http://lkml.org/lkml/2008/4/23/131
> > > that contains a superset of the first patch
> > > (and got no response at all)
> >
> > Adrian, I am sorry for duplicating your work. The clash wasn't
> > intentional: I did not notice your earlier patch in the high traffic
> > of this mailing list.
>
> No problem, and I'm actually more interested why my patch got lost.
It's simple: in this case i had two patches in my backlog, one from a
new person and one from a frequent contributor - doing the very same
change. I preferred the newbie's patch, to encourage Dmitri to keep
contributing to Linux and to help him learn from the experience of
working with various Linux maintainers.
You contributed a lot of similar changes already, and are 1500 similar
patches down the line, and for "trivial" patches like this you probably
aren't going to learn anything new.
That doesn't mean your work is not appreciated - there's 5 of your
patches queued up in x86.git this very moment [one of them is a subset
of the patch you mention above] and a few more in my mbox, but it does
mean that for a case like this, the newbie's change wins. And that
applies to my own changes just as much : often a newbie submits a
cleanup that i have done already but i'll put in the newbie's patch and
drop mine.
Ingo
next prev parent reply other threads:[~2008-04-28 15:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-27 23:15 x86: fix a couple of sparse warnings Dmitri Vorobiev
2008-04-27 23:15 ` [PATCH 1/2] x86: iommu_sac_force can become static Dmitri Vorobiev
2008-04-27 23:15 ` [PATCH 2/2] x86: add proper header for reboot_force Dmitri Vorobiev
2008-04-28 12:38 ` x86: fix a couple of sparse warnings Ingo Molnar
2008-04-28 13:37 ` Adrian Bunk
2008-04-28 13:43 ` Dmitri Vorobiev
2008-04-28 13:59 ` Adrian Bunk
2008-04-28 15:01 ` Ingo Molnar [this message]
2008-04-28 18:56 ` Adrian Bunk
2008-04-28 19:13 ` Sam Ravnborg
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=20080428150156.GA7412@elte.hu \
--to=mingo@elte.hu \
--cc=bunk@kernel.org \
--cc=dmitri.vorobiev@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=viro@ftp.linux.org.uk \
/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