Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1509314 > unrolled thread
| Started by | Uwe Kleine-König <u.kleine-koenig@pengutronix.de> |
|---|---|
| First post | 2016-10-26 15:00 +0200 |
| Last post | 2016-10-27 09:00 +0200 |
| Articles | 4 — 3 participants |
Back to article view | Back to linux.kernel
[PATCH 0/5] print a hex number after a 0x prefix Uwe Kleine-König <u.kleine-koenig@pengutronix.de> - 2016-10-26 15:00 +0200
Re: [PATCH 0/5] print a hex number after a 0x prefix Andrew Morton <akpm@linux-foundation.org> - 2016-10-26 22:00 +0200
Re: [PATCH 0/5] print a hex number after a 0x prefix Joe Perches <joe@perches.com> - 2016-10-27 01:40 +0200
Re: [PATCH 0/5] print a hex number after a 0x prefix Uwe Kleine-König <u.kleine-koenig@pengutronix.de> - 2016-10-27 09:00 +0200
| From | Uwe Kleine-König <u.kleine-koenig@pengutronix.de> |
|---|---|
| Date | 2016-10-26 15:00 +0200 |
| Subject | [PATCH 0/5] print a hex number after a 0x prefix |
| Message-ID | <swvYe-3Qk-13@gated-at.bofh.it> |
Hello, these were found by git grep -i 0x%[lh]*[du] Maybe it would make sense to catch this type of unconvenience in checkpatch? Best regards Uwe Uwe Kleine-König (5): fs: exofs: print a hex number after a 0x prefix block: DAC960: print a hex number after a 0x prefix ipack: print a hex number after a 0x prefix misc: sgi-gru: print a hex number after a 0x prefix cris/arch-v32: cryptocop: print a hex number after a 0x prefix arch/cris/arch-v32/drivers/cryptocop.c | 2 +- drivers/block/DAC960.c | 4 ++-- drivers/ipack/ipack.c | 2 +- drivers/misc/sgi-gru/grumain.c | 5 +++-- fs/exofs/dir.c | 2 +- 5 files changed, 8 insertions(+), 7 deletions(-) -- 2.9.3
[toc] | [next] | [standalone]
| From | Andrew Morton <akpm@linux-foundation.org> |
|---|---|
| Date | 2016-10-26 22:00 +0200 |
| Message-ID | <swCwG-8id-17@gated-at.bofh.it> |
| In reply to | #1509314 |
On Wed, 26 Oct 2016 14:56:53 +0200 Uwe Kleine-K__nig <u.kleine-koenig@pengutronix.de> wrote: > Hello, > > these were found by > > git grep -i 0x%[lh]*[du] > > Maybe it would make sense to catch this type of unconvenience in > checkpatch? > > Best regards > Uwe > > Uwe Kleine-K__nig (5): > fs: exofs: print a hex number after a 0x prefix > block: DAC960: print a hex number after a 0x prefix > ipack: print a hex number after a 0x prefix > misc: sgi-gru: print a hex number after a 0x prefix > cris/arch-v32: cryptocop: print a hex number after a 0x prefix um, lol, yup, thanks. I'll slam all five into 4.9-rcX.
[toc] | [prev] | [next] | [standalone]
| From | Joe Perches <joe@perches.com> |
|---|---|
| Date | 2016-10-27 01:40 +0200 |
| Message-ID | <swFXz-2ch-13@gated-at.bofh.it> |
| In reply to | #1509314 |
On Wed, 2016-10-26 at 14:56 +0200, Uwe Kleine-König wrote: > Hello, > > these were found by > > git grep -i 0x%[lh]*[du] > > Maybe it would make sense to catch this type of unconvenience in > checkpatch? Already there.
[toc] | [prev] | [next] | [standalone]
| From | Uwe Kleine-König <u.kleine-koenig@pengutronix.de> |
|---|---|
| Date | 2016-10-27 09:00 +0200 |
| Message-ID | <swMPs-6M3-21@gated-at.bofh.it> |
| In reply to | #1509948 |
On Wed, Oct 26, 2016 at 04:35:22PM -0700, Joe Perches wrote: > On Wed, 2016-10-26 at 14:56 +0200, Uwe Kleine-König wrote: > > Hello, > > > > these were found by > > > > git grep -i 0x%[lh]*[du] > > > > Maybe it would make sense to catch this type of unconvenience in > > checkpatch? > > Already there. Oh, you're right. It's there since over a year. Strange that noone fixed this before then. Best regards Uwe -- Pengutronix e.K. | Uwe Kleine-König | Industrial Linux Solutions | http://www.pengutronix.de/ |
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web