public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Pavel Herrmann <morpheus.ibis@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4 1/2] Loop block device for sandbox
Date: Fri, 07 Sep 2012 11:38:42 +0200	[thread overview]
Message-ID: <3758685.YXC1Fgde2a@bloomfield> (raw)
In-Reply-To: <201209071126.48768.marex@denx.de>

On Friday 07 of September 2012 11:26:48 Marek Vasut wrote:
> Dear Pavel Herrmann,
> 
> > On Friday 07 of September 2012 01:29:55 Marek Vasut wrote:
> > > Dear Pavel Herrmann,
> > > 
> > > > This driver uses files as block devices, can be used for testing disk
> > > > operations on sandbox.
> > > > A new command "sata_loop" is introduced to load files in runtime.
> > > 
> > > WARNING: externs should be avoided in .c files
> > > #141: FILE: drivers/block/sata_loopback.c:39:
> > > +extern block_dev_desc_t sata_dev_desc[];
> > > 
> > > total: 0 errors, 1 warnings, 231 lines checked
> > > 
> > > NOTE: Ignored message types: COMPLEX_MACRO CONSIDER_KSTRTO MINMAX
> > > MULTISTATEMENT_MACRO_USE_DO_WHILE
> > 
> > Yes, i know about that, and chose to ignore it.
> 
> Sorry, this is not how it works.
> 
> > i will not create a header file for a single line that checkpatch doesnt
> > like (with just a warning), especially when other drivers have such a line
> > in them as well.
> 
> So, implement proper accessor for this list? Or export the structure through
> some sata-related header? How does other do it?

other drivers have the same line that i do, therefore ignore the checkpatch 
warning, same as i do

see sata_dwc.c, ata_piix.c, fsl_sata.c, sata_sil3114.c

Pavel Herrmann

  reply	other threads:[~2012-09-07  9:38 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-29 15:46 [U-Boot] [PATCH] Loop block device for sandbox Pavel Herrmann
2012-08-29 15:48 ` Pavel Herrmann
2012-08-29 22:18 ` Marek Vasut
2012-08-30 17:14   ` Pavel Herrmann
2012-08-30 18:45     ` Marek Vasut
2012-08-30 19:07       ` Pavel Herrmann
2012-08-30 21:53         ` Marek Vasut
2012-08-31  9:09           ` Pavel Herrmann
2012-08-31 12:57             ` Marek Vasut
2012-08-31 14:25               ` Pavel Herrmann
2012-08-31 16:02                 ` Marek Vasut
2012-08-31 17:56                   ` Pavel Herrmann
2012-08-31 19:02                     ` Marek Vasut
2012-09-01 13:19 ` [U-Boot] [PATCH v2 1/2] " Pavel Herrmann
2012-09-01 13:19   ` [U-Boot] [PATCH 2/2] Use loop block device in sandbox board Pavel Herrmann
2012-09-01 14:20     ` Marek Vasut
2012-09-03 17:24       ` Pavel Herrmann
2012-09-03 17:23     ` [U-Boot] [PATCH v2 " Pavel Herrmann
2012-09-03 16:49   ` [U-Boot] [PATCH v2 1/2] Loop block device for sandbox Marek Vasut
2012-09-03 17:31     ` Pavel Herrmann
2012-09-03 20:20       ` Marek Vasut
2012-09-05 11:16   ` [U-Boot] [PATCH v3 " Pavel Herrmann
2012-09-05 11:16     ` [U-Boot] [PATCH v3 2/2] Use loop block device in sandbox board Pavel Herrmann
2012-09-05 11:33     ` [U-Boot] [PATCH v3 1/2] Loop block device for sandbox Marek Vasut
2012-09-05 12:38       ` Pavel Herrmann
2012-09-05 12:48         ` Marek Vasut
2012-09-05 20:25           ` Pavel Herrmann
2012-09-06  1:08             ` Marek Vasut
2012-09-06  8:45               ` Pavel Herrmann
2012-09-06  8:48                 ` Marek Vasut
2012-09-05 12:42       ` Pavel Herrmann
2012-09-05 12:52         ` Marek Vasut
2012-09-06 12:31     ` [U-Boot] [PATCH v4 " Pavel Herrmann
2012-09-06 23:29       ` Marek Vasut
2012-09-07  9:19         ` Pavel Herrmann
2012-09-07  9:26           ` Marek Vasut
2012-09-07  9:38             ` Pavel Herrmann [this message]
2012-09-07  9:42               ` Marek Vasut
2012-09-13 22:31           ` Tom Rini
2012-09-16 11:49             ` Pavel Herrmann
2012-09-16 11:58       ` [U-Boot] [PATCH v5 " Pavel Herrmann
2012-09-28  9:21         ` [U-Boot] [PATCH v6 " Pavel Herrmann
2012-09-28 18:22           ` Marek Vasut

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=3758685.YXC1Fgde2a@bloomfield \
    --to=morpheus.ibis@gmail.com \
    --cc=u-boot@lists.denx.de \
    /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