On Sat, Aug 5, 2017 at 3:23 PM, Corey Minyard wrote:
> On 08/04/2017 08:18 PM, Brendan Higgins wrote:
>>
>> This patchset introduces IPMI Block Transfer over I2C (BT-I2C), which has
>> the
>> same semantics as IPMI Block Transfer except it done over I2C.
>>
>> For the OpenBMC people, this is based
On (08/07/17 11:52), Prarit Bhargava wrote:
[..]
> +/**
> + * enum printk_time_type - Timestamp types for printk() messages.
> + * @PRINTK_TIME_DISABLE: No time stamp.
> + * @PRINTK_TIME_LOCAL: Local hardware clock timestamp.
> + * @PRINTK_TIME_BOOT: Boottime clock timestamp.
> + * @PRINTK_TIME_MON
On Mon, Aug 07, 2017 at 04:06:09PM -0400, Prarit Bhargava wrote:
>
>
> On 08/07/2017 02:47 PM, John Stultz wrote:
> > On Mon, Aug 7, 2017 at 11:04 AM, Prarit Bhargava wrote:
> >> On 08/07/2017 12:52 PM, John Stultz wrote:
> >>> Still not quite following why you're updating all the defconfigs. I'
On Mon, 31 Jul 2017 09:53:01 +0800
Alex Shi wrote:
> On 07/31/2017 09:50 AM, Alex Shi wrote:
> > -Reviewers: Ingo Molnar, Thomas Gleixner, Thomas Duetsch, and Randy Dunlap
> > +Original Reviewers: Ingo Molnar, Thomas Gleixner, Thomas Duetsch, and
> > +Randy Dunlap
> > +Update (7
On Mon, 24 Jul 2017 11:01:31 +0200
Thierry Reding wrote:
> From: Thierry Reding
>
> There's no use for this blank line at the end of the file. Remove it.
>
> Signed-off-by: Thierry Reding
> ---
> Documentation/driver-api/miscellaneous.rst | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --gi
On Mon, 24 Jul 2017 09:09:24 -0300
Mauro Carvalho Chehab wrote:
> RHEL 7.x and clone distros are shipped with Sphinx 1.1.x,
> with is incompatible with Kernel ReST markups.
>
> So, on those systems, the only alternative is to install
> it via a Python virtual environment.
>
> While seeking for
On Mon, 24 Jul 2017 17:27:05 +0200
Sedat Dilek wrote:
> The old example to describe ccflags-y usage is no more valid.
>
> Signed-off-by: Sedat Dilek
I've applied this; had to clean up some whitespace weirdness on the way.
Thanks,
jon
--
To unsubscribe from this list: send the line "unsubscri
On Fri, 4 Aug 2017 11:28:39 +0100
James Hogan wrote:
> Since commit 64e2a42bca12 ("parisc: Add ARCH_TRACEHOOK and regset
> support") in v4.7, parisc selects HAVE_ARCH_TRACEHOOK, so update its
> entry in Documentation/features from TODO to ok.
Applied to the docs tree, thanks.
jon
--
To unsubscr
On 08/07/2017 02:47 PM, John Stultz wrote:
> On Mon, Aug 7, 2017 at 11:04 AM, Prarit Bhargava wrote:
>> On 08/07/2017 12:52 PM, John Stultz wrote:
>>> Still not quite following why you're updating all the defconfigs. I'd
>>> make sure the Kconfig default settings are right, and leave updating
>>
On Mon, Aug 7, 2017 at 11:04 AM, Prarit Bhargava wrote:
> On 08/07/2017 12:52 PM, John Stultz wrote:
>> Still not quite following why you're updating all the defconfigs. I'd
>> make sure the Kconfig default settings are right, and leave updating
>> the defconfig to arch/device maintainers. It adds
On 08/07/2017 01:14 PM, Luis R. Rodriguez wrote:
>
> Note printk_late_init() is a late_initcall(). This means if the
> printk_time_setting was disabled it will take a while to enable it. Enabling
> it
> is done at the device_initcall(), so if printk setting is disabled but a user
> enables it
On 08/07/2017 12:58 PM, Mark Salyzyn wrote:
> On 08/07/2017 08:52 AM, Prarit Bhargava wrote:
>> diff --git a/arch/arm/configs/aspeed_g4_defconfig
>> b/arch/arm/configs/aspeed_g4_defconfig
>> index cfc2465e8b77..5f3c50914e92 100644
>> --- a/arch/arm/configs/aspeed_g4_defconfig
>> +++ b/arch/arm/co
On 08/07/2017 12:52 PM, John Stultz wrote:
> On Mon, Aug 7, 2017 at 8:52 AM, Prarit Bhargava wrote:
>> printk.time=1/CONFIG_PRINTK_TIME=1 adds a unmodified local hardware clock
>> timestamp to printk messages. The local hardware clock loses time each
>> day making it difficult to determine exac
On Mon, Aug 07, 2017 at 11:52:42AM -0400, Prarit Bhargava wrote:
> +static u64 printk_get_ts(void)
> +{
> + u64 mono, offset_real;
> +
> + if (printk_time <= PRINTK_TIME_LOCAL)
> + return local_clock();
> +
> + if (printk_time == PRINTK_TIME_BOOT)
> + return ktim
On Mon, Aug 07, 2017 at 09:52:10AM -0700, John Stultz wrote:
> On Mon, Aug 7, 2017 at 8:52 AM, Prarit Bhargava wrote:
> > +u64 ktime_get_real_log_ts(u64 *offset_real)
> > +{
> > + *offset_real = ktime_to_ns(tk_core.timekeeper.offs_real);
> > +
> > + if (timekeeping_active)
> > +
On Thu, Aug 03, 2017 at 09:18:44PM -0400, Prarit Bhargava wrote:
> index fc47863f629c..8f093dd0a733 100644
> --- a/kernel/printk/printk.c
> +++ b/kernel/printk/printk.c
> @@ -1202,8 +1204,119 @@ static inline void boot_delay_msec(int level)
> }
> #endif
>
> -static bool printk_time = IS_ENABLED
On 08/07/2017 08:52 AM, Prarit Bhargava wrote:
diff --git a/arch/arm/configs/aspeed_g4_defconfig
b/arch/arm/configs/aspeed_g4_defconfig
index cfc2465e8b77..5f3c50914e92 100644
--- a/arch/arm/configs/aspeed_g4_defconfig
+++ b/arch/arm/configs/aspeed_g4_defconfig
@@ -162,7 +162,7 @@ CONFIG_JFFS2_F
On Mon, Aug 7, 2017 at 8:52 AM, Prarit Bhargava wrote:
> printk.time=1/CONFIG_PRINTK_TIME=1 adds a unmodified local hardware clock
> timestamp to printk messages. The local hardware clock loses time each
> day making it difficult to determine exactly when an issue has occurred in
> the kernel log
On 08/07/2017 09:31 AM, Yubin Ruan wrote:
> Hi, I am wondering whether there is any progress for NPTL. In page[1]
> I see lots of pthread-related pages are missing. Pretty shocked by
> that.
>
> Are there any plan for that? Who is the maintainer of NPTL? Why are
> such an important lib missing man
Hi, I am wondering whether there is any progress for NPTL. In page[1]
I see lots of pthread-related pages are missing. Pretty shocked by
that.
Are there any plan for that? Who is the maintainer of NPTL? Why are
such an important lib missing manual pages?
[1]: https://www.kernel.org/doc/man-pages/
printk.time=1/CONFIG_PRINTK_TIME=1 adds a unmodified local hardware clock
timestamp to printk messages. The local hardware clock loses time each
day making it difficult to determine exactly when an issue has occurred in
the kernel log, and making it difficult to determine how kernel and
hardware i
On (08/07/17 08:41), Prarit Bhargava wrote:
[..]
> >> +static int printk_time_set(const char *val, const struct kernel_param *kp)
> >> +{
> >> +char *param = strstrip((char *)val);
> >> +int _printk_time;
> >> +
> >> +if (strlen(param) != 1)
> >> +return -EINVAL;
> > (see below)
On Sun, Aug 6, 2017 at 4:00 PM, Ludovic Desroches
wrote:
> Update deprecated references to Documentation/pinctrl.txt since it has been
> moved to Documentation/driver-api/pinctl.rst.
>
> Signed-off-by: Ludovic Desroches
> Fixes: 5a9b73832e9e ("pinctrl.txt: move it to the driver-api book")
Patch
Hello.
On 08/06/2017 06:28 PM, Jian-Hong Pan wrote:
The function declaration in the lastest include/net/mac802154.h has been
changed since v3.19.
ieee802154_alloc_device => ieee802154_alloc_hw
ieee802154_free_device => ieee802154_free_hw
ieee802154_register_device => ieee802154_register_hw
ieee
On 08/04/2017 11:36 AM, Mark Salyzyn wrote:
> On 08/03/2017 06:18 PM, Prarit Bhargava wrote:
>
>> diff --git a/arch/arm/configs/aspeed_g4_defconfig
>> b/arch/arm/configs/aspeed_g4_defconfig
>> index cfc2465e8b77..6c73c305ad17 100644
>> --- a/arch/arm/configs/aspeed_g4_defconfig
>> +++ b/arch/arm
Hi Mark/Will,
Appreciate your comments.
Thanks.
Shaokun
On 2017/7/25 20:10, Shaokun Zhang wrote:
> This patchset adds support for HiSilicon SoC uncore PMUs driver. It
> includes L3C, Hydra Home Agent (HHA) and DDRC.
>
> Changes in v4:
> * remove redundant code and comments
> * reverse the funct
26 matches
Mail list logo
