From: "Bjørn Mork" <bjorn@mork.no>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Felipe Balbi <balbi@ti.com>,
Dongsheng Song <dongsheng.song@gmail.com>,
Greg KH <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org,
Linux ARM Kernel Mailing List
<linux-arm-kernel@lists.infradead.org>
Subject: Re: Linux 3.8.3
Date: Sun, 17 Mar 2013 21:10:42 +0100 [thread overview]
Message-ID: <87ip4p4wjh.fsf@nemi.mork.no> (raw)
In-Reply-To: <20130317195709.GC4977@n2100.arm.linux.org.uk> (Russell King's message of "Sun, 17 Mar 2013 19:57:10 +0000")
Russell King - ARM Linux <linux@arm.linux.org.uk> writes:
> Sigh.
>
> At times, I really don't know why I bother wasting my time commenting on
> patches if they just go and agree with them, and promptly ignore them.
> I pointed out what this should be:
>
> http://marc.info/?l=linux-kernel&m=135972750522902&w=2
>
> And it was agreed:
>
> http://marc.info/?l=linux-kernel&m=135993546317541&w=2
>
> But for some reason the wrong patch got merged:
>
> http://marc.info/?l=git-commits-head&m=136147889001219&w=2
>
> Maybe because it was "simpler" ? Don't know. But... well, we now know
> what the outcome of it was. Let's try a different technique. I'm going
> to say nothing of any real help and hopefully it will get fixed properly.
> Maybe that'll work.
To be fair, looking at the commitdate of that commit it was already in
Greg's tree when you commented on it. So the discussion you had would
have to be about a followup-fix to this, and not about that particular
patch.
Bjørn
next prev parent reply other threads:[~2013-03-17 20:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 18:47 Greg KH
2013-03-14 18:47 ` Greg KH
2013-03-17 14:00 ` Dongsheng Song
2013-03-17 14:05 ` Greg KH
2013-03-17 14:31 ` Dongsheng Song
2013-03-17 19:33 ` Felipe Balbi
2013-03-17 19:57 ` Russell King - ARM Linux
2013-03-17 20:10 ` Bjørn Mork [this message]
2013-03-18 2:51 ` Greg KH
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=87ip4p4wjh.fsf@nemi.mork.no \
--to=bjorn@mork.no \
--cc=balbi@ti.com \
--cc=dongsheng.song@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.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
all inboxes | Powered by JetHome®