public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@mvista.com>
To: Sarah Sharp <sarah.a.sharp@linux.intel.com>
Cc: Sergei Shtylyov <sshtylyov@mvista.com>,
	Takashi Iwai <tiwai@suse.de>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC 2/3] xhci: Fix cycle bit calculation during stall handling.
Date: Thu, 24 Feb 2011 22:22:03 +0300	[thread overview]
Message-ID: <4D66AFDB.5010005@ru.mvista.com> (raw)
In-Reply-To: <20110224153855.GA25590@xanatos>

Hello.

Sarah Sharp wrote:

>>> +	if (ep_ring->first_seg == ep_ring->first_seg->next&&
>>> +			state->new_deq_ptr < dev->eps[ep_index].stopped_trb)
>>> +			state->new_cycle_state ^= 0x1;

>>    The last line seems overindented.

> Hi Sergei,

> checkpatch.pl doesn't complain about it.  It is not a good use of my
> time to respin this patch for one stylistic change that is not a
> violation of the Kernel community norms.

> I really feel strongly that you are wasting the community's time by
> commenting on style when it is only a violation of your personal style,
> without providing any useful feedback on the code itself.

    Not only of my personal style, as Dmitry's comment has shown. Like him, I 
had some trouble seeing where the *if* expression ends and the branch starts, 
due to both lines starting on the same level of indentation...

> I feel so strongly that I'm seriously considering setting up a feedback
> bot for you.  It would run any patch you reply to through checkpatch.pl,
> and send you a small reminder when the patch passes, but you complained
> about style.  I think it would allow you to have a sense of how
> frustrating it is to receive these unnecessary stylistic comments.

    Well, I'll try to save you that trouble and avoid commenting on your patches 
in the future.

> Sarah Sharp

WBR, Sergei

      parent reply	other threads:[~2011-02-24 19:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1298514502.git.sarah.a.sharp@linux.intel.com>
     [not found] ` <e1b54e2b29b06b62174de33a74fa7469173abc92.1298514502.git.sarah.a.sharp@linux.intel.com>
     [not found]   ` <4D663E80.8050906@ru.mvista.com>
2011-02-24 15:38     ` [RFC 2/3] xhci: Fix cycle bit calculation during stall handling Sarah Sharp
2011-02-24 17:04       ` Greg KH
2011-02-24 18:35         ` Dmitry Torokhov
2011-02-24 19:22       ` Sergei Shtylyov [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=4D66AFDB.5010005@ru.mvista.com \
    --to=sshtylyov@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=sarah.a.sharp@linux.intel.com \
    --cc=tiwai@suse.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