From: Johan Hovold <johan@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Tilman Schmidt <tilman@imap.cc>, Johan Hovold <johan@kernel.org>,
Sasha Levin <sashal@kernel.org>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Hansjoerg Lipp <hjlipp@web.de>,
stable@vger.kernel.org
Subject: Re: [PATCH 1/4] staging: gigaset: fix general protection fault on probe
Date: Sun, 1 Dec 2019 14:04:37 +0100 [thread overview]
Message-ID: <20191201130437.GB23996@localhost> (raw)
In-Reply-To: <20191201124156.GA3836284@kroah.com>
On Sun, Dec 01, 2019 at 01:41:56PM +0100, Greg Kroah-Hartman wrote:
> 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.
I'll be sending a v2 of this series shortly. Somehow I managed to
overlook usb_endpoint_is_bulk_in() and friends so patch 4/4 should no
longer be needed either.
Johan
next prev parent reply other threads:[~2019-12-01 13:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191129101753.9721-1-johan@kernel.org>
2019-11-29 10:17 ` [PATCH 1/4] staging: gigaset: fix general protection fault on probe Johan Hovold
[not found] ` <20191201001505.964E72075A@mail.kernel.org>
2019-12-01 12:30 ` Tilman Schmidt
2019-12-01 12:41 ` Greg Kroah-Hartman
2019-12-01 13:04 ` Johan Hovold [this message]
2019-11-29 10:17 ` [PATCH 2/4] staging: gigaset: fix illegal free on probe errors Johan Hovold
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191201130437.GB23996@localhost \
--to=johan@kernel.org \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=hjlipp@web.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tilman@imap.cc \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).