From: Stephen Boyd <sboyd@codeaurora.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Ladislav Michl <ladis@linux-mips.org>,
Tero Kristo <t-kristo@ti.com>,
linux-omap@vger.kernel.org, linux-clk@vger.kernel.org,
Paul Walmsley <paul@pwsan.com>, Richard Watts <rrw@kynesim.co.uk>,
Tony Lindgren <tony@atomide.com>,
Alexander Kinzer <a.kinzer@plusoptix.de>,
Michael Turquette <mturquette@baylibre.com>
Subject: Re: [PATCH v3] clk: ti: omap36xx: Work around sprz319 advisory 2.1
Date: Thu, 8 Dec 2016 13:14:35 -0800 [thread overview]
Message-ID: <20161208211435.GJ5423@codeaurora.org> (raw)
In-Reply-To: <3225321.q72K2erxPs@avalon>
On 12/08, Laurent Pinchart wrote:
> Hi Ladislav,
>
> On Thursday 08 Dec 2016 08:11:55 Ladislav Michl wrote:
> > On Wed, Dec 07, 2016 at 04:16:54PM -0800, Stephen Boyd wrote:
> > > On 12/05, Tero Kristo wrote:
> > > > The compiler should ideally generate same size code for these both.
> > > > Personally, I don't mind which version goes in; I'd say both are as
> > > > readable.
> > > >
> > > > Stephen, Mike, is one of you going to pick this up? I don't think I
> > > > have anything else to pull due to the ongoing discussion with the
> > > > other pending stuff.
> > >
> > > I have no problem picking up either version. Please send it with
> > > the appropriate tags added and I can merge it.
> >
> > Here it is for your convenience. Of course I'd like to see smaller code
> > to go in as exactly those sneaky tiny incremental code size increases
> > made Linux kernel unusable on most of my hardware over time ;-)
> > However, if Laurent is unhappy with changes I made, I will not object
> > merging his version any more.
>
> I'd rather keep my version, thank you. Let's not spend time chasing bytes.
>
Ok so I'll go apply the original patch v3 in this thread and dig
out the tags myself.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2016-12-08 21:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 21:14 [PATCH v3] clk: ti: omap36xx: Work around sprz319 advisory 2.1 Laurent Pinchart
2016-12-02 22:41 ` Michael Turquette
2016-12-05 8:22 ` Ladislav Michl
2016-12-05 8:46 ` Laurent Pinchart
2016-12-05 9:36 ` Ladislav Michl
2016-12-05 11:08 ` Laurent Pinchart
2016-12-05 12:24 ` Tero Kristo
2016-12-08 0:16 ` Stephen Boyd
2016-12-08 7:11 ` Ladislav Michl
2016-12-08 11:40 ` Laurent Pinchart
2016-12-08 21:14 ` Stephen Boyd [this message]
2016-12-05 23:59 ` Laurent Pinchart
2016-12-07 16:34 ` Ladislav Michl
2016-12-08 21:16 ` Stephen Boyd
2016-12-08 21:24 ` Laurent Pinchart
2017-01-03 18:00 ` Adam Ford
2017-01-03 18:49 ` Stephen Boyd
2017-01-03 22:16 ` Laurent Pinchart
2017-01-04 12:59 ` Adam Ford
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=20161208211435.GJ5423@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=a.kinzer@plusoptix.de \
--cc=ladis@linux-mips.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=paul@pwsan.com \
--cc=rrw@kynesim.co.uk \
--cc=t-kristo@ti.com \
--cc=tony@atomide.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).