On Thu, 25 Feb 2016 09:05:34 -0700
Troy Kisky wrote:
> On 2/24/2016 7:52 PM, Joshua Clayton wrote:
> > Hello Troy,
> > I'm replying here instead of to a particular commit because several
> > of the commit messages seem inadequate.
> >
> > The first line summaries all look good.
> >
> > The desc
On 2/24/2016 7:52 PM, Joshua Clayton wrote:
> Hello Troy,
> I'm replying here instead of to a particular commit because several of
> the commit messages seem inadequate.
>
> The first line summaries all look good.
>
> The descriptions should each also include the "user visible impact" of
> the pa
On 2/25/2016 1:39 AM, Holger Schurig wrote:
> Hi Troy,
>
> what is the general aim of your patches? Stability? Speed? Cleanup?
>
1. Stability
2. performance
3. easier to read
4. more debug info
The 2nd goal is very hard to measure. It seems function alignment changes swamp
most any other im
Hi Troy,
what is the general aim of your patches? Stability? Speed? Cleanup?
Hello Troy,
I'm replying here instead of to a particular commit because several of
the commit messages seem inadequate.
The first line summaries all look good.
The descriptions should each also include the "user visible impact" of
the patch and the justification for it (i.e. why you made the chan
V2 is a rebase on top of johannes endian-safe patch and
this set is only the next 16 patches.
The testing for this series was done on a nitrogen6x.
The base commit was
commit f5461c27631672b9e95282812ee521c53f502eca
Merge branch 'dsa-pass-bridge-to-drivers'
Testing showed no change in performa
