On Tue, Sep 17, 2013 at 07:53:36PM +, KY Srinivasan wrote:
> > > Thanks Gleb. Here is the link for the latest Hyper-V specification:
> > > http://www.microsoft.com/en-us/download/details.aspx?id=39289
> > >
> > > This spec talks about how migration is handled with regards to TSC.
> > >
> > All
From: Shalin Mehta
The function implementations of the PHSModule didn't match with the
declaration. The functions are static
in the declaration but in the implemntation they are non-static
Signed-off-by: Shalin Mehta
---
NOTE: Submitting the same patch again. Added NOTE at wrong location the
Add a new driver to support synthetic keyboard. On the next generation
Hyper-V guest firmware, many legacy devices will not be emulated and this
driver will be required.
I would like to thank Vojtech Pavlik for helping me with the
details of the AT keyboard driver. I would also like to thank
Dan
On Tue, Sep 17 2013 at 8:43am -0400,
Akira Hayakawa wrote:
> Hi, Mike
>
> There are two designs in my mind
> regarding the formatting cache.
>
> You said
> > administer the writeboost devices. There is no need for this. Just
> > have a normal DM target whose .ctr takes care of validation
This is a patch to lvfs_linux.c that fixes incorrect switch case statement
indenting found by checkpatch.pl.
Signed-off-by: Jon Bernard
---
drivers/staging/lustre/lustre/lvfs/lvfs_linux.c | 50 -
1 file changed, 25 insertions(+), 25 deletions(-)
diff --git a/drivers/stag
On Tue, Sep 17 2013 at 8:41am -0400,
Akira Hayakawa wrote:
> Mike,
>
> First, thank you for your commenting.
> I was looking forward to your comments.
>
>
> I suppose you are sensing some "smell" in my design.
> You are worrying that dm-writeboost will not only confuse users
> but also fall i
On Tue, Sep 17, 2013 at 02:53:23PM -0300, Fabio Estevam wrote:
> Since commit b5dc0d10 (drm/imx: kill firstopen callback) the following probe
> failure is seen:
>
> [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
> [drm] No driver support for vblank timestamp query.
> [drm] Initialized
> -Original Message-
> From: Gleb Natapov [mailto:g...@redhat.com]
> Sent: Tuesday, September 17, 2013 6:59 AM
> To: KY Srinivasan
> Cc: H. Peter Anvin; x...@kernel.org; gre...@linuxfoundation.org; linux-
> ker...@vger.kernel.org; de...@linuxdriverproject.org; o...@aepfle.de;
> a...@canon
> -Original Message-
> From: Greg Kroah-Hartman [mailto:gre...@linuxfoundation.org]
> Sent: Friday, September 13, 2013 11:33 AM
> To: KY Srinivasan; Haiyang Zhang
> Cc: de...@linuxdriverproject.org; linux-ker...@vger.kernel.org
> Subject: [PATCH 00/13] hv: clean up dev_attr usage
>
> Hi,
Since commit b5dc0d10 (drm/imx: kill firstopen callback) the following probe
failure is seen:
[drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[drm] No driver support for vblank timestamp query.
[drm] Initialized imx-drm 1.0.0 20120507 on minor 0
imx-ldb ldb.10: adding encoder failed wi
Hello,
On (09/16/13 09:02), Minchan Kim wrote:
> Hello Sergey,
>
> Sorry for really slow response. I was really busy by internal works
> and Thanks for pointing the BUG, Dan, Jerome and Sergey.
> I read your threads roughly so I may miss something. If so, sorry
> for that. Anyway I will put my o
On Mon, 2013-09-16 at 15:43 +0200, Iker Pedrosa wrote:
> The previously used printk lacked the warning level, now we've got a more
> accurate way to know the error.
[]
> diff --git a/drivers/staging/winbond/wb35tx.c
> b/drivers/staging/winbond/wb35tx.c
[]
> @@ -32,7 +32,7 @@ static void Wb35Tx_co
On Fri, Sep 13, 2013 at 02:28:35PM +, KY Srinivasan wrote:
>
>
> > -Original Message-
> > From: Gleb Natapov [mailto:g...@redhat.com]
> > Sent: Friday, September 13, 2013 2:55 AM
> > To: KY Srinivasan
> > Cc: H. Peter Anvin; x...@kernel.org; gre...@linuxfoundation.org; linux-
> > ker.
Hi, Mike
There are two designs in my mind
regarding the formatting cache.
You said
> administer the writeboost devices. There is no need for this. Just
> have a normal DM target whose .ctr takes care of validation and
> determines whether a device needs formatting, etc.
makes me wonder
Mike,
First, thank you for your commenting.
I was looking forward to your comments.
I suppose you are sensing some "smell" in my design.
You are worrying that dm-writeboost will not only confuse users
but also fall into worst situation of giving up backward-compatibility
after merging into tree.
On 06/03/2013 08:14 PM, Marcus Overhagen wrote:
Using correct transfer interval as specified by the USB endpoint
when doing the interrupt transfer fixes the warning printed by
xhci USB core on every transfer that resulted in spamming
"xhci_queue_intr_tx: 74 callbacks suppressed" to syslog
every 5
On Tue, Sep 17, 2013 at 02:29:22PM +0530, Adil Mujeeb wrote:
> Hi,
>
>
> >- PowerData = (1 << 31) | (0 << 30) | (24 << 24) |
> BitReverse(w89rf242_txvga_data[i][0], 24);
> >+ PowerData = (1 << 31) | (0 << 30) | (24 << 24)
> >+ | BitReverse(w89rf242_txvga_data
On Tue, 17 Sep 2013, Shalin Mehta wrote:
> From: Shalin Mehta
>
> NOTE: Sending it again. I got mail delivery failure due to typo in emai ID
> gre...@linuxfoundation.org
I think that such a comment should go below the ---, since it doesn't have
to be preserved in git.
julia
>
>
> The function
On Tue, Sep 17, 2013 at 12:12:42AM -0700, Shalin Mehta wrote:
> From: Shalin Mehta
>
> NOTE: Sending it again. I got mail delivery failure due to typo in emai ID
> gre...@linuxfoundation.org
>
Put these comments that don't belong in the changelog under the ---
cut off line with the diffstat.
Hi Dmitry,
On Monday 16 September 2013 17:28:46 Dmitry Torokhov wrote:
> [...]
> > > static int mxs_lradc_ts_register(struct mxs_lradc *lradc)
> > > @@ -641,6 +1056,7 @@ static void mxs_lradc_ts_unregister(struct
> > > mxs_lradc *lradc)
> > >
> > > cancel_work_sync(&lradc->ts_work);
> > >
> > >
From: Shalin Mehta
NOTE: Sending it again. I got mail delivery failure due to typo in emai ID
gre...@linuxfoundation.org
The function implementations of the PHSModule didn't match with the
declaration. The functions are static
in the declaration but in the implemntation they are non-static
S
From: Shalin Mehta
The function implementations of the PHSModule didn't match with the
declaration. The functions are static
in the declaration but in the implemntation they are non-static
Signed-off-by: Shalin Mehta
---
drivers/staging/bcm/PHSModule.c | 12 ++--
1 file changed, 6 ins
22 matches
Mail list logo
