linux-kernel - Re: [git pull] habanalabs fixes for 5.2-rc1/2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAFCwf11-8f9jvTQd41K5=72AL49eB2NysZexBfhhDOmfGkttwA@mail.gmail.com>
Date:   Fri, 24 May 2019 22:44:58 +0300
From:   Oded Gabbay <oded.gabbay@...il.com>
To:     Greg KH <gregkh@...uxfoundation.org>
Cc:     "Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>
Subject: Re: [git pull] habanalabs fixes for 5.2-rc1/2

On Fri, May 24, 2019 at 9:36 PM Greg KH <gregkh@...uxfoundation.org> wrote:
>
> On Sun, May 12, 2019 at 10:41:36PM +0300, Oded Gabbay wrote:
> > Hi Greg,
> >
> > This is the pull request containing fixes for 5.2-rc1/2.
> >
> > It contains 2 fixes (1 of them for stable) and 1 change to a new IOCTL
> > that was introduced to kernel 5.2 in the previous pull requests.
> >
> > See the tag comment for more details.
> >
> > Thanks,
> > Oded
> >
> > The following changes since commit 8ea5b2abd07e2280a332bd9c1a7f4dd15b9b6c13:
> >
> >   Merge branch 'fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs (2019-05-09 19:35:41 -0700)
> >
> > are available in the Git repository at:
> >
> >   git://people.freedesktop.org/~gabbayo/linux tags/misc-habanalabs-fixes-2019-05-12
>
> Is this pull request still needed, or was it also part of the other one?
not needed, I've sent you a new one that includes this and I wrote it
in the pull request.

>
> How about fixing all of this by just sending patches?  :)
Starting of next week, all my team members are starting to send
patches individually upstream, and I really think the right way to go
is for me to apply them to my -next and -fixes branches and then I
will send it to you at the appropriate time and to the correct
branches.
I'm sorry for the confusion that was here (I sent the fixes pull too
early), but I assure you it won't happen again.
Oded

>
> thanks,
>
> greg k-h