On 2015/3/4 2:59, Joseph Salisbury wrote:
> Hello,
>
> Please consider including mainline commit
> 4b552bc9edfdc947862af225a0e2521edb5d37a0 in the next 3.2.y, 3.4.y,
> 3.10.y, 3.12.y, 3.13.y-ckt, 3.14.y, 3.16.y-ckt and 3.18.y upstream
> stable releases. It was included in the mainline tree
On 2015/3/4 2:59, Joseph Salisbury wrote:
Hello,
Please consider including mainline commit
4b552bc9edfdc947862af225a0e2521edb5d37a0 in the next 3.2.y, 3.4.y,
3.10.y, 3.12.y, 3.13.y-ckt, 3.14.y, 3.16.y-ckt and 3.18.y upstream
stable releases. It was included in the mainline tree as of
On Mon, 2015-03-16 at 13:19 +, Ben Hutchings wrote:
> On Mon, 2015-03-16 at 13:41 +0100, Greg KH wrote:
> > On Tue, Mar 03, 2015 at 01:59:00PM -0500, Joseph Salisbury wrote:
> > > Hello,
> > >
> > > Please consider including mainline commit
> > > 4b552bc9edfdc947862af225a0e2521edb5d37a0
On Mon, 2015-03-16 at 13:19 +, Ben Hutchings wrote:
On Mon, 2015-03-16 at 13:41 +0100, Greg KH wrote:
On Tue, Mar 03, 2015 at 01:59:00PM -0500, Joseph Salisbury wrote:
Hello,
Please consider including mainline commit
4b552bc9edfdc947862af225a0e2521edb5d37a0 in the next
On Mon, Mar 16, 2015 at 01:19:53PM +, Ben Hutchings wrote:
> On Mon, 2015-03-16 at 13:41 +0100, Greg KH wrote:
> > On Tue, Mar 03, 2015 at 01:59:00PM -0500, Joseph Salisbury wrote:
> > > Hello,
> > >
> > > Please consider including mainline commit
> > >
On Mon, 2015-03-16 at 13:41 +0100, Greg KH wrote:
> On Tue, Mar 03, 2015 at 01:59:00PM -0500, Joseph Salisbury wrote:
> > Hello,
> >
> > Please consider including mainline commit
> > 4b552bc9edfdc947862af225a0e2521edb5d37a0 in the next 3.2.y, 3.4.y,
> > 3.10.y, 3.12.y, 3.13.y-ckt, 3.14.y,
On Tue, Mar 03, 2015 at 01:59:00PM -0500, Joseph Salisbury wrote:
> Hello,
>
> Please consider including mainline commit
> 4b552bc9edfdc947862af225a0e2521edb5d37a0 in the next 3.2.y, 3.4.y,
> 3.10.y, 3.12.y, 3.13.y-ckt, 3.14.y, 3.16.y-ckt and 3.18.y upstream
> stable releases. It was
On Mon, 2015-03-16 at 13:41 +0100, Greg KH wrote:
On Tue, Mar 03, 2015 at 01:59:00PM -0500, Joseph Salisbury wrote:
Hello,
Please consider including mainline commit
4b552bc9edfdc947862af225a0e2521edb5d37a0 in the next 3.2.y, 3.4.y,
3.10.y, 3.12.y, 3.13.y-ckt, 3.14.y, 3.16.y-ckt and
On Tue, Mar 03, 2015 at 01:59:00PM -0500, Joseph Salisbury wrote:
Hello,
Please consider including mainline commit
4b552bc9edfdc947862af225a0e2521edb5d37a0 in the next 3.2.y, 3.4.y,
3.10.y, 3.12.y, 3.13.y-ckt, 3.14.y, 3.16.y-ckt and 3.18.y upstream
stable releases. It was included in
On Mon, Mar 16, 2015 at 01:19:53PM +, Ben Hutchings wrote:
On Mon, 2015-03-16 at 13:41 +0100, Greg KH wrote:
On Tue, Mar 03, 2015 at 01:59:00PM -0500, Joseph Salisbury wrote:
Hello,
Please consider including mainline commit
4b552bc9edfdc947862af225a0e2521edb5d37a0 in the
On 03/03/2015, 07:59 PM, Joseph Salisbury wrote:
> Hello,
>
> Please consider including mainline commit
> 4b552bc9edfdc947862af225a0e2521edb5d37a0 in the next 3.2.y, 3.4.y,
> 3.10.y, 3.12.y, 3.13.y-ckt, 3.14.y, 3.16.y-ckt and 3.18.y upstream
Added to 3.12. Thanks.
--
js
suse labs
--
To
On 03/03/2015, 07:59 PM, Joseph Salisbury wrote:
Hello,
Please consider including mainline commit
4b552bc9edfdc947862af225a0e2521edb5d37a0 in the next 3.2.y, 3.4.y,
3.10.y, 3.12.y, 3.13.y-ckt, 3.14.y, 3.16.y-ckt and 3.18.y upstream
Added to 3.12. Thanks.
--
js
suse labs
--
To
On Tue, 2015-03-03 at 13:59 -0500, Joseph Salisbury wrote:
> Hello,
>
> Please consider including mainline commit
> 4b552bc9edfdc947862af225a0e2521edb5d37a0 in the next 3.2.y, 3.4.y,
> 3.10.y, 3.12.y, 3.13.y-ckt, 3.14.y, 3.16.y-ckt and 3.18.y upstream
> stable releases. It was included in
On 03/03/2015 01:59 PM, Joseph Salisbury wrote:
> Hello,
>
> Please consider including mainline commit
> 4b552bc9edfdc947862af225a0e2521edb5d37a0 in the next 3.2.y, 3.4.y,
> 3.10.y, 3.12.y, 3.13.y-ckt, 3.14.y, 3.16.y-ckt and 3.18.y upstream
> stable releases. It was included in the mainline
Hello,
Please consider including mainline commit
4b552bc9edfdc947862af225a0e2521edb5d37a0 in the next 3.2.y, 3.4.y,
3.10.y, 3.12.y, 3.13.y-ckt, 3.14.y, 3.16.y-ckt and 3.18.y upstream
stable releases. It was included in the mainline tree as of v3.19-rc1
but not cc'd to stable. It has been
Hello,
Please consider including mainline commit
4b552bc9edfdc947862af225a0e2521edb5d37a0 in the next 3.2.y, 3.4.y,
3.10.y, 3.12.y, 3.13.y-ckt, 3.14.y, 3.16.y-ckt and 3.18.y upstream
stable releases. It was included in the mainline tree as of v3.19-rc1
but not cc'd to stable. It has been
On 03/03/2015 01:59 PM, Joseph Salisbury wrote:
Hello,
Please consider including mainline commit
4b552bc9edfdc947862af225a0e2521edb5d37a0 in the next 3.2.y, 3.4.y,
3.10.y, 3.12.y, 3.13.y-ckt, 3.14.y, 3.16.y-ckt and 3.18.y upstream
stable releases. It was included in the mainline tree
On Tue, 2015-03-03 at 13:59 -0500, Joseph Salisbury wrote:
Hello,
Please consider including mainline commit
4b552bc9edfdc947862af225a0e2521edb5d37a0 in the next 3.2.y, 3.4.y,
3.10.y, 3.12.y, 3.13.y-ckt, 3.14.y, 3.16.y-ckt and 3.18.y upstream
stable releases. It was included in the
18 matches
Mail list logo