Re: [PATCH 0/2] *** SUBJECT HERE ***

2021-04-16 Thread Greg Kroah-Hartman
On Fri, Apr 16, 2021 at 04:07:54PM +0800, Tao Zhang wrote: > *** BLURB HERE *** Where is the blurb? And your subject is not ok :(

[PATCH 0/2] *** SUBJECT HERE ***

2021-04-16 Thread Tao Zhang
*** BLURB HERE *** Tao Zhang (2): coresight: Add support for device names dt-bindings: arm: add property for coresight component name Documentation/devicetree/bindings/arm/coresight.txt | 2 ++ drivers/hwtracing/coresight/coresight-core.c| 6 ++ 2 files changed, 8 insertions(+)

[PATCH 0/2] *** SUBJECT HERE ***

2016-03-13 Thread Andrew Pinski
*** BLURB HERE *** Andrew Pinski (2): ARM64:VDSO: Improve gettimeofday, don't use udiv ARM64:VDSO: Improve __do_get_tspec, don't use udiv arch/arm64/kernel/vdso/gettimeofday.S | 47 1 files changed, 35 insertions(+), 12 deletions(-) -- 1.7.2.5

[PATCH 0/2] *** SUBJECT HERE ***

2016-03-13 Thread Andrew Pinski
*** BLURB HERE *** Andrew Pinski (2): ARM64:VDSO: Improve gettimeofday, don't use udiv ARM64:VDSO: Improve __do_get_tspec, don't use udiv arch/arm64/kernel/vdso/gettimeofday.S | 47 1 files changed, 35 insertions(+), 12 deletions(-) -- 1.7.2.5

Re: [PATCH 0/2] *** SUBJECT HERE ***

2013-07-02 Thread Johan Hovold
On Tue, Jul 02, 2013 at 01:22:01AM +0200, Anders Hammarquist wrote: > In a message of Fri, 28 Jun 2013 12:23:33 +0200, Johan Hovold writes: > >> I did a quick check of adding the device id though sysfs, and although > >> it partly works, it doesn't find the correct firmware (it ends up trying > >>

Re: [PATCH 0/2] *** SUBJECT HERE ***

2013-07-02 Thread Johan Hovold
On Tue, Jul 02, 2013 at 01:22:01AM +0200, Anders Hammarquist wrote: In a message of Fri, 28 Jun 2013 12:23:33 +0200, Johan Hovold writes: I did a quick check of adding the device id though sysfs, and although it partly works, it doesn't find the correct firmware (it ends up trying to load

Re: [PATCH 0/2] *** SUBJECT HERE ***

2013-07-01 Thread Anders Hammarquist
In a message of Fri, 28 Jun 2013 12:23:33 +0200, Johan Hovold writes: >> I did a quick check of adding the device id though sysfs, and although >> it partly works, it doesn't find the correct firmware (it ends up trying >> to load 5052 firmware for a 3410 device. Looking at the code it seems >>

Re: [PATCH 0/2] *** SUBJECT HERE ***

2013-07-01 Thread Anders Hammarquist
In a message of Fri, 28 Jun 2013 12:23:33 +0200, Johan Hovold writes: I did a quick check of adding the device id though sysfs, and although it partly works, it doesn't find the correct firmware (it ends up trying to load 5052 firmware for a 3410 device. Looking at the code it seems (struct

Re: [PATCH 0/2] *** SUBJECT HERE ***

2013-06-28 Thread Johan Hovold
On Thu, Jun 27, 2013 at 11:50:52PM +0200, Anders Hammarquist wrote: > In a message of Wed, 26 Jun 2013 12:39:24 +0200, Johan Hovold writes: > >On Wed, Jun 26, 2013 at 10:29:59AM +0200, Anders Hammarquist wrote: > >> In a message of Tue, 25 Jun 2013 16:39:11 -0700, Greg KH writes: > >> >> Indeed.

Re: [PATCH 0/2] *** SUBJECT HERE ***

2013-06-28 Thread Johan Hovold
On Thu, Jun 27, 2013 at 11:50:52PM +0200, Anders Hammarquist wrote: In a message of Wed, 26 Jun 2013 12:39:24 +0200, Johan Hovold writes: On Wed, Jun 26, 2013 at 10:29:59AM +0200, Anders Hammarquist wrote: In a message of Tue, 25 Jun 2013 16:39:11 -0700, Greg KH writes: Indeed. I'd already

Re: [PATCH 0/2] *** SUBJECT HERE ***

2013-06-27 Thread Anders Hammarquist
In a message of Wed, 26 Jun 2013 12:39:24 +0200, Johan Hovold writes: >On Wed, Jun 26, 2013 at 10:29:59AM +0200, Anders Hammarquist wrote: >> In a message of Tue, 25 Jun 2013 16:39:11 -0700, Greg KH writes: >> >> Indeed. I'd already had some (failed) thoughts about how to handle it >> >> nicely.

Re: [PATCH 0/2] *** SUBJECT HERE ***

2013-06-27 Thread Anders Hammarquist
In a message of Wed, 26 Jun 2013 12:39:24 +0200, Johan Hovold writes: On Wed, Jun 26, 2013 at 10:29:59AM +0200, Anders Hammarquist wrote: In a message of Tue, 25 Jun 2013 16:39:11 -0700, Greg KH writes: Indeed. I'd already had some (failed) thoughts about how to handle it nicely. Now I've had

Re: [PATCH 0/2] *** SUBJECT HERE ***

2013-06-26 Thread Johan Hovold
On Wed, Jun 26, 2013 at 10:29:59AM +0200, Anders Hammarquist wrote: > In a message of Tue, 25 Jun 2013 16:39:11 -0700, Greg KH writes: > >> Indeed. I'd already had some (failed) thoughts about how to handle it > >> nicely. Now I've had another think through, and I have something which > >> deals

Re: [PATCH 0/2] *** SUBJECT HERE ***

2013-06-26 Thread Anders Hammarquist
In a message of Tue, 25 Jun 2013 16:39:11 -0700, Greg KH writes: >> Indeed. I'd already had some (failed) thoughts about how to handle it >> nicely. Now I've had another think through, and I have something which >> deals with it and at least complains if TI_EXTRA_VID_PID_COUNT is changed >>

Re: [PATCH 0/2] *** SUBJECT HERE ***

2013-06-26 Thread Anders Hammarquist
In a message of Tue, 25 Jun 2013 16:39:11 -0700, Greg KH writes: Indeed. I'd already had some (failed) thoughts about how to handle it nicely. Now I've had another think through, and I have something which deals with it and at least complains if TI_EXTRA_VID_PID_COUNT is changed without

Re: [PATCH 0/2] *** SUBJECT HERE ***

2013-06-26 Thread Johan Hovold
On Wed, Jun 26, 2013 at 10:29:59AM +0200, Anders Hammarquist wrote: In a message of Tue, 25 Jun 2013 16:39:11 -0700, Greg KH writes: Indeed. I'd already had some (failed) thoughts about how to handle it nicely. Now I've had another think through, and I have something which deals with it and

Re: [PATCH 0/2] *** SUBJECT HERE ***

2013-06-25 Thread Greg KH
On Sat, Jun 22, 2013 at 08:54:43PM +0200, Anders Hammarquist wrote: > In a message of Fri, 21 Jun 2013 16:56:03 -0700, Greg KH writes: > >Please resend this in a format that I can apply it in (i.e. one that > >does not require me to edit it by hand...) > > After more fighting with git, I belive I

Re: [PATCH 0/2] *** SUBJECT HERE ***

2013-06-25 Thread Greg KH
On Sat, Jun 22, 2013 at 08:54:43PM +0200, Anders Hammarquist wrote: In a message of Fri, 21 Jun 2013 16:56:03 -0700, Greg KH writes: Please resend this in a format that I can apply it in (i.e. one that does not require me to edit it by hand...) After more fighting with git, I belive I now

Re: [PATCH 0/2] *** SUBJECT HERE ***

2013-06-22 Thread Anders Hammarquist
In a message of Fri, 21 Jun 2013 16:56:03 -0700, Greg KH writes: >Please resend this in a format that I can apply it in (i.e. one that >does not require me to edit it by hand...) After more fighting with git, I belive I now made it spit out what I wanted. Patch 1/2 ahead. >> -static struct

Re: [PATCH 0/2] *** SUBJECT HERE ***

2013-06-22 Thread Anders Hammarquist
In a message of Fri, 21 Jun 2013 16:56:03 -0700, Greg KH writes: Please resend this in a format that I can apply it in (i.e. one that does not require me to edit it by hand...) After more fighting with git, I belive I now made it spit out what I wanted. Patch 1/2 ahead. -static struct

Re: [PATCH 0/2] *** SUBJECT HERE ***

2013-06-21 Thread Greg KH
On Sat, Jun 22, 2013 at 01:08:12AM +0200, Anders Hammarquist wrote: > In a message of Wed, 19 Jun 2013 15:53:15 -0700, Greg KH writes: > >I think you forgot a Subject :) > > Indeed. I blame it on my first fight with git format-patch ;-) > > >On Wed, Jun 19, 2013 at 02:05:07AM +0200, Anders

Re: [PATCH 0/2] *** SUBJECT HERE ***

2013-06-21 Thread Anders Hammarquist
In a message of Wed, 19 Jun 2013 15:53:15 -0700, Greg KH writes: >I think you forgot a Subject :) Indeed. I blame it on my first fight with git format-patch ;-) >On Wed, Jun 19, 2013 at 02:05:07AM +0200, Anders Hammarquist wrote: >> This patch set adds the product id to the driver, and makes the

Re: [PATCH 0/2] *** SUBJECT HERE ***

2013-06-21 Thread Anders Hammarquist
In a message of Wed, 19 Jun 2013 15:53:15 -0700, Greg KH writes: I think you forgot a Subject :) Indeed. I blame it on my first fight with git format-patch ;-) On Wed, Jun 19, 2013 at 02:05:07AM +0200, Anders Hammarquist wrote: This patch set adds the product id to the driver, and makes the

Re: [PATCH 0/2] *** SUBJECT HERE ***

2013-06-21 Thread Greg KH
On Sat, Jun 22, 2013 at 01:08:12AM +0200, Anders Hammarquist wrote: In a message of Wed, 19 Jun 2013 15:53:15 -0700, Greg KH writes: I think you forgot a Subject :) Indeed. I blame it on my first fight with git format-patch ;-) On Wed, Jun 19, 2013 at 02:05:07AM +0200, Anders Hammarquist

Re: [PATCH 0/2] *** SUBJECT HERE ***

2013-06-19 Thread Greg KH
I think you forgot a Subject :) On Wed, Jun 19, 2013 at 02:05:07AM +0200, Anders Hammarquist wrote: > The USB cable to read out data from the Abbott FreeStyle Precision > meters, known as the Abbott stip port cable, uses the TI 3410 chip, > just as the already added stereo port cable. They are

Re: [PATCH 0/2] *** SUBJECT HERE ***

2013-06-19 Thread Greg KH
I think you forgot a Subject :) On Wed, Jun 19, 2013 at 02:05:07AM +0200, Anders Hammarquist wrote: The USB cable to read out data from the Abbott FreeStyle Precision meters, known as the Abbott stip port cable, uses the TI 3410 chip, just as the already added stereo port cable. They are

[PATCH 0/2] *** SUBJECT HERE ***

2013-06-18 Thread Anders Hammarquist
The USB cable to read out data from the Abbott FreeStyle Precision meters, known as the Abbott stip port cable, uses the TI 3410 chip, just as the already added stereo port cable. They are essestially the same cable, just with different connectors at the end. This patch set adds the product id to

[PATCH 0/2] *** SUBJECT HERE ***

2013-06-18 Thread Anders Hammarquist
The USB cable to read out data from the Abbott FreeStyle Precision meters, known as the Abbott stip port cable, uses the TI 3410 chip, just as the already added stereo port cable. They are essestially the same cable, just with different connectors at the end. This patch set adds the product id to