linux-kernel - Re: [PATCH 1/4] staging: gigaset: fix general protection fault on probe

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20191201124156.GA3836284@kroah.com>
Date:   Sun, 1 Dec 2019 13:41:56 +0100
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Tilman Schmidt <tilman@...p.cc>
Cc:     Johan Hovold <johan@...nel.org>, Sasha Levin <sashal@...nel.org>,
        devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org,
        Hansjoerg Lipp <hjlipp@....de>, stable@...r.kernel.org
Subject: Re: [PATCH 1/4] staging: gigaset: fix general protection fault on
 probe

On Sun, Dec 01, 2019 at 01:30:42PM +0100, Tilman Schmidt wrote:
> Hi Johan,
> 
> this is probably caused by the move of the driver to staging in
> kernel release 5.3 half a year ago. If you want your patches to
> apply to pre-5.3 stable releases you'll have to submit a version
> with the paths changed from drivers/staging/isdn/gigaset to
> drivers/isdn/gigaset.

That's trivial for me to do when they get added to the stable tree(s),
no need to worry about it.

thanks,

greg k-h