* [PATCH] staging: bcm2835-audio: Fixed spacing around '&' @ 2017-02-26 17:47 ` Narcisa Ana Maria Vasile 0 siblings, 0 replies; 24+ messages in thread From: Narcisa Ana Maria Vasile @ 2017-02-26 17:47 UTC (permalink / raw) To: swarren, lee, eric, f.fainelli, rjui, sbranden Cc: daniel.baluta, gregkh, outreachy-kernel, bcm-kernel-feedback-list, mzoran, danielperezdeandres, dan.carpenter, devel, linux-rpi-kernel, linux-arm-kernel, linux-kernel, Narcisa Ana Maria Vasile This was reported by checkpatch.pl Signed-off-by: Narcisa Ana Maria Vasile <narcisaanamaria12@gmail.com> --- drivers/staging/bcm2835-audio/bcm2835-pcm.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/bcm2835-audio/bcm2835-pcm.c b/drivers/staging/bcm2835-audio/bcm2835-pcm.c index 9e79236..328bee4a 100644 --- a/drivers/staging/bcm2835-audio/bcm2835-pcm.c +++ b/drivers/staging/bcm2835-audio/bcm2835-pcm.c @@ -91,7 +91,7 @@ void bcm2835_playback_fifo(struct bcm2835_alsa_stream *alsa_stream) frames_to_bytes(alsa_stream->substream->runtime, alsa_stream->substream->runtime->status->hw_ptr), new_period); if (alsa_stream->buffer_size) { - alsa_stream->pos += consumed &~(1 << 30); + alsa_stream->pos += consumed & ~(1 << 30); alsa_stream->pos %= alsa_stream->buffer_size; } -- 1.9.1 ^ permalink raw reply related [flat|nested] 24+ messages in thread
* [PATCH] staging: bcm2835-audio: Fixed spacing around '&' @ 2017-02-26 17:47 ` Narcisa Ana Maria Vasile 0 siblings, 0 replies; 24+ messages in thread From: Narcisa Ana Maria Vasile @ 2017-02-26 17:47 UTC (permalink / raw) To: linux-arm-kernel This was reported by checkpatch.pl Signed-off-by: Narcisa Ana Maria Vasile <narcisaanamaria12@gmail.com> --- drivers/staging/bcm2835-audio/bcm2835-pcm.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/bcm2835-audio/bcm2835-pcm.c b/drivers/staging/bcm2835-audio/bcm2835-pcm.c index 9e79236..328bee4a 100644 --- a/drivers/staging/bcm2835-audio/bcm2835-pcm.c +++ b/drivers/staging/bcm2835-audio/bcm2835-pcm.c @@ -91,7 +91,7 @@ void bcm2835_playback_fifo(struct bcm2835_alsa_stream *alsa_stream) frames_to_bytes(alsa_stream->substream->runtime, alsa_stream->substream->runtime->status->hw_ptr), new_period); if (alsa_stream->buffer_size) { - alsa_stream->pos += consumed &~(1 << 30); + alsa_stream->pos += consumed & ~(1 << 30); alsa_stream->pos %= alsa_stream->buffer_size; } -- 1.9.1 ^ permalink raw reply related [flat|nested] 24+ messages in thread
* Re: [Outreachy kernel] [PATCH] staging: bcm2835-audio: Fixed spacing around '&' 2017-02-26 17:47 ` Narcisa Ana Maria Vasile @ 2017-02-26 18:03 ` Julia Lawall -1 siblings, 0 replies; 24+ messages in thread From: Julia Lawall @ 2017-02-26 18:03 UTC (permalink / raw) To: Narcisa Ana Maria Vasile Cc: swarren, lee, eric, f.fainelli, rjui, sbranden, daniel.baluta, gregkh, outreachy-kernel, bcm-kernel-feedback-list, mzoran, danielperezdeandres, dan.carpenter, devel, linux-rpi-kernel, linux-arm-kernel, linux-kernel On Sun, 26 Feb 2017, Narcisa Ana Maria Vasile wrote: > This was reported by checkpatch.pl > > Signed-off-by: Narcisa Ana Maria Vasile <narcisaanamaria12@gmail.com> Acked-by: Julia Lawall <julia.lawall@lip6.fr> Actually, the outreachy tutorial says not to send patches to mailing lists, only to people (except in the case of IIO, where the maintainers asked for patches to be sent to mailing lists as well). The get_maintainer command to use is shown here: https://kernelnewbies.org/FirstKernelPatch#submit_a_patch > --- > drivers/staging/bcm2835-audio/bcm2835-pcm.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/staging/bcm2835-audio/bcm2835-pcm.c b/drivers/staging/bcm2835-audio/bcm2835-pcm.c > index 9e79236..328bee4a 100644 > --- a/drivers/staging/bcm2835-audio/bcm2835-pcm.c > +++ b/drivers/staging/bcm2835-audio/bcm2835-pcm.c > @@ -91,7 +91,7 @@ void bcm2835_playback_fifo(struct bcm2835_alsa_stream *alsa_stream) > frames_to_bytes(alsa_stream->substream->runtime, alsa_stream->substream->runtime->status->hw_ptr), > new_period); > if (alsa_stream->buffer_size) { > - alsa_stream->pos += consumed &~(1 << 30); > + alsa_stream->pos += consumed & ~(1 << 30); > alsa_stream->pos %= alsa_stream->buffer_size; > } > > -- > 1.9.1 > > -- > You received this message because you are subscribed to the Google Groups "outreachy-kernel" group. > To unsubscribe from this group and stop receiving emails from it, send an email to outreachy-kernel+unsubscribe@googlegroups.com. > To post to this group, send email to outreachy-kernel@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/msgid/outreachy-kernel/1488131271-2908-1-git-send-email-narcisaanamaria12%40gmail.com. > For more options, visit https://groups.google.com/d/optout. > ^ permalink raw reply [flat|nested] 24+ messages in thread
* [Outreachy kernel] [PATCH] staging: bcm2835-audio: Fixed spacing around '&' @ 2017-02-26 18:03 ` Julia Lawall 0 siblings, 0 replies; 24+ messages in thread From: Julia Lawall @ 2017-02-26 18:03 UTC (permalink / raw) To: linux-arm-kernel On Sun, 26 Feb 2017, Narcisa Ana Maria Vasile wrote: > This was reported by checkpatch.pl > > Signed-off-by: Narcisa Ana Maria Vasile <narcisaanamaria12@gmail.com> Acked-by: Julia Lawall <julia.lawall@lip6.fr> Actually, the outreachy tutorial says not to send patches to mailing lists, only to people (except in the case of IIO, where the maintainers asked for patches to be sent to mailing lists as well). The get_maintainer command to use is shown here: https://kernelnewbies.org/FirstKernelPatch#submit_a_patch > --- > drivers/staging/bcm2835-audio/bcm2835-pcm.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/staging/bcm2835-audio/bcm2835-pcm.c b/drivers/staging/bcm2835-audio/bcm2835-pcm.c > index 9e79236..328bee4a 100644 > --- a/drivers/staging/bcm2835-audio/bcm2835-pcm.c > +++ b/drivers/staging/bcm2835-audio/bcm2835-pcm.c > @@ -91,7 +91,7 @@ void bcm2835_playback_fifo(struct bcm2835_alsa_stream *alsa_stream) > frames_to_bytes(alsa_stream->substream->runtime, alsa_stream->substream->runtime->status->hw_ptr), > new_period); > if (alsa_stream->buffer_size) { > - alsa_stream->pos += consumed &~(1 << 30); > + alsa_stream->pos += consumed & ~(1 << 30); > alsa_stream->pos %= alsa_stream->buffer_size; > } > > -- > 1.9.1 > > -- > You received this message because you are subscribed to the Google Groups "outreachy-kernel" group. > To unsubscribe from this group and stop receiving emails from it, send an email to outreachy-kernel+unsubscribe at googlegroups.com. > To post to this group, send email to outreachy-kernel at googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/msgid/outreachy-kernel/1488131271-2908-1-git-send-email-narcisaanamaria12%40gmail.com. > For more options, visit https://groups.google.com/d/optout. > ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [Outreachy kernel] [PATCH] staging: bcm2835-audio: Fixed spacing around '&' 2017-02-26 18:03 ` Julia Lawall @ 2017-02-26 18:34 ` Joe Perches -1 siblings, 0 replies; 24+ messages in thread From: Joe Perches @ 2017-02-26 18:34 UTC (permalink / raw) To: Julia Lawall, Narcisa Ana Maria Vasile Cc: swarren, lee, eric, f.fainelli, rjui, sbranden, daniel.baluta, gregkh, outreachy-kernel, bcm-kernel-feedback-list, mzoran, danielperezdeandres, dan.carpenter, devel, linux-rpi-kernel, linux-arm-kernel, linux-kernel On Sun, 2017-02-26 at 19:03 +0100, Julia Lawall wrote: > > On Sun, 26 Feb 2017, Narcisa Ana Maria Vasile wrote: > > > This was reported by checkpatch.pl > > > > Signed-off-by: Narcisa Ana Maria Vasile <narcisaanamaria12@gmail.com> > > Acked-by: Julia Lawall <julia.lawall@lip6.fr> > > Actually, the outreachy tutorial says not to send patches to mailing > lists, only to people (except in the case of IIO, where the maintainers > asked for patches to be sent to mailing lists as well). The > get_maintainer command to use is shown here: > > https://kernelnewbies.org/FirstKernelPatch#submit_a_patch That doesn't make any sense to me. Mailing lists _should_ be copied on patch submissions. And the displayed output of that command-line does not match the actual behavior. The command-line is: $ perl scripts/get_maintainer.pl --separator , --nokeywords --nogit --nogit-fallback --norolestats --nol -f drivers/staging/most/aim-sound/sound.c And the output shown is: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,devel@driverdev.osuosl.org,linux-kernel@vger.kernel.org That's not what's actually output by that command-line as it would not show the mailing list. $ perl scripts/get_maintainer.pl --separator , --nokeywords --nogit --nogit-fallback --norolestats --nol -f drivers/staging/most/aim-sound/sound.c Greg Kroah-Hartman <gregkh@linuxfoundation.org> ^ permalink raw reply [flat|nested] 24+ messages in thread
* [Outreachy kernel] [PATCH] staging: bcm2835-audio: Fixed spacing around '&' @ 2017-02-26 18:34 ` Joe Perches 0 siblings, 0 replies; 24+ messages in thread From: Joe Perches @ 2017-02-26 18:34 UTC (permalink / raw) To: linux-arm-kernel On Sun, 2017-02-26 at 19:03 +0100, Julia Lawall wrote: > > On Sun, 26 Feb 2017, Narcisa Ana Maria Vasile wrote: > > > This was reported by checkpatch.pl > > > > Signed-off-by: Narcisa Ana Maria Vasile <narcisaanamaria12@gmail.com> > > Acked-by: Julia Lawall <julia.lawall@lip6.fr> > > Actually, the outreachy tutorial says not to send patches to mailing > lists, only to people (except in the case of IIO, where the maintainers > asked for patches to be sent to mailing lists as well). The > get_maintainer command to use is shown here: > > https://kernelnewbies.org/FirstKernelPatch#submit_a_patch That doesn't make any sense to me. Mailing lists _should_ be copied on patch submissions. And the displayed output of that command-line does not match the actual behavior. The command-line is: $ perl scripts/get_maintainer.pl --separator , --nokeywords --nogit --nogit-fallback --norolestats --nol -f drivers/staging/most/aim-sound/sound.c And the output shown is: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,devel at driverdev.osuosl.org,linux-kernel at vger.kernel.org That's not what's actually output by that command-line as it would not show the mailing list. $ perl scripts/get_maintainer.pl --separator , --nokeywords --nogit --nogit-fallback --norolestats --nol -f drivers/staging/most/aim-sound/sound.c Greg Kroah-Hartman <gregkh@linuxfoundation.org> ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [Outreachy kernel] [PATCH] staging: bcm2835-audio: Fixed spacing around '&' 2017-02-26 18:34 ` Joe Perches @ 2017-02-26 18:59 ` Julia Lawall -1 siblings, 0 replies; 24+ messages in thread From: Julia Lawall @ 2017-02-26 18:59 UTC (permalink / raw) To: Joe Perches Cc: Julia Lawall, Narcisa Ana Maria Vasile, swarren, lee, eric, f.fainelli, rjui, sbranden, daniel.baluta, gregkh, outreachy-kernel, bcm-kernel-feedback-list, mzoran, danielperezdeandres, dan.carpenter, devel, linux-rpi-kernel, linux-arm-kernel, linux-kernel On Sun, 26 Feb 2017, Joe Perches wrote: > On Sun, 2017-02-26 at 19:03 +0100, Julia Lawall wrote: > > > > On Sun, 26 Feb 2017, Narcisa Ana Maria Vasile wrote: > > > > > This was reported by checkpatch.pl > > > > > > Signed-off-by: Narcisa Ana Maria Vasile <narcisaanamaria12@gmail.com> > > > > Acked-by: Julia Lawall <julia.lawall@lip6.fr> > > > > Actually, the outreachy tutorial says not to send patches to mailing > > lists, only to people (except in the case of IIO, where the maintainers > > asked for patches to be sent to mailing lists as well). The > > get_maintainer command to use is shown here: > > > > https://kernelnewbies.org/FirstKernelPatch#submit_a_patch > > That doesn't make any sense to me. > Mailing lists _should_ be copied on patch submissions. The idea of outreachy is that it should be a place for people to get started without too much criticism from the outside. Originally, only the outreachy mailing list received patches. But staging maintainers were confused to have their drivers receiving patches that they had not seen. So we expanded it to maintainers. > > And the displayed output of that command-line does not match > the actual behavior. > > The command-line is: > $ perl scripts/get_maintainer.pl --separator , --nokeywords --nogit --nogit-fallback --norolestats --nol -f drivers/staging/most/aim-sound/sound.c > > And the output shown is: > Greg Kroah-Hartman <gregkh@linuxfoundation.org>,devel@driverdev.osuosl.org,linux-kernel@vger.kernel.org > > That's not what's actually output by that command-line > as it would not show the mailing list. > > $ perl scripts/get_maintainer.pl --separator , --nokeywords --nogit --nogit-fallback --norolestats --nol -f drivers/staging/most/aim-sound/sound.c > Greg Kroah-Hartman <gregkh@linuxfoundation.org> Thanks for the report, I will fix the output. julia > -- > You received this message because you are subscribed to the Google Groups "outreachy-kernel" group. > To unsubscribe from this group and stop receiving emails from it, send an email to outreachy-kernel+unsubscribe@googlegroups.com. > To post to this group, send email to outreachy-kernel@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/msgid/outreachy-kernel/1488134072.9188.3.camel%40perches.com. > For more options, visit https://groups.google.com/d/optout. > ^ permalink raw reply [flat|nested] 24+ messages in thread
* [Outreachy kernel] [PATCH] staging: bcm2835-audio: Fixed spacing around '&' @ 2017-02-26 18:59 ` Julia Lawall 0 siblings, 0 replies; 24+ messages in thread From: Julia Lawall @ 2017-02-26 18:59 UTC (permalink / raw) To: linux-arm-kernel On Sun, 26 Feb 2017, Joe Perches wrote: > On Sun, 2017-02-26 at 19:03 +0100, Julia Lawall wrote: > > > > On Sun, 26 Feb 2017, Narcisa Ana Maria Vasile wrote: > > > > > This was reported by checkpatch.pl > > > > > > Signed-off-by: Narcisa Ana Maria Vasile <narcisaanamaria12@gmail.com> > > > > Acked-by: Julia Lawall <julia.lawall@lip6.fr> > > > > Actually, the outreachy tutorial says not to send patches to mailing > > lists, only to people (except in the case of IIO, where the maintainers > > asked for patches to be sent to mailing lists as well). The > > get_maintainer command to use is shown here: > > > > https://kernelnewbies.org/FirstKernelPatch#submit_a_patch > > That doesn't make any sense to me. > Mailing lists _should_ be copied on patch submissions. The idea of outreachy is that it should be a place for people to get started without too much criticism from the outside. Originally, only the outreachy mailing list received patches. But staging maintainers were confused to have their drivers receiving patches that they had not seen. So we expanded it to maintainers. > > And the displayed output of that command-line does not match > the actual behavior. > > The command-line is: > $ perl scripts/get_maintainer.pl --separator , --nokeywords --nogit --nogit-fallback --norolestats --nol -f drivers/staging/most/aim-sound/sound.c > > And the output shown is: > Greg Kroah-Hartman <gregkh@linuxfoundation.org>,devel at driverdev.osuosl.org,linux-kernel at vger.kernel.org > > That's not what's actually output by that command-line > as it would not show the mailing list. > > $ perl scripts/get_maintainer.pl --separator , --nokeywords --nogit --nogit-fallback --norolestats --nol -f drivers/staging/most/aim-sound/sound.c > Greg Kroah-Hartman <gregkh@linuxfoundation.org> Thanks for the report, I will fix the output. julia > -- > You received this message because you are subscribed to the Google Groups "outreachy-kernel" group. > To unsubscribe from this group and stop receiving emails from it, send an email to outreachy-kernel+unsubscribe at googlegroups.com. > To post to this group, send email to outreachy-kernel at googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/msgid/outreachy-kernel/1488134072.9188.3.camel%40perches.com. > For more options, visit https://groups.google.com/d/optout. > ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [Outreachy kernel] [PATCH] staging: bcm2835-audio: Fixed spacing around '&' 2017-02-26 18:59 ` Julia Lawall @ 2017-02-26 19:37 ` Joe Perches -1 siblings, 0 replies; 24+ messages in thread From: Joe Perches @ 2017-02-26 19:37 UTC (permalink / raw) To: Julia Lawall Cc: Narcisa Ana Maria Vasile, swarren, lee, eric, f.fainelli, rjui, sbranden, daniel.baluta, gregkh, outreachy-kernel, bcm-kernel-feedback-list, mzoran, danielperezdeandres, dan.carpenter, devel, linux-rpi-kernel, linux-arm-kernel, linux-kernel On Sun, 2017-02-26 at 19:59 +0100, Julia Lawall wrote: > On Sun, 26 Feb 2017, Joe Perches wrote: > > Mailing lists _should_ be copied on patch submissions. > > The idea of outreachy is that it should be a place for people to get > started without too much criticism from the outside. Originally, only the > outreachy mailing list received patches. But staging maintainers were > confused to have their drivers receiving patches that they had not seen. > So we expanded it to maintainers. That also doesn't make much sense as patches should not be applied that have not reached a mailing list for review. As long as initial outreachy patches are not applied and are just for internal review by any outside person but the outreachy list and are not be applied by maintainers, then perhaps it's best if neither maintainers nor lists are cc'd on the patches. And the link you sent is for newbies, not for outreachy. The "don't cc lists" --nol use is inappropriate there. ^ permalink raw reply [flat|nested] 24+ messages in thread
* [Outreachy kernel] [PATCH] staging: bcm2835-audio: Fixed spacing around '&' @ 2017-02-26 19:37 ` Joe Perches 0 siblings, 0 replies; 24+ messages in thread From: Joe Perches @ 2017-02-26 19:37 UTC (permalink / raw) To: linux-arm-kernel On Sun, 2017-02-26 at 19:59 +0100, Julia Lawall wrote: > On Sun, 26 Feb 2017, Joe Perches wrote: > > Mailing lists _should_ be copied on patch submissions. > > The idea of outreachy is that it should be a place for people to get > started without too much criticism from the outside. Originally, only the > outreachy mailing list received patches. But staging maintainers were > confused to have their drivers receiving patches that they had not seen. > So we expanded it to maintainers. That also doesn't make much sense as patches should not be applied that have not reached a mailing list for review. As long as initial outreachy patches are not applied and are just for internal review by any outside person but the outreachy list and are not be applied by maintainers, then perhaps it's best if neither maintainers nor lists are cc'd on the patches. And the link you sent is for newbies, not for outreachy. The "don't cc lists" --nol use is inappropriate there. ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [Outreachy kernel] [PATCH] staging: bcm2835-audio: Fixed spacing around '&' 2017-02-26 19:37 ` Joe Perches @ 2017-02-26 19:40 ` Julia Lawall -1 siblings, 0 replies; 24+ messages in thread From: Julia Lawall @ 2017-02-26 19:40 UTC (permalink / raw) To: Joe Perches Cc: Julia Lawall, Narcisa Ana Maria Vasile, swarren, lee, eric, f.fainelli, rjui, sbranden, daniel.baluta, gregkh, outreachy-kernel, bcm-kernel-feedback-list, mzoran, danielperezdeandres, dan.carpenter, devel, linux-rpi-kernel, linux-arm-kernel, linux-kernel On Sun, 26 Feb 2017, Joe Perches wrote: > On Sun, 2017-02-26 at 19:59 +0100, Julia Lawall wrote: > > On Sun, 26 Feb 2017, Joe Perches wrote: > > > Mailing lists _should_ be copied on patch submissions. > > > > The idea of outreachy is that it should be a place for people to get > > started without too much criticism from the outside. Originally, only the > > outreachy mailing list received patches. But staging maintainers were > > confused to have their drivers receiving patches that they had not seen. > > So we expanded it to maintainers. > > That also doesn't make much sense as patches > should not be applied that have not reached > a mailing list for review. > > As long as initial outreachy patches are not > applied and are just for internal review by > any outside person but the outreachy list and > are not be applied by maintainers, then perhaps > it's best if neither maintainers nor lists are > cc'd on the patches. The patches are applied by Greg. Greg suggested the policy of adding maintainers but not including mailing lists. I'll let him consider whether the policy should be changed. > And the link you sent is for newbies, not for > outreachy. The link is part of the outreachy tutorial, which is hosted by the kernelnewbies website. julia > > The "don't cc lists" --nol use is inappropriate > there. > > ^ permalink raw reply [flat|nested] 24+ messages in thread
* [Outreachy kernel] [PATCH] staging: bcm2835-audio: Fixed spacing around '&' @ 2017-02-26 19:40 ` Julia Lawall 0 siblings, 0 replies; 24+ messages in thread From: Julia Lawall @ 2017-02-26 19:40 UTC (permalink / raw) To: linux-arm-kernel On Sun, 26 Feb 2017, Joe Perches wrote: > On Sun, 2017-02-26 at 19:59 +0100, Julia Lawall wrote: > > On Sun, 26 Feb 2017, Joe Perches wrote: > > > Mailing lists _should_ be copied on patch submissions. > > > > The idea of outreachy is that it should be a place for people to get > > started without too much criticism from the outside. Originally, only the > > outreachy mailing list received patches. But staging maintainers were > > confused to have their drivers receiving patches that they had not seen. > > So we expanded it to maintainers. > > That also doesn't make much sense as patches > should not be applied that have not reached > a mailing list for review. > > As long as initial outreachy patches are not > applied and are just for internal review by > any outside person but the outreachy list and > are not be applied by maintainers, then perhaps > it's best if neither maintainers nor lists are > cc'd on the patches. The patches are applied by Greg. Greg suggested the policy of adding maintainers but not including mailing lists. I'll let him consider whether the policy should be changed. > And the link you sent is for newbies, not for > outreachy. The link is part of the outreachy tutorial, which is hosted by the kernelnewbies website. julia > > The "don't cc lists" --nol use is inappropriate > there. > > ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [Outreachy kernel] [PATCH] staging: bcm2835-audio: Fixed spacing around '&' 2017-02-26 19:40 ` Julia Lawall @ 2017-02-26 21:56 ` Joe Perches -1 siblings, 0 replies; 24+ messages in thread From: Joe Perches @ 2017-02-26 21:56 UTC (permalink / raw) To: Julia Lawall Cc: Narcisa Ana Maria Vasile, swarren, lee, eric, f.fainelli, rjui, sbranden, daniel.baluta, gregkh, outreachy-kernel, bcm-kernel-feedback-list, mzoran, danielperezdeandres, dan.carpenter, devel, linux-rpi-kernel, linux-arm-kernel, linux-kernel On Sun, 2017-02-26 at 20:40 +0100, Julia Lawall wrote: > On Sun, 26 Feb 2017, Joe Perches wrote: > > On Sun, 2017-02-26 at 19:59 +0100, Julia Lawall wrote: > > > On Sun, 26 Feb 2017, Joe Perches wrot > > > > Mailing lists _should_ be copied on patch submissions. > > > The idea of outreachy is that it should be a place for people to get > > > started without too much criticism from the outside. Originally, only the > > > outreachy mailing list received patches. But staging maintainers were > > > confused to have their drivers receiving patches that they had not seen. > > > So we expanded it to maintainers. > > > > That also doesn't make much sense as patches > > should not be applied that have not reached > > a mailing list for review. > > > > As long as initial outreachy patches are not > > applied and are just for internal review by > > any outside person but the outreachy list and > > are not be applied by maintainers, then perhaps > > it's best if neither maintainers nor lists are > > cc'd on the patches. > > The patches are applied by Greg. Greg suggested the policy of adding > maintainers but not including mailing lists. I'll let him consider > whether the policy should be changed. Well, I will comment on patches sent to the kernel list. I'm not subscribed to outreachy and I don't want to be subscribed to that list either. ^ permalink raw reply [flat|nested] 24+ messages in thread
* [Outreachy kernel] [PATCH] staging: bcm2835-audio: Fixed spacing around '&' @ 2017-02-26 21:56 ` Joe Perches 0 siblings, 0 replies; 24+ messages in thread From: Joe Perches @ 2017-02-26 21:56 UTC (permalink / raw) To: linux-arm-kernel On Sun, 2017-02-26 at 20:40 +0100, Julia Lawall wrote: > On Sun, 26 Feb 2017, Joe Perches wrote: > > On Sun, 2017-02-26 at 19:59 +0100, Julia Lawall wrote: > > > On Sun, 26 Feb 2017, Joe Perches wrot > > > > Mailing lists _should_ be copied on patch submissions. > > > The idea of outreachy is that it should be a place for people to get > > > started without too much criticism from the outside. Originally, only the > > > outreachy mailing list received patches. But staging maintainers were > > > confused to have their drivers receiving patches that they had not seen. > > > So we expanded it to maintainers. > > > > That also doesn't make much sense as patches > > should not be applied that have not reached > > a mailing list for review. > > > > As long as initial outreachy patches are not > > applied and are just for internal review by > > any outside person but the outreachy list and > > are not be applied by maintainers, then perhaps > > it's best if neither maintainers nor lists are > > cc'd on the patches. > > The patches are applied by Greg. Greg suggested the policy of adding > maintainers but not including mailing lists. I'll let him consider > whether the policy should be changed. Well, I will comment on patches sent to the kernel list. I'm not subscribed to outreachy and I don't want to be subscribed to that list either. ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [Outreachy kernel] [PATCH] staging: bcm2835-audio: Fixed spacing around '&' 2017-02-26 21:56 ` Joe Perches @ 2017-02-27 0:08 ` Scott Branden -1 siblings, 0 replies; 24+ messages in thread From: Scott Branden @ 2017-02-27 0:08 UTC (permalink / raw) To: Joe Perches, Julia Lawall Cc: Narcisa Ana Maria Vasile, swarren, lee, eric, f.fainelli, rjui, sbranden, daniel.baluta, gregkh, outreachy-kernel, bcm-kernel-feedback-list, mzoran, danielperezdeandres, dan.carpenter, devel, linux-rpi-kernel, linux-arm-kernel, linux-kernel On 17-02-26 01:56 PM, Joe Perches wrote: > On Sun, 2017-02-26 at 20:40 +0100, Julia Lawall wrote: >> On Sun, 26 Feb 2017, Joe Perches wrote: >>> On Sun, 2017-02-26 at 19:59 +0100, Julia Lawall wrote: >>>> On Sun, 26 Feb 2017, Joe Perches wrot >>>>> Mailing lists _should_ be copied on patch submissions. >>>> The idea of outreachy is that it should be a place for people to get >>>> started without too much criticism from the outside. Originally, only the >>>> outreachy mailing list received patches. But staging maintainers were >>>> confused to have their drivers receiving patches that they had not seen. >>>> So we expanded it to maintainers. >>> >>> That also doesn't make much sense as patches >>> should not be applied that have not reached >>> a mailing list for review. >>> >>> As long as initial outreachy patches are not >>> applied and are just for internal review by >>> any outside person but the outreachy list and >>> are not be applied by maintainers, then perhaps >>> it's best if neither maintainers nor lists are >>> cc'd on the patches. >> >> The patches are applied by Greg. Greg suggested the policy of adding >> maintainers but not including mailing lists. I'll let him consider >> whether the policy should be changed. > > Well, I will comment on patches sent to the kernel list. > > I'm not subscribed to outreachy and I don't want to be > subscribed to that list either. > I would prefer this outreachy work uses their own mailing list and reviews their patches first. Then once they have everything sorted out they send out the patch series to the proper maintainers/mailing lists. That way we're not spammed with all these emails of people as they are learning how to format and send out proper patches. Thanks, Scott ^ permalink raw reply [flat|nested] 24+ messages in thread
* [Outreachy kernel] [PATCH] staging: bcm2835-audio: Fixed spacing around '&' @ 2017-02-27 0:08 ` Scott Branden 0 siblings, 0 replies; 24+ messages in thread From: Scott Branden @ 2017-02-27 0:08 UTC (permalink / raw) To: linux-arm-kernel On 17-02-26 01:56 PM, Joe Perches wrote: > On Sun, 2017-02-26 at 20:40 +0100, Julia Lawall wrote: >> On Sun, 26 Feb 2017, Joe Perches wrote: >>> On Sun, 2017-02-26 at 19:59 +0100, Julia Lawall wrote: >>>> On Sun, 26 Feb 2017, Joe Perches wrot >>>>> Mailing lists _should_ be copied on patch submissions. >>>> The idea of outreachy is that it should be a place for people to get >>>> started without too much criticism from the outside. Originally, only the >>>> outreachy mailing list received patches. But staging maintainers were >>>> confused to have their drivers receiving patches that they had not seen. >>>> So we expanded it to maintainers. >>> >>> That also doesn't make much sense as patches >>> should not be applied that have not reached >>> a mailing list for review. >>> >>> As long as initial outreachy patches are not >>> applied and are just for internal review by >>> any outside person but the outreachy list and >>> are not be applied by maintainers, then perhaps >>> it's best if neither maintainers nor lists are >>> cc'd on the patches. >> >> The patches are applied by Greg. Greg suggested the policy of adding >> maintainers but not including mailing lists. I'll let him consider >> whether the policy should be changed. > > Well, I will comment on patches sent to the kernel list. > > I'm not subscribed to outreachy and I don't want to be > subscribed to that list either. > I would prefer this outreachy work uses their own mailing list and reviews their patches first. Then once they have everything sorted out they send out the patch series to the proper maintainers/mailing lists. That way we're not spammed with all these emails of people as they are learning how to format and send out proper patches. Thanks, Scott ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [Outreachy kernel] [PATCH] staging: bcm2835-audio: Fixed spacing around '&' 2017-02-27 0:08 ` Scott Branden @ 2017-02-27 6:25 ` Julia Lawall -1 siblings, 0 replies; 24+ messages in thread From: Julia Lawall @ 2017-02-27 6:25 UTC (permalink / raw) To: Scott Branden Cc: Joe Perches, Julia Lawall, Narcisa Ana Maria Vasile, swarren, lee, eric, f.fainelli, rjui, sbranden, daniel.baluta, gregkh, outreachy-kernel, bcm-kernel-feedback-list, mzoran, danielperezdeandres, dan.carpenter, devel, linux-rpi-kernel, linux-arm-kernel, linux-kernel On Sun, 26 Feb 2017, Scott Branden wrote: > > > On 17-02-26 01:56 PM, Joe Perches wrote: > > On Sun, 2017-02-26 at 20:40 +0100, Julia Lawall wrote: > > > On Sun, 26 Feb 2017, Joe Perches wrote: > > > > On Sun, 2017-02-26 at 19:59 +0100, Julia Lawall wrote: > > > > > On Sun, 26 Feb 2017, Joe Perches wrot > > > > > > Mailing lists _should_ be copied on patch submissions. > > > > > The idea of outreachy is that it should be a place for people to get > > > > > started without too much criticism from the outside. Originally, only > > > > > the > > > > > outreachy mailing list received patches. But staging maintainers were > > > > > confused to have their drivers receiving patches that they had not > > > > > seen. > > > > > So we expanded it to maintainers. > > > > > > > > That also doesn't make much sense as patches > > > > should not be applied that have not reached > > > > a mailing list for review. > > > > > > > > As long as initial outreachy patches are not > > > > applied and are just for internal review by > > > > any outside person but the outreachy list and > > > > are not be applied by maintainers, then perhaps > > > > it's best if neither maintainers nor lists are > > > > cc'd on the patches. > > > > > > The patches are applied by Greg. Greg suggested the policy of adding > > > maintainers but not including mailing lists. I'll let him consider > > > whether the policy should be changed. > > > > Well, I will comment on patches sent to the kernel list. > > > > I'm not subscribed to outreachy and I don't want to be > > subscribed to that list either. > > > I would prefer this outreachy work uses their own mailing list and reviews > their patches first. Then once they have everything sorted out they send out > the patch series to the proper maintainers/mailing lists. That way we're not > spammed with all these emails of people as they are learning how to format and > send out proper patches. If you consider that you are getting too much outreachy mail at the moment, just let me know what subsystem you want me to add an exception for. thanks, julia ^ permalink raw reply [flat|nested] 24+ messages in thread
* [Outreachy kernel] [PATCH] staging: bcm2835-audio: Fixed spacing around '&' @ 2017-02-27 6:25 ` Julia Lawall 0 siblings, 0 replies; 24+ messages in thread From: Julia Lawall @ 2017-02-27 6:25 UTC (permalink / raw) To: linux-arm-kernel On Sun, 26 Feb 2017, Scott Branden wrote: > > > On 17-02-26 01:56 PM, Joe Perches wrote: > > On Sun, 2017-02-26 at 20:40 +0100, Julia Lawall wrote: > > > On Sun, 26 Feb 2017, Joe Perches wrote: > > > > On Sun, 2017-02-26 at 19:59 +0100, Julia Lawall wrote: > > > > > On Sun, 26 Feb 2017, Joe Perches wrot > > > > > > Mailing lists _should_ be copied on patch submissions. > > > > > The idea of outreachy is that it should be a place for people to get > > > > > started without too much criticism from the outside. Originally, only > > > > > the > > > > > outreachy mailing list received patches. But staging maintainers were > > > > > confused to have their drivers receiving patches that they had not > > > > > seen. > > > > > So we expanded it to maintainers. > > > > > > > > That also doesn't make much sense as patches > > > > should not be applied that have not reached > > > > a mailing list for review. > > > > > > > > As long as initial outreachy patches are not > > > > applied and are just for internal review by > > > > any outside person but the outreachy list and > > > > are not be applied by maintainers, then perhaps > > > > it's best if neither maintainers nor lists are > > > > cc'd on the patches. > > > > > > The patches are applied by Greg. Greg suggested the policy of adding > > > maintainers but not including mailing lists. I'll let him consider > > > whether the policy should be changed. > > > > Well, I will comment on patches sent to the kernel list. > > > > I'm not subscribed to outreachy and I don't want to be > > subscribed to that list either. > > > I would prefer this outreachy work uses their own mailing list and reviews > their patches first. Then once they have everything sorted out they send out > the patch series to the proper maintainers/mailing lists. That way we're not > spammed with all these emails of people as they are learning how to format and > send out proper patches. If you consider that you are getting too much outreachy mail at the moment, just let me know what subsystem you want me to add an exception for. thanks, julia ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [Outreachy kernel] [PATCH] staging: bcm2835-audio: Fixed spacing around '&' 2017-02-27 6:25 ` Julia Lawall @ 2017-02-27 14:44 ` Dan Carpenter -1 siblings, 0 replies; 24+ messages in thread From: Dan Carpenter @ 2017-02-27 14:44 UTC (permalink / raw) To: Julia Lawall Cc: Scott Branden, devel, outreachy-kernel, f.fainelli, sbranden, swarren, eric, linux-arm-kernel, rjui, Narcisa Ana Maria Vasile, lee, linux-kernel, mzoran, bcm-kernel-feedback-list, daniel.baluta, gregkh, Joe Perches, danielperezdeandres, linux-rpi-kernel On Mon, Feb 27, 2017 at 07:25:30AM +0100, Julia Lawall wrote: > > > On Sun, 26 Feb 2017, Scott Branden wrote: > > > > > > > On 17-02-26 01:56 PM, Joe Perches wrote: > > > On Sun, 2017-02-26 at 20:40 +0100, Julia Lawall wrote: > > > > On Sun, 26 Feb 2017, Joe Perches wrote: > > > > > On Sun, 2017-02-26 at 19:59 +0100, Julia Lawall wrote: > > > > > > On Sun, 26 Feb 2017, Joe Perches wrot > > > > > > > Mailing lists _should_ be copied on patch submissions. > > > > > > The idea of outreachy is that it should be a place for people to get > > > > > > started without too much criticism from the outside. Originally, only > > > > > > the > > > > > > outreachy mailing list received patches. But staging maintainers were > > > > > > confused to have their drivers receiving patches that they had not > > > > > > seen. > > > > > > So we expanded it to maintainers. > > > > > It was mostly me being annoyed because outreachy reviews are not that good frankly. We just were just looking at outreachy code from 2013 where they "fixed" sparse endian notations by removing the endian conversions. It was so obviously wrong just from reading the changelog before you even got to the patch itself... > > > > > That also doesn't make much sense as patches > > > > > should not be applied that have not reached > > > > > a mailing list for review. > > > > > > > > > > As long as initial outreachy patches are not > > > > > applied and are just for internal review by > > > > > any outside person but the outreachy list and > > > > > are not be applied by maintainers, then perhaps > > > > > it's best if neither maintainers nor lists are > > > > > cc'd on the patches. > > > > > > > > The patches are applied by Greg. Greg suggested the policy of adding > > > > maintainers but not including mailing lists. I'll let him consider > > > > whether the policy should be changed. > > > > > > Well, I will comment on patches sent to the kernel list. > > > > > > I'm not subscribed to outreachy and I don't want to be > > > subscribed to that list either. > > > > > I would prefer this outreachy work uses their own mailing list and reviews > > their patches first. Then once they have everything sorted out they send out > > the patch series to the proper maintainers/mailing lists. That way we're not > > spammed with all these emails of people as they are learning how to format and > > send out proper patches. > Outreachy emails are not really worse than normal staging patches so I don't mind the spam. But it would be good if driver-devel were always CC'd on the final patch. I know Greg feels differently. regards, dan carpenter ^ permalink raw reply [flat|nested] 24+ messages in thread
* [Outreachy kernel] [PATCH] staging: bcm2835-audio: Fixed spacing around '&' @ 2017-02-27 14:44 ` Dan Carpenter 0 siblings, 0 replies; 24+ messages in thread From: Dan Carpenter @ 2017-02-27 14:44 UTC (permalink / raw) To: linux-arm-kernel On Mon, Feb 27, 2017 at 07:25:30AM +0100, Julia Lawall wrote: > > > On Sun, 26 Feb 2017, Scott Branden wrote: > > > > > > > On 17-02-26 01:56 PM, Joe Perches wrote: > > > On Sun, 2017-02-26 at 20:40 +0100, Julia Lawall wrote: > > > > On Sun, 26 Feb 2017, Joe Perches wrote: > > > > > On Sun, 2017-02-26 at 19:59 +0100, Julia Lawall wrote: > > > > > > On Sun, 26 Feb 2017, Joe Perches wrot > > > > > > > Mailing lists _should_ be copied on patch submissions. > > > > > > The idea of outreachy is that it should be a place for people to get > > > > > > started without too much criticism from the outside. Originally, only > > > > > > the > > > > > > outreachy mailing list received patches. But staging maintainers were > > > > > > confused to have their drivers receiving patches that they had not > > > > > > seen. > > > > > > So we expanded it to maintainers. > > > > > It was mostly me being annoyed because outreachy reviews are not that good frankly. We just were just looking at outreachy code from 2013 where they "fixed" sparse endian notations by removing the endian conversions. It was so obviously wrong just from reading the changelog before you even got to the patch itself... > > > > > That also doesn't make much sense as patches > > > > > should not be applied that have not reached > > > > > a mailing list for review. > > > > > > > > > > As long as initial outreachy patches are not > > > > > applied and are just for internal review by > > > > > any outside person but the outreachy list and > > > > > are not be applied by maintainers, then perhaps > > > > > it's best if neither maintainers nor lists are > > > > > cc'd on the patches. > > > > > > > > The patches are applied by Greg. Greg suggested the policy of adding > > > > maintainers but not including mailing lists. I'll let him consider > > > > whether the policy should be changed. > > > > > > Well, I will comment on patches sent to the kernel list. > > > > > > I'm not subscribed to outreachy and I don't want to be > > > subscribed to that list either. > > > > > I would prefer this outreachy work uses their own mailing list and reviews > > their patches first. Then once they have everything sorted out they send out > > the patch series to the proper maintainers/mailing lists. That way we're not > > spammed with all these emails of people as they are learning how to format and > > send out proper patches. > Outreachy emails are not really worse than normal staging patches so I don't mind the spam. But it would be good if driver-devel were always CC'd on the final patch. I know Greg feels differently. regards, dan carpenter ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [Outreachy kernel] [PATCH] staging: bcm2835-audio: Fixed spacing around '&' 2017-02-27 6:25 ` Julia Lawall @ 2017-02-27 20:35 ` Scott Branden -1 siblings, 0 replies; 24+ messages in thread From: Scott Branden @ 2017-02-27 20:35 UTC (permalink / raw) To: Julia Lawall Cc: Joe Perches, Narcisa Ana Maria Vasile, swarren, lee, eric, f.fainelli, rjui, sbranden, daniel.baluta, gregkh, outreachy-kernel, bcm-kernel-feedback-list, mzoran, danielperezdeandres, dan.carpenter, devel, linux-rpi-kernel, linux-arm-kernel, linux-kernel Hi Julia, On 17-02-26 10:25 PM, Julia Lawall wrote: > > > On Sun, 26 Feb 2017, Scott Branden wrote: > >> >> >> On 17-02-26 01:56 PM, Joe Perches wrote: >>> On Sun, 2017-02-26 at 20:40 +0100, Julia Lawall wrote: >>>> On Sun, 26 Feb 2017, Joe Perches wrote: >>>>> On Sun, 2017-02-26 at 19:59 +0100, Julia Lawall wrote: >>>>>> On Sun, 26 Feb 2017, Joe Perches wrot >>>>>>> Mailing lists _should_ be copied on patch submissions. >>>>>> The idea of outreachy is that it should be a place for people to get >>>>>> started without too much criticism from the outside. Originally, only >>>>>> the >>>>>> outreachy mailing list received patches. But staging maintainers were >>>>>> confused to have their drivers receiving patches that they had not >>>>>> seen. >>>>>> So we expanded it to maintainers. >>>>> >>>>> That also doesn't make much sense as patches >>>>> should not be applied that have not reached >>>>> a mailing list for review. >>>>> >>>>> As long as initial outreachy patches are not >>>>> applied and are just for internal review by >>>>> any outside person but the outreachy list and >>>>> are not be applied by maintainers, then perhaps >>>>> it's best if neither maintainers nor lists are >>>>> cc'd on the patches. >>>> >>>> The patches are applied by Greg. Greg suggested the policy of adding >>>> maintainers but not including mailing lists. I'll let him consider >>>> whether the policy should be changed. >>> >>> Well, I will comment on patches sent to the kernel list. >>> >>> I'm not subscribed to outreachy and I don't want to be >>> subscribed to that list either. >>> >> I would prefer this outreachy work uses their own mailing list and reviews >> their patches first. Then once they have everything sorted out they send out >> the patch series to the proper maintainers/mailing lists. That way we're not >> spammed with all these emails of people as they are learning how to format and >> send out proper patches. > > If you consider that you are getting too much outreachy mail at the > moment, just let me know what subsystem you want me to add an exception > for. The emails seem to mostly be coming with bcm2835-audio. > > thanks, > julia Thanks, Scott > ^ permalink raw reply [flat|nested] 24+ messages in thread
* [Outreachy kernel] [PATCH] staging: bcm2835-audio: Fixed spacing around '&' @ 2017-02-27 20:35 ` Scott Branden 0 siblings, 0 replies; 24+ messages in thread From: Scott Branden @ 2017-02-27 20:35 UTC (permalink / raw) To: linux-arm-kernel Hi Julia, On 17-02-26 10:25 PM, Julia Lawall wrote: > > > On Sun, 26 Feb 2017, Scott Branden wrote: > >> >> >> On 17-02-26 01:56 PM, Joe Perches wrote: >>> On Sun, 2017-02-26 at 20:40 +0100, Julia Lawall wrote: >>>> On Sun, 26 Feb 2017, Joe Perches wrote: >>>>> On Sun, 2017-02-26 at 19:59 +0100, Julia Lawall wrote: >>>>>> On Sun, 26 Feb 2017, Joe Perches wrot >>>>>>> Mailing lists _should_ be copied on patch submissions. >>>>>> The idea of outreachy is that it should be a place for people to get >>>>>> started without too much criticism from the outside. Originally, only >>>>>> the >>>>>> outreachy mailing list received patches. But staging maintainers were >>>>>> confused to have their drivers receiving patches that they had not >>>>>> seen. >>>>>> So we expanded it to maintainers. >>>>> >>>>> That also doesn't make much sense as patches >>>>> should not be applied that have not reached >>>>> a mailing list for review. >>>>> >>>>> As long as initial outreachy patches are not >>>>> applied and are just for internal review by >>>>> any outside person but the outreachy list and >>>>> are not be applied by maintainers, then perhaps >>>>> it's best if neither maintainers nor lists are >>>>> cc'd on the patches. >>>> >>>> The patches are applied by Greg. Greg suggested the policy of adding >>>> maintainers but not including mailing lists. I'll let him consider >>>> whether the policy should be changed. >>> >>> Well, I will comment on patches sent to the kernel list. >>> >>> I'm not subscribed to outreachy and I don't want to be >>> subscribed to that list either. >>> >> I would prefer this outreachy work uses their own mailing list and reviews >> their patches first. Then once they have everything sorted out they send out >> the patch series to the proper maintainers/mailing lists. That way we're not >> spammed with all these emails of people as they are learning how to format and >> send out proper patches. > > If you consider that you are getting too much outreachy mail at the > moment, just let me know what subsystem you want me to add an exception > for. The emails seem to mostly be coming with bcm2835-audio. > > thanks, > julia Thanks, Scott > ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [Outreachy kernel] [PATCH] staging: bcm2835-audio: Fixed spacing around '&' 2017-02-27 20:35 ` Scott Branden @ 2017-02-27 20:47 ` Michael Zoran -1 siblings, 0 replies; 24+ messages in thread From: Michael Zoran @ 2017-02-27 20:47 UTC (permalink / raw) To: Scott Branden, Julia Lawall Cc: Joe Perches, Narcisa Ana Maria Vasile, swarren, lee, eric, f.fainelli, rjui, sbranden, daniel.baluta, gregkh, outreachy-kernel, bcm-kernel-feedback-list, danielperezdeandres, dan.carpenter, devel, linux-rpi-kernel, linux-arm-kernel, linux-kernel On Mon, 2017-02-27 at 12:35 -0800, Scott Branden wrote: > > > Hi Julia, > > On 17-02-26 10:25 PM, Julia Lawall wrote: > > > > If you consider that you are getting too much outreachy mail at the > > moment, just let me know what subsystem you want me to add an > > exception > > for. > > The emails seem to mostly be coming with bcm2835-audio. > > > > thanks, > > julia > > Thanks, > Scott I submitted the driver to stagging, so I feel a bit responsible for this. I personally don't mind e-mails like this since people have to get started somehow, and e-mail is rather easy to ignore or delete... Perhaps it would make sense to either update the maintainer list for this driver or move the driver somewhere else in staging? I was looking at the maintainer list for bcm2835, and it already marks vc04_services as part of the bcm2835 files. Perhaps another mark should be added or the driver moved under vc04_services? ^ permalink raw reply [flat|nested] 24+ messages in thread
* [Outreachy kernel] [PATCH] staging: bcm2835-audio: Fixed spacing around '&' @ 2017-02-27 20:47 ` Michael Zoran 0 siblings, 0 replies; 24+ messages in thread From: Michael Zoran @ 2017-02-27 20:47 UTC (permalink / raw) To: linux-arm-kernel On Mon, 2017-02-27 at 12:35 -0800, Scott Branden wrote: > > > Hi Julia, > > On 17-02-26 10:25 PM, Julia Lawall wrote: > > > > If you consider that you are getting too much outreachy mail at the > > moment, just let me know what subsystem you want me to add an > > exception > > for. > > The emails seem to mostly be coming with bcm2835-audio. > > > > thanks, > > julia > > Thanks, > ? Scott I submitted the driver to stagging, so I feel a bit responsible for this. I personally don't mind e-mails like this since people have to get started somehow, and e-mail is rather easy to ignore or delete... Perhaps it would make sense to either update the maintainer list for this driver or move the driver somewhere else in staging? I was looking at the maintainer list for bcm2835, and it already marks vc04_services as part of the bcm2835 files. Perhaps another mark should be added or the driver moved under vc04_services? ^ permalink raw reply [flat|nested] 24+ messages in thread
end of thread, other threads:[~2017-02-27 21:11 UTC | newest] Thread overview: 24+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2017-02-26 17:47 [PATCH] staging: bcm2835-audio: Fixed spacing around '&' Narcisa Ana Maria Vasile 2017-02-26 17:47 ` Narcisa Ana Maria Vasile 2017-02-26 18:03 ` [Outreachy kernel] " Julia Lawall 2017-02-26 18:03 ` Julia Lawall 2017-02-26 18:34 ` Joe Perches 2017-02-26 18:34 ` Joe Perches 2017-02-26 18:59 ` Julia Lawall 2017-02-26 18:59 ` Julia Lawall 2017-02-26 19:37 ` Joe Perches 2017-02-26 19:37 ` Joe Perches 2017-02-26 19:40 ` Julia Lawall 2017-02-26 19:40 ` Julia Lawall 2017-02-26 21:56 ` Joe Perches 2017-02-26 21:56 ` Joe Perches 2017-02-27 0:08 ` Scott Branden 2017-02-27 0:08 ` Scott Branden 2017-02-27 6:25 ` Julia Lawall 2017-02-27 6:25 ` Julia Lawall 2017-02-27 14:44 ` Dan Carpenter 2017-02-27 14:44 ` Dan Carpenter 2017-02-27 20:35 ` Scott Branden 2017-02-27 20:35 ` Scott Branden 2017-02-27 20:47 ` Michael Zoran 2017-02-27 20:47 ` Michael Zoran
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.