All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Karoly Pados <pados@pados.hu>
Cc: Johan Hovold <johan@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [v2] USB: serial: cp210x: Implement GPIO support for CP2102N
Date: Fri, 20 Jul 2018 12:16:29 +0200	[thread overview]
Message-ID: <20180720101629.GB19245@localhost> (raw)

On Wed, Jul 18, 2018 at 09:38:12PM +0000, Karoly Pados wrote:
> Hello Johan,
> 
> I hope maybe after you come back from your vacation you can still
> merge this into 4.19, I guess the merge window will still be open.

You shouldn't make assumptions about peoples vacation plans. ;)

> Given that there are
> about another 5 weeks until 4.19rc1 merge window closes,
> I didn't think I'd be late with this patch, I am sorry.

New code must be ready and reviewed well in time before the merge window
*opens*. So generally you cannot expect anything you post this week to
be included in 4.19.

> However, as already explained to you, it'd be very important
> for me to get this patch at least into 4.19, as otherwise the
> time I loose is much greater than a single release cycle (due
> to distro cycles), and I have actually a crowdfunding product
> depending on this.

I know, and I already cut some corners for you with the baud-rate
handling changes even though this is strictly not a valid reason to
change the normal procedures.

That being said, I took a look at your gpio patch today and as it looks
like you've addressed the major concerns with v1, and done so in a clean
way, I'll make an exception.

I'll post some review comments, but I've already fixed up the patch
myself. It's mostly style issues, but I did also find two bugs.

I do need you to respin the commit message, though; a commit message
should be self-contained and not rely on external discussions to make
sense (you can of course still refer/link to it). Patch-revision info
should generally go below the cut-off line, unless it is useful to have
it recorded.

Can you post a reworked commit message today so I can include this in my
4.19 updates?

Thanks,
Johan
---
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Johan Hovold <johan@kernel.org>
To: Karoly Pados <pados@pados.hu>
Cc: Johan Hovold <johan@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] USB: serial: cp210x: Implement GPIO support for CP2102N
Date: Fri, 20 Jul 2018 12:16:29 +0200	[thread overview]
Message-ID: <20180720101629.GB19245@localhost> (raw)
In-Reply-To: <ea05b80064d32c7beef3f2039adb89aa@pados.hu>

On Wed, Jul 18, 2018 at 09:38:12PM +0000, Karoly Pados wrote:
> Hello Johan,
> 
> I hope maybe after you come back from your vacation you can still
> merge this into 4.19, I guess the merge window will still be open.

You shouldn't make assumptions about peoples vacation plans. ;)

> Given that there are
> about another 5 weeks until 4.19rc1 merge window closes,
> I didn't think I'd be late with this patch, I am sorry.

New code must be ready and reviewed well in time before the merge window
*opens*. So generally you cannot expect anything you post this week to
be included in 4.19.

> However, as already explained to you, it'd be very important
> for me to get this patch at least into 4.19, as otherwise the
> time I loose is much greater than a single release cycle (due
> to distro cycles), and I have actually a crowdfunding product
> depending on this.

I know, and I already cut some corners for you with the baud-rate
handling changes even though this is strictly not a valid reason to
change the normal procedures.

That being said, I took a look at your gpio patch today and as it looks
like you've addressed the major concerns with v1, and done so in a clean
way, I'll make an exception.

I'll post some review comments, but I've already fixed up the patch
myself. It's mostly style issues, but I did also find two bugs.

I do need you to respin the commit message, though; a commit message
should be self-contained and not rely on external discussions to make
sense (you can of course still refer/link to it). Patch-revision info
should generally go below the cut-off line, unless it is useful to have
it recorded.

Can you post a reworked commit message today so I can include this in my
4.19 updates?

Thanks,
Johan

             reply	other threads:[~2018-07-20 10:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-20 10:16 Johan Hovold [this message]
2018-07-20 10:16 ` [PATCH v2] USB: serial: cp210x: Implement GPIO support for CP2102N Johan Hovold
  -- strict thread matches above, loose matches on Subject: below --
2018-07-20 16:58 [v2] " Johan Hovold
2018-07-20 16:58 ` [PATCH v2] " Johan Hovold
2018-07-20 12:43 [v2] " Karoly Pados
2018-07-20 12:43 ` [PATCH v2] " Karoly Pados
2018-07-20 10:44 [v2] " Johan Hovold
2018-07-20 10:44 ` [PATCH v2] " Johan Hovold
2018-07-18 21:38 [v2] " Karoly Pados
2018-07-18 21:38 ` [PATCH v2] " Karoly Pados
2018-07-18 21:20 [v2] " Karoly Pados
2018-07-18 21:20 ` [PATCH v2] " Karoly Pados

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=20180720101629.GB19245@localhost \
    --to=johan@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=pados@pados.hu \
    /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.