Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1309160
| From | Mark Brown <broonie@kernel.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v2 9/9] regulator: add LM363X driver |
| Date | 2016-01-14 11:30 +0100 |
| Message-ID | <qQNke-5Dw-21@gated-at.bofh.it> (permalink) |
| References | <qyYH7-1f6-3@gated-at.bofh.it> <qyYH7-1f6-5@gated-at.bofh.it> <qQKZ3-3XE-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
On Thu, Jan 14, 2016 at 04:56:03PM +0900, Milo Kim wrote: > So, I'd like to know which is better for you. > a) Create a patch based on linux-next tree (the above patch) > Or > b) Re-generate a patch based on linux-mfd tree At this point the easiest thing might be to wait for v4.5-rc1 then send a patch for that after everything gets merged.
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [PATCH v2 9/9] regulator: add LM363X driver Milo Kim <milo.kim@ti.com> - 2016-01-14 09:00 +0100
Re: [PATCH v2 9/9] regulator: add LM363X driver Mark Brown <broonie@kernel.org> - 2016-01-14 11:30 +0100
Re: [PATCH v2 9/9] regulator: add LM363X driver "Kim, Milo" <milo.kim@ti.com> - 2016-01-15 00:50 +0100
csiph-web