Hey Konrad,
it looks like you forgot about this.
Cheers,
Stefano
On Fri, 18 Nov 2016, Konrad Rzeszutek Wilk wrote:
> That way we have one person who can: a) poke other maintainers
> or pull them in with new drivers are introduced, b) we have
> one maintainer who can shepherd the patches along i
>>> On 18.11.16 at 18:45, wrote:
> On Fri, Nov 18, 2016 at 10:06:59AM -0700, Jan Beulich wrote:
>> >>> On 18.11.16 at 17:18, wrote:
>> > --- a/MAINTAINERS
>> > +++ b/MAINTAINERS
>> > @@ -304,6 +304,11 @@ X:xen/arch/x86/acpi/lib.c
>> > F:xen/drivers/cpufreq/
>> > F:xen/includ
On 18/11/16 17:57, Stefano Stabellini wrote:
> On Fri, 18 Nov 2016, Konrad Rzeszutek Wilk wrote:
>> On Fri, Nov 18, 2016 at 10:06:59AM -0700, Jan Beulich wrote:
>> On 18.11.16 at 17:18, wrote:
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -304,6 +304,11 @@ X:xen/arch/x86/acpi/lib.c
On Fri, 18 Nov 2016, Konrad Rzeszutek Wilk wrote:
> On Fri, Nov 18, 2016 at 10:06:59AM -0700, Jan Beulich wrote:
> > >>> On 18.11.16 at 17:18, wrote:
> > > --- a/MAINTAINERS
> > > +++ b/MAINTAINERS
> > > @@ -304,6 +304,11 @@ X: xen/arch/x86/acpi/lib.c
> > > F: xen/drivers/cpufreq/
> > >
On Fri, 18 Nov 2016, Stefano Stabellini wrote:
> On Fri, 18 Nov 2016, Konrad Rzeszutek Wilk wrote:
> > On Fri, Nov 18, 2016 at 10:06:59AM -0700, Jan Beulich wrote:
> > > >>> On 18.11.16 at 17:18, wrote:
> > > > --- a/MAINTAINERS
> > > > +++ b/MAINTAINERS
> > > > @@ -304,6 +304,11 @@ X: xen/arch/x8
On Fri, Nov 18, 2016 at 10:06:59AM -0700, Jan Beulich wrote:
> >>> On 18.11.16 at 17:18, wrote:
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -304,6 +304,11 @@ X: xen/arch/x86/acpi/lib.c
> > F: xen/drivers/cpufreq/
> > F: xen/include/acpi/cpufreq/
> >
> > +PUBLIC INTERFACES
> > +M: K
>>> On 18.11.16 at 17:18, wrote:
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -304,6 +304,11 @@ X: xen/arch/x86/acpi/lib.c
> F: xen/drivers/cpufreq/
> F: xen/include/acpi/cpufreq/
>
> +PUBLIC INTERFACES
> +M: Konrad Rzeszutek Wilk
> +S: Supported
> +F: xen/include/public/
I thin
On Fri, Nov 18, 2016 at 11:18:24AM -0500, Konrad Rzeszutek Wilk wrote:
> That way we have one person who can: a) poke other maintainers
> or pull them in with new drivers are introduced, b) we have
> one maintainer who can shepherd the patches along instead of
> depending on the REST maintainers wh
On Fri, Nov 18, 2016 at 11:18:24AM -0500, Konrad Rzeszutek Wilk wrote:
> That way we have one person who can: a) poke other maintainers
> or pull them in with new drivers are introduced, b) we have
> one maintainer who can shepherd the patches along instead of
> depending on the REST maintainers wh
On 18/11/16 16:18, Konrad Rzeszutek Wilk wrote:
> That way we have one person who can: a) poke other maintainers
> or pull them in with new drivers are introduced, b) we have
> one maintainer who can shepherd the patches along instead of
> depending on the REST maintainers which may be busy with
>
That way we have one person who can: a) poke other maintainers
or pull them in with new drivers are introduced, b) we have
one maintainer who can shepherd the patches along instead of
depending on the REST maintainers which may be busy with
other responsibilities.
Signed-off-by: Konrad Rzeszutek W
11 matches
Mail list logo
