linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Mark Einon <mark.einon@gmail.com>
Cc: gregkh@suse.de, devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/12 RESEND] Mainly checkpatch fixes
Date: Sun, 23 Oct 2011 11:36:51 +0200	[thread overview]
Message-ID: <20111023093651.GA22285@kroah.com> (raw)
In-Reply-To: <1319361774-3148-1-git-send-email-mark.einon@gmail.com>

On Sun, Oct 23, 2011 at 10:22:42AM +0100, Mark Einon wrote:
> Resending patches. Reduces the number of checkpatch warnings, removing
> forward declarations and whitespace changes.
> 
> Last patch removes some redundant code.

Thanks, now applied, so we should be all synced up now, right?

greg k-h

  parent reply	other threads:[~2011-10-23  9:37 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-23  9:22 [PATCH 00/12 RESEND] Mainly checkpatch fixes Mark Einon
2011-10-23  9:22 ` [PATCH 01/12] staging: et131x: Remove unused rx_ring.recv_buffer_pool Mark Einon
2011-10-23  9:22 ` [PATCH 02/12] staging: et131x: Remove redundant et131x_reset_recv() call Mark Einon
2011-10-23  9:22 ` [PATCH 03/12] staging: et131x: Remove call to find pci pm capability Mark Einon
2011-10-23  9:22 ` [PATCH 04/12] staging: et131x: Remove unused rx_ring.recv_packet_pool Mark Einon
2011-10-23  9:22 ` [PATCH 05/12] staging: et131x: Remove some forward declarations Mark Einon
2011-10-23  9:22 ` [PATCH 06/12] staging: et131x: Remove forward declaration of et131x_adapter_setup Mark Einon
2011-10-23  9:22 ` [PATCH 07/12] staging: et131x: Remove more forward declarations Mark Einon
2011-10-23  9:22 ` [PATCH 08/12] staging: et131x: Remove yet " Mark Einon
2011-10-23  9:22 ` [PATCH 09/12] staging: et131x: Remove even " Mark Einon
2011-10-23  9:22 ` [PATCH 10/12] staging: et131x: Remove last of the " Mark Einon
2011-10-23  9:22 ` [PATCH 11/12] staging: et131x: Mainly whitespace changes to appease checkpatch Mark Einon
2011-10-23  9:22 ` [PATCH 12/12] staging: et131x: Remove redundant check and return statement Mark Einon
2011-10-23  9:36 ` Greg KH [this message]
2011-10-23  9:42   ` [PATCH 00/12 RESEND] Mainly checkpatch fixes Mark Einon
2011-10-23 17:11     ` [PATCH staging 1/6] et131x: add static qualifiers Francois Romieu
2011-10-24 20:34       ` Mark Einon
2011-10-23 17:11     ` [PATCH staging 2/6] et131x: uintxy_t removal Francois Romieu
2011-10-24 20:33       ` Mark Einon
2011-10-25 15:58         ` Francois Romieu
2011-10-23 17:11     ` [PATCH staging 3/6] et131x: fix error paths in et131x_pci_setup Francois Romieu
2011-10-24 20:21       ` Mark Einon
2011-10-25 15:59         ` Francois Romieu
2011-10-25 17:53       ` Mark Einon
2011-10-23 17:11     ` [PATCH staging 4/6] et131x: remove extraneous pci_save_state Francois Romieu
2011-10-24 20:17       ` Mark Einon
2011-10-23 17:12     ` [PATCH staging 5/6] et131x: kiss netdev.{base_addr, irq} goodbye Francois Romieu
2011-10-24 20:16       ` Mark Einon
2011-10-23 17:12     ` [PATCH staging 6/6] et131x: uncloak PCIe capabilities Francois Romieu
2011-10-24 19:56       ` Mark Einon
2011-10-25 15:59         ` Francois Romieu
2011-10-25 17:42           ` Mark Einon
2011-10-25 17:54       ` Mark Einon

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=20111023093651.GA22285@kroah.com \
    --to=greg@kroah.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.einon@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).