All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Connor Kuehl <connor.kuehl@canonical.com>
Cc: devel@driverdev.osuosl.org, gregkh@linuxfoundation.org,
	kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
	Larry.Finger@lwfinger.net
Subject: Re: NACK: [PATCH] staging: rtl8188eu: remove dead code in do-while conditional step
Date: Tue, 24 Sep 2019 15:25:15 +0000	[thread overview]
Message-ID: <20190924152515.GD29696@kadam> (raw)
In-Reply-To: <52e473f0-6b92-9504-b86e-a73a0d82617f@canonical.com>

This email is fine, but I just want to make sure that you don't think
it's required.  We all assumed that you would send a v2.  I sort of hate
the word NACK as well because it sounds like shouting or ducks and those
are my two pet peeves.

Sometimes  people send a v2 patch without any replies to the original
email and we apply the v1 patch that's the only thing to avoid.

regards,
dan carpenter

WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Connor Kuehl <connor.kuehl@canonical.com>
Cc: Larry.Finger@lwfinger.net, gregkh@linuxfoundation.org,
	straube.linux@gmail.com, devel@driverdev.osuosl.org,
	kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: NACK: [PATCH] staging: rtl8188eu: remove dead code in do-while conditional step
Date: Tue, 24 Sep 2019 18:25:15 +0300	[thread overview]
Message-ID: <20190924152515.GD29696@kadam> (raw)
In-Reply-To: <52e473f0-6b92-9504-b86e-a73a0d82617f@canonical.com>

This email is fine, but I just want to make sure that you don't think
it's required.  We all assumed that you would send a v2.  I sort of hate
the word NACK as well because it sounds like shouting or ducks and those
are my two pet peeves.

Sometimes  people send a v2 patch without any replies to the original
email and we apply the v1 patch that's the only thing to avoid.

regards,
dan carpenter


  reply	other threads:[~2019-09-24 15:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-23 19:48 [PATCH] staging: rtl8188eu: remove dead code in do-while conditional step Connor Kuehl
2019-09-23 19:48 ` Connor Kuehl
2019-09-23 20:38 ` Larry Finger
2019-09-23 20:38   ` Larry Finger
2019-09-23 20:49   ` Connor Kuehl
2019-09-23 20:49     ` Connor Kuehl
2019-09-24  6:17   ` Dan Carpenter
2019-09-24  6:17     ` Dan Carpenter
2019-09-24  6:15 ` Dan Carpenter
2019-09-24  6:15   ` Dan Carpenter
2019-09-24 14:25 ` NACK: " Connor Kuehl
2019-09-24 14:25   ` Connor Kuehl
2019-09-24 15:25   ` Dan Carpenter [this message]
2019-09-24 15:25     ` Dan Carpenter

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=20190924152515.GD29696@kadam \
    --to=dan.carpenter@oracle.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=connor.kuehl@canonical.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.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.