On 11/02/2015 11:16 PM, Greg Kroah-Hartman wrote:
> This too was something we discussed at the kernel summit, it's
> recommended that you just delete the drivers from where they are now, no
> need to move them to staging first.
So, don't take any more patches against them then. I'll delete them
On 11/04/2015 12:16 PM, Greg Kroah-Hartman wrote:
> On Wed, Nov 04, 2015 at 10:00:38AM -0500, Doug Ledford wrote:
>> On 11/02/2015 11:16 PM, Greg Kroah-Hartman wrote:
>>> This too was something we discussed at the kernel summit, it's
>>> recommended that you just delete the drivers from where they
On Wed, Nov 04, 2015 at 10:00:38AM -0500, Doug Ledford wrote:
> On 11/02/2015 11:16 PM, Greg Kroah-Hartman wrote:
> > This too was something we discussed at the kernel summit, it's
> > recommended that you just delete the drivers from where they are now, no
> > need to move them to staging first.
> On Nov 2, 2015, at 6:37 PM, Greg Kroah-Hartman
> wrote:
>
> On Mon, Nov 02, 2015 at 06:20:40PM -0500, Doug Ledford wrote:
>> 1) Aging, but working, drivers that will be removed in the future.
>> Since we no longer have a deprecation mechanism, I was informed that
On Mon, Nov 02, 2015 at 06:20:40PM -0500, Doug Ledford wrote:
> 1) Aging, but working, drivers that will be removed in the future.
> Since we no longer have a deprecation mechanism, I was informed that the
> normal procedure now is to move the driver to staging for a while and
> then remove it
On Mon, Nov 02, 2015 at 07:02:04PM -0500, Doug Ledford wrote:
> Because they are *scheduled* for removal. If I simply didn't care if
> they went away, then I wouldn't screw around with deprecating them or
> tagging them to be removed, I'd just delete them. Breaking them before
> the scheduled
On 11/01/2015 01:06 PM, Greg Kroah-Hartman wrote:
> On Sun, Nov 01, 2015 at 02:10:48PM +0200, Or Gerlitz wrote:
>> On 10/29/2015 1:51 PM, Christoph Hellwig wrote:
>>> On Wed, Oct 28, 2015 at 10:57:59PM -0400, Doug Ledford wrote:
>>> I had to do a minor hand merge to get this to apply, but it
On 11/02/2015 06:37 PM, Greg Kroah-Hartman wrote:
> On Mon, Nov 02, 2015 at 06:20:40PM -0500, Doug Ledford wrote:
>> 1) Aging, but working, drivers that will be removed in the future.
>> Since we no longer have a deprecation mechanism, I was informed that the
>> normal procedure now is to move the
On Mon, Nov 02, 2015 at 07:02:04PM -0500, Doug Ledford wrote:
> > so overall it still benifits being in the
> > staging tree, so a few minor breakages every once in a while should be
> > easy for you to fix up, _if_ they happen.
> >
> > Again, I don't know of any recent api change that has caused
On Mon, Nov 02, 2015 at 05:18:45PM -0700, Jason Gunthorpe wrote:
> On Mon, Nov 02, 2015 at 07:02:04PM -0500, Doug Ledford wrote:
>
> > Because they are *scheduled* for removal. If I simply didn't care if
> > they went away, then I wouldn't screw around with deprecating them or
> > tagging them
On 11/02/2015 07:18 PM, Jason Gunthorpe wrote:
> On Mon, Nov 02, 2015 at 07:02:04PM -0500, Doug Ledford wrote:
>
>> Because they are *scheduled* for removal. If I simply didn't care if
>> they went away, then I wouldn't screw around with deprecating them or
>> tagging them to be removed, I'd
On Mon, Nov 02, 2015 at 07:52:05PM -0500, Doug Ledford wrote:
> It shouldn't be. I reviewed those changes and they looked right (given
> the limitations). All you needed was to boot with nopat on the kernel
> command line to get the old kernel behavior and it would continue to
> work as before,
On Mon, Nov 02, 2015 at 09:03:35PM -0500, Doug Ledford wrote:
> On 11/02/2015 08:28 PM, Jason Gunthorpe wrote:
> > On Mon, Nov 02, 2015 at 07:52:05PM -0500, Doug Ledford wrote:
> >> It shouldn't be. I reviewed those changes and they looked right (given
> >> the limitations). All you needed was
On Mon, Nov 02, 2015 at 10:14:06PM -0500, Doug Ledford wrote:
> On 11/02/2015 07:49 PM, Greg Kroah-Hartman wrote:
> > On Mon, Nov 02, 2015 at 07:02:04PM -0500, Doug Ledford wrote:
> >>> so overall it still benifits being in the
> >>> staging tree, so a few minor breakages every once in a while
On Mon, Nov 02, 2015 at 09:03:35PM -0500, Doug Ledford wrote:
> No, one kernel consumer that never worked on iWARP before now works on a
> different iWARP controller but doesn't work on the old iWARP controller.
> Hardly the end of the world.
NFS is gone/going as well, and that used to work. No
On 11/02/2015 07:49 PM, Greg Kroah-Hartman wrote:
> On Mon, Nov 02, 2015 at 07:02:04PM -0500, Doug Ledford wrote:
>>> so overall it still benifits being in the
>>> staging tree, so a few minor breakages every once in a while should be
>>> easy for you to fix up, _if_ they happen.
>>>
>>> Again, I
On 10/29/2015 1:51 PM, Christoph Hellwig wrote:
On Wed, Oct 28, 2015 at 10:57:59PM -0400, Doug Ledford wrote:
> >I had to do a minor hand merge to get this to apply, but it has been
> >pulled in for 4.4.
>
>This breaks all of the drivers in staging BTW. That will need fixed up
>before the
On Sun, Nov 01, 2015 at 02:10:48PM +0200, Or Gerlitz wrote:
> On 10/29/2015 1:51 PM, Christoph Hellwig wrote:
> >On Wed, Oct 28, 2015 at 10:57:59PM -0400, Doug Ledford wrote:
> >I had to do a minor hand merge to get this to apply, but it has been
> >pulled in for 4.4.
> >>>
> >>>This
On Wed, Oct 28, 2015 at 10:57:59PM -0400, Doug Ledford wrote:
> > I had to do a minor hand merge to get this to apply, but it has been
> > pulled in for 4.4.
>
> This breaks all of the drivers in staging BTW. That will need fixed up
> before the pull request goes in during the merge window.
On 10/29/2015 07:51 AM, Christoph Hellwig wrote:
> On Wed, Oct 28, 2015 at 10:57:59PM -0400, Doug Ledford wrote:
>>> I had to do a minor hand merge to get this to apply, but it has been
>>> pulled in for 4.4.
>>
>> This breaks all of the drivers in staging BTW. That will need fixed up
>> before
On 10/28/2015 10:25 PM, Doug Ledford wrote:
> On 09/13/2015 11:13 AM, Christoph Hellwig wrote:
>> This series shrinks the WR size by splitting out the different WR
>> types.
>>
>> Patch number one is too large for the mailinglist, so if you didn't
>> get it grab it here:
>>
>>
>>
On 09/13/2015 11:13 AM, Christoph Hellwig wrote:
> This series shrinks the WR size by splitting out the different WR
> types.
>
> Patch number one is too large for the mailinglist, so if you didn't
> get it grab it here:
>
>
>
On Sun, Sep 13, 2015 at 05:13:33PM +0200, Christoph Hellwig wrote:
> This series shrinks the WR size by splitting out the different WR
> types.
>
> Patch number one is too large for the mailinglist, so if you didn't
> get it grab it here:
>
>
>
On 13/09/2015 18:13, Christoph Hellwig wrote:
> This series shrinks the WR size by splitting out the different WR
> types.
>
> Patch number one is too large for the mailinglist, so if you didn't
> get it grab it here:
>
>
>
24 matches
Mail list logo