From: Timur Tabi <timur@freescale.com>
To: Richard Cochran <richardcochran@gmail.com>
Cc: Paul Gortmaker <paul.gortmaker@windriver.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Wei Yang <Wei.Yang@windriver.com>,
Manoil Claudiu-B08782 <B08782@freescale.com>
Subject: Re: [PATCH] gianfar_ptp: use iomem, not ioports resource tree in probe
Date: Thu, 25 Oct 2012 15:17:48 -0500 [thread overview]
Message-ID: <50899E6C.8040403@freescale.com> (raw)
In-Reply-To: <20121025200853.GA6151@netboy.at.omicron.at>
Richard Cochran wrote:
> Getting back to your really ignorant comment, I suggest that you look
> at this review. It was made by Grant Likely. Perhaps you have heard of
> him?
>
> https://lkml.org/lkml/2011/2/23/281
>
> I was the original developer of the PTP code, and my code went through
> fifteen rounds of review. And guess what - I actually listened to the
> reviewer's comments and changed my work accordingly.
I'm sorry for what I said. It was inappropriate. I deal with crappy code
from co-workers on a daily basis, and sometimes I forgot that just because
something is done differently than I would have done it, that doesn't mean
it's wrong.
> You can read all about what happened, but you will have to find v15
> yourself. Be sure to pay special attention to the history of
> irq_of_parse_and_map() verses platform_get_irq().
I actually did that research and saw Grant's comments. I asked him about
it on IRC, and although I understand his reasoning, I'm not sure I agree
with all of it. In particular, I think
platform_get_resource/request_resource/ioremap is less elegant than just
calling of_iomap.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2012-10-25 20:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 15:21 [PATCH] gianfar_ptp: use iomem, not ioports resource tree in probe Paul Gortmaker
2012-10-24 17:59 ` Tabi Timur-B04825
2012-10-24 19:09 ` Paul Gortmaker
2012-10-24 19:12 ` Timur Tabi
2012-10-24 19:42 ` Richard Cochran
2012-10-24 20:11 ` Timur Tabi
2012-10-24 20:50 ` Richard Cochran
2012-10-25 11:41 ` wyang1
2012-10-25 20:08 ` Richard Cochran
2012-10-25 20:17 ` Timur Tabi [this message]
2012-10-26 10:32 ` Richard Cochran
2012-10-25 3:19 ` David Miller
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=50899E6C.8040403@freescale.com \
--to=timur@freescale.com \
--cc=B08782@freescale.com \
--cc=Wei.Yang@windriver.com \
--cc=netdev@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=richardcochran@gmail.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 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.