linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jonathan Olds" <jontio@i4free.co.nz>
To: "'Johan Hovold'" <johan@kernel.org>
Cc: <linux-usb@vger.kernel.org>, <frank@kingswood-consulting.co.uk>,
	<werner@cornelius-consult.de>, <boris@hajduk.org>
Subject: RE: [PATCH] USB: serial: ch341: fix wrong baud rate setting calculation
Date: Sat, 2 Nov 2019 08:18:27 +1300	[thread overview]
Message-ID: <001001d590e9$262004f0$72600ed0$@co.nz> (raw)
In-Reply-To: <20191101095725.GA3657@localhost>

Hi Johan,

> Thanks for testing. Do you mind if I add a tested-by tag for you to the
> patch?

Sure no problems. I tested it on a 64 bit I5 computer with the ch340g.
The Kernel was 5.0.0-32-generic.

> Not sure why that doesn't work, perhaps you just need to provide an
> appropriate "-p" option to strip the directory prefix?

I figured out the patching issue, my email client was removing some
line breaks.

> I suggest you use git directly instead. Clone Linus's repo at
> kernel.org, or use mine
> 
> 	git://git.kernel.org/pub/scm/linux/kernel/git/johan/usb-serial.git
> 
> to get the latest USB serial changes.
> 
> Then you can apply patches directly from a mailbox using git-am (or from
> a patch using git-apply).

Thanks, will do. I didn't know about the git-am and git-apply commands.

Cheers,
Jonti


  reply	other threads:[~2019-11-01 19:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-08  5:13 [PATCH] USB: serial: ch341: fix wrong baud rate setting calculation jontio
2019-06-20 13:43 ` Johan Hovold
2019-06-29  0:05   ` Jonathan Olds
2019-10-29 19:18     ` Jonathan Olds
2019-10-30  9:47       ` Johan Hovold
2019-11-01  0:17         ` Jonathan Olds
2019-11-01  9:57           ` Johan Hovold
2019-11-01 19:18             ` Jonathan Olds [this message]
2019-11-01  9:25 Michael Dreher
2019-11-01 14:20 ` 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='001001d590e9$262004f0$72600ed0$@co.nz' \
    --to=jontio@i4free.co.nz \
    --cc=boris@hajduk.org \
    --cc=frank@kingswood-consulting.co.uk \
    --cc=johan@kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=werner@cornelius-consult.de \
    /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).