TO: Mark Brown broo...@kernel.org
tree: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: bbdef57970d5e1887de755474ff1562baa17ef11
commit: 9169051617df7fca597274e9e43324332cb8f0ee [5753/6487] spi: spidev: Don't
mangle max_speed_hz in underlying spi device
::
I reported this one earlier.
regards,
dan carpenter
On Thu, Nov 13, 2014 at 04:24:12PM +0800, kbuild test robot wrote:
TO: Mark Brown broo...@kernel.org
tree: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
master
head: bbdef57970d5e1887de755474ff1562baa17ef11
I see you have upgraded to the latest and greatest version of Smatch.
:)
This one is a false positive, though, sorry for that. I'm not sure how
it gets triggered and I can't reproduce it on my end.
2147383647 is a magic number which means approximately the highest valid
pointer on 32 bit
Hi Julia,
On Thu, Nov 13, 2014 at 11:26:23AM +0100, Julia Lawall wrote:
Is there any way that we can improve this process? At the moment, I just
take the message I get and forward it.
How about always send the patches to public LKML, with you in the CC list?
Thanks,
Fengguang
--
On Thu, Nov 13, 2014 at 08:22:21PM +0800, Fengguang Wu wrote:
No problem. From now on the smatch I run here should be auto upgraded
to your latest git HEAD. :)
Oh wow... That's a lot of presure and I've traditionally sucked at QC.
Right now, I feel like Smatch is at a stable place. I guess
On Thu, Nov 13, 2014 at 08:23:36PM +0800, Fengguang Wu wrote:
Hi Julia,
On Thu, Nov 13, 2014 at 11:26:23AM +0100, Julia Lawall wrote:
Is there any way that we can improve this process? At the moment, I just
take the message I get and forward it.
I normally forward bug warnings if I
On Thu, Nov 13, 2014 at 01:45:39PM +0100, Julia Lawall wrote:
But overall the problem is for the lower confidence ones how to get the
patch to the developer in the form that they want. Is the idea that there
are some lines that I should be removing (To, CC, and the file and line
generated by
On Thu, Nov 13, 2014 at 02:12:33PM +0100, Julia Lawall wrote:
On Thu, 13 Nov 2014, Dan Carpenter wrote:
On Thu, Nov 13, 2014 at 01:45:39PM +0100, Julia Lawall wrote:
But overall the problem is for the lower confidence ones how to get the
patch to the developer in the form that they
On Thu, Nov 13, 2014 at 09:20:16PM +0800, Fengguang Wu wrote:
I'm a robot, after all. ;)
Heh. One time I was credited to as:
Reported-by: The Intel Backend
And I had to tell them that I might be a backend, but I work for Oracle.
regards,
dan carpenter
On Thu, Nov 13, 2014 at 04:29:15PM +0300, Dan Carpenter wrote:
On Thu, Nov 13, 2014 at 09:20:16PM +0800, Fengguang Wu wrote:
I'm a robot, after all. ;)
Heh. One time I was credited to as:
Reported-by: The Intel Backend
And I had to tell them that I might be a backend, but I work for
TO: Michal Kazior michal.kaz...@tieto.com
CC: Kalle Valo kv...@adurom.com
tree: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: bbdef57970d5e1887de755474ff1562baa17ef11
commit: a6aa5da3029670816b3eb9358bc1a63f2e2564fb [125/6487] ath10k: re-work
scan start
TO: Hante Meuleman meule...@broadcom.com
CC: John W. Linville linvi...@tuxdriver.com
CC: Arend van Spriel ar...@broadcom.com
tree: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: bbdef57970d5e1887de755474ff1562baa17ef11
commit:
TO: Jukka Rissanen jukka.rissa...@linux.intel.com
CC: Johannes Berg johannes.b...@intel.com
tree: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: bbdef57970d5e1887de755474ff1562baa17ef11
commit: 579a05f29611dcef94b6bda21f1d059ab189a263 [2918/6487]
TO: Lendacky, Thomas thomas.lenda...@amd.com
CC: Tom Lendacky thomas.lenda...@amd.com
tree: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: bbdef57970d5e1887de755474ff1562baa17ef11
commit: 5b9dfe299e55604af47cdca9d03d2e9d4fe2ad53 [4226/6487] amd-xgbe: Provide
tree: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: bbdef57970d5e1887de755474ff1562baa17ef11
commit: a6aa5da3029670816b3eb9358bc1a63f2e2564fb [125/6487] ath10k: re-work
scan start command building
drivers/net/wireless/ath/ath10k/wmi.c:3170
I reported this one earlier.
regards,
dan carpenter
On Thu, Nov 13, 2014 at 10:08:36PM +0800, kbuild test robot wrote:
TO: Hante Meuleman meule...@broadcom.com
CC: John W. Linville linvi...@tuxdriver.com
CC: Arend van Spriel ar...@broadcom.com
tree:
This one is sort of a false positive. The code works. I feel like it
should be written:
memcpy(data, ath10k_gstrings_stats, sizeof(ath10k_gstrings_stats));
But that's a style issue rather than a bug.
regards,
dan carpenter
On Thu, Nov 13, 2014 at 10:04:33PM +0800, kbuild test robot
TO: Bart Van Assche bvanass...@acm.org
CC: Christoph Hellwig h...@lst.de
tree: git://git.infradead.org/users/hch/scsi.git queue-depth-cleanups
head: 00868993ece2e5af973e0f60990f7781f5e03e88
commit: 509c07bc18500c3ded1a8e6273ace5002136c9d2 [78/90] IB/srp: Separate
target and channel variables
TO: Minghuan Lian minghuan.l...@freescale.com
CC: Bjorn Helgaas bhelg...@google.com
drivers/pci/host/pci-layerscape.c:170:3-8: No need to set .owner here. The core
will do it.
Remove .owner field if calls are used which set it automatically
Generated by:
19 matches
Mail list logo