All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Brivio <sbrivio@redhat.com>
To: Kaaira Gupta <kgupta@es.iitr.ac.in>
Cc: jerome.pouiller@silabs.com,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH 0/6] Clean-ups in wfx driver
Date: Tue, 10 Mar 2020 20:30:32 +0100	[thread overview]
Message-ID: <20200310203032.3475fb07@elisabeth> (raw)
In-Reply-To: <20200310192431.GA1336@kaaira-HP-Pavilion-Notebook>

On Wed, 11 Mar 2020 00:54:31 +0530
Kaaira Gupta <kgupta@es.iitr.ac.in> wrote:

> On Tue, Mar 10, 2020 at 07:45:21PM +0100, Stefano Brivio wrote:
> > On Tue, 10 Mar 2020 23:43:02 +0530
> > Kaaira Gupta <kgupta@es.iitr.ac.in> wrote:
> >   
> > > On Tue, Mar 10, 2020 at 11:37:49PM +0530, Kaaira Gupta wrote:  
> > > > On Tue, Mar 10, 2020 at 06:40:33PM +0100, Stefano Brivio wrote:  
> > > >  
> > > > > And as you're posting this series for the second time, you should
> > > > > indicate this with v2 (check out the "--subject-prefix" option of git
> > > > > format-patch), and indicate the change history for these patches -- see
> > > > > other recent discussions on this list for examples of how it's done.    
> > > > 
> > > > Hey! No, I am not posting this series for the second time. As was
> > > > pointed out in my earlier patchset( which included 5/6 and 2/6 of this
> > > > patch set) that I have to create a patch set of related changes or
> > > > changes in the same driver, hence I sent this different patch set.    
> > > 
> > > THe previous patch set stands discarded, as it was not a proper set. I
> > > didn't even write a proper cover letter in that one :/  
> > 
> > Oh, right, I got confused by the fact that patch 2/6 here was 3/7 in
> > the non-series, and 5/6 was 4/7.
> > 
> > Now, at a second look, I see the series is very different, but see: if
> > you included a description of the differences for those two patches it
> > would have helped :)  
> 
> Yes, sorry I should have take care of this. I'll remember from now.
> 
> > 
> > I'll review this later. Thanks for the clarification.  
> 
> Should I correct the spellings and submit a v2? Or should I just take
> care from the next time?

I (personally) don't consider spelling mistakes very relevant in cover
letters: they don't end up in the git log, so they won't affect
later searches for specific words.

In general, I would recommend that you wait a bit (few hours to
few days, depending on how big/complicated the series is) before
re-posting: reviewers might need some time. So... give me/us time to
review this, first :)

-- 
Stefano



      reply	other threads:[~2020-03-10 19:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-10 14:25 [PATCH 0/6] Clean-ups in wfx driver Kaaira Gupta
2020-03-10 14:25 ` [PATCH 1/6] staging: wfx: data_rx.c: remove space after cast Kaaira Gupta
2020-03-10 14:25 ` [PATCH 2/6] staging: wfx: change 1 to bool Kaaira Gupta
2020-03-10 14:25 ` [PATCH 3/6] staging: wfx: dat_tx.c: remove space after a cast Kaaira Gupta
2020-03-10 14:25 ` [PATCH 4/6] staging: wfx: data_tx.h: remove space after cast Kaaira Gupta
2020-03-10 14:25 ` [PATCH 5/6] staging: wfx: remove variable declaration Kaaira Gupta
2020-03-10 14:25 ` [PATCH 6/6] staging: wfx: remove unused structure Kaaira Gupta
2020-03-10 17:40 ` [Outreachy kernel] [PATCH 0/6] Clean-ups in wfx driver Stefano Brivio
2020-03-10 18:07   ` Kaaira Gupta
2020-03-10 18:13     ` Kaaira Gupta
2020-03-10 18:45       ` Stefano Brivio
2020-03-10 19:24         ` Kaaira Gupta
2020-03-10 19:30           ` Stefano Brivio [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=20200310203032.3475fb07@elisabeth \
    --to=sbrivio@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jerome.pouiller@silabs.com \
    --cc=kgupta@es.iitr.ac.in \
    --cc=outreachy-kernel@googlegroups.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.