From: Ingo Molnar <mingo@elte•hu>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org
Subject: Re: linux-next: ftrace tree build failure
Date: Fri, 2 Jan 2009 12:16:39 +0100 [thread overview]
Message-ID: <20090102111639.GB20172@elte.hu> (raw)
In-Reply-To: <20090102212242.13f9007e.sfr@canb.auug.org.au>
* Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> Hi Ingo,
>
> On Fri, 2 Jan 2009 10:14:56 +0100 Ingo Molnar <mingo@elte•hu> wrote:
> >
> > this has been fixed already a few days ago (if you google for the build
> > failure string it will send you straight to the fix patch) - i just didnt
> > push it out to the -next branches yet during the hollidays. (did that now)
>
> Thanks.
>
> > Generally if you see a problem with our trees you can check whether an
> > issue is still present in tip/master:
> >
> > http://people.redhat.com/mingo/tip.git/README
>
> I'll try to remember ...
>
> [I wish you had stopped there]
>
> > before duplicating fixing effort and reporting it as a genuine issue -
>
> It broke a linux-next build - just how genuine does an issue have to be?
as genuine i mean 'new, unknown issue' - not an issue that has been
reported to lkml already by testers and has been fixed already.
The thing is, i wouldnt have said that had you not said:
> > [...] A bit more care, please.
i can do without such suggestions in the merge window really - it looked
rather condescending to me. A lkml search or a trivial google for the
build failure pattern would have given you a working patch.
Ingo
next prev parent reply other threads:[~2009-01-02 11:16 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-02 9:07 linux-next: ftrace tree build failure Stephen Rothwell
2009-01-02 9:14 ` Ingo Molnar
2009-01-02 10:22 ` Stephen Rothwell
2009-01-02 11:16 ` Ingo Molnar [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-07 0:53 Stephen Rothwell
2009-01-07 9:55 ` Ingo Molnar
2009-01-07 21:20 ` Stephen Rothwell
2008-11-25 3:21 Stephen Rothwell
2008-11-25 3:48 ` Steven Rostedt
2008-11-25 4:13 ` Stephen Rothwell
2008-11-25 4:31 ` Steven Rostedt
2008-11-25 5:09 ` Stephen Rothwell
2008-11-25 5:44 ` Steven Rostedt
2008-11-25 6:57 ` Stephen Rothwell
2008-11-25 7:14 ` Ingo Molnar
2008-11-25 7:26 ` Stephen Rothwell
2008-11-25 5:24 ` Steven Rostedt
2008-11-25 3:07 Stephen Rothwell
2008-11-25 3:21 ` Steven Rostedt
2008-11-25 7:28 ` Ingo Molnar
2008-11-25 7:43 ` Stephen Rothwell
2008-11-25 8:04 ` Ingo Molnar
2008-11-25 14:57 ` John W. Linville
2008-11-25 18:46 ` Luis R. Rodriguez
2008-11-26 0:08 ` Stephen Rothwell
2008-11-26 0:14 ` Luis R. Rodriguez
2008-08-25 3:08 Stephen Rothwell
2008-08-25 6:05 ` Ingo Molnar
2008-08-25 6:11 ` Ingo Molnar
2008-08-25 6:31 ` Stephen Rothwell
2008-08-25 3:01 Stephen Rothwell
2008-08-25 6:09 ` Ingo Molnar
2008-08-25 16:42 ` Steven Rostedt
2008-08-25 16:46 ` Steven Rostedt
2008-08-15 2:27 Stephen Rothwell
2008-08-15 7:56 ` Ingo Molnar
2008-08-15 8:29 ` Stephen Rothwell
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=20090102111639.GB20172@elte.hu \
--to=mingo@elte$(echo .)hu \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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