linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: balbi@ti.com (Felipe Balbi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] s3c2410_udc: fix custom UDC command handling
Date: Mon, 20 Jun 2011 19:06:51 +0300	[thread overview]
Message-ID: <20110620160650.GA26623@legolas.emea.dhcp.ti.com> (raw)
In-Reply-To: <BANLkTi=tuh028X-Rr9i8ZF_B_Q6VBK2-Lw@mail.gmail.com>

Hi,

On Mon, Jun 20, 2011 at 05:57:31PM +0200, Skacore Systems wrote:
> Oh and I've finally cloned the mainline git. So here it's the last
> try. I hope the TI people will not sabotage the Samsung's drivers any
> way longer !!!

Now you're just making an ass of yourself.

what do you think you will get making such kind of statements ? I just
happen to be hired by TI, there's no such thing as TI trying to sabotage
Samsung's drivers.

I'll fix this one out myself just to make you stop bothering me, but
don't expect me to put your patches in my priority list. If you really
think TI is sabotaging samsung's drivers, look at the big re-factor we
are doing on the entire Gadget framework, involving not only Samsung's
drivers but all the others.

Even though you cloned the tree you still make a mistake which will
prevent me from applying the patch without manually editting it.

On top of that, you decided not to follow our netiquette or our patch
formatting rules just because you think it's "nonsense". If you really
think that, why do you even bother sending the patch to this mailing
list ?

> diff --git a/drivers/usb/gadget/s3c2410_udc.c b/drivers/usb/gadget/s3c2410_udc.c
> index 100f263..b6e1ca5 100644
> --- a/drivers/usb/gadget/s3c2410_udc.c
> +++ b/drivers/usb/gadget/s3c2410_udc.c
> @@ -1567,7 +1567,7 @@ static void s3c2410_udc_command(enum
> s3c2410_udc_cmd_e cmd)

there shouldn't be this line break here.

>                 return;
> 
>         if (udc_info->udc_command) {
> -               udc_info->udc_command(S3C2410_UDC_P_DISABLE);
> +               udc_info->udc_command(cmd);
>         } else if (gpio_is_valid(udc_info->pullup_pin)) {
>                 int value;

tabs where converted into spaces too.

Next time, instead of been such an ass, spend some time learning the
process we use to do development. You'll see things will go smoother.

-- 
balbi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 490 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20110620/8cd60a22/attachment.sig>

  reply	other threads:[~2011-06-20 16:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-16  8:04 [PATCH] s3c2410_udc: fix custom UDC command handling 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
2011-06-20 15:48           ` Skacore Systems
2011-06-20 15:57             ` Skacore Systems
2011-06-20 16:06               ` Felipe Balbi [this message]
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=20110620160650.GA26623@legolas.emea.dhcp.ti.com \
    --to=balbi@ti.com \
    --cc=linux-arm-kernel@lists.infradead.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 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).