linux-kernel - Re: Please pull the (new) Trivial tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <9a8748490804211621s7e19394bn6911d8d093fcb8dc@mail.gmail.com>
Date:	Tue, 22 Apr 2008 01:21:32 +0200
From:	"Jesper Juhl" <jesper.juhl@...il.com>
To:	"Linus Torvalds" <torvalds@...ux-foundation.org>
Cc:	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
	"Adrian Bunk" <bunk@...sta.de>,
	"Jesper Juhl" <jesper.juhl@...il.com>
Subject: Re: Please pull the (new) Trivial tree

On 22/04/2008, Jesper Juhl <jesper.juhl@...il.com> wrote:
> Hi Linus,
>
>  Please pull git://git.kernel.org/pub/scm/linux/kernel/git/juhl/trivial.git
>  for-linus
>
>  This is the (new) trivial tree.
>
>  I took over Trivial maintainership from Adrian Bunk and this is my
>  very first pull request as maintainer, so please let me know if I've
>  done anything wrong.
>
>  I know you have better things to do than look through trivial patches
>  (that's my job now), but since this is the very first tree I've
>  created I would ask you to please take the time to look it over
>  carefully. I cloned your tip-of-tree and then applied all the patches
>  I had filtered out to a 'for-linus' branch. I plan to then merge those
>  patches back from you into my 'master' branch once you've pulled, then
>  ditch my 'for-linus' branch and create a new one with new patches once
>  the next merge window opens - if that's not the right way to go about
>  it, please let me know.
>
>  To the various other tree maintainers; if there are patches in this
>  tree that I should not have merged and then told Linus to pull, but
>  should instead have sent to you, please tell me so I can do a better
>  job next time. I want to develop a good working relationship with
>  other maintainers, but I'm new at this and don't know exactely what to
>  do, so I've tried my best and hope it's good enough - but if not, I
>  want to be told so I can learn and do better in the future.
>
>  I've tried to not add patches that were already merged elsewhere as
>  well as patches that didn't really qualify as trivial. I hope I
>  succeeded.
>
>  Any and all comments on the tree I created, the patches in it etc are
>  more than welcome.
>

I guess one thing I should remember to do is include the git-shortlog
of the changes I'm asking you to pull ;-)

Here it is :

Benoit Boissinot (1):
      ext*: spelling fix prefered -> preferred

Cyril Brulebois (1):
      Documentation: Remove last references to BitKeeper.

Jesper Juhl (1):
      Correct a few trivial tree details in Documentation/SubmittingPatches

Johannes Weiner (1):
      Remove unused MAX_NODES_SHIFT

Nick Andrew (1):
      RAID: remove trailing space from printk line

Pavel Machek (2):
      trivial: small cleanups
      firmware_sample_driver.c: fix coding style

Robert P. J. Day (5):
      MAINTAINERS: Clarify access to OCFS2 development mailing list.
      KEYS:  Fix the comment to match the file name in rxrpc-type.h.
      DOCUMENTATION:  Use newer DEFINE_SPINLOCK macro in docs.
      Generate a slightly more informative error msg for bad HZ
      DOC:  A couple corrections and clarifications in USB doc.

Rusty Russell (1):
      Remove documentation of non-existent sk_alloc arg

Sebastian Siewior (1):
      DMA engine: typo fixes

Tobias Klauser (8):
      acpi: Storage class should be before const qualifier
      ALSA: Storage class should be before const qualifier
      arm: Storage class should be before const qualifier
      DVB: Storage class should be before const qualifier
      intel_menlow: Storage class should be before const qualifier
      sonypi: Storage class should be before const qualifier
      V4L: Storage class should be before const qualifier
      V4L: Storage class should be before const qualifier (sn9c102)

Uwe Kleine-König (1):
      fix typo "is" -> "if" in Makefile

Ville Syrjala (1):
      MAINTAINERS: Add ati_remote2 driver


-- 
Jesper Juhl <jesper.juhl@...il.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/