All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alison Schofield <amsfield22@gmail.com>
To: Tamara Diaconita <diaconitatamara@gmail.com>
Cc: aditya.shankar@microchip.com, ganesh.krishna@microchip.com,
	gregkh@linuxfoundation.org, outreachy-kernel@googlegroups.com,
	Tamara Diaconita <diaconita.tamara@gmail.com>
Subject: Re: [Outreachy kernel] [PATCH 0/7] staging: wilc1000: Improve code readability
Date: Fri, 10 Mar 2017 11:49:29 -0800	[thread overview]
Message-ID: <20170310194928.GD23892@d830.WORKGROUP> (raw)
In-Reply-To: <20170310192056.GB23892@d830.WORKGROUP>

On Fri, Mar 10, 2017 at 11:20:57AM -0800, Alison Schofield wrote:
> On Fri, Mar 10, 2017 at 09:06:06PM +0200, Tamara Diaconita wrote:
> > Improve code readability in wilc_spi.c file in wilc1000 driver.
> 
> Hi Tamara,
> 
> Just realized why my inbox is getting disorganized.  These patchsets
> need to be sent 'threaded' so they stick together.  See how to do
> that in the first patch tutorial.  
> 
> I'm already in the middle of your last patchset, so I will keep
> going with that, but I think I'd like you to do a [PATCH RESEND]
> on this one and send it threaded.  Basically the PATCH RESEND
> says nothing has changed inside it.

Tamara,

OK...i peeked at it.  Please don't RESEND as is.  
The first 3 patches make a great set.  Improving the 
single func wilc_spi_read_int().

Can you resend just those top 3 as a single patch set,
and reflect that in your cover letter that you are

Note - I'm not disregarding patches 4-7, just don't think
they belong in the set. Hold onto them.

alisons




> 
> Thanks,
> alisons
> 
> > 
> > Tamara Diaconita (7):
> >   staging: wilc1000: Remove unnecessary brackets
> >   staging: wilc1000: Declare variables at top of function
> >   staging: wilc1000: Correct name of variables
> >   staging: wilc1000: Add blank line
> >   staging: wilc1000: Removing extra tabs
> >   staging: wilc1000: Use kernel preferred commenting style
> >   staging: wilc1000: Rearrange code
> > 
> >  drivers/staging/wilc1000/wilc_spi.c | 101 +++++++++++++++++++-----------------
> >  1 file changed, 54 insertions(+), 47 deletions(-)
> > 
> > -- 
> > 2.9.3
> > 
> > -- 
> > You received this message because you are subscribed to the Google Groups "outreachy-kernel" group.
> > To unsubscribe from this group and stop receiving emails from it, send an email to outreachy-kernel+unsubscribe@googlegroups.com.
> > To post to this group, send email to outreachy-kernel@googlegroups.com.
> > To view this discussion on the web visit https://groups.google.com/d/msgid/outreachy-kernel/20170310190606.19766-1-diaconita.tamara%40gmail.com.
> > For more options, visit https://groups.google.com/d/optout.


      reply	other threads:[~2017-03-10 19:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-10 19:06 [PATCH 0/7] staging: wilc1000: Improve code readability Tamara Diaconita
2017-03-10 19:20 ` [Outreachy kernel] " Alison Schofield
2017-03-10 19:49   ` Alison Schofield [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=20170310194928.GD23892@d830.WORKGROUP \
    --to=amsfield22@gmail.com \
    --cc=aditya.shankar@microchip.com \
    --cc=diaconita.tamara@gmail.com \
    --cc=diaconitatamara@gmail.com \
    --cc=ganesh.krishna@microchip.com \
    --cc=gregkh@linuxfoundation.org \
    --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.