All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Johan Hovold <johan@kernel.org>
Cc: linux-usb@vger.kernel.org, Davidlohr Bueso <dave@stgolabs.net>,
	linux-kernel@vger.kernel.org, stable <stable@vger.kernel.org>
Subject: Re: [PATCH] USB: serial: mos7720: fix parallel-port state restore
Date: Wed, 4 Nov 2020 17:59:10 +0100	[thread overview]
Message-ID: <20201104165910.GA2342981@kroah.com> (raw)
In-Reply-To: <20201104164727.26351-1-johan@kernel.org>

On Wed, Nov 04, 2020 at 05:47:27PM +0100, Johan Hovold wrote:
> The parallel-port restore operations is called when a driver claims the
> port and is supposed to restore the provided state (e.g. saved when
> releasing the port).
> 
> Fixes: b69578df7e98 ("USB: usbserial: mos7720: add support for parallel port on moschip 7715")
> Cc: stable <stable@vger.kernel.org>     # 2.6.35
> Signed-off-by: Johan Hovold <johan@kernel.org>
> ---
>  drivers/usb/serial/mos7720.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/drivers/usb/serial/mos7720.c b/drivers/usb/serial/mos7720.c
> index 5eed1078fac8..5a5d2a95070e 100644
> --- a/drivers/usb/serial/mos7720.c
> +++ b/drivers/usb/serial/mos7720.c
> @@ -639,6 +639,8 @@ static void parport_mos7715_restore_state(struct parport *pp,
>  		spin_unlock(&release_lock);
>  		return;
>  	}
> +	mos_parport->shadowDCR = s->u.pc.ctr;
> +	mos_parport->shadowECR = s->u.pc.ecr;

Wow that's old code.  I'm guessing no one uses these devices really :(

Anyway, nice work:

Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

>  	write_parport_reg_nonblock(mos_parport, MOS7720_DCR,
>  				   mos_parport->shadowDCR);
>  	write_parport_reg_nonblock(mos_parport, MOS7720_ECR,
> -- 
> 2.26.2
> 

  reply	other threads:[~2020-11-04 16:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-04 16:47 [PATCH] USB: serial: mos7720: fix parallel-port state restore Johan Hovold
2020-11-04 16:59 ` Greg KH [this message]
2020-11-05  8:05   ` 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=20201104165910.GA2342981@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=dave@stgolabs.net \
    --cc=johan@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.