Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1353382
| From | Saiyam Doshi <saiyamdoshi.in@gmail.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 1/1] staging: android: Fixed coding style issues reported by checkpatch |
| Date | 2016-03-08 21:30 +0100 |
| Message-ID | <rawqt-5Yf-3@gated-at.bofh.it> (permalink) |
| References | <r9MH0-Wy-9@gated-at.bofh.it> <r9S9I-4sw-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
On Sun, Mar 06, 2016 at 05:21:08PM -0800, Greg KH wrote: > You need to do only one thing per patch, please split this up into > multiple patches. Created two separate patches out of it having same logical change in each. > Also verify that these are all really needed, please always work against > linux-next, not Linus's kernel tree. In 'drivers/staging/android/TODO' checkpatch.pl cleanup mentioned. Also this patches are created from latest linux-next tree. How you get information about target kernel version for submitted patch? I mean in patch there is no information about kernel version from which the patch is created.
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH 1/1] staging: android: Fixed coding style issues reported by checkpatch Saiyam Doshi <saiyamdoshi.in@gmail.com> - 2016-03-06 20:40 +0100
Re: [PATCH 1/1] staging: android: Fixed coding style issues reported by checkpatch Greg KH <gregkh@linuxfoundation.org> - 2016-03-07 02:30 +0100
Re: [PATCH 1/1] staging: android: Fixed coding style issues reported by checkpatch Saiyam Doshi <saiyamdoshi.in@gmail.com> - 2016-03-08 21:30 +0100
Re: [PATCH 1/1] staging: android: Fixed coding style issues reported by checkpatch Greg KH <gregkh@linuxfoundation.org> - 2016-03-11 23:00 +0100
csiph-web