public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Luben Tuikov <ltuikov@yahoo.com>
To: Matthew Wilcox <willy@linux.intel.com>
Cc: Greg KH <greg@kroah.com>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [USB] UAS: Rename urbs by pipe
Date: Mon, 8 Nov 2010 09:52:36 -0800 (PST)	[thread overview]
Message-ID: <732901.49803.qm@web31801.mail.mud.yahoo.com> (raw)

--- On Mon, 11/8/10, Luben Tuikov <ltuikov@yahoo.com> wrote:
> --- On Mon, 11/8/10, Matthew Wilcox
> <willy@linux.intel.com>
> wrote:
> > -0700, Luben Tuikov wrote:
> > > The reason to do this is to accommodate sending
> > > different IU types using the existing
> > > infrastructure.
> > 
> > Applied, with a modified changelog entry ...
> 
> Again, where is it applied and what is the (new) modified
> changelog entry? Why would you leave this detail out in your
> response to the patch?

Please have some professional integrity and EITHER a) ask me to
resubmit the patch with a new change log (what would you like?) or b) discuss it here publicly.

See my previous post on your other modification of the change log
to my other patch against your code.

> 
> > 
> > >      struct urb *data_out_urb;
> > >      struct list_head list;
> > >  };
> > >  
> > > -/* I hate forward declarations, but I actually
> have a
> > loop */
> > >  static int uas_submit_urbs(struct scsi_cmnd
> > *cmnd,
> > >         
> >         struct uas_dev_info
> > *devinfo, gfp_t gfp);
> > >  
> > 
> > Except for this spurious chunk.
> 
> Sorry, please help us understand: You'll LEAVE a
> self-gratifying, narcissistic and pompous statement like "I
> hate forward-declarations"? Why would you use such a strong
> word? Why would you "hate"? How about: "I don't like" or "I
> know lk style discourages", etc. Why would you add /one
> more/ "hate" word into the kernel?
> 
> I think everyone sees why this forward-decl is needed.
> 
> I wonder if the relation of the number of the "hate" word
> in the linux kernel versus time correlates to something,
> anything? Now that's easier to track and analyze in time
> using git.
> 
> Compared to people losing their homes and jobs nowadays,
> I'll take a forward declaration any time of day and night.
> 
> Bottom line: please consider the patch as is.
> 
> 

             reply	other threads:[~2010-11-08 17:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-08 17:52 Luben Tuikov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-12-10 10:50 [PATCH] [USB] UAS: Rename urbs by pipe Luben Tuikov
2010-10-28 20:05 Luben Tuikov
2010-10-28 20:41 ` Greg KH
2010-10-28 21:43   ` Luben Tuikov
2010-11-08 11:22 ` Matthew Wilcox
2010-11-08 17:17   ` Luben Tuikov
2010-12-01  1:07 ` Greg KH
2010-12-02 21:40   ` Matthew Wilcox
2010-12-02 22:26     ` Luben Tuikov
2010-12-03  0:07       ` Greg KH

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=732901.49803.qm@web31801.mail.mud.yahoo.com \
    --to=ltuikov@yahoo.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=willy@linux.intel.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