[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAE_Gge1SSLD66r_Gzj668w_K8=9P=1MqmRd3oWQ_G5iK5BkiBQ@mail.gmail.com>
Date: Tue, 18 Aug 2015 02:02:49 -0400
From: Raphaël Beamonte <raphael.beamonte@...il.com>
To: Sudip Mukherjee <sudipm.mukherjee@...il.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org,
Greg Donald <gdonald@...il.com>,
Cristina Opriceana <cristina.opriceana@...il.com>
Subject: Re: [PATCH 02/20] staging: rtl8192u: r8192U_core: fix consistent
spacing code style error
2015-08-18 1:44 GMT-04:00 Sudip Mukherjee <sudipm.mukherjee@...il.com>:
> I think that will be better, since you are sending the patch for
> consistent spacing.
Actually, going through the bunch of patches, it seems that the
whitespace neatening one is taking care of that. That one patch was
mostly about taking care of the checkpatch "consistent spacing"
warning.
Two solutions here:
(1) I can merge both patches and make a general whitespace neatening
one, taking care of that too.
(2) I can clarify the commit messages of each patches to explain the
aim of each.
Of course, in (1) too I'd take care of explaining the whole point of
the commit. What do you think would be the best approach at this
point?
> And some of your patches are not having any commit message. Greg will
> not accept such patches. So while you are sending take care of that
> also.
Ok!
Thanks again!
Raphaël
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists