Thorsten Leemhuis writes:
> Hi! A mailing list for regressions was finally created as
> regressi...@lists.linux.dev (we dropped the linux- prefix as the term is
> already
> in the domain name). Hence, add it to MAINTAINERS, as that where people will
> look it up. I was a bi
On Fri, Apr 09, 2021 at 01:47:23PM +0200, Thorsten Leemhuis wrote:
> Add the newly created regression mailing list finally created after it
> already had been agreed on during the maintainers summit 2017 (see
> https://lwn.net/Articles/738216/ ). The topic was recently discussed
> aga
Hi! A mailing list for regressions was finally created as
regressi...@lists.linux.dev (we dropped the linux- prefix as the term is already
in the domain name). Hence, add it to MAINTAINERS, as that where people will
look it up. I was a bit unsure how to actually do that, see the note in the
first
Add the newly created regression mailing list finally created after it
already had been agreed on during the maintainers summit 2017 (see
https://lwn.net/Articles/738216/ ). The topic was recently discussed
again, where an idea to create a broader list for all issues was
discussed, but Linus
On 07.04.21 16:56, Greg KH wrote:
> On Wed, Apr 07, 2021 at 12:51:43PM +0200, Thorsten Leemhuis wrote:
>> On 07.04.21 11:56, Greg KH wrote:
>>> On Wed, Apr 07, 2021 at 11:21:55AM +0200, Thorsten Leemhuis wrote:
>>>> Add the newly created regression mailing
On Wed, Apr 07, 2021 at 12:51:43PM +0200, Thorsten Leemhuis wrote:
> On 07.04.21 11:56, Greg KH wrote:
> > On Wed, Apr 07, 2021 at 11:21:55AM +0200, Thorsten Leemhuis wrote:
> >> Add the newly created regression mailing list finally created after it
> >> already ha
On 07.04.21 11:56, Greg KH wrote:
> On Wed, Apr 07, 2021 at 11:21:55AM +0200, Thorsten Leemhuis wrote:
>> Add the newly created regression mailing list finally created after it
>> already had been agreed on during the maintainers summit 2017 (see
>> https://lwn.net/Articles
On Wed, Apr 07, 2021 at 11:21:55AM +0200, Thorsten Leemhuis wrote:
> Add the newly created regression mailing list finally created after it
> already had been agreed on during the maintainers summit 2017 (see
> https://lwn.net/Articles/738216/ ). The topic was recently discussed
> aga
Hi! A mailing list for regressions was finally created as
regressi...@lists.linux.dev (we dropped the linux- prefix as the term is already
in the domain name). Hence, add it to MAINTAINERS, as that where people will
look it up. I was a bit unsure how to actually do that, see the note in the
first
Add the newly created regression mailing list finally created after it
already had been agreed on during the maintainers summit 2017 (see
https://lwn.net/Articles/738216/ ). The topic was recently discussed
again, where an idea to create a broader list for all issues was
discussed, but Linus
Em Mon, Mar 15, 2021 at 11:56:32AM +0800, Tiezhu Yang escreveu:
> Add entry "L: linux-perf-us...@vger.kernel.org" to archive the
> related mail on https://lore.kernel.org/linux-perf-users/, add
> entry "W: https://perf.wiki.kernel.org/"; so that newbies could
> get some useful materials.
Thanks, a
re the
> > > boxes that catch the most issues, and if they do, they are pretty
> > > much guaranteed to be a regression.
> > >
> > > I like the "linux-regressions" mailing list idea.
> >
> > Can't we use the fancy features of public inb
they do, they are pretty
> > much guaranteed to be a regression.
> >
> > I like the "linux-regressions" mailing list idea.
>
> Can't we use the fancy features of public inbox to get the best of both
> worlds? Have the bug list (or even a collection of lists)
On 23.03.21 16:01, Konstantin Ryabitsev wrote:
> On Tue, 23 Mar 2021 at 04:58, Thorsten Leemhuis wrote:
>>> If we can
>>> actually get users to *read* it, I think it's going to save kernel
>>> developers a huge amount of time and frustration.
>> And users hopefully as well. But yes, making them r
d) check the text
from their point of view (above patchset changes quite a few things in
that area, that's why it needs to be applied first)
* get feedback reg. the two FIXME boxes remaining afterwards. One is
about bugzilla (```The old text took a totally different approach to
bugzilla.kernel.
On Tue, Mar 23, 2021 at 09:57:57AM +0100, Thorsten Leemhuis wrote:
> On 22.03.21 22:56, Theodore Ts'o wrote:
> > On Mon, Mar 22, 2021 at 08:25:15PM +0100, Thorsten Leemhuis wrote:
> >> I agree to the last point and yeah, maybe regressions are the more
> >> important problem we should work on – at l
On Tue, Mar 23, 2021 at 12:20:25PM -0400, Steven Rostedt wrote:
> On Mon, 22 Mar 2021 20:25:15 +0100
> Thorsten Leemhuis wrote:
>
> > I agree to the last point and yeah, maybe regressions are the more
> > important problem we should work on – at least from the perspective of
> > kernel developmen
on of a regression. My test
> boxes still run old distros (one is running fedora 13). These are the
> boxes that catch the most issues, and if they do, they are pretty
> much guaranteed to be a regression.
>
> I like the "linux-regressions" mailing list idea.
Can't
es, and if
they do, they are pretty much guaranteed to be a regression.
I like the "linux-regressions" mailing list idea.
-- Steve
On Tue, 23 Mar 2021 at 04:58, Thorsten Leemhuis wrote:
> > If we can
> > actually get users to *read* it, I think it's going to save kernel
> > developers a huge amount of time and frustration.
>
> And users hopefully as well. But yes, making them read it is the
> problem. :-/
I've added a very
On Mon, Mar 22, 2021 at 1:25 PM Thorsten Leemhuis wrote:
>
>
>
> On 22.03.21 19:32, Linus Torvalds wrote:
> > On Mon, Mar 22, 2021 at 8:18 AM Thorsten Leemhuis
> > wrote:
> >>
> >> I even requested a
> >> "linux-regressi...@vger.kernel.org" a while later, but didn't hear
> >> anything back;
On 22.03.21 22:56, Theodore Ts'o wrote:
> On Mon, Mar 22, 2021 at 08:25:15PM +0100, Thorsten Leemhuis wrote:
>> I agree to the last point and yeah, maybe regressions are the more
>> important problem we should work on – at least from the perspective of
>> kernel development. But from the users per
On Mon, Mar 22, 2021 at 08:25:15PM +0100, Thorsten Leemhuis wrote:
> I agree to the last point and yeah, maybe regressions are the more
> important problem we should work on – at least from the perspective of
> kernel development. But from the users perspective (and
> reporting-issues.rst is writt
tiple times has known downsides for everyone
>> involved. That's why I propose to create this new mailing list:
>>
>> linux-iss...@lists.linux.dev
>>
>> Developers and users reporting or handling issues then can CC it or
>> search it via lore. But this will on
On 22.03.21 19:32, Linus Torvalds wrote:
> On Mon, Mar 22, 2021 at 8:18 AM Thorsten Leemhuis wrote:
>>
>> I even requested a
>> "linux-regressi...@vger.kernel.org" a while later, but didn't hear
>> anything back; and, sadly, about the same time I started having trouble
>> finding spare time
On Mon, Mar 22, 2021 at 07:55:29PM +0100, Thorsten Leemhuis wrote:
> Out of curiosity: will that work for other bug trackers as well? Like
> the gitlab instance used by the drm developers? It's not really
> important and I guess the answer will be "no", but the question came up
> while at it...
If
On 22.03.21 19:34, Eric Wong wrote:
> James Bottomley wrote:
>> On Mon, 2021-03-22 at 13:16 -0400, Konstantin Ryabitsev wrote:
>>> On Mon, Mar 22, 2021 at 04:18:14PM +0100, Thorsten Leemhuis wrote:
Note, there is a second reason why ksummit-discuss is CCed: another
reason why I want to c
James Bottomley wrote:
> On Mon, 2021-03-22 at 13:16 -0400, Konstantin Ryabitsev wrote:
> > On Mon, Mar 22, 2021 at 04:18:14PM +0100, Thorsten Leemhuis wrote:
> > > Note, there is a second reason why ksummit-discuss is CCed: another
> > > reason why I want to create this new list is making it easi
On Mon, Mar 22, 2021 at 8:18 AM Thorsten Leemhuis wrote:
>
> I even requested a
> "linux-regressi...@vger.kernel.org" a while later, but didn't hear
> anything back; and, sadly, about the same time I started having trouble
> finding spare time for working on regression tracking. :-/
Honestly,
On Mon, 2021-03-22 at 13:16 -0400, Konstantin Ryabitsev wrote:
> On Mon, Mar 22, 2021 at 04:18:14PM +0100, Thorsten Leemhuis wrote:
> > Note, there is a second reason why ksummit-discuss is CCed: another
> > reason why I want to create this new list is making it easier to
> > find and track regress
On Mon, Mar 22, 2021 at 04:18:14PM +0100, Thorsten Leemhuis wrote:
> Note, there is a second reason why ksummit-discuss is CCed: another
> reason why I want to create this new list is making it easier to find
> and track regressions reported to our various mailing lists (often
> without LKML in CC,
; involved. That's why I propose to create this new mailing list:
>
> linux-iss...@lists.linux.dev
>
> Developers and users reporting or handling issues then can CC it or
> search it via lore. But this will only fly if the idea has buy-in from
> at least the core kern
Lo! I want to provide users with an easier way to search our multitude
of mailing lists for reports about issues (aka bugs), as reporting the
same kernel problem multiple times has known downsides for everyone
involved. That's why I propose to create this new mailing list:
linu
From: Greg Kroah-Hartman
commit f8d70fd6a5a7a38a95eb8021e00d2e547f88efec upstream.
The VME and Android drivers still have their MAINTAINERS entries
pointing to the "driverdevel" mailing list, due to them having their
codebase move out of the drivers/staging/ directory, but no one
rem
From: Greg Kroah-Hartman
commit f8d70fd6a5a7a38a95eb8021e00d2e547f88efec upstream.
The VME and Android drivers still have their MAINTAINERS entries
pointing to the "driverdevel" mailing list, due to them having their
codebase move out of the drivers/staging/ directory, but no one
rem
Hi,
I just want to know which is the right and active mailing list for
contributing and discussing about rt-linux and preempt-rt related
changes.
Thanks,
Pintu
Hi all,
After almost 14 years of being hosted by OSUOSL, the driverdev mailing
list is moving to lists.linux.dev. This should help out with the
occasional mailman issues that driverdev had at times, and is one of the
first lists to help stress-test the new linux.dev mailing lists
infrastructure
Add entry "L: linux-perf-us...@vger.kernel.org" to archive the
related mail on https://lore.kernel.org/linux-perf-users/, add
entry "W: https://perf.wiki.kernel.org/"; so that newbies could
get some useful materials.
Signed-off-by: Tiezhu Yang
---
MAINTAINERS | 2 ++
1 file changed, 2 insertions
The VME and Android drivers still have their MAINTAINERS entries
pointing to the "driverdevel" mailing list, due to them having their
codebase move out of the drivers/staging/ directory, but no one
remembered to change the mailing list entries.
Move them both to linux-kernel for lack
Mark the acrn-dev mailing list as subscribers-only.
Evidence from a previous patch:
acrn-...@lists.projectacrn.org
SMTP error from remote mail server after end of data:
510 5.1.1 Your email address, rdun...@infradead.org, is not subscribed to
that group.
Signed-off-by: Randy Dunlap
rg/pipermail|
> > > + marc.info|
> > > + ozlabs.org/pipermail|
> > > + spinics.net
> > > +)};
> >
> > Strictly, these all need \Q \E escaping so uses like lkmlAorg do not match.
> >
> >
> > > @@ -3101,6 +3112,12 @@ sub process
; > + lists.infradead.org|
> > + lkml.org|
> > + mail-archive.com|
> > + mailman.alsa-project.org/pipermail|
> > + marc.info|
> > + ozlabs.org/pipermail|
> > + spinics.net
> > +)};
>
> Strictly, these all need \Q \E escaping so uses lik
On Wed, 2020-12-23 at 02:50 +, patchwork-bot+netdev...@kernel.org
wrote:
> Hello:
>
> This patch was applied to netdev/net.git (refs/heads/master):
>
> On Sat, 19 Dec 2020 10:55:38 -0800 you wrote:
> > When searching for inactive maintainers it's useful to f
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Sat, 19 Dec 2020 10:55:38 -0800 you wrote:
> When searching for inactive maintainers it's useful to filter
> out mailing list addresses. Such "maintainers" will obviously
> never feature in a "
On 2020-12-19 10:55, Jakub Kicinski wrote:
When searching for inactive maintainers it's useful to filter
out mailing list addresses. Such "maintainers" will obviously
never feature in a "From:" line of an email or a review tag.
Since "L:" entries only pr
When searching for inactive maintainers it's useful to filter
out mailing list addresses. Such "maintainers" will obviously
never feature in a "From:" line of an email or a review tag.
Since "L:" entries only provide the address of a mailing list
without a f
labs.org/pipermail|
> + spinics.net
> +)};
Strictly, these all need \Q \E escaping so uses like lkmlAorg do not match.
> @@ -3101,6 +3112,12 @@ sub process {
> }
> }
>
> +# Check for mailing list archives other than lore.kernel
|
+ mailman.alsa-project.org/pipermail|
+ marc.info|
+ ozlabs.org/pipermail|
+ spinics.net
+)};
+
our @typeListMisordered = (
qr{char\s+(?:un)?signed},
qr{int\s+(?:(?:un)?signed\s+)?short\s},
@@ -3101,6 +3112,12 @@ sub process {
}
On Thu, Oct 29, 2020 at 04:44:14PM +0100, Krzysztof Kozlowski wrote:
> The entries for JZ47xx SoCs and its drivers lacked MIPS mailing list.
> Only MTD NAND driver pointed linux-mtd. Add linux-mips so the relevant
> patches will get attention of MIPS developers.
>
> Signed-of
The entries for JZ47xx SoCs and its drivers lacked MIPS mailing list.
Only MTD NAND driver pointed linux-mtd. Add linux-mips so the relevant
patches will get attention of MIPS developers.
Signed-off-by: Krzysztof Kozlowski
Acked-by: Paul Cercueil
---
Changes since v1:
1. Do not update DMA
As more email from git history gets aimed at the OpenWall
kernel-hardening@ list, there has been a desire to separate "new topics"
from "on-going" work. To handle this, the superset of hardening email
topics are now to be directed to linux-harden...@vger.kernel.org. Update
the MAINTAINERS file and
From: Nick Desaulniers
Date: Mon, 5 Oct 2020 10:50:35 -0700
> Now that the lore archive has been set up
> (https://lore.kernel.org/linux-toolchains/), would you mind linking to
> it from http://vger.kernel.org/vger-lists.html under archives of
> linux-toolchains?
Done.
On Mon, Oct 05, 2020 at 04:19:49PM -0700, Randy Dunlap wrote:
> On 10/5/20 3:53 PM, Kees Cook wrote:
> > As more email from git history gets aimed at the OpenWall
> > kernel-hardening@ list, there has been a desire to separate "new topics"
> > from "on-going" work. To handle this, the superset of h
On 10/5/20 3:53 PM, Kees Cook wrote:
> As more email from git history gets aimed at the OpenWall
> kernel-hardening@ list, there has been a desire to separate "new topics"
> from "on-going" work. To handle this, the superset of hardening email
> topics are now to be directed to linux-harden...@vger
As more email from git history gets aimed at the OpenWall
kernel-hardening@ list, there has been a desire to separate "new topics"
from "on-going" work. To handle this, the superset of hardening email
topics are now to be directed to linux-harden...@vger.kernel.org. Update
the MAINTAINTERS file and
am subscribed, too.
> > >>
> > >> Will there be a(n)...?
> > >>
> > >> * archive (for example marc.info)
> > >
> > > A lore archive would be good?
> >
> > That has already been requested.
>
> Hi David,
> Thank
>>> Date: Wed, 30 Sep 2020 12:29:38 -0700
> >>>> linux-toolcha...@vger.kernel.org
> >>>
> >>> Created.
> >>
> >> I am subscribed, too.
> >>
> >> Will there be a(n)...?
> >>
> >> * archive (for example
On 10/2/20 10:22 AM, Segher Boessenkool wrote:
> On Fri, Oct 02, 2020 at 02:01:13PM +0200, Sedat Dilek wrote:
>> On Thu, Oct 1, 2020 at 12:26 AM David Miller wrote:
>>> From: Nick Desaulniers
>>> Date: Wed, 30 Sep 2020 12:29:38 -0700
linux-toolcha...@vger.kernel.org
>>>
>>> Created.
>>
>> I
On Fri, Oct 02, 2020 at 02:01:13PM +0200, Sedat Dilek wrote:
> On Thu, Oct 1, 2020 at 12:26 AM David Miller wrote:
> > From: Nick Desaulniers
> > Date: Wed, 30 Sep 2020 12:29:38 -0700
> > > linux-toolcha...@vger.kernel.org
> >
> > Created.
>
> I am subscribed, too.
>
> Will there be a(n)...?
>
On Thu, Oct 1, 2020 at 12:26 AM David Miller wrote:
>
> From: Nick Desaulniers
> Date: Wed, 30 Sep 2020 12:29:38 -0700
>
> > linux-toolcha...@vger.kernel.org
>
> Created.
>
I am subscribed, too.
Will there be a(n)...?
* archive (for example marc.info)
* patchwork url
- Sedat -
[1] https://gi
Hi Guys,
>> linux-toolcha...@vger.kernel.org
> Created.
I have been able to subscribe to this list, so it looks like thunderbirds are
go...
Cheers
Nick
From: Nick Desaulniers
Date: Wed, 30 Sep 2020 12:29:38 -0700
> linux-toolcha...@vger.kernel.org
Created.
Hi David,
Apologies if this request has crossed your desk already; I know my
unreads in my inbox seems to have doubled this week somehow...(should
I send them all to /dev/null? I think I should.)
>From Linux Plumbers conf Binutils BoF, Peter had the idea of setting a
toolchain agnostic email list,
On Wed, Sep 30, 2020 at 10:25:40AM -0700, Nick Desaulniers wrote:
> Does anyone know who's behind postmas...@vger.kernel.org? Maybe I can
> email them directly if perhaps they don't check this email often?
> (Benefit of the doubt)
davem iirc.
Does anyone know who's behind postmas...@vger.kernel.org? Maybe I can
email them directly if perhaps they don't check this email often?
(Benefit of the doubt)
On Tue, Sep 15, 2020 at 1:49 PM Nick Desaulniers
wrote:
>
> Hello postmaster,
> Any thoughts on linux-toolcha...@vger.kernel.org?
>
> On
Add CoreSight mailing list so that people can participate in patch
reviews and know what features are coming next.
Signed-off-by: Mathieu Poirier
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 286fd7263982..54cb47e8a0b2 100644
--- a
Hello postmaster,
Any thoughts on linux-toolcha...@vger.kernel.org?
On Wed, Aug 26, 2020 at 3:14 AM Nick Clifton wrote:
>
> Hi Guys,
>
> Would it be possible to setup:
> linux-tool...@vger.kernel.org
>
> >>> s/linux-tooling/linux-toolchains (better plural toolchains)
>
> >> FWIW FreeBSD
>
> I've created phone-de...@vger.kernel.org
Thank you!
Pavel
I've created phone-de...@vger.kernel.org
could use as a _phone_, running mainline
> kernel. So far N900 with original Maemo is closest I could get.
>
> Would it be possible to create a mailing list on vger.kernel.org?
Hm. My experience with asking for creating an openpvrsgx mailing list
at vger.kernel.org was like asking the s
* Bhaskar Chowdhury [200908 23:08]:
> On 00:56 Wed 09 Sep 2020, Pavel Machek wrote:
> > Would it be possible to create a mailing list on vger.kernel.org?
> > Probably phones@ or phone-devel@? I believe it would be useful to
> > cover hardware-dependend pieces of t
se as a _phone_, running mainline
kernel. So far N900 with original Maemo is closest I could get.
Would it be possible to create a mailing list on vger.kernel.org?
Probably phones@ or phone-devel@? I believe it would be useful to
cover hardware-dependend pieces of the phone stack (ofono,
modemmana
0 with original Maemo is closest I could get.
Would it be possible to create a mailing list on vger.kernel.org?
Probably phones@ or phone-devel@? I believe it would be useful to
cover hardware-dependend pieces of the phone stack (ofono,
modemmanager) as well as kernel
The entries for JZ47xx SoCs and its drivers lacked MIPS mailing list.
Only MTD NAND driver pointed linux-mtd. Add linux-mips so the relevant
patches will get attention of MIPS developers.
Signed-off-by: Krzysztof Kozlowski
Acked-by: Paul Cercueil
---
Changes since v1:
1. Do not update DMA
The entries for JZ47xx SoCs and its drivers lacked MIPS mailing list.
Only MTD NAND driver pointed linux-mtd. Add linux-mips so the relevant
patches will get attention of MIPS developers.
Signed-off-by: Krzysztof Kozlowski
Acked-by: Paul Cercueil
---
Changes since v1:
1. Do not update DMA
Hi Krzysztof,
Le ven. 24 juil. 2020 à 17:58, Krzysztof Kozlowski a
écrit :
The entries for JZ47xx SoCs and its drivers lacked MIPS mailing list.
Only MTD NAND driver pointed linux-mtd. Add linux-mips so the
relevant
patches will get attention of MIPS developers.
Signed-off-by: Krzysztof
The entries for JZ47xx SoCs and its drivers lacked MIPS mailing list.
Only MTD NAND driver pointed linux-mtd. Add linux-mips so the relevant
patches will get attention of MIPS developers.
Signed-off-by: Krzysztof Kozlowski
---
MAINTAINERS | 3 +++
1 file changed, 3 insertions(+)
diff --git a
Hello arm-soc maintainers,
Please pull this patch updatating the TEE mailing list to
op-...@lists.trustedfirmware.org.
Thanks,
Jens
The following changes since commit b3a9e3b9622ae10064826dccb4f7a52bd88c7407:
Linux 5.8-rc1 (2020-06-14 12:45:04 -0700)
are available in the Git repository at
On Mon, 15 Jun 2020 at 18:49, Jens Wiklander wrote:
>
> The old TEE mailing list tee-...@lists.linaro.org is about to be
> retired. From now on please use op-...@lists.trustedfirmware.org
> instead.
>
> Signed-off-by: Jens Wiklander
> ---
> MAINTAINERS | 6 +++---
> 1
The old TEE mailing list tee-...@lists.linaro.org is about to be
retired. From now on please use op-...@lists.trustedfirmware.org
instead.
Signed-off-by: Jens Wiklander
---
MAINTAINERS | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index
Am 19.10.19 um 16:13 schrieb Andreas Färber:
> Document linux-realtek-soc mailing list to be CC'ed on patches.
>
> Signed-off-by: Andreas Färber
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index c
Document linux-realtek-soc mailing list to be CC'ed on patches.
Signed-off-by: Andreas Färber
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index c7b48525822a..8be71b3d25e7 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2168,6 +2168,7
From: Guo Ren
Add mailing list and it's convenient for maintain C-SKY
subsystem.
Signed-off-by: Guo Ren
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 55199ef..d8fc16d 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -3556,6 +3556,7
Both MESON AO CEC and MESON VIDEO DECODER point to the wrong linux-media
mailing list. Update it to linux-me...@vger.kernel.org.
Signed-off-by: Maxime Jourdan
---
MAINTAINERS | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index ad2bf808b02c
From: Guo Ren
Add the newly created linux-c...@vger.kernel.org mailing list for patch
reviews and discussions.
Signed-off-by: Guo Ren
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 5cfbea4..b5fadcc 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
On Thu, May 9, 2019 at 11:33 AM Sumit Garg wrote:
>
> On Wed, 8 May 2019 at 15:44, Sumit Garg wrote:
> >
> > Add a mailing list for patch reviews and discussions related to TEE
> > subsystem.
> >
> > Signed-off-by: Sumit Garg
>
> I forgot to include fol
From: Guo Ren
Add the newly created linux-c...@vger.kernel.org mailing list for patch
reviews and discussions.
Signed-off-by: Guo Ren
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 5cfbea4..b5fadcc 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
On Wed, 8 May 2019 at 15:44, Sumit Garg wrote:
>
> Add a mailing list for patch reviews and discussions related to TEE
> subsystem.
>
> Signed-off-by: Sumit Garg
I forgot to include following tag as this change was suggested by Daniel. So:
Suggested-by: Daniel Th
Add a mailing list for patch reviews and discussions related to TEE
subsystem.
Signed-off-by: Sumit Garg
---
MAINTAINERS | 3 +++
1 file changed, 3 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 920a0a1..c05dff7 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -11556,11 +11556,13 @@ F
iang
>
> Neil
>
> >
> > Regards,
> > Qiang
> >
> > On Mon, Apr 8, 2019 at 3:12 AM Randy Dunlap wrote:
> >>
> >> From: Randy Dunlap
> >>
> >> Note that the lima mailing list is moderated.
> >>
> >> Signed-off-
Add a mailing list for patch reviews and discussions related to tuning
the on-chip interconnects. For now i am not expecting a lot of traffic,
so let's use the linux-pm@ list.
Acked-by: Rafael J. Wysocki
Signed-off-by: Georgi Djakov
---
Hi Greg,
Can you please pick this fix for the
On Thursday, March 21, 2019 4:50:50 PM CET Georgi Djakov wrote:
> Add a mailing list for patch reviews and discussions related to tuning
> the on-chip interconnects. For now i am not expecting a lot of traffic,
> so let's use the linux-pm@ list.
>
> Signed-off-by: Georgi Djako
Add a mailing list for patch reviews and discussions related to tuning
the on-chip interconnects. For now i am not expecting a lot of traffic,
so let's use the linux-pm@ list.
Signed-off-by: Georgi Djakov
---
Hi Rafael,
Please ack the patch if you don't mind this.
Thanks!
MAINTAINER
t up. :)
I'm all open here. Not sure which practices apply to IMA. I kind of tend
to dilate to question does it make sense to CC to LSM for two reasons:
1. I think the original reason was that tpmdd mailing list was small.
Now with the new linux-integrity mailing list up and running there
> I'm all open here. Not sure which practices apply to IMA. I kind of tend
> to dilate to question does it make sense to CC to LSM for two reasons:
>
> 1. I think the original reason was that tpmdd mailing list was small.
> Now with the new linux-integrity mailing list up and r
From: Haiyang Zhang
The new mailing list is: linux-hyp...@vger.kernel.org
Signed-off-by: Haiyang Zhang
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 86aa227b5782..403d6e4b8257 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
From: Haiyang Zhang
The new mailing list is: linux-hyp...@vger.kernel.org
Signed-off-by: Haiyang Zhang
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 86aa227b5782..ef65de3cfe1b 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -7137,6 +7137,7
[PATCH] MAINTAINERS: Add mailing list for Hyper-V CORE AND
> DRIVERS
>
> On Wed, Feb 20, 2019 at 07:48:23PM +, Haiyang Zhang wrote:
> > From: Haiyang Zhang
> >
> > The new mailing list is: linux-hyp...@vger.kernel.org
> >
> > Signed-off-by: Haiyang Zhang
On Wed, Feb 20, 2019 at 07:48:23PM +, Haiyang Zhang wrote:
> From: Haiyang Zhang
>
> The new mailing list is: linux-hyp...@vger.kernel.org
>
> Signed-off-by: Haiyang Zhang
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/MAI
ike it was a general request.
> If it is, I'll be more likely to remember if get_maintainers.pl
> brings it up. :)
I'm all open here. Not sure which practices apply to IMA. I kind of tend
to dilate to question does it make sense to CC to LSM for two reasons:
1. I think the original r
1 - 100 of 429 matches
Mail list logo
