All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Mark Brown <broonie@kernel.org>
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Ben Dooks" <ben@simtec.co.uk>,
	"Brian W Hart" <hartb@linux.vnet.ibm.com>,
	"Bruno Prémont" <bonbons@linux-vserver.org>,
	"Christian Engelmayer" <cengelma@gmx.at>,
	"Christopher Brannon" <chris@the-brannons.com>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Greg Kroah-Hartman" <greg@kroah.com>,
	"James Bottomley" <JBottomley@Parallels.com>,
	"Jiri Kosina" <jkosina@suse.cz>,
	"Lindar Liu" <lindar_liu@usish.com>,
	"Robert Jarzmik" <robert.jarzmik@free.fr>,
	"Samuel Thibault" <samuel.thibault@ens-lyon.org>,
	"Simon Wood" <simon@mungewell.org>,
	"Vincent Sanders" <vince@simtec.co.uk>
Subject: Re: [PULL] modules-next
Date: Thu, 12 Jun 2014 10:55:00 +0930	[thread overview]
Message-ID: <87y4x2q5qr.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20140611105503.GG5099@sirena.org.uk>

Mark Brown <broonie@kernel.org> writes:
> On Wed, Jun 11, 2014 at 03:03:47PM +0930, Rusty Russell wrote:
>
>>       drivers/regulator/virtual: avoid world-writable sysfs files.
>
> Acked-by: Mark Brown <broonie@linaro.org>
>
> if you need to respin - please do send patches to maintainers.

If the address in drivers/regulator/virtual.c is incorrect, please
update it:

 Subject: [PATCH 5/9] drivers/regulator/virtual: avoid world-writable sysfs files.
 To: linux-kernel@vger.kernel.org
 Cc: Rusty Russell <rusty@rustcorp.com.au>, Mark Brown <broonie@opensource.wolfsonmicro.com>
 Date: Tue, 22 Apr 2014 13:03:28 +0930

 In line with practice for module parameters, we're adding a build-time
 check that sysfs files aren't world-writable.

Thanks,
Rusty.

  reply	other threads:[~2014-06-12  3:08 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-11  5:33 [PULL] modules-next Rusty Russell
2014-06-11 10:55 ` Mark Brown
2014-06-12  1:25   ` Rusty Russell [this message]
2014-06-12 11:27     ` Mark Brown
2014-06-13  1:03       ` Rusty Russell
2014-06-13  9:24         ` Mark Brown
2014-06-13 10:04           ` Geert Uytterhoeven
  -- strict thread matches above, loose matches on Subject: below --
2016-08-01  1:02 Rusty Russell
2016-08-01  1:44 ` Linus Torvalds
2016-08-01 19:11   ` Ben Hutchings
2016-08-02  0:10   ` Rusty Russell
2016-08-04  0:50     ` Rusty Russell
2015-11-08 23:42 Rusty Russell
2015-06-30  2:47 Rusty Russell
2015-02-13  6:43 Rusty Russell
2014-12-19  0:55 Rusty Russell
2014-12-19  5:01 ` Linus Torvalds
2014-12-22  1:21   ` Rusty Russell
2014-09-16 15:48 Rusty Russell
2014-08-11  2:32 Rusty Russell
2013-07-10  3:55 Rusty Russell
2013-02-19 23:14 Rusty Russell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y4x2q5qr.fsf@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=JBottomley@Parallels.com \
    --cc=akpm@linux-foundation.org \
    --cc=ben@simtec.co.uk \
    --cc=bonbons@linux-vserver.org \
    --cc=broonie@kernel.org \
    --cc=cengelma@gmx.at \
    --cc=chris@the-brannons.com \
    --cc=greg@kroah.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hartb@linux.vnet.ibm.com \
    --cc=jkosina@suse.cz \
    --cc=lindar_liu@usish.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robert.jarzmik@free.fr \
    --cc=samuel.thibault@ens-lyon.org \
    --cc=simon@mungewell.org \
    --cc=torvalds@linux-foundation.org \
    --cc=vince@simtec.co.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.