Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1649686 > unrolled thread

Re: [PATCH v4 0/8] Fix issues and factorize arm/arm64 capacity information code

Started byJuri Lelli <juri.lelli@arm.com>
First post2017-05-24 16:50 +0200
Last post2017-05-25 15:40 +0200
Articles 3 — 2 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PATCH v4 0/8] Fix issues and factorize arm/arm64 capacity  information code Juri Lelli <juri.lelli@arm.com> - 2017-05-24 16:50 +0200
    Re: [PATCH v4 0/8] Fix issues and factorize arm/arm64 capacity  information code Greg KH <gregkh@linuxfoundation.org> - 2017-05-25 15:20 +0200
      Re: [PATCH v4 0/8] Fix issues and factorize arm/arm64 capacity  information code Juri Lelli <juri.lelli@arm.com> - 2017-05-25 15:40 +0200

#1649686 — Re: [PATCH v4 0/8] Fix issues and factorize arm/arm64 capacity information code

FromJuri Lelli <juri.lelli@arm.com>
Date2017-05-24 16:50 +0200
SubjectRe: [PATCH v4 0/8] Fix issues and factorize arm/arm64 capacity information code
Message-ID<tKFLR-3z2-35@gated-at.bofh.it>
Hi,

On 11/05/17 11:27, Juri Lelli wrote:
> On 11/05/17 10:59, Greg KH wrote:
> > On Thu, May 11, 2017 at 09:48:30AM +0100, Juri Lelli wrote:
> > > Hi Greg,
> > > 
> > > I'm not sure what your plans are with this set. Are we targeting 4.12?
> > > 
> > > IMHO, if possible, it would be good to have this refactoring in now, so
> > > that we can base further development on it for the next cycle.
> > 
> > It's way too late for new features that have not been in linux-next for
> > a few weeks, to get merged into 4.12-rc1, sorry.  I'll review this
> > patchset after -rc1 is out, and I get a chance to catch up on pending
> > patches.
> > 
> 
> Thanks for your reply, I perfecly understand.
> 
> OK, let's target 4.13 then. Looking forward to receive your comments
> after -rc1 is out.
> 

Did you have any chance to have a look at this set?

Thanks,

- Juri

[toc] | [next] | [standalone]


#1650493

FromGreg KH <gregkh@linuxfoundation.org>
Date2017-05-25 15:20 +0200
Message-ID<tL0Qi-fG-21@gated-at.bofh.it>
In reply to#1649686
On Wed, May 24, 2017 at 03:45:15PM +0100, Juri Lelli wrote:
> Hi,
> 
> On 11/05/17 11:27, Juri Lelli wrote:
> > On 11/05/17 10:59, Greg KH wrote:
> > > On Thu, May 11, 2017 at 09:48:30AM +0100, Juri Lelli wrote:
> > > > Hi Greg,
> > > > 
> > > > I'm not sure what your plans are with this set. Are we targeting 4.12?
> > > > 
> > > > IMHO, if possible, it would be good to have this refactoring in now, so
> > > > that we can base further development on it for the next cycle.
> > > 
> > > It's way too late for new features that have not been in linux-next for
> > > a few weeks, to get merged into 4.12-rc1, sorry.  I'll review this
> > > patchset after -rc1 is out, and I get a chance to catch up on pending
> > > patches.
> > > 
> > 
> > Thanks for your reply, I perfecly understand.
> > 
> > OK, let's target 4.13 then. Looking forward to receive your comments
> > after -rc1 is out.
> > 
> 
> Did you have any chance to have a look at this set?

Now reviewed.  Looks fine except for the final names in the last patch,
naming is hard, I know :)

thanks,

greg k-h

[toc] | [prev] | [next] | [standalone]


#1650513

FromJuri Lelli <juri.lelli@arm.com>
Date2017-05-25 15:40 +0200
Message-ID<tL19E-me-21@gated-at.bofh.it>
In reply to#1650493
On 25/05/17 15:18, Greg KH wrote:
> On Wed, May 24, 2017 at 03:45:15PM +0100, Juri Lelli wrote:
> > Hi,
> > 
> > On 11/05/17 11:27, Juri Lelli wrote:
> > > On 11/05/17 10:59, Greg KH wrote:
> > > > On Thu, May 11, 2017 at 09:48:30AM +0100, Juri Lelli wrote:
> > > > > Hi Greg,
> > > > > 
> > > > > I'm not sure what your plans are with this set. Are we targeting 4.12?
> > > > > 
> > > > > IMHO, if possible, it would be good to have this refactoring in now, so
> > > > > that we can base further development on it for the next cycle.
> > > > 
> > > > It's way too late for new features that have not been in linux-next for
> > > > a few weeks, to get merged into 4.12-rc1, sorry.  I'll review this
> > > > patchset after -rc1 is out, and I get a chance to catch up on pending
> > > > patches.
> > > > 
> > > 
> > > Thanks for your reply, I perfecly understand.
> > > 
> > > OK, let's target 4.13 then. Looking forward to receive your comments
> > > after -rc1 is out.
> > > 
> > 
> > Did you have any chance to have a look at this set?
> 
> Now reviewed.  Looks fine except for the final names in the last patch,
> naming is hard, I know :)
> 

Thanks!

Just skimmed through your comments on 8/8. I'll address them in the next
few days and post again.

Best,

- Juri

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web