On Mon, Nov 21, 2016 at 05:42:07PM -0200, Mauro Carvalho Chehab wrote:
> Em Mon, 21 Nov 2016 17:03:55 +0100
> Daniel Vetter escreveu:
>
> > On Mon, Nov 21, 2016 at 08:53:17AM -0200, Mauro Carvalho Chehab wrote:
> > > Inserting images with Sphinx is tricky, due to its limited
> > > image support.
mono and mono_raw trace clocks access CLOCK_MONOTONIC and CLOCK_MONOTONIC_RAW
clocks for tracing purposes. Add documentation for the same.
Signed-off-by: Joel Fernandes
---
Steven,
I skipped adding docs for boot clock as that patch is still being discussed,
but please accept documentation for the
On 11/08/2016 07:13 AM, Daniel Vetter wrote:
> On Mon, Nov 07, 2016 at 01:24:14PM -0700, Shuah Khan wrote:
>> Update kselftest.txt with details on how to run tests after install.
>>
>> Signed-off-by: Shuah Khan
>> ---
>> Documentation/kselftest.txt | 11 +++
>> 1 file changed, 11 insertio
The path to a few documentation files have changed since the switch to
Sphinx. Point to the proper files.
Signed-off-by: Alexandre Belloni
---
lib/Kconfig.debug | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index b01e547d4d04
On 11/21/2016 02:17 PM, Peter Rosin wrote:
[...]
> I have a piece of hardware that is using the same 3 GPIO pins
> to control four 8-way muxes. Three of them control ADC lines
> to an ADS1015 chip with an iio driver, and the last one
> controls the SDA line of an i2c bus. We have some deployed
> co
On Tue, Nov 22, 2016 at 04:41:37PM +0100, Borislav Petkov wrote:
> On Tue, Nov 22, 2016 at 05:22:38PM +0200, Michael S. Tsirkin wrote:
> > The issue is it's a (potential) security hole, not a slowdown.
>
> How? Because the bounce buffers will be unencrypted and someone might
> intercept them?
Or
On Wed, Nov 09, 2016 at 06:37:40PM -0600, Tom Lendacky wrote:
> Add support to check if memory encryption is active in the kernel and that
> it has been enabled on the AP. If memory encryption is active in the kernel
> but has not been enabled on the AP then do not allow the AP to continue
> start
On Wed, Nov 09, 2016 at 06:38:38PM -0600, Tom Lendacky wrote:
> This patch adds the support to check if SME has been enabled and if the
> mem_encrypt=on command line option is set. If both of these conditions
> are true, then the encryption mask is set and the kernel is encrypted
> "in place."
Som
> Here are a couple of additional questions:
>
> - When the network interface is created, there is no IP address
> assigned (or negotiated ?) on the Linux side. But it is done on the
> MacOS side. And in the Linux kernel logs I can also read the message:
> "ready for ThunderboltIP negotiatio
On Fri, Nov 18, 2016 at 12:20:07PM +0100, Simon Guinot wrote:
> On Fri, Nov 18, 2016 at 08:48:36AM +, Levy, Amir (Jer) wrote:
> > On Tue, Nov 15 2016, 12:59 PM, Simon Guinot wrote:
> > > On Wed, Nov 09, 2016 at 03:42:53PM +, Levy, Amir (Jer) wrote:
> > > > On Wed, Nov 9 2016, 04:36 PM, Simo
Em Tue, 22 Nov 2016 17:40:27 +0200
Jani Nikula escreveu:
> On Tue, 22 Nov 2016, Mauro Carvalho Chehab wrote:
> > I tried both, none broke the long lines on
> > Documentation/media/uapi/v4l/fieldseq_tb.svg.
>
> How about:
>
> 'tidy -xml -i Documentation/media/uapi/v4l/fieldseq_tb.svg | fmt -
On Tue, Nov 22, 2016 at 05:22:38PM +0200, Michael S. Tsirkin wrote:
> The issue is it's a (potential) security hole, not a slowdown.
How? Because the bounce buffers will be unencrypted and someone might
intercept them?
> To disable unsecure things. If someone enables SEV one might have an
> expec
On Tue, 22 Nov 2016, Mauro Carvalho Chehab wrote:
> I tried both, none broke the long lines on
> Documentation/media/uapi/v4l/fieldseq_tb.svg.
How about:
'tidy -xml -i Documentation/media/uapi/v4l/fieldseq_tb.svg | fmt -sw 80'
Both pretty indents and folds. I think it should Just Work(tm).
B
On Tue, Nov 22, 2016 at 12:38:59PM +0100, Borislav Petkov wrote:
> On Tue, Nov 15, 2016 at 12:29:35PM -0600, Tom Lendacky wrote:
> > > Makes sense, but I think at least a dmesg warning here
> > > might be a good idea.
> >
> > Good idea. Should it be a warning when it is first being set up or
> >
Em Tue, 22 Nov 2016 15:49:47 +0200
Jani Nikula escreveu:
> On Mon, 21 Nov 2016, Mauro Carvalho Chehab wrote:
> > Em Mon, 21 Nov 2016 10:44:44 -0700
> > Jonathan Corbet escreveu:
> >
> >> On Sun, 20 Nov 2016 14:08:31 -0200
> >> Mauro Carvalho Chehab wrote:
> >> > NOTE: some images use more
On Mon, 21 Nov 2016, Mauro Carvalho Chehab wrote:
> Em Mon, 21 Nov 2016 10:44:44 -0700
> Jonathan Corbet escreveu:
>
>> On Sun, 20 Nov 2016 14:08:31 -0200
>> Mauro Carvalho Chehab wrote:
>> > NOTE: some images use more than 998 columns, causing troubles
>> > with some MTA and MUA that could refu
On Tue, Nov 15, 2016 at 12:29:35PM -0600, Tom Lendacky wrote:
> > Makes sense, but I think at least a dmesg warning here
> > might be a good idea.
>
> Good idea. Should it be a warning when it is first being set up or
> a warning the first time the bounce buffers need to be used. Or maybe
> both
Em Tue, 22 Nov 2016 10:09:53 +0100
Markus Heiser escreveu:
> Am 22.11.2016 um 09:44 schrieb Mauro Carvalho Chehab
> :
>
> > Em Mon, 21 Nov 2016 08:48:00 +0100
> > Markus Heiser escreveu:
> >
> >> Am 19.11.2016 um 19:22 schrieb Mauro Carvalho Chehab
> >> :
> >>>
> >>> And, a more detaile
Am 22.11.2016 um 09:44 schrieb Mauro Carvalho Chehab :
> Em Mon, 21 Nov 2016 08:48:00 +0100
> Markus Heiser escreveu:
>
>> Am 19.11.2016 um 19:22 schrieb Mauro Carvalho Chehab
>> :
>>>
>>> And, a more detailed description using --man. Right now --man
>>> displays an identical content of the p
Keeping both rst and in-file documentation in sync can be harsh.
So, simplify the script's internal documntation to a bare minimum,
and add a mention to the ReST file with its full documentation.
This way, a quick help is still available at the command line,
while the complete one is maintained a
Em Mon, 21 Nov 2016 08:48:00 +0100
Markus Heiser escreveu:
> Am 19.11.2016 um 19:22 schrieb Mauro Carvalho Chehab
> :
>
> >> What are the chances of just making the rst doc be the definitive one
> >> and putting a pointer into pod2rst?
> >
> > Not sure what exactly you want. IMO, it is usefu
Em Mon, 21 Nov 2016 17:21:38 -0200
Mauro Carvalho Chehab escreveu:
> > My preference, honestly, would be to put the documentation in RST and
> > maintain that as the definitive documentation for the tool. It's not as
> > if there's going to be a lot of interactive users of parse-headers.pl...
>
Keeping both rst and in-file documentation in sync can be harsh.
So, simplify the script's internal documntation to a bare minimum,
and add a mention to the ReST file with its full documentation.
This way, a quick help is still available at the command line,
while the complete one is maintained a
23 matches
Mail list logo
