From: Joe Perches <joe@perches.com>
To: Peter Senna Tschudin <peter.senna@collabora.com>
Cc: thomas@winischhofer.net, gregkh@linuxfoundation.org,
trivial@kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] usb-misc: cleanup sisusbvga
Date: Wed, 06 Jan 2016 08:04:35 -0800 [thread overview]
Message-ID: <1452096275.24575.9.camel@perches.com> (raw)
In-Reply-To: <20160106153005.GA3022@collabora.com>
On Wed, 2016-01-06 at 16:30 +0100, Peter Senna Tschudin wrote:
> is it ok to fix horizontal issues caused by vertical changes in the
> vertical changes patch?
Yes.
> Is it reasonable to respin if other issues are
> reported for this series?
Your choice.
I think it'd be better to respin in any case.
> > It's also nice to use objdiff and show no object changes.
> Nice tool. I didn't know about it. Should I create a README file for the
> scripts directory?
Maybe.
I think most script and patch submission documentation
is in Documentation/
Maybe this should be added to SubmittingPatches and/or
SubmitChecklist.
prev parent reply other threads:[~2016-01-06 16:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 16:54 [PATCH 0/5] usb-misc: cleanup sisusbvga Peter Senna Tschudin
2016-01-05 16:54 ` [PATCH 1/5] usb-misc: sisusbvga: Fix coding style: white space Peter Senna Tschudin
2016-01-05 16:54 ` [PATCH 2/5] usb-misc: sisusbvga: Fix trivial coding style Peter Senna Tschudin
2016-01-05 16:54 ` [PATCH 3/5] usb-misc: sisusbvga: Remove assignments from if tests Peter Senna Tschudin
2016-01-05 16:54 ` [PATCH 4/5] usb-misc: sisusbvga: Remove kmalloc logs and fix error path Peter Senna Tschudin
2016-01-06 18:28 ` Sergei Shtylyov
2016-01-07 15:19 ` Peter Senna Tschudin
2016-01-05 16:54 ` [PATCH 5/5] usb-misc: sisusbvga: Remove null test before kfree() Peter Senna Tschudin
2016-01-05 18:53 ` [PATCH 0/5] usb-misc: cleanup sisusbvga Joe Perches
2016-01-06 15:30 ` Peter Senna Tschudin
2016-01-06 16:04 ` Joe Perches [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=1452096275.24575.9.camel@perches.com \
--to=joe@perches.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=peter.senna@collabora.com \
--cc=thomas@winischhofer.net \
--cc=trivial@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.