From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Michal Kubecek <mkubecek@suse.cz>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH 4/4] parport: daisy: use new parport device model
Date: Mon, 11 Nov 2019 15:43:59 +0000 [thread overview]
Message-ID: <CADVatmMJgb1b5foOZeFres5ubk53H8Amy0_Mggo9obO0CTV0SA@mail.gmail.com> (raw)
In-Reply-To: <20191017211022.4247d821@gandalf.local.home>
Hi Greg,
On Fri, Oct 18, 2019 at 2:10 AM Steven Rostedt <rostedt@goodmis.org> wrote:
>
> On Wed, 16 Oct 2019 15:45:40 +0100
> Sudip Mukherjee <sudipm.mukherjee@gmail.com> wrote:
>
> > Modify parport daisy driver to use the new parallel port device model.
> >
> > Last attempt was '1aec4211204d ("parport: daisy: use new parport device
> > model")' which failed as daisy was also trying to load the low level
> > driver and that resulted in a deadlock.
> >
> > Cc: Michal Kubecek <mkubecek@suse.cz>
> > Cc: Steven Rostedt (VMware) <rostedt@goodmis.org>
> > Signed-off-by: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
> > ---
> >
> > Steven, Michal,
> > Can you please test this series in your test environment and verify that
> > I am not breaking anything this time.
> >
> >
>
> I checked out 1aec4211204d~1 (just before the broken commit), and
> applied these four patches. It booted with the config that wouldn't
> boot with the broken commit.
>
> Tested-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
A gentle ping on this series.
--
Regards
Sudip
prev parent reply other threads:[~2019-11-11 15:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 14:45 [PATCH 1/4] parport: daisy: avoid hardcoded name Sudip Mukherjee
2019-10-16 14:45 ` [PATCH 2/4] parport: do not check portlist when using device-model Sudip Mukherjee
2019-10-16 14:45 ` [PATCH 3/4] parport: load lowlevel driver if ports not found Sudip Mukherjee
2019-10-16 14:45 ` [PATCH 4/4] parport: daisy: use new parport device model Sudip Mukherjee
2019-10-18 1:10 ` Steven Rostedt
2019-11-11 15:43 ` Sudip Mukherjee [this message]
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=CADVatmMJgb1b5foOZeFres5ubk53H8Amy0_Mggo9obO0CTV0SA@mail.gmail.com \
--to=sudipm.mukherjee@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkubecek@suse.cz \
--cc=rostedt@goodmis.org \
/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).