From: Felipe Balbi <balbi@ti.com>
To: Skacore Systems <skacore.systems@gmail.com>
Cc: balbi@ti.com, Alan Stern <stern@rowland.harvard.edu>,
Viliam Mateicka <viliam.mateicka@gmail.com>,
Ben Dooks <ben-linux@fluff.org>,
Kukjin Kim <kgene.kim@samsung.com>,
David Brownell <dbrownell@users.sourceforge.net>,
Greg Kroah-Hartman <gregkh@suse.de>,
linux-arm-kernel@lists.infradead.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] s3c2410_udc: fix custom UDC command handling
Date: Mon, 20 Jun 2011 18:36:47 +0300 [thread overview]
Message-ID: <20110620153645.GQ14262@legolas.emea.dhcp.ti.com> (raw)
In-Reply-To: <BANLkTi=5S6bWs3jr9hTsg2=LXh4xKAprUA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2116 bytes --]
Hi,
On Mon, Jun 20, 2011 at 05:20:02PM +0200, Skacore Systems wrote:
> I've been exactly following
> http://www.kernel.org/doc/Documentation/SubmittingPatches:
>
> To create a patch for a single file, it is often sufficient to do:
>
> SRCTREE= linux-2.6
> MYFILE= drivers/net/mydriver.c
>
> cd $SRCTREE
> cp $MYFILE $MYFILE.orig
> vi $MYFILE # make your change
> cd ..
> diff -up $SRCTREE/$MYFILE{.orig,} > /tmp/patch
>
> And that's what I've done. What do you think is wrong with it ???
patch should be in 'p1' format to start with, not 'p0'!!
Your commit log shouldn't include your "regards" or anything like that,
or that will go into the git history.
> Subject: [PATCH] s3c2410_udc: fix custom UDC command handling
this should be something like:
[PATCH] usb: gadget: s3c2410_udc: fix custom UDC command handling
we generally put the subsystem on the subject to help maintainers
filter patches related to them.
> There is a bug in Samsung's UDC driver, which is completely disabling
> the USB device when a custom UDC command is used.
> Following patch seems to get the right?behavior (e.g. enabling pull-up
> instead of disabling then Vcc is applied).
"seems to get the right behavior" makes me wonder if you really tested
this properly. Either it fixes the problem, or it doesn't. Have you
tried with other possible commands to see if also helps ?
> Also I'm not in mailing list so please CC me.
this would go to commit log, shouldn't be here.
> Greetingz,
> Vilo
this shouldn't be here either.
> Signed-off-by: Viliam Mateicka <viliam.mateicka@gmail.com>
there should be a tear line here. (---)
> --- drivers/usb/gadget/s3c2410_udc.c.orig ? ? ? 2011-05-19
> 06:06:34.000000000 +0200
this line break is bogus.
you could have looked at any mailing list archive for properly formatted
patches, but instead you chose to be unpolite with the persons who are
giving you a "service" free of charge.
At [1] you can find an example of a proper patch
[1] http://marc.info/?l=linux-usb&m=130833192703040&w=2
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2011-06-20 15:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-16 8:04 Viliam Mateicka
2011-06-20 8:25 ` Viliam Mateicka
2011-06-20 15:07 ` Alan Stern
2011-06-20 15:15 ` Felipe Balbi
2011-06-20 15:20 ` Skacore Systems
2011-06-20 15:36 ` Felipe Balbi [this message]
2011-06-20 15:48 ` Skacore Systems
2011-06-20 15:57 ` Skacore Systems
2011-06-20 16:06 ` Felipe Balbi
2011-06-20 16:41 ` Skacore Systems
2011-06-20 17:05 ` Felipe Balbi
2011-06-20 17:27 ` Viliam Mateicka
2011-06-20 17:34 ` Felipe Balbi
2011-06-20 19:05 ` Viliam Mateicka
2011-06-20 16:07 ` Jassi Brar
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=20110620153645.GQ14262@legolas.emea.dhcp.ti.com \
--to=balbi@ti.com \
--cc=ben-linux@fluff.org \
--cc=dbrownell@users.sourceforge.net \
--cc=gregkh@suse.de \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=skacore.systems@gmail.com \
--cc=stern@rowland.harvard.edu \
--cc=viliam.mateicka@gmail.com \
/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
all inboxes | Powered by JetHome®