All of lore.kernel.org
 help / color / mirror / Atom feed
From: Preeti U Murthy <preeti@linux.vnet.ibm.com>
To: Vaishali Thakkar <vthakkar1994@gmail.com>
Cc: Julia Lawall <julia.lawall@lip6.fr>, outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH v3 2/2] Staging: rtl8723au: Use put_unaligned_le16
Date: Fri, 20 Feb 2015 13:32:15 +0530	[thread overview]
Message-ID: <54E6EA07.2020603@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAK-LDbL70HbEiDNmE3A499dAvxP7JteJB9nvmEs_tMRePggT_g@mail.gmail.com>

On 02/20/2015 01:20 PM, Vaishali Thakkar wrote:
>>
>> Yes I would suggest that. I missed this. Additionally I would recommend
>> in this case to not prefix any version number to the cover letter.
>> Instead prefix the appropriate version numbers to the individual patches
>> mentioning the changes from the previous versions.
> 
> Ok. So, in next patch-series cover letter will not have any version number and
> both of these patches will have v4 as I already prefixed them as v3.
> And for this
> particular patch I should write that there is no v2 under signed off
> by line. Right??

1. No version number for the cover letter.
2. Retain [PATCH v3 1/2] Staging: rtl8188eu: Use put_unaligned_le16 as
v3 itself.
3. Change [PATCH v3 2/2] Staging: rtl8723au: Use put_unaligned_le16: to
v2. So it would be:
[PATCH v2 2/2] Staging: rtl8723au: Use put_unaligned_le16, since it has
undergone just one revision.

The reason I ask not to change the version numbers again is because
there is nothing that has significantly changed from the previous
versions. There will be a change only in the manner of sending patches.

So now the question is about how you indicate to the maintainer that the
fresh series that you will post now is the one to be picked up. Usually
under such circumstances we append RESEND to the patches.
So now you can resend the next version as mentioned in the points above
but with a RESEND tag to the cover letter and patches.

Something like: [RESEND PATCH 0/2] Staging: Use put_unaligned_le16.
The maintainer will thus know that this is the one to be picked up.

Regards
Preeti U Murthy


> 
>> Regards
>> Preeti U Murthy



  reply	other threads:[~2015-02-20  8:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-20  3:30 [PATCH v3 0/2] Staging: Use put_unaligned_le16 Vaishali Thakkar
2015-02-20  3:30 ` [PATCH v3 1/2] Staging: rtl8188eu: " Vaishali Thakkar
2015-02-20  7:24   ` [Outreachy kernel] " Preeti U Murthy
2015-02-20  7:26     ` Vaishali Thakkar
2015-02-20  3:31 ` [PATCH v3 2/2] Staging: rtl8723au: " Vaishali Thakkar
2015-02-20  7:17   ` [Outreachy kernel] " Julia Lawall
2015-02-20  7:24     ` Vaishali Thakkar
2015-02-20  7:38       ` Preeti U Murthy
2015-02-20  7:50         ` Vaishali Thakkar
2015-02-20  8:02           ` Preeti U Murthy [this message]
2015-02-20  8:27             ` Vaishali Thakkar
2015-02-20  7:25   ` Preeti U Murthy

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=54E6EA07.2020603@linux.vnet.ibm.com \
    --to=preeti@linux.vnet.ibm.com \
    --cc=julia.lawall@lip6.fr \
    --cc=outreachy-kernel@googlegroups.com \
    --cc=vthakkar1994@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 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.